Scheduling & production
Production schedules rebuilt every morning in a spreadsheet
The scheduler gets in at five to re-sequence the day: two rush orders landed yesterday afternoon, a press is down, and the material for job 1187 still hasn't arrived. The schedule that gets printed at seven is obsolete by nine. Everyone on the floor knows it, so they check with the scheduler instead of the schedule.
The plan exists. It's just that the real one lives in one person's head, updated by radio, and the spreadsheet is its occasional snapshot.
What it looks like
- Yesterday's rush orders force a full re-sequence every morning, and the 'final' schedule is a starting suggestion by mid-morning.
- Sales promises delivery dates from the gut, without checking load or capacity—then production absorbs the promise.
- A machine goes down and the floor finds out by walking past it; the schedule doesn't know for hours.
- Jobs get sequenced without grouping changeovers, burning setup hours that a different order of the same jobs would have saved.
- Material arrives but nobody told the schedule, so a ready job sits while a blocked one holds a work center.
Why it happens
The ERP knows the orders, the due dates, and the routings. It does not know the floor: which press is down today, which operator is certified on which line, which material physically arrived, which job the tooling is still set up for. The true state of production is a stream of events that never reaches the plan.
So the scheduler becomes the integration layer—holding orders, floor reality, and tribal rules in their head, and rebuilding the plan manually every time reality shifts, which is daily. The spreadsheet isn't the scheduling system. The scheduler is. The spreadsheet is just where they sometimes write it down.
What it costs
The honest answer is that it depends on your volumes, your margins, and how long it has been going on. What is consistent across companies is where the cost shows up:
Labor
The scheduler's early mornings and constant re-planning, plus every supervisor's time spent asking 'what are we running next?'
Late orders and expediting
Promises made without capacity visibility get kept with overtime and premium freight—or not kept at all.
Changeover waste
Poorly sequenced jobs repeat setups that good sequencing would share. The hours vanish into 'how the day went.'
Idle capacity
Work centers wait on material or tooling that another sequence would have routed around—capacity you paid for and didn't use.
How a purpose-built system fixes it
A purpose-built scheduling board connects the two halves that currently meet only in the scheduler's head: the ERP's orders and due dates on one side, live floor status—machines, material, operators—on the other. The plan on the wall is the plan in the system, and when reality changes, the board changes with it.
Sequencing becomes drag-and-drop with guardrails: the board knows the constraints—material availability, tooling, operator certification, changeover families—so a move that would break something gets flagged before it's made, not discovered on the floor.
Concept Interface
Production board — this week
Jobs sequenced against live material, machine, and due-date status.
| Job | Work center | Material | Due | Status |
|---|---|---|---|---|
| J-1187 | Press 2 | Short — ETA Wed | Jul 25 | Material short |
| J-1191 | Press 2 | Staged | Jul 26 | Ready to run |
| J-1189 | CNC 1 | On hand | Jul 28 | Ready pending inspection |
| J-1194 | CNC 1 | On hand | Jul 29 | Changeover family B |
Example System — the same plan the scheduler sees and the floor sees, updated by events, not by re-typing.
The scheduler doesn't disappear—the job changes. Instead of rebuilding the plan every morning, they manage exceptions and improvements on a plan the system keeps current. The tribal rules get written into the board, where they survive vacations.
When a simpler fix is enough
If you run one line with a handful of jobs, a whiteboard and a daily fifteen-minute meeting genuinely work—many good shops run exactly that way. And if your constraints are simple, the scheduling module already in your ERP may deserve a serious try before anything custom.
The break point is multiple work centers, frequent rush orders, real setup-time economics, and constraints that live on the floor rather than in the ERP. When the schedule is obsolete by 9am every day, the gap is exactly the kind a purpose-built scheduling board is made for.
Related systems and industries
- Custom internal toolsScheduling boards built around your work centers, constraints, and changeover rules.
- Operational dashboardsLive floor status—machines, material, jobs—visible to everyone who plans around it.
- System integrationsERP orders and due dates flowing into the plan without re-entry.
- Contract manufacturingWhere mix, due dates, and changeovers make sequencing a daily economics problem.
Common questions
- ERP schedulers plan against the data the ERP has: orders, routings, standard times. They struggle with what the ERP doesn't know—today's down press, the material on the dock that isn't receipted yet, the operator certifications, the changeover logic your scheduler applies instinctively. If your scheduling is simple, use the ERP. If your scheduler rebuilds its output every morning, the missing piece is floor reality, and that's what a purpose-built board adds.
- They use what is current. Floor teams ignore schedules that are stale by 9am because they have to. When the board reflects reality—a down machine shows as down, a material arrival unblocks a job—checking it becomes the fastest way to know what's next. Adoption follows accuracy.
Your real schedule lives in one person's head. What happens when they're out?
A Workflow Review maps how the plan actually gets made each morning—and what a live version would take.