None of the mistakes below is exotic. Every one is a discipline that seems optional on a busy day and is quietly expensive across a year. What they share is a root cause: a break in the chain that should link a released definition, a work order, every material movement and every unit of output. Fix the chain and the mistakes close together.
It is worth being honest about why these gaps persist. Each one saves a few seconds or a small argument in the moment — nobody skips reservation to cause a shortage, or leaves WIP unbooked to lose their rejection data. The gaps open because the disciplined path costs a little now and the undisciplined one costs a lot later, on someone else's shift. That asymmetry is exactly why a connected system pays back: it makes the disciplined path the path of least resistance, so the right thing happens by default rather than by heroics.
1 — Issuing material without reserving it
Reservation earmarks stock against a work order so nothing else can claim it; issue is the real deduction when material leaves stores for the line. Skip the reserve step and issue straight from the shelf, and two jobs can each assume they hold the same material. Planning can no longer see what is genuinely available, and shortages announce themselves only when a job halts for want of parts.
The fix: a genuine reserve-then-issue discipline, where stock is earmarked first — often by MRP upstream — and only deducted at issue. This is also the first of the two true stock-commit points that keep on-hand figures honest.
2 — Running unreleased BOMs in production
A Bill of Materials that has not been formally released is a draft, and a draft on the floor is a liability. Work orders exploded from an unapproved or silently edited BOM requisition the wrong material, are costed against a definition nobody controls, and cannot be traced when something goes wrong.
The fix: release discipline. Production runs only against a released BOM and process list, and any change to a released definition goes through an engineering change so the revision becomes active while superseded revisions stay traceable — no silent edits under a job already in progress.
3 — Never booking WIP
This is the mistake that makes all the others invisible. If operators do not book good and reject WIP as a job moves down its route, finished goods eventually appear in stock with no record of how they were made. The plant loses its live job position, its consumption-versus-BOM variance and its rejection data in a single omission.
The fix: book good, reject and scrap WIP at each operation. The bookings track quantity through the route without touching finished-goods stock until transfer, so the plant sees progress live and finished goods never seem to materialise from nowhere.
4 — Tracking rejection as one number
A single end-of-line reject total tells you that you have a quality problem and nothing about where it lives. You cannot Pareto it, cannot tie it to a work center, cannot separate a component cause from an assembly cause. So the number persists year after year while effort scatters.
The fix: capture reject where it happens — good and reject WIP per operation, and line rejection at part and child-part level with each defect mapped to its work center. That is the whole subject of the reduce line rejection and rework guide, and it is the difference between a complaint and a plan.
| Mistake | What it costs | The discipline that fixes it |
|---|---|---|
| Issue without reserve | Double-committed stock, surprise shortages | Reserve-then-issue |
| Unreleased BOMs | Wrong material, uncontrolled costing | Release + engineering change |
| WIP never booked | No live status, FG from nowhere | Book good/reject per operation |
| Rejection as one number | No cause, no reduction | Capture per operation & work center |
| Stale standard times | Wrong schedule, cost and OEE | Maintain route standards |
| Rework off the books | Unmeasured salvage, hidden loss | Routed, booked rework |
| Production on islands | Re-keying, reconciliation gaps | One shared engine |
5 — Letting standard times go stale
Standard operation times are load-bearing: they drive scheduling, process costing and the performance factor of OEE. Left unmaintained, every number resting on them quietly becomes wrong — schedules assume impossible speeds, quotations understate process cost, and performance metrics turn to fiction.
The fix: maintain standard times on the route sheet as ordinary housekeeping. It is low effort and it keeps three separate systems — planning, costing and OEE — honest at once.
Recognise a few of these on your own floor?
See the connected chain that closes all seven — reserve-then-issue, released BOMs, WIP per operation, rejection by work center — on your own parts, in 30 minutes.
6 — Reworking off the books
Rework done informally — parts quietly fixed and slipped back into the flow — feels efficient and hides a real loss. Nobody knows how much material is being salvaged, how much salvage itself fails, or whether the rework is costing more than the scrap it avoids.
The fix: route and book rework like primary production. A rework process sheet defines the salvage operations, rework status records its own good and reject, and salvaged parts transfer to finished goods or back to the main flow — so rework yield is measured, not assumed. The full method, from capturing rejection per work center to deciding rework versus scrap, is set out in the reduce line rejection and rework guide.
7 — Running production on islands
The final mistake is architectural. When planning, production, inventory and quality each live in their own system, every handoff is a file export and a re-key, and the numbers never quite reconcile. Material issued in production does not match stock in inventory; rejections in quality do not tie to work orders in production.
The fix: run production on the same engine as the modules on either side of it, so a work order, a material issue, a WIP booking and a finished-goods transfer are linked documents rather than exported rows — the architecture argument the pillar guide, what is production management software, makes in full.
How the fixes come together
Fast Production Software closes all seven gaps not with seven features but with one connected chain, because each mistake is a broken link in the same line from release to finished goods.
Frequently asked questions
What is the most common production management mistake?
The most common and most damaging mistake is letting stock figures drift by not committing stock at defined points. When material is issued without ever being reserved, or finished goods appear without WIP ever being booked, on-hand stock stops matching reality. Almost every downstream problem — wrong planning, phantom inventory, unreconcilable costing — traces back to stock that was not committed cleanly at issue and at finished-goods transfer.
Why is issuing material without reservation a problem?
Reservation earmarks stock against a work order so it cannot be double-committed; issue is the real deduction. Skipping reservation and issuing straight from stores means two work orders can each assume they have the same material, planning cannot see what is truly available, and shortages surface only when a job stops for want of parts. The two-step reserve-then-issue discipline exists precisely to prevent that double-commitment and to keep available stock honest.
What goes wrong when WIP is never booked?
If operators do not book good and reject WIP as a job moves down its route, finished goods eventually appear in stock with no record of how they were made, no operation-level yield, and no rejection data. The plant loses its live job position, its consumption-versus-BOM variance and its rejection MIS in one stroke. Worse, finished goods that seem to materialise from nowhere make stock and costing impossible to reconcile.
How does an unreleased BOM cause production errors?
A BOM that has not been formally released — or worse, one edited silently while the floor is already building against it — means work orders can explode the wrong quantities, requisition the wrong material and be costed against a definition nobody controls. Release discipline, with engineering change for revisions, ensures production only ever runs against an approved definition and that superseded revisions stay traceable rather than overwritten.
Why do stale standard times hurt a plant?
Standard operation times drive scheduling, process costing and the performance factor of OEE. If they are never maintained, every number built on them is quietly wrong: schedules slip because the plan assumed impossible speeds, quotations lose money because process cost is understated, and performance metrics become fiction. Maintaining standard times on the route sheet is low-effort housekeeping that keeps costing, planning and OEE trustworthy at once.