Answer ‘why is it like this?’ in seconds

Every change, who made it, and why.
The answer is one click, not a week.

Change orders link the parts, BOMs, and designs they touch and ride a controlled status workflow. Underneath, a complete audit log records who changed what and when — across the whole platform — so the history is always there when a customer, an auditor, or your own team needs it.

Change & audit trail

CO-2026-118
  1. just now Released rev C · effective on next build
  2. 2m ago Approved by J. Kowalski (Engineering)
  3. 1h ago Stud spacing 24″ → 16″ o.c.
  4. 1h ago Linked 2 BOMs · 1 design

What actually changes

Not “more paperwork.” The opposite: the paper trail writes itself, and the answers are instant.

1 week → 1 click

When someone asks “why is it built this way?”, you trace the exact change, the reason, and the person — instead of starting an archaeology project.

100% attributed

Every edit to a part, BOM, design, document, or configuration carries a name and a timestamp. Even AI co-pilot actions are logged.

0 dead ends

Mistakes are recoverable. Reversible history and a rollback view mean a bad change is something you undo, not something you live with.

Change orders

A controlled path for every change

ECO and ECN change orders are first-class objects, not a comment in a spreadsheet. Each one links the parts, BOMs, and designs it touches and rides a controlled status workflow — wip → in_review → approved → released → obsolete — with revision tracking at every step. Nothing released changes by accident.

  • Change orders link every affected part, BOM, and design
  • Controlled status flow from draft to released to obsolete
  • Revision tracking captures what each change actually altered
  • Released items only move through a reviewed, approved order

Part lifecycle

server-enforced
Draft
Under review
Approved 2 approvals · CN check
Released
→ Transition blocked: change notice required before release

Entity-level audit log

A history that writes itself

Behind every screen, Manufacts records who changed what and when — across the whole platform. Parts, BOMs, designs, documents, configurations, everything. There’s no “turn on logging” step and no gaps: the trail is captured automatically, with full user attribution and timestamps, so you’re never reconstructing the past from memory.

  • Every entity audited — parts, BOMs, designs, docs, configurations
  • User attribution and timestamps on every recorded change
  • AI co-pilot actions are audited alongside human edits
  • Reversible history with a rollback view to recover from mistakes

The best paper trail is the one nobody had to remember to keep.

Defensible by default

Ship into regulated markets without the dread

When an auditor or a customer asks how a product came to be, you don’t scramble. The complete, attributed history is already there — change orders tied to an automatic audit trail — so a compliance review is a query, not a fire drill. The same record that protects you also makes ‘who changed this and when?’ a non-question.

  • A defensible paper trail for regulated and audited markets
  • Trace any released item back to the change that produced it
  • No more “who changed this, and when?” — it’s already recorded
Explore Defensible by default

Part lifecycle

server-enforced
Draft
Under review
Approved 2 approvals · CN check
Released
→ Transition blocked: change notice required before release

How it works

From a proposed change to a permanent record

  1. 1

    Raise a change order

    An ECO opens against a released item, gathering the parts, BOMs, and designs the change will touch into one controlled request.

  2. 2

    Review & approve

    The order moves through wip → in_review → approved with revision tracking, so the right people sign off before anything ships.

  3. 3

    Release & broadcast

    On release, an ECN notifies everyone affected, and the prior revision is preserved — superseded, never silently overwritten.

  4. 4

    Audit forever

    Every step is captured in the entity-level audit log, attributed and timestamped, ready to answer “why?” at any point later.

ECO / ECN Engineering Change Order / Notice

An ECO (Engineering Change Order) is the controlled request to change a released item — what’s changing, why, and what it touches. An ECN (Engineering Change Notice) is the notice that broadcasts the approved change to everyone affected. Manufacts makes both first-class and ties them to an automatic audit trail, so the request and the record are never out of sync.

See how workflow enforces it

Under the hood

Everything change & audit covers

ECO / ECN change orders

First-class change requests and notices, not buried comments or side spreadsheets.

Linked impact

Each order links the exact parts, BOMs, and designs it affects, so scope is never guesswork.

Controlled status workflow

wip → in_review → approved → released → obsolete, enforced for every change.

Revision tracking

Prior revisions are preserved and superseded, never silently overwritten.

Entity-level audit log

Who changed what and when, across parts, BOMs, designs, documents, and configurations.

User attribution & timestamps

Every recorded change carries a name and a time — including AI co-pilot actions.

Reversible history & rollback

A rollback view lets you recover from mistakes instead of living with them.

Audit-ready exports

A defensible trail you can hand to an auditor or customer without a week of prep.

Turn “why is it built this way?” into a one-click answer.

Bring the change history that keeps your team up at night — a contested revision, an audit you’re dreading. We’ll show you the change order, the attribution, and the rollback view, live, in 30 minutes.

No rip-and-replace — Manufacts runs alongside your ERP and CAD. Prefer email? hello@manufacts.ai