Change management
Formal change control is how released data evolves without losing traceability.
Change types
| Type | Purpose |
|---|---|
| ECR | Engineering Change Request — proposes and scopes a change |
| ECO | Engineering Change Order — authorizes the work |
| ECN | Engineering Change Notice — communicates an implemented change |
A change can be promoted (e.g. an approved ECR spawns an ECO) — the parent closes and the successor carries the affected items forward.
States
draft → submitted → in_review → approved → implemented, with rejected and
cancelled as terminal exits. Any rejection in a workflow rejects the change
immediately.
Approval workflows
Reusable workflow templates (Admin → Change Workflows) define approval steps. Each step names an assignee directly or a required role (resolved to a user at submission). Two execution modes:
- Sequential — steps activate one at a time; the next step's assignee is notified when the previous step fully approves.
- Parallel — every assignment is active at once.
Assignees get an in-app notification the moment an approval lands on them; the change's initiator is notified when the change is finally approved or rejected.
Affected items & signatures
Changes record the items, documents and BOMs they touch (with add / modify / remove / obsolete actions), collect threaded comments, and capture digital signatures on approval decisions for your audit trail. Change volume per month is limited on the community plan — see plans.