It is 7:40 on a Tuesday at a bakery plant outside Pune. The shift supervisor has the day’s sheet in one hand and a phone in the other. The sheet says sponge cake, then muffins, then pound cake. The phone says a distributor wants the muffins first. He reshuffles the line, loses a changeover, and by evening the pound cake is short again. Everyone calls it a scheduling problem.
Our view is simple: most “scheduling problems” on an Indian plant floor are planning problems that arrived late, and no amount of clever sequencing fixes a week that never fitted in the first place. Good production planning software settles the weekly question before the morning one is asked, so the supervisor only has to sequence work that can actually be done.
Planning and scheduling answer different questions
Production planning asks: given the orders we count as firm, how much of each SKU should each line make on each day, and what raw material and packaging does that need? Its unit is the day, the line and the tonne. Its horizon is days to months.
Production scheduling asks: given today’s planned quantities, in what order do the jobs run on each machine, and who runs them? Its unit is the hour or the batch. Its horizon is a shift or a day.
| Production planning | Production scheduling | |
|---|---|---|
| Core question | How much, on which line, on which day | In what order, on which machine, at what hour |
| Horizon | Days, weeks and a rolling few months | A shift or a day |
| Main inputs | Firm orders, line capacity, calendar, stock, lead times | The day’s planned quantities, changeovers, crew on shift |
| Main outputs | Daily plan per line, raw material need, buy list | Job sequence, start times, crew assignment |
| Who owns it | Production planner, with procurement | Shift supervisor or line in-charge |
| Cost of getting it wrong | Rush buys, overtime, late orders | Lost changeovers, idle minutes, waiting crews |
Both matter. But they fail in different ways, and they need different tools and different people.
Planning has to come first, because capacity is a weekly fact
A line has a fixed number of hours in a week. If the orders loaded onto it need more hours than that, the shortfall exists before anyone picks a sequence. Scheduling can trim minutes from changeovers. It cannot create a missing shift.
This is why we argue the capacity check belongs in planning. Each working day, due SKUs should take capacity in priority order, and only then should early work pull ahead into the hours left. If a line shows above 100 % load for Thursday on Monday, the planner can move volume, add a shift or tell sales. If it shows up on Thursday morning, the supervisor can only choose which order to disappoint. Our guide to capacity planning in production walks through that load check line by line.
A worked example: four missing hours no sequence can find
Take an illustrative cake line. These are round numbers to show the arithmetic, not results from any plant.
- The line runs two shifts of 8 hours, 5 days a week: 2 × 8 × 5 = 80 hours available.
- This week’s firm orders need 50 hours of sponge cake, 20 hours of muffins and 14 hours of pound cake, counting the changeovers of a typical week: 50 + 20 + 14 = 84 hours.
- Load is 84 ÷ 80 = 105 %. The week is 4 hours short before a single job is sequenced.
Now give the supervisor the best possible schedule. Say each changeover takes 30 minutes, and the 84 hours assume a typical week of 10 changeovers, which is 5 hours. A well-sequenced week, grouping flavours and sizes, might have 6, which is 3 hours. Good scheduling saves 2 hours: 84 − 2 = 82 hours needed.
Against 80 available, the week is still 2 hours short. Something will be late, and by the time scheduling finds out, the only levers left are overtime or a missed dispatch. The planner, looking at the same numbers on Monday, had better choices: add a short Saturday shift, or agree a later date for part of the pound cake while there was still time to ask nicely.
Scheduling decides who waits. Planning decides whether anyone has to.
The buy list belongs to planning, not to the shift
There is a second reason planning comes first: materials. A schedule assumes the flour, fat, wrappers and cartons are already in the store. Only the plan can say whether they will be.
When the plan is fixed for the days ahead, projected production becomes raw material need, net of stock and in-transit, and packaging need comes from the packaging bill of materials. Compare that need with cover on hand and the real lead time, and each material gets an “order by” date. Miss that link and procurement learns what the plan needs only after it is published, so every buy becomes a rush. A supervisor with a perfect sequence and an empty wrapper bin still has a stopped line.
What a plant looks like when the two are separated
The morning changes first. The supervisor opens a daily plan that already fits the line’s hours, so the conversation is about sequence, not about which order to drop. The phone call from the distributor is still there, but it is a request to swap two jobs that both fit, not a crisis.
The planner’s week changes too. Monday is for checking load, freezing the days already committed to the floor and confirming the buy list. Tuesday’s bottleneck is visible on Monday. At the end of each day, the gap between what was planned and what was made gets a reason, so the next plan learns from it. Our post on production plan vs actual variance covers how to read those gaps without turning them into blame.
The strongest objection: “our plan changes every hour anyway”
We hear this often, and it deserves a straight answer. Some plants really do get orders by phone at noon for dispatch at six. In those plants, a weekly plan can feel like fiction, and the schedule is the only plan that exists.
We do not think the answer is to give up planning. It is to plan at the right level and protect the near days. Keep a short frozen window that only changes by a deliberate, recorded decision. Keep the days after it firm but open to adjustment. Leave the rest fluid. The noon order then lands in the first open slot that has hours and materials, rather than knocking over a shift that was already running. The plan still changes. It just changes on purpose.
There is also an honest limit. A daily, line-level plan does not replace minute-by-minute machine sequencing on a complex job shop with dozens of routings. If that is your floor, you may need a scheduling layer on top. But that layer will only be as good as the weekly plan it is fed.
In Indian plants, the planner and the scheduler are often one tired person
In many mid-sized plants here, one planner keeps a workbook of dozens of sheets, does the weekly plan, writes the daily sheet and takes the supervisor’s calls. The two jobs blur because one person does both, usually late in the evening. When that person is on leave, the plant guesses at both levels at once.
Separating the decisions does not need two new hires. It needs the plan to live somewhere anyone can read it, with capacity and materials checked, so the scheduling conversation on the floor starts from numbers that fit. More on the planning side is in our production planning guides.
What to do this week
- For one line, add up available hours for next week and the hours its firm orders need. Write down the load as a percentage.
- If load is above 100 %, decide on Monday what moves, rather than letting the shift decide on the day.
- List every material that line needs next week and check each against cover on hand and lead time.
- Agree how many near days are frozen and who may change them.
- Ask the supervisor which morning reshuffles were really missing hours or missing materials. Count them.
If most of the reshuffles trace back to the week, not the morning, you have a planning problem wearing a scheduling badge. That is good news. It is the easier one to fix.