> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firstresonance.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage run batches

> Group runs that share steps so a single sign-off, redline, or status change propagates to every batched run at once.

A run batch groups runs that share steps so a sign-off, redline, or state change on one step propagates to every sibling step across the batch. For what propagates and when to batch, see the [Overview](/build-hardware/runs-and-execution/overview). This page covers creating and managing batch membership.

## Prerequisites

* The runs you want to batch must follow procedures whose step structure matches enough to have shared ("sibling") steps. Two runs of the same procedure version are the canonical case.
* Permission to modify run batch membership.

## Create a batch from the runs table

You create a batch by selecting runs in the runs table:

1. In the runs table, select the runs you want to batch.
2. In the floating toolbar that appears, click **Batch**.

ION creates a new batch and adds the selected runs to it. From that point, changes to shared steps propagate across the batched runs.

## Open the batch manager

Once a run is in a batch, open the batch manager from inside the run: click the batch pill in the run header, then click **Manage batch**. The dialog header reads **Batch {id}** (or **Batch {id}: {title}** once a title is set). If the run is no longer in a batch, the dialog shows "This run is no longer in a batch." Inside the dialog you'll see:

* A title row below the header. Click it to set or edit the batch title.
* **Search runs in batch**: filter the runs list by run ID or run title.
* **Add a run to the batch** dropdown: multi-select picker for runs not yet in the batch.
* **Expand all** / **Collapse all**: toggle the run cards open or closed.
* **Unbatch all**: footer action to remove every run from the batch.

## Add runs to a batch

1. In the batch manager, click **Add a run to the batch**.
2. Search runs by title or ID in the dropdown. Runs already in this batch are excluded.
3. Multi-select the runs you want, then click **Add N to batch** in the dropdown footer. Use **Clear selection** to reset.

After ION updates the batch, those runs immediately participate in propagation for any future changes on shared steps.

## Set or rename the batch title

Click the title row below the dialog header to enter edit mode. Type the new title, then click **Submit**. Cancelling reverts to the previous title. The title shows up alongside the batch ID in the run header and run list.

## Remove a run from a batch

In the runs list, expand the run card and click **Remove** on the run you want out, or **Remove & go to run** to remove it and navigate to it. ION updates the batch and the run continues independently from that point forward. It keeps any sign-offs and redlines it accumulated while batched.

## Unbatch every run

Click **Unbatch all** in the dialog footer. ION asks you to confirm before clearing the batch. After confirming, every run leaves the batch and continues independently. The batch itself is dissolved.

## Batch propagation

When you change a step inside a run that belongs to a batch, ION looks at every other run in the batch and finds **sibling steps**: steps in those runs that match the same step in the batched procedure. The change propagates to every sibling found:

* **Sign-offs**: completing or signing a step propagates the same completion to every sibling step.
* **Redlines**: redline changes propagate to siblings. For how redlines are merged across runs, see [Redline a run](/build-hardware/runs-and-execution/redlines-and-deviations).
* **State changes**: skipping, failing, or reopening a step propagates to siblings.

If a step is unique to the current run, with no siblings, only the current run changes.

### Cascade an aBOM install across the batch

Part installs are not cascaded automatically. When you add a build requirement to a run that belongs to a batch, the **Part Installs (aBOM)** tool shows an informative bar reading "Added {part} to this run only." with an **Apply to N runs in batch** button. Cascading to the sibling runs is a deliberate click, so an edit to a single run stays the default. Click **Dismiss** to keep the change on the current run only.

## Related

* [Runs and execution](/build-hardware/runs-and-execution)
* [Redline a run](/build-hardware/runs-and-execution/redlines-and-deviations)
* [Procedures](/build-hardware/procedures)
* [Bills of materials](/build-hardware/bills-of-materials)