The format most small makers settle on is a grid: products down the side, days across the top, units in the cells. Three more columns turn it from a wish list into a plan: the batch size, so the units come out as whole batches, the units the line makes in an hour, so the units become hours, and a total. Then one more sheet adds up the hours day by day against the hours you have, because a week can fit in total and not fit on Thursday. Below is the format filled in for a made-up granola maker, the Thursday problem and its fix, and the file.
The short version
- Rows are products. Columns are days. Cells are units to make.
- Plan in whole batches: every cell is a multiple of the batch size.
- Units ÷ units an hour = hours. Add the hours up by day, not only by week.
- Compare each day with the hours you have. Move work off the day that's over.
- Leave some hours unplanned. Something always takes longer.
- TaroStack's planning says what to make and what will run short. More below.
The format, filled in
| Product | Batch size | Units an hour | Mon | Tue | Wed | Thu | Fri | Week total | Batches | Hours |
|---|---|---|---|---|---|---|---|---|---|---|
| Granola, maple pecan, 12 oz | 240 | 120 | 480 | 0 | 480 | 0 | 240 | 1,200 | 5 | 10.0 |
| Granola, cherry almond, 12 oz | 240 | 120 | 0 | 480 | 0 | 240 | 0 | 720 | 3 | 6.0 |
| Granola, plain, 5 lb bag | 60 | 40 | 0 | 0 | 120 | 0 | 60 | 180 | 3 | 4.5 |
| Granola bars, box of 6 | 180 | 60 | 180 | 180 | 0 | 360 | 0 | 720 | 4 | 12.0 |
| Trail mix, 8 oz | 300 | 150 | 0 | 0 | 0 | 300 | 300 | 600 | 2 | 4.0 |
Seventeen batches, 36.5 hours. The line has one eight-hour shift, five days: 40 hours. On this sheet the week fits, with three and a half hours to spare.
Batch size is what one batch makes: a mixer's load, an oven's racks. Every number in the day columns is a multiple of it, because nobody makes two-thirds of a batch.
Units an hour is the line's real rate for that product, baking, cooling and packing included. Take it from your own production log, not from the best day you remember. Bars are slow here, 60 boxes an hour, because they're cut and wrapped by hand.
The same week, by day
| Day | Hours planned | Hours available | Over or under | What runs |
|---|---|---|---|---|
| Mon | 7.0 | 8 | −1.0 | Maple pecan 480, bars 180 |
| Tue | 7.0 | 8 | −1.0 | Cherry almond 480, bars 180 |
| Wed | 7.0 | 8 | −1.0 | Maple pecan 480, plain 120 |
| Thu | 10.0 | 8 | +2.0 | Cherry almond 240, bars 360, trail mix 300 |
| Fri | 5.5 | 8 | −2.5 | Maple pecan 240, plain 60, trail mix 300 |
| Week | 36.5 | 40 | −3.5 |
Thursday is ten hours of work in an eight-hour day. Friday has two and a half hours free. The weekly total hid both.
The fix is a move, not overtime. Thursday's trail mix, 300 bags, is two hours. Friday already runs trail mix, so moving it there means one longer run instead of two. Thursday drops to 8.0 hours and Friday rises to 7.5. Nothing else changes: the same 17 batches, the same 36.5 hours.
Before moving a run, check two things. Is the product needed Thursday, for a Friday truck? And will the materials be in the building by then? Whether they will is a separate sum: see material requirements planning example.
Where the numbers in the cells come from
The format holds the plan. It doesn't decide it. The units come from what's expected to ship, less what's on the shelf, plus the stock you want left: that sum is worked through in production planning and inventory control and, step by step, in how to prepare a production plan. A plan that looks further ahead, by week, is a master production schedule.
Rules that keep the format honest
- One line, one sheet. If you have two ovens that can run at once, each gets its own hours-by-day table.
- Changeovers are hours. Going from a nut product to a plain one means a clean-down. Add a row for it or lower the units an hour.
- Don't plan to 100%. This maker plans to 36.5 of 40 hours. The spare three and a half are for the batch that has to be made twice.
- Freeze the next two days. Change Thursday on Monday if you must. Don't change tomorrow at 4 pm.
- Put Friday's actuals beside the plan. A plan nobody checks drifts: see production plan vs actual.
Get the format
Download the production plan format. Two sheets and a read-me: the week's grid, with totals, batches and hours worked out as you type, and the hours by day against the hours available. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The grid knows hours. It doesn't know that Wednesday's maple pecan needs 96 lb of pecans and 60 are on the shelf, or that the cherry almond planned for Tuesday is for an order that was cancelled on Monday. Every one of those is a phone call and an edit, and the hours-by-day table has to be redone by hand each time a cell moves.
How TaroStack does it
Planning in TaroStack, on Growth, starts from stock and orders, not from an empty grid.
What to make, what to buy, and when, in plain words. Every suggestion is a draft you approve.
Work centers and capacity, so a week's plan doesn't promise more hours than you have.
Exceptions in plain words: what will run short, what will arrive too late, what will expire before it's used.
"What could I make right now" checks a batch against the materials actually on hand.
Each batch is recorded against what was planned, with the lots it used.
| The job | Excel grid | In TaroStack |
|---|---|---|
| How much of each to make | Work it out, type it in | Suggested from stock, orders and safety stock |
| Does each day fit | The second sheet, redone by hand | Work centers and capacity |
| Are the pecans here | Walk to the shelf | Named as an exception, days ahead |
| What was really made | Friday's sheet | On each batch |
Planning is on Growth at $39 a month (50 recipes). Recipes and batches alone are on every plan, from $9.99 a month (5 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
