A plan vs actual sheet has one row for each product in the week's plan: the units planned, the good units made, the difference, and a reason for any gap. Its job is to turn "we had a rough week" into a short list of causes. The trap is the total. A week can come in at 90% of plan overall while one product came in at nothing, and extra units of one thing can hide a miss on another. So the sheet below works out two numbers: attainment, actual over planned, and schedule attainment, where each product counts only up to its plan. Below is a week for a made-up salsa maker, how to read it, a month view, and the file.
The short version
- One row a product: planned, good units made, difference, reason.
- Count good units only. Rejects weren't made.
- Attainment = actual ÷ planned.
- Schedule attainment counts each product only up to its plan.
- Every miss gets a reason, written that week.
- Read the rows before the total.
- TaroStack records each batch against what was planned. More below.
An example week
| Product | Planned | Actual, good units | Difference | Attainment | Counted toward the plan | Status | Reason |
|---|---|---|---|---|---|---|---|
| Salsa, mild, 16 oz | 1,200 | 1,180 | −20 | 98% | 1,180 | ON PLAN | Short fills rejected at the checkweigher |
| Salsa, hot, 16 oz | 800 | 800 | 0 | 100% | 800 | ON PLAN | |
| Salsa verde, 16 oz | 600 | 420 | −180 | 70% | 420 | MISSED | Tomatillos arrived Wednesday, a day late |
| Pico de gallo, 12 oz | 400 | 460 | 60 | 115% | 400 | OVER | Made ahead for the weekend order |
| Tortilla chips, 12 oz | 900 | 900 | 0 | 100% | 900 | ON PLAN | |
| Queso dip, 12 oz | 300 | 0 | −300 | 0% | 0 | MISSED | Kettle down Tuesday to Thursday |
| Total | 4,200 | 3,760 | −440 | 90% | 3,700 |
Reading it
The total says 90%. 3,760 good units against 4,200 planned. That sounds like a week that nearly worked.
The rows say otherwise. No queso was made at all, and the verde was 180 short. A customer waiting for queso got none of it, whatever the total says.
Schedule attainment says 88%. The pico line made 60 more than planned. Those jars are real, but nobody planned to sell them this week, and they don't make up for missing verde. Counting each product only up to its plan gives 3,700 of 4,200. The gap between the two percentages is the overproduction: 60 units here.
Status. The sheet marks a product MISSED under 95% of plan and OVER above 105%. Those are this maker's limits. The mild salsa, 20 short, is inside them.
The reasons
A reason is worth writing only if it's specific enough to act on. "Short on materials" isn't. "Tomatillos arrived Wednesday, a day late" is: it names a supplier and a day.
| Reason | Units short | What it points to |
|---|---|---|
| Kettle down Tuesday to Thursday | 300 | Maintenance, and no second way to make queso |
| Tomatillos arrived a day late | 180 | The supplier's lead time, or how late they were ordered |
| Short fills rejected | 20 | The filler's setting |
Three hundred of the 500 units missed were one kettle. That's a different week from "we were 10% short".
The month
| Week starting | Planned | Actual, good units | Attainment | Counted toward the plan | Schedule attainment | Biggest miss, and why |
|---|---|---|---|---|---|---|
| Nov 2 | 4,000 | 3,950 | 99% | 3,900 | 98% | Chips 100 short: a film changeover ran long |
| Nov 9 | 4,200 | 4,230 | 101% | 4,150 | 99% | Hot salsa 50 short: jars arrived Thursday |
| Nov 16 | 4,200 | 3,760 | 90% | 3,700 | 88% | Queso 300 short: kettle down three days |
| Nov 23 | 4,400 | 4,310 | 98% | 4,280 | 97% | Verde 120 short: one cook out |
The week of November 9 made more than its plan, 101%, and still missed 50 jars of hot salsa. Over the month, 16,250 good units were made against 16,800 planned, 97%, and 16,030 of them counted toward the plan, 95%. Late materials show up twice, the jars on the 9th and the tomatillos on the 16th. That's the pattern a month shows and a week can't.
Where the numbers come from
Planned units come from the week's schedule: see production schedule Gantt chart and master production schedule template. Good units come from each day's production report template. Whether the materials would be there is a question to ask before the week starts: see material requirements planning example. During the week, a production tracking board shows what's stuck.
Get the format
Download the production plan vs actual sheet. Two sheets and a read-me: a week that works out the difference, attainment, units counted toward the plan and a status for each product, and a month with a row for each week. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The sheet is filled in on Friday, from memory and the week's reports. By then the reason for Tuesday's miss has been simplified, and the kettle that was "down" was really waiting two days for a part nobody had ordered. And it looks backward. It can't say on Monday that the tomatillos due Tuesday are the ones Wednesday's batch needs.
How TaroStack does it
TaroStack keeps the plan and the result on the same batch.
Each batch is a record that is planned, started and finished, with the amount planned and the amount made.
Planning, on Growth, names what will run short or arrive too late, in plain words, days ahead.
"What could I make right now" says which batches the materials on hand will cover.
Actual against standard: what a batch used and made, set against its recipe.
The batch notes the lots it used, automatically, and your own checks are fields on its record.
| The question | Friday's sheet | In TaroStack |
|---|---|---|
| What was planned and what was made | Typed in afterward | On each batch |
| Will Wednesday's materials be here | Find out Wednesday | Planning, on Growth |
| Can the queso be made today | Walk to the store room | What could I make right now |
| What the short batch used | The batch sheet, if kept | On the batch record |
TaroStack doesn't count units off a machine: what was made is what someone records on the batch. Recipes, batches and lots are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes, with planning). 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.
