---
title: "Process an engineering change order"
slug: "bc-how-to-process-an-engineering-change-order"
description: "Learn to process Engineering Change Orders (ECO) effectively, manage notifications, and handle rejections in your engineering workflow."
tags: ["Task"]
updated: 2026-06-25T09:59:00Z
published: 2026-06-25T09:59:00Z
canonical: "docs.staedean.com/bc-how-to-process-an-engineering-change-order"
---

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

# Process an engineering change order

Once the Engineering Change Order is created from the EC Staging line, you can process it. Coordinate the moment of processing carefully with the stakeholders.

## Steps

1. Choose the ![](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/search_small(2).png) icon (Alt+Q).
2. Type **Engineering Change Orders** to open the list.
3. Select **Edit** to open the order. The ECO has the following tabs:

## Engineering Change Orders form

### General

> [!NOTE]
> Note
> 
> The header information is not editable.

### Filter Line Details

Filters the lines in the Eng. Change Order subform. The options are:

- **Show All**: shows all three line types.
- **Existing Values**: shows the values from the existing record.
- **Staging Values**: shows the values as imported through the staging table.
- **User Entry Values**: allows the user to make final changes before inserting or modifying the record.

> [!NOTE]
> Note
> 
> These lines are created based on the setup: **Allow Edit On Order Line** creates the **User Entry Values** lines. **Show Current Values** creates the **Existing Values** lines.

### Fact box and Actions

#### Item Inventory Details fact box

This fact box shows the documents currently depending on the item.

#### Where Used

The **Where Used** actions for items, production BOMs, and routings show in which list the item is used.

#### Carryout Action

This action implements the change as set in the ECO: updates the item, creates a substitution, updates the BOM or routing, or creates new versions for the BOM or routing. The request page for **Carryout Action** has one option: **Certify**. When checked, Anywhere Mobility Solutions BOMs or routings in the ECO are set to **Certified** when created.

#### Get ECR Lines and Applied ECRs

When the ECO is based on an ECR, the ECR number is shown in the header of the ECO. If not, or when several ECRs relate to the ECO, use the **Get ECR Lines** action to link these ECRs. The **Applied ECRs** action shows the linked ECRs.

#### ECO Rejection

Even a pre-approved ECO can contain errors or be rejected for other reasons. Use the **Reject ECO** action for this scenario. When using the **Reject** option, select a reason code on the **Staging Values** line.

The rejected ECO is removed and can be found in **Rejected ECOs**. From the **Archived Engineering Change Order** list, open the card. The card contains an **Undo Rejected ECO** action to restore the ECO.

The ECO is restored with the status **Open**. Use **Engineering Change Orders** in the role center to show a list of ECOs. Select the restored ECO and use the **Change Status** action to set the status to **Approved**. Once approved, use **Carryout Action** to process the ECO.

## Notifications

Engineering Change Management uses two types of notifications:

- Notification to ECR user, informs the user that the ECR has been completed.
- New Revision Code notification, informs users about a new revision code, provided the user has checked this option in **My Notifications**.

## Related

- [Engineering Change Management ](/bc-engineering-change-management.md)