Committed 93, Dispatched 45: How to Run a Monthly Production Commitment Review
2026-08-02
A commitment without a closure is optimism with a date on it. How to turn 'we'll make 93 batches' into a reason-coded, carry-or-drop, signed-off and rated monthly number.
At the start of the month a plant commits to a number. "We'll dispatch 93 batches in July." Everyone nods. The number goes into a plan, maybe a WhatsApp message, maybe a review deck. Then the month happens — a raw material lands late, a packing line is down for two days, a customer puts an order on hold — and by the 31st nobody actually goes back and asks: of the 93 we committed, how many left the gate, and why did the rest not?
That question — asked the same way, every month, with the misses coded by reason — is the single most useful management ritual a manufacturing plant can run. Most don't. The commitment quietly becomes fiction, the shortfall gets absorbed into "next month," and the same reasons cause the same slippage in perpetuity because no one is counting them. Here's how to build a monthly commitment review that actually closes the loop.
Why "we committed 93" becomes fiction by the 5th
A commitment without a closure is just optimism with a date on it. Three things go wrong:
- Nobody re-reads the number. The plan is made, then the plant runs on today's fires, not last month's promise. The 93 is never reconciled against reality.
- The shortfall has no owner and no reason. When 48 batches don't ship, "the month was tough" is not an analysis. If you can't say why each one slipped, you can't fix anything.
- The miss silently rolls forward. Undispatched batches drift into next month with no decision — are we still making this, or is it dead? Without an explicit carry-or-drop, your next commitment is already polluted with last month's ghosts.
The fix isn't a better plan. It's a closure — a short, disciplined end-of-month step that turns the commitment from a promise into a measured, reason-coded, signed-off number.
What a real monthly commitment actually looks like
A commitment you can close has a lifecycle, not just a target. Every committed batch moves through the same funnel, and at month-end each one lands in exactly one bucket:
COMMIT → DISPATCH → CLOSE
------------------ ----------------- --------------------------------
Plant commits N Batch either ships Each undispatched batch gets:
batches for the (dispatched) or • a REASON (why it slipped)
month, per unit doesn't (missed) • a DECISION: carry forward or drop
Then the month is signed off, locked,
and scored — one number per unit.
The discipline is in the last column. Dispatched is easy to count. The value is forcing every miss to carry a reason and every carry to be a conscious choice — before the month is allowed to close.
The four reasons a batch actually slips
You cannot improve what you don't categorise. When a committed batch doesn't ship, the plant head picks one reason. Keep the list short and honest — four buckets cover almost everything on a real shop floor:
REASON WHAT IT REALLY MEANS
---------------- --------------------------------------------------------
RM Delay Raw material didn't arrive / wasn't released in time
PM Delay Packing material shortfall held up the finish
Breakdown Equipment down — a line or utility failed
Customer Hold The customer paused / rescheduled the order
Four codes, and suddenly a shapeless "we missed 48" becomes "48 RM Delay" — which points a finger at procurement and QC release, not at the plant floor. Next month it might be "30 Breakdown, 12 PM Delay" — a completely different conversation, with a completely different owner. The reason mix is the insight. The count is just the score.
One deliberate design choice: don't excuse any reason from the score. It's tempting to exclude "Customer Hold" because it feels external — not the plant's fault. Resist it. The moment one reason is exempt, every miss migrates to that reason. The rating measures what actually shipped against what was promised, full stop. Root cause lives in the reason code; the score stays honest.
Carry forward, or drop — the honesty test
Every undispatched batch faces one binary question at close: is it moving to next month, or is it dead?
- Carry forward — still a live commitment; it rolls into next month's number and stays on the hook.
- Drop — it's off the commitment. Cancelled, superseded, or no longer wanted. Say so explicitly and it stops haunting the plan.
This is the step almost everyone skips, and it's the one that keeps the whole system honest. A commitment that only ever carries and never drops inflates forever. Forcing a per-batch decision — and showing the CEO exactly which batches were dropped at approval — means next month's "we commit X" is a clean number, not last month's wishful thinking wearing a new date. It's the same principle behind stopping overdue purchase orders before they hurt production: an item with no decision on it is a liability, not a plan.
The month-end close: submit, approve, score
The close itself is a two-signature ritual, and it should take minutes, not a meeting:
1. The plant head submits. All units visible, misses reason-coded, each batch marked carry or drop, with a running total: "I confirm 45 dispatched, 48 carried, 0 dropped."
2. The CEO (or ops head) approves. They see the dispatched count, the reason mix, and — critically — which batches were dropped and why. Approve, or reject with a reason that goes straight back to the plant head.
3. The month locks, and each unit gets one rated line. Not a paragraph — one scored sentence, logged against that plant head's record:
★☆☆☆☆ (1/5) Unit — Jul 2026 commitment: dispatched 45 of 93 (48%).
Not dispatched 48: 48 RM Delay. Carried forward 48.
That line is the whole month, closed. It's unarguable, it's comparable across units, and it accumulates into a trend nobody can spin.
How the score works — and why it should be blunt
Rate the commitment on the one thing that matters: dispatched ÷ committed. A fixed band keeps it objective and impossible to negotiate:
DISPATCH % RATING
------------- ----------
≥ 95% ★★★★★
≥ 85% ★★★★☆
≥ 70% ★★★☆☆
≥ 50% ★★☆☆☆
below 50% ★☆☆☆☆
45 of 93 is 48% — just under the line — so it scores the bottom band. That feels harsh, and it's meant to: a plant that shipped fewer than half the batches it promised had a bad month, and the score should say so plainly. The reason code (48 RM Delay) tells you it wasn't the floor's fault — it was inbound material. But the number stays honest. Blend cause into the score and you lose both: a soft number and a buried cause. Keep them separate — blunt score, precise reason.
What changes when you close every month
Run this for three months and the plant changes shape:
- Accountability stops being vague. "Tough month" is replaced by "48% dispatched, all RM Delay" — a specific, ownable, fixable fact.
- The reason mix tells you where to invest. Months of RM Delay means the problem is procurement and QC release, not capacity. Months of Breakdown means maintenance. You stop buying the wrong solution.
- The commitment gets more honest. When you know you'll be scored on dispatched-vs-committed and every drop is visible to the CEO, you commit to a number you can actually hit — which is the entire point.
- The trend becomes the review. One rated line per unit per month stacks into a picture the numbers a CEO actually needs — is adherence climbing, and is the reason mix shifting toward things you're actually fixing?
None of this needs a new ERP or a six-month project. It needs the commitment lifecycle to be tracked as data instead of remembered as intent — the same jump as going from a process description to a live workflow, applied to the one number your plant lives and dies by. Plants that still run this in scattered sheets and WhatsApp groups aren't lacking effort — they're lacking a closure. Give the commitment a lifecycle and a month-end lock, and "we'll try to make 93" finally becomes a number someone owns.
Flobri Insights turns your monthly production commitment into a tracked lifecycle: commit per unit, watch dispatched vs missed in real time, code every miss by reason, carry or drop each batch with a decision the CEO signs off — and close the month with one rated KPI line per plant head, logged and trended automatically. No ERP project, no spreadsheets. See how it works.