The information around a design change matters just as much as the component list itself.
A bill of materials is a decision in context.
A BOM describes what a machine requires. Its version also tells the next team which design was agreed, what changed and which work should follow. If production sees a list without a reliable release context, the handover is incomplete.
Separate a draft from a release.
Engineering needs room to work on a new revision while other teams continue with an approved one. Make the state explicit. A proposed change should not silently replace the version used for purchasing or production.
Compare what changed.
A version comparison helps a reviewer see added, removed or changed components. The important question is what those differences mean for the current work: material requirements, routings, existing orders and the people who need to respond.
Keep the version with the order.
The production dossier should point to the relevant released BOM and its decision history. When a later change is introduced, the responsible team needs a clear way to understand its scope and decide how to handle work already in progress.
Treat release as a handover.
A release is useful when the next team has the right information and ownership. Review the version, the linked work and the exceptions together. That makes the design decision understandable beyond engineering.
See how this fits into Evermill.
Explore the workflow ↗