Dates You Can Keep: Finite-Capacity Scheduling Told from the Floor

March 5, 2026

At 2:17 p.m. on a Wednesday, the paint booth timer hit zero. Two jobs were booked for the same hour. Neither had the right topcoat ready. Both were “promised for Friday.”
Someone gave priority to the newer job — bigger customer, louder emails. The older job, just as important, got pushed to next week.

Within thirty minutes:
Sales asked for a new promise date.
Production tried to “find an hour.”
Maintenance got blamed for a booth that wasn’t even broken.
But the failure didn’t start on Wednesday. It started on Monday, when we built a plan that assumed time stretches and materials magically appear.
The week we stopped lying to ourselves, we didn’t add new software.
We added honesty.

A real schedule only says yes when:
The people are available.
The bottleneck (constraint) is open.
The materials are physically ready.
That’s the difference between a real date and a guess.

Monday: The Last Week of Guesswork

We started with one board everyone could see. It showed only the constraint — our paint booth — divided into real shift blocks.
Not “available hours.”
Staffed hours minus breaks, cleaning, and changeovers.

We wrote the real numbers:
Setup for Family A: 42 minutes
Setup for Family B: 58 minutes
Clean A → B: 28 minutes
Clean B → A: 35 minutes
Run rate: 11.3 hours for an average day (when the plan fits)
When we laid jobs into actual time blocks, three fake promises disappeared immediately.
Second truth: materials are either pickable, or they don’t exist.
We banned the phrase “on order.”
If a seal, pigment, or masking kit wasn’t in a bin and ready to pick, the job did not go on the board.
Purchasing didn’t love it.
Operations loved the quiet after 5 p.m.

Tuesday: The Rule of the Constraint

Before this, every department tried to optimize itself.
Machining padded queues “just in case.”
Assembly ran FIFO to be fair.
QA worked on whoever complained loudest.
The booth got whatever showed up.
We changed the rule:
Schedule the constraint first. Everything else works backward from it.
If the booth was full, the week was full.

The new sequence:
1.Batch by product family to reduce setups.
2.Place batches into real hours.
3.Backward-schedule upstream work.
4.Confirm materials are available-to-pick.
No arguing. The board showed the truth.

Wednesday: We Put a Price on Expedites

Rush jobs happen. Chaos doesn’t have to.
We created three rules.

1. Swap Rule

An expedite can only enter if it replaces a specific job.
The replaced job gets a new date immediately.
Sales owns that conversation.
No “we’ll catch up later.”

2. Capacity Bank

We keep 3–5 overtime hours for real emergencies.
If we use them, we log why.
Next week, we decide whether to refill the bank.

3. Red Means Stop

If materials are not pickable inside the risk window (for example, 48 hours before start), the job stays red and cannot run.
By Thursday, expedites weren’t fights. They were business decisions with clear trade-offs.

Join Our Pre-Release List

We are thrilled that you are interested in the FireFlight Data Systems. Very shortly, we’ll be opening our demo site up for FireFlight Data Systems Release 5. It’s an exciting time and the new release has so many features we can’t even list them here. Please put in your Name and Email Address and we will keep you up to date on the latest launch date. The FireFlight Design Team at Phoenix Consultants Group.

Thursday: Setup Time Matters

Changeovers are not free.
We used magnets to group jobs by family.
Sometimes that meant running a smaller job first to protect a bigger shipment.
Customers cared about stable dates more than perfect order.
We stopped chasing local efficiency.
If a feeder cell had to wait 40 minutes to avoid starving the booth later, that was a good trade.

Leadership tracked only two numbers:
Schedule credibility (% shipped on or before promise)
Constraint utilization (planned vs. actual hours, plus why variance happened)
When both improved, the floor felt calmer.

Friday: Short, Focused Huddle

Fifteen minutes. Same place. Same time.
Four questions:
1.What changed at the constraint?
2.Which jobs are yellow or red for materials?
3.What’s today’s setup sequence?
4.What new orders can we place, and where do they land?
If a topic took more than a minute, it moved offline.
Meetings got shorter.
The board got clearer.

When Failure Tested the System

Two months later, the booth exhaust failed mid-shift. We lost 92 minutes.
Old system: push everything downstream and beg the night shift.

New system:
Merged two Family A jobs to save setup time.
Moved one lower-priority Family B job to Tuesday.
Used 3 hours from the capacity bank.
We still shipped Friday.
The moved job was updated immediately while the customer was on the phone.
No drama.
Just facts.

The Simple Math That Helps

You don’t need advanced math. Just a few rules.

Little’s Law

WIP = Throughput × Lead Time
If WIP rises, lead time rises.
Control WIP at the constraint.

Changeover Economics

Bigger batches aren’t always better.
The right batch size balances setup cost and waiting cost across the whole week.

Queue Discipline

FIFO is fair.
Priority-weighted FIFO makes sense when customers differ.
Random order creates rework and apologies.

Materials: Truth or Nothing

Two rules saved the most pain.

Receiving is complete only when available-to-pick.
If QC or relabeling is needed, it sits in quarantine with a clock.
Yellow and Red tags mean something.
Yellow = inside risk window.
Red = blocked.

Overrides happen in public, with the trade-off written on the board.
Promise-making moved from email to the floor — where reality lives.

What Changed Quickly

Promise accuracy improved.
Fewer after-hours emergencies.
Expedites became clearer and less frequent.
Material surprises dropped.
Emergency freight costs flattened.
Customers noticed.
“We’ll try for Friday” became:
“You have Thursday at 10:20 a.m. We protected it.”
That’s what a real date sounds like.

A Two-Week Start You Can Copy

Week 1

Identify your constraint.
Print a board with real shift blocks.
Model honest setup and run times.
Schedule the constraint first.
Confirm materials are available-to-pick.
Run daily 15-minute huddles.

Week 2

Enforce the Swap Rule.
Create a 3–5 hour capacity bank.
Batch by family to reduce setups.
Track schedule credibility and constraint utilization.
Hold a Friday review: what slipped, why, and how to prevent it.
If you stop hearing “We’ll try” and start hearing exact time slots, you’re doing it right.