The production management process, stage by stage

The production management process in six stages

The production management process is the disciplined path a plant follows to turn a released engineering definition into finished stock. Whatever the industry — machined automotive components, welded fabrications, multi-level assemblies — a well-run shop moves through the same six stages: (1) engineering release of the BOM, Bill of Resources and route sheet; (2) work order, raised or generated from the plan; (3) material reserve and issue; (4) process execution and WIP capture; (5) finished-goods transfer; and (6) line rejection and the rework loop. Each stage produces a linked document, so the whole run is traceable end to end.

The reason to treat this as a defined process — rather than a series of loosely connected registers — is that the stages are dependent. A work order cannot run until the BOM is released; material cannot be issued until a requisition explodes that BOM; WIP cannot be booked until material is on the line; finished goods cannot be transferred until the route is complete. Get one stage right and the next inherits clean data. Let one stage slip to a spreadsheet and the chain breaks. This guide walks each of the six stages in the order the floor experiences them.

Stage 1 — Engineering release

Everything downstream depends on a clean engineering definition, so the process begins in the design and process-planning office rather than on the floor. Three things are authored here. The Bill of Materials (BOM) says what the product is made of — child items, quantity-per, and scrap or yield allowance at each level. The Bill of Resources (BOR) says what it takes to make it — the machines, labour, tools and operations each level consumes. And the process or route sheet lays out the ordered sequence of operations, each tied to a work center and a standard time. Together, a released BOM plus its Bill of Resources plus its route sheet is a manufacturable part.

A serious system holds a BOM in more than one form. A master BOM is the standard, reusable definition authored once and used by every work order for that part. A structural, multi-level BOM is the indented explosion of a finished good through its sub-assemblies down to raw material (FG → SFG → RM), so each level can be made, costed and traced in its own right. And an order-specific BOM is carried against a particular customer order, so a make-to-order job can differ from the standard without corrupting the master. In the reference deployments these structures run at real scale — thousands of BOM position lines and resource lines behind a single manufacturing plant.

Nothing is usable by production until it is released. A definition moves from draft status through to a released status, and only then can a work order be opened against it. Because a released BOM is the trigger for everything downstream, later changes are controlled: an engineering change (ECN) revises a released BOM or process so the new definition becomes active while superseded revisions stay traceable — no silent edits to a definition the floor is already building against. See BOM & Bill of Resources.

Stage 2 — Work order

With a released definition in hand, the plant raises the instruction to make a quantity by a date: the work order. There are two kinds. An internal work order (WO) is typically made to stock. A sales work order (SWO) is raised against a specific customer order, so a make-to-order job stays tied to its demand from start to finish. Work orders can be entered by hand, but in a connected plant they are usually generated from the plan — planning suggests the quantity and the system opens the order automatically, carrying the demand straight through.

Once a work order exists, it is dressed for the floor. Job cards — the printed shop packets that tell an operator what to run — are generated and allocated, and work-order specifications capture the per-category attributes a particular order needs. As the job runs, the system tracks consumption against BOM, so actual material usage can be compared with the standard the BOM predicted, and a live job-card view shows where each order stands on the floor.

A work order also carries a status that tells everyone where it is in its life. It is born at draft, moves to released when it is ready to run, passes through in-progress as operations complete, and ends at completed and then closed once output is transferred. Jobs that stop early take a short-close path, and orders can be cancelled — with related documents echoed as cancelled entries so the record stays clean. See Work Orders & Job Cards.

Stage 3 — Material reserve & issue

Now material moves from stores onto the work order, and it does so as a deliberate two-step discipline — reserve, then issue — that mirrors the warehouse's own reserve-and-pick habit. Understanding the difference between the two is the single most important idea in the whole process.

First, the work order's released BOM is exploded into a material requisition (PRMR), listing exactly what and how much the order needs. Against that, stock is reserved. A reservation earmarks stock so it cannot be double-committed to another order — but the material is still physically in stores, and on-hand stock is not reduced. A reservation is a promise, not a movement, and it is often created upstream by MRP for production to draw against. Then the material is issued to the line. Issue is the real stock deduction: material leaves store stock and is charged to the work order. A wrong issue can be reversed, unused material returns through the same issue-and-return slip, and cancellations post as cancelled-reserve or cancelled-issue documents so nothing is left dangling.

This distinction is why a production system's stock can be trusted at all. Because issue is the one place raw material leaves the shelf, on-hand stock stays honest right up to the moment of consumption, and any discrepancy traces cleanly to an issue or a return. See Material Issue & WIP.

