In small job shops, work rarely moves in one clean batch from release to shipment. Ten parts finish at the mill while forty are still in queue. A weld cell starts on half the lot because fixtures are tied up. Five pieces pass inspection, two get scrapped, and the rest wait on rework or the next shift. If that partial movement is not recorded correctly, the schedule starts lying, inventory drifts, and customer promise dates become guesswork.
That is why manufacturing partial completion tracking matters. The goal is simple: at every operation, record what was completed, what was scrapped, what moved forward, and what remains open. When you do that consistently, your dispatch list reflects reality, downstream work centers stop waiting on phantom quantities, and no one has to hunt through clipboards to figure out where the missing WIP went.
Why partial completion tracking breaks down in small shops
Most small manufacturers do not struggle because the concept is complicated. They struggle because the shop floor process is inconsistent. One operator reports completed quantity at the end of the shift. Another reports only when the full traveler is done. A supervisor manually adjusts the work order later. Someone in the office receives finished parts into inventory, but nobody records the scrap that happened two operations earlier.
The result is a common set of problems:
- Open quantities stay inflated. The system still shows 50 at an operation even though 20 already moved.
- Downstream work centers are starved or overloaded. Scheduling assumes material is available when it is not, or ignores partials that are ready now.
- Inventory posts too early or too late. Good parts may be counted before final completion, or not counted when they are available to ship.
- Scrap disappears into variance. Losses are found later during closeout instead of at the operation where they occurred.
- Shipment promises drift. Sales hears that a job is “in production,” but cannot tell whether that means 2 units are ready or 200.
If that sounds familiar, it helps to treat partial completions as a standard transaction, not an exception. Shops that already deal with dispatch confusion often see the same root cause covered in dispatch list accuracy problems and queue time tracking issues.
The core rule: every operation needs three live numbers
For each work order and operation, you should always be able to answer three questions:
- How many good units were completed at this operation?
- How many units were lost here? This includes scrap, and where relevant, rework holds that are not yet good.
- How many units are still open at this operation?
Those three numbers sound basic, but they create the control point that keeps WIP from disappearing.
What counts as “good completed”
Good completed means the quantity that successfully finished the current step and is available to move to the next status. Depending on your process, that might mean moved to the next operation, placed in an inspection hold location, or staged for shipment if it was the final operation.
What matters is consistency. If a shop says an operation is complete only after inspection, then operators should not report machine completion as good output unless inspection is built into that same operation.
What counts as scrap
Scrap should be recorded where it happened, with a reason code if possible. If 3 parts were damaged during drilling, they should not disappear later at final closeout as a generic shortfall. Immediate reporting gives you usable process data and keeps open balances accurate. If scrap cost is a blind spot, pair this process with a tool like the scrap cost calculator.
What counts as open balance
Open balance is not a rough estimate. It is a live calculation:
Open balance at operation = quantity released to operation - good completed - scrap - authorized transfers out for outside processing or approved alternate routing
If you also track rework separately, keep it visible rather than burying it inside open quantity. An open balance of 25 means 25 are still expected to be worked at that operation. It should not hide 10 pieces sitting in MRB and 15 waiting in queue.
How to structure move tickets for split quantities
A move ticket should not just say that the job moved. It should say how much moved and in what condition. For batch movement, each transaction needs enough detail to preserve the story of the lot.
Minimum fields for a usable move transaction
- Work order number
- Part number and revision
- Operation number or work center
- Date and time
- Quantity completed good
- Quantity scrapped
- Quantity moved to next operation or status
- Quantity remaining open
- Operator or employee ID
- Scrap reason code when applicable
That may look like more data than a paper traveler usually captures, but in practice it is the minimum needed to avoid ambiguity later.
Example of a split batch move
Suppose a work order is released for 50 brackets.
| Operation | Starting Qty | Good Completed | Scrap | Moved Forward | Open Balance |
|---|---|---|---|---|---|
| Cutting | 50 | 20 | 1 | 20 | 29 |
| Cutting | 29 | 15 | 0 | 15 | 14 |
| Cutting | 14 | 14 | 2 | 12 | 0 |
After three partial transactions, cutting is complete. A downstream operation should see 47 available to process, not 50, and not some unclear note that the job is “mostly done.”
This is where many shops fail with handwritten move tickets. They may note the 20 that moved first, but not update the operation balance, so the schedule still treats all 50 as available or all 50 as unfinished. A digital production tracking workflow prevents that mismatch and is one reason many small shops move toward a manufacturing execution system.
How partial completion data should flow through the shop
To keep planning and shipment promises accurate, each partial completion needs to update three areas immediately or at least within the same shift.
1. Dispatch and scheduling
If 12 pieces are ready at the next operation, the next work center should be able to pull or be scheduled against those 12 now. This is especially important in high-mix, low-volume environments where a small quantity can unblock a rush order or combine with another setup. For more on that, see the high-mix low-volume scheduling guide.
2. WIP visibility by location and status
Partial completions should change not only quantity, but also status. For example:
- Queue at Op 20
- Running at Op 20
- Completed Op 20, waiting for Op 30
- Inspection hold
- Scrapped at Op 20
Without status movement, quantities float in the system with no physical meaning. That is how jobs become “lost” even though everyone insists they were updated.
3. Inventory and shipment readiness
Do not wait for full work order closeout to tell customer service what can ship. If your final operation reports partial good completions, the business should know what quantity is actually available. That supports better partial shipment decisions and more honest customer communication. It also reduces end-of-month cleanup, a related issue covered in work order closeout delays.
A simple transaction model small shops can implement fast
You do not need a massive ERP project to improve this. Even a modest digital process can work if the transaction logic is disciplined.
Use one completion event per operation touch
Every time an operator hands off quantity from an operation, record a transaction. Do not wait until the entire order is complete. If a machine finishes 8 parts at 10:00 a.m., those 8 should become visible then.
Separate good, scrap, and rework
Avoid combined fields like “processed quantity” that lump everything together. Good, scrap, and rework each drive different actions:
- Good affects next operation availability and eventual shipment.
- Scrap affects yield, cost, and replacement planning.
- Rework affects capacity and queue but is not yet shippable output.
Require balance checks
The system or form should force a simple math check so that operators cannot move more than remains open. This catches common errors immediately, such as entering 25 good against an operation with only 18 left open.
Use short, practical reason codes
For scrap and holds, keep the code list short enough that operators will actually use it. Examples might include setup damage, dimensional fail, wrong material, weld defect, handling damage, and machine issue. If the list is too long, people choose “other” every time.
Common mistakes that cause WIP loss
Posting only when the traveler is complete
This is the biggest cause of drift. The physical job moves in pieces, but the data waits for paperwork. By the time someone enters it, the next work center, inventory, and customer service have all been working from stale assumptions.
Recording moves without scrap
If 10 parts moved and 2 were scrapped, the transaction cannot just say 10 completed unless the operation balance is also reduced for the 2 losses. Otherwise those 2 pieces remain as phantom open WIP.
Treating partials as informal side notes
Comments like “sent some to paint” or “12 pcs to inspection” are not enough. Partial quantities must update the official order record, not just the traveler margin or a whiteboard.
Ignoring queue and hold locations
When quantities leave one machine but have not started the next step, they still need a visible location. This is particularly important if you want real-time shop floor data without heavy automation; a practical path is outlined in this guide to real-time shop-floor data without IoT.
How to roll this out on your floor
Start with one product family or one bottleneck area
Choose an area where jobs frequently split, such as machining to inspection, fabrication to weld, or paint to assembly. Do not launch everywhere at once. Prove the transaction method in one flow first.
Define the handoff rule
Write one sentence operators can follow: “Any quantity leaving your operation must be recorded as good, scrap, or hold before it moves.” That rule eliminates most ambiguity.
Train supervisors to audit open balances daily
At the end of each shift or day, supervisors should review a short exception list:
- Operations with open balance but no activity for several days
- Negative balances or over-reported completions
- Jobs with downstream activity but no upstream move posted
- Scrap posted without reason code
This is less about policing operators and more about catching process gaps early.
Connect quality decisions to quantity status
If first article approval, in-process inspection, or final inspection can block movement, the quantity should reflect that state explicitly. Good tracking gets stronger when quality and production statuses align, which is why many shops also standardize digital inspection records using resources like a digital quality inspection checklist.
What good partial completion tracking improves downstream
When partial completions are recorded correctly, the benefits show up beyond the work center where the transaction happened.
- Scheduling becomes more credible. Planners can sequence work based on actual available quantity, not assumptions.
- Customer commitments improve. Sales can answer whether 15 can ship Friday even if the full order of 40 will finish next week.
- Scrap becomes actionable. You see losses by operation while the issue is still fresh.
- WIP aging becomes visible. Stuck quantities in hold or queue stand out faster.
- Month-end close gets easier. Fewer manual reconciliations are needed between paper, production, and inventory.
These are the same operational fundamentals emphasized by trusted manufacturing improvement resources such as NIST Manufacturing: use timely process data to make production decisions based on what is actually happening on the floor.
What to look for in software support
If you are evaluating tools, the key question is not whether the system can close work orders. It is whether operators and supervisors can record partial progress quickly enough that the data stays current.
Look for software that can:
- Post partial quantities by operation in real time
- Track good, scrap, and rework separately
- Update open balance automatically
- Show WIP by operation and status
- Expose partial availability to scheduling and shipping
- Keep data entry simple enough for the floor to use consistently
If you are comparing options, the MES software for job shops guide and MES selection guide for small manufacturers can help you narrow the must-have features.
Partial completion tracking sounds like a small reporting detail, but in job shops it is one of the main controls that keeps WIP, schedule, and shipment commitments aligned. When every operation records good units, scrap, and remaining balance as work moves in batches, the shop stops relying on tribal knowledge to find material and answer customer questions.
If you want a simpler way to track split quantities and keep live WIP accurate, start a free FactoryOS trial and see how digital production tracking can make partial completions visible without adding paperwork.