> ## 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 standard steps

> Create, review, and reuse standard steps so shared instructions stay in sync across every procedure and run that uses them.

<Note>
  Standard steps are called out with a blue **S** icon or the words **Standard Step**.
</Note>

## Create a standard step

Open the standard steps page by clicking **Standard Steps** in the **Production** section of the sidebar. Standard steps are listed in a table.

Click **Create Standard Step** to open the creation dialog, then enter a **Title**, an optional **Description**, and a **Type** (Content or Datagrid). Once created, edit the standard step as you would a regular step. You can optionally add child steps for longer, more complicated operations, but you cannot add a standard step as a child step.

Standard steps use the same review process as procedures. To release a step, click **Move to In Review** and add reviewers as required. When all reviewers have signed off, the step moves to **Released** and may be copied into procedures and runs.

## Use a standard step

You can use standard steps in any place a regular step can be used. When adding a step in a procedure or in a redline, open the **Add Existing Step** tab, search for the standard step by name, and click it to copy it in.

Standard Steps can be also used as child steps to standardize one part of a larger action.

## Execute a standard step in a run

<Note>
  **Initializing** is when the step takes on details of the latest released version the standard step and will not receive further updates.
</Note>

You can execute a standard step the same way you execute a regular step in a Run. Standard steps **initialize** when the Status moves to any of the following:

* **IN PROGRESS**
* **REDLINE**
* **CANCELED**
* **FAILED**
* **COMPLETED**\
  \
  At that time, the details of the standard step will be updated to reflect the latest released version. This is indicated by the version you will see in the step queue and near the step title.

Another indicator appears in the header of the run step. When you see the “linked” icon, it means the standard step will continue to receive updates if a new version is released.

If you see the “broken link” icon, the standard step is frozen because one of the statuses above was used at some point in its history, which prevented further updates.

**Initialization** also occurs when a standard step is redlined into a run. For example, if you add Version 2 of the standard step 'Torque Bolt' to a run, it will always remain as Version 2. Even if the redlined step is not started, 'Torque Bolt' will not inherit any new versions.

### Approvals

<Note>
  Contact your Customer Success Manager to enable role based reviews
</Note>

When you are done updating a new version of a standard step, you can submit it for review. Click **Move to In Review** on the standard step. From there, you can add the roles and users or teams who should review the procedure.

Approvers will see the pending review requests in their home dashboard. Clicking into the review request will take the reviewer to the standard step to leave a review. Once all reviewers have *approved* the standard step, it will be automatically set to "released".

#### Required approvers

To configure which reviewer roles are required on a standard step, see [Configure standard step reviewer roles](/administration/production-settings/configure-standard-step-reviewer-roles). Required approvers can also be configured through the API.

```graphql theme={null}
mutation createStepApprovalRole($input: CreateStepApprovalRoleInput!) {
  createStepApprovalRole(input: $input) {
    approvalRole {
      _created
      _etag
      _updated
      count
      createdById
      gateType
      roleId
      updatedById
    }
  }
}

{
  "input": {
    "roleId": 3,
    "count": 1,
    "gateType": "RELEASED"
  }
}

```

This configuration requires that 1 user with `roleId` of 3 approves the standard step for it to be released. These reviewers appear in the **Required approvers** section of the review dialog.