Stage 4 — Process execution & WIP

With material issued, the work order runs down its route — the ordered sequence of operations, each on a work center, each with a standard time and any process specifications. The route can be held as a master process sheet per item and generated order-specific, printed for the floor, and tracked as each operation is completed and its status recorded. At each operation the operator books the output into three buckets that are kept separate for a reason:

• Good WIP — the quantity that passed the operation and moves forward down the route.
• Reject / not-OK WIP — the quantity that failed at that operation, captured where it happened rather than lumped into a final total.
• Process scrap — material removed from the route entirely.

Production slips move work-in-progress from one operation to the next and, ultimately, toward finished-goods transfer. Crucially, these WIP bookings track quantity through the route without touching finished-goods stock — the plant watches a job progress operation by operation while its inventory figures stay still until material actually leaves or finished goods actually arrive. That is the stock-commit principle in action.

Two branches make the execution stage powerful. An in-process inspection branch lets an operation hand off to quality before the next step is allowed to run, and a defect-to-work-center mapping ties every reject to the station that produced it. Where the floor is barcoded, process status is booked by scan, so the operation, the quantity and the good/reject split are captured at source with no re-keying. The result is yield visibility down to the operation and the work center — the foundation of any real rejection-reduction effort. See Process & Route Sheets.

Stage 5 — Finished-goods transfer

When the route is complete, the good output leaves work-in-progress and becomes stock. This happens as two linked postings: a manufacture event that creates the finished goods, and a transfer-to-stock posting that puts them on-hand. This is the second true stock-commit point in the whole process — the first was material issue — and from here the finished goods are visible to inventory and dispatch and are ready for finished-goods inspection.

The transfer stage carries the nuance a real plant needs. Finished goods can be transferred by lot, so each batch keeps its own identity and a customer audit or field-failure investigation can trace a specific lot back to the exact material and operations that made it. Semi-finished goods (SFG) transfer the same way — a sub-assembly is manufactured, transferred to stock, and then feeds the next-level assembly as its own child item, which is how multi-level structural BOMs are actually built one level at a time. And over-production is handled honestly as an excess transfer rather than being quietly absorbed.

As the output is transferred, the work order is completed and then closed, closing the loop on the instruction that started in Stage 2. At this point a clean run is done: material was issued, operations were run and measured, and finished goods are on the shelf with their lineage intact. See FG, Rejection & Rework.

Stage 6 — Line rejection & the rework loop

Not every part passes, and how a plant handles the ones that fail is where margin is either recovered or quietly lost. Line rejection captures parts rejected on the production line — as distinct from incoming-material rejection — and it captures them at three useful levels: at the level of the manufactured part, at child-part level for a rejected component, and booked against the specific work order so the loss is attributed where it belongs. From there, rejected parts enter a controlled loop rather than being written off in a book nobody analyses.

Handled this way, the loop turns rejection from an accepted cost into a managed one. The rework decision — scrap or salvage — is a genuine choice rather than a default; the rework process sheet and rework status give the salvage its own measured route; and the salvaged parts either land in finished goods or rejoin the main flow through a controlled transfer back. Because every reject was captured against an operation, a work center and a work order, the plant ends up with a reject-and-scrap picture it can act on — attacking the biggest recurring cause first instead of paying for the same material twice. See FG, Rejection & Rework.

How the stages connect to planning, inventory & quality

The six-stage process does not run in isolation — it is the execution hinge in a longer chain, and it is at its best when it is natively connected to the modules on either side of it rather than exchanging files with them.

Upstream, planning feeds Stages 1 and 2. Fast Planning / MRP turns sales and component demand into a plan, suggests quantities, and can generate the work order directly — while MRP reservation creates the very stock earmarks that Stage 3 issues against. Plan → work order → reserve → issue becomes one continuous chain instead of four disconnected steps.

Alongside, inventory anchors Stages 3 and 5. Because material issue and finished-goods transfer post to the same stock ledger the warehouse uses, the two stock-commit points are immediately visible to Fast Inventory — raw-material depletion at issue and finished-goods receipt at transfer, with no double entry and no lag.

Downstream, quality drives Stages 4 and 6. The in-process inspection branch and finished-goods inspection flow into Fast Quality, and the line-rejection and rework decisions run through its non-conformance and rework handling. The result is a manufacturing core — planning, production, inventory and quality — that shares one customer, item and stock foundation. Explore the full integrations overview, and for the wider picture start from the pillar guide, what is production management software.

Frequently asked questions