How to build a production schedule

Outcome

You have a production schedule that says what runs where and when, that the shop floor can read without interpretation, and that survives contact with the first change.

What a schedule has to contain

A production schedule is a set of answers to one question repeated: this job — where, and when? Which means every entry needs four things.

The job. What is being made, in enough detail that the floor recognises it.
The place. The workstation it runs at — the mill, the bay, the bench.
The window. Start and end. For most shops, dates are the right granularity.
The claim. How much of that workstation it consumes while it is there.

Anything else — priority, customer, due date, operator — is useful, but those four are what makes it a schedule rather than a list.

Step 1 — List the places before the work

Write down every workstation the work passes through, with what stands at each and how much it can take in a day.

Do this before touching the job list. A schedule is an assignment of work to places, and if the places are vague the assignment cannot be checked. It is also the step that determines whether your schedule can catch its own mistakes: you cannot detect that two jobs collide without a shared definition of what they are colliding over.

Keep machines and their locations as one thing rather than two lists. The mill is a workstation; what stands at it is a property of that workstation. Two separate lists drift apart, and the schedule ends up trusting the one that is wrong.

Step 2 — Get durations you believe

For each job, how long at each workstation, and how much of it per day.

Use whatever your shop can estimate honestly. Historical actuals beat quoted times, quoted times beat guesses, and a rough number you believe beats a precise one you do not. Note setup separately if it is significant — a two-hour setup on a four-hour job changes which sequence makes sense.

Step 3 — Place the constrained work first

Start with the workstations that constrain output, and with the jobs whose dates are fixed by a customer commitment. Everything else has more freedom than it appears to, and freedom is easier to spend later.

Placing loose work first is the common mistake: the flexible jobs fill the bottleneck, and the committed job that arrives next has nowhere to go without unpicking the plan.

Step 4 — Check the plan against capacity

For every workstation and every day, compare what you have placed against what it can absorb. Anywhere booked exceeds capacity, you have not finished scheduling — you have written down a wish.

Resolve each overbooked day deliberately: move the job, add capacity, move it to another workstation or site, or renegotiate the date. Four options, and choosing none of them is itself a choice, made silently.

Capacity planning covers this comparison in more depth; the free template does it by formula and colours the overbooked days red.

Step 5 — Publish it where one version exists

The schedule has to be readable by the people doing the work, and there has to be exactly one of it.

This sounds trivial and is the most common point of failure. A schedule that exists as a file on one laptop, printed on Monday and annotated by hand through the week, is three schedules by Thursday. Whatever you use, the test is: if two people look right now, do they see the same thing?

Step 6 — Plan for the change, because it is coming

A schedule’s real quality is not how good it looks on Monday, it is how cheaply it absorbs the rush job on Tuesday.

When a job moves, everything it consumed moves with it, and anything that no longer fits has to resurface as a decision. If that reshuffle is manual, keep the schedule coarse enough that a rebuild is minutes rather than an afternoon — that is a real argument for planning in days rather than minutes, not a compromise.

Set a rhythm for revisiting: a fixed weekly review, plus a re-check after anything that invalidates the plan.

Three ways schedules stop being believed

Precision nobody trusts. A schedule to the minute, built on estimates good to the half-day, is fiction with decimal places. It gets ignored the first time reality diverges, and then it gets ignored permanently.

Planned to exactly 100%. A shop with no slack has no capacity to absorb the normal, which means every rush job breaks the plan rather than fitting into it.

Updated late. A schedule that lags reality is worse than none, because people act on it before discovering it is stale. If maintaining it is too expensive to keep current, the mechanics are wrong — which is a specific, recognisable point rather than a discipline failure.