## Configure run enforcement

Run enforcement settings control what you can and can’t do during run execution.

1. In ION, go to **Settings > Production > Runs**.
2. Turn on or off the settings you need:

| Setting | What it does |
| --- | --- |
| **Require part-procedure relationship** | Parts must be linked to procedures before they can be used in runs. |
| **Allow run steps to complete without required install** | Steps can be marked complete even if required parts haven’t been installed. |
| **Enforce peer signoff** | A different user must sign off on each step completion. |
| **Enforce run title template** | Run titles must follow the configured naming template. |
| **Enforce all aBOM parts installed for completion** | Runs can’t be completed if any aBOM parts remain uninstalled. |

When **Enforce all aBOM parts installed for completion** is on, you can also turn on **Allow completion with justification** to complete runs with uninstalled parts by providing a written justification. The **Number of redline approvers required** field on the same page sets how many approvals a redline needs. See [Set the redline approver count](https://docs.firstresonance.io/administration/production-settings/set-redline-approver-count).

## Set the run title template

The run title template names new runs automatically. Set it before turning on **Enforce run title template**, which stays disabled until a valid template is saved.

1. In ION, go to **Settings > Production > Runs**.
2. In **Run title template**, enter the pattern to apply to new run titles, for example `${id}-${partNumber}-${partRevision}`.
3. Include `${id}` (required), plus any of these tokens: `${partNumber}`, `${partRevision}`, `${partDescription}`, `${procedureTitle}`, `${procedureVersion}`, `${serialNumber}`, `${lotNumber}`, `${quantity}`, and `${dueDate}`. Text outside the tokens is kept as written. ION flags a template that omits `${id}` or uses an unknown token.