Skip to content
simple-plm

Propose an ECO

When you want a change reviewed before it lands on main, propose an ECO. ECOs are how simple-plm coordinates everything from a single resistor value tweak to a full board respin.

Steps

  1. From any part or BOM page, click “Propose change”. The dashboard opens a new ECO in draft state and creates a Git branch behind the scenes (typically eco/ECO-<id>).

  2. Fill in the ECO fields:

    • Title — one-line summary that will show up in the reviewer’s inbox.
    • Description — markdown-supported. Explain why, not just what — reviewers can see the diff themselves.
    • Reviewers — pick teammates with the reviewer (or higher) role.
    • Parts changed — auto-populates as you edit, but you can add explicitly.

  3. Make your edits. Any part or BOM edit you save while the ECO is open lands on its branch, not main. The branch switcher in the top-left shows which branch you’re on.

    ECO draft / review screen

  4. Save as draft as you go. Drafts don’t notify anyone.

  5. Submit for review. This moves the ECO from draft → review and emails the reviewers. From this point, further edits are still allowed on the branch but they re-set any prior approval votes — the spirit being “if you change the proposal, reviewers should re-confirm”.

Cancelling an ECO

A draft ECO can be deleted outright. An ECO in review can be withdrawn — the branch is preserved (you can reopen later) but the ECO record moves to withdrawn.

Next

Once the ECO is in review, jump to Review and release for the reviewer-side workflow.