Predicted and actual usage: 7 steps to check gaps

1. Work out the predicted use first

Start with the number your sales should have produced. The idea is simple: multiply what you sold by how much of each input a single unit is expected to use. OpenStax uses a popcorn theater to show the method. The text states the result this way: "Therefore, if the theater sells 300 bags of popcorn with two tablespoons of butter on each, the total amount of butter that should be used is 600 tablespoons." ( OpenStax, Compute and Evaluate Materials Variances)

The same logic works for any product with a standard recipe. The OpenStax chapter also gives a candy example: "Each box of candy is expected to use 0.25 pounds of candy-making materials." ( OpenStax)

Pay attention to units while you build this number. If your sales report counts menu items but your recipes count pounds, you have to translate one into the other before you can multiply. Pick one unit for each input, such as ounces, cups, pieces, or pounds, and use it everywhere in the calculation. A mix of units is an easy source of confusion, and it is usually fixable on paper before anyone opens a box.

Write down the expected amount for each unit of every input you track, and keep that figure next to the sales count for the same period. If the amount for each unit only lives in someone's head, write it down now. A predicted number you cannot reproduce will make every gap look like a mystery, and you will spend the count arguing about the standard instead of the stock.

2. Pull the actual use for the same period

Next, find the actual amount used. For most shops, that is the opening count, plus what came in during the period, minus the closing count. Use the same start and end dates as your sales report. A count taken late in the period, compared with sales from a different stretch of time, will produce a gap that has nothing to do with how the product was handled.

Before you trust the result, check two things. First, confirm that deliveries were logged in the same units your recipes use. A case that is recorded as a case, while the recipe calls for single units, will distort the figure. Second, confirm that transfers to another location, returns to a vendor, and product moved to a prep area were all recorded. Any of these can make the closing count look higher or lower than what the kitchen actually used.

Count the same way each time. Count sealed cases and open containers separately, and write down how much is left in each partly used container, by weight or by measure, instead of estimating it by eye. Two people counting the same shelf will often disagree by a little, and a little disagreement, repeated across many items, can look like a large gap. If the team has a standard way to count, follow it, and if it does not, agree on one before the next count. For the count itself, see physical inventory reconciliation.

Look at the closing count for anything that does not make sense. A shelf that is suddenly full of an item you rarely stock, or an empty bin for something you order every delivery, is worth a second look before you use it in the math.

Write the actual figure down with its inputs visible. Opening count, deliveries, and closing count should sit on the same line so the next reader can see where each part came from. A single number with no inputs is hard to check, and hard to defend.

The OpenStax butter example makes the same move: "Management can then compare the predicted use of 600 tablespoons of butter to the actual amount used." ( OpenStax)

3. Measure the gap in both directions

Subtract the predicted use from the actual use, using the same units for both. A positive result means more was used than sales predicted. A negative result means less was used. A result near zero means the item behaved about as expected, but check it anyway if the total is only near zero because a large overage and a large shortage cancelled each other out.

A category can look fine on the summary line while some items run high and others run low. Break the gap down by item, so each result can be investigated on its own and the two directions do not hide each other.

The OpenStax example shows why both directions matter. Its predicted use is 600 tablespoons of butter. For the high side, the text says: "If more than 600 tablespoons of butter were used, management would investigate to determine why." ( OpenStax) The low side raises a different concern, which step five covers.

Decide in advance how big a gap has to be before it gets a full investigation. A shop may prefer a band of tolerance, so that small differences from counting error do not take up the whole review. Write the band down and apply it the same way on every count, so the rule does not change depending on who is counting.

If you also track cost, price the gap after you have the units right. Units tell you what happened on the floor; cost tells you how much it matters.

4. Investigate the overuse gap

When actual use is higher than predicted, start with the parts of the process that move product without a sale. Check each of these against what you saw on the floor:

• Portioning. A scoop, ladle, or pour that runs a little heavy on every serving adds up over time. Watch a few servings being made, and compare them with the standard you wrote down in step one.
• Waste and spoilage. Product that was thrown out, dropped, burned, or past its date still left the storeroom, so it counts as used. Ask the team what went in the bin during the period.
• Staff meals and samples. Food taken for staff meals, tastings, and test batches often never goes through the register. It is real use, but it never reaches the sales figure.
• Recipe changes. If the recipe was updated but the figure for each unit was not, your predicted number is out of date. Compare the current recipe with the one you used to build the standard.
• Transfers and returns. Product sent to another location or back to a vendor that was never recorded looks like use. Pull the transfer log and match it against the gap.
• Loss. Product that left without a sale, a transfer, or a waste entry may be theft or plain error. The record cannot tell you which, so treat it as an open question, not a conclusion.

Walk the line during a busy shift if you can. A portion that looks right at the start of service may drift by the end, when people are tired and rushed, and a single observation will tell you more than guessing from the count.

A practical check for portioning is to weigh or measure a handful of servings and compare them with the standard, then do the same at a different time of day. Matching portions at both times do not rule out drift during other shifts. If they do not match, check training and equipment before changing the standard.

Prioritize by size. Start with the cause that could explain the largest part of the gap, since testing it first tells you the most for the least effort. Then move down the list.

Tie each cause to evidence you can point to: a waste log, a register report, a photo of a scale reading, a transfer slip. A guess about what happened is a lead to test, not a finding.

For each cause you test, write down what you checked and what you found. If you cannot confirm a cause, record it as unresolved and say what you would check on the next count. If the overage is large and you cannot find a cause in the process, bring in a manager who did not take part in the count, so the review is not based only on the people who did the work.

5. Investigate the underuse gap

Less product used than predicted feels like good news, and it is easy to skip. The OpenStax text does not treat it that way. It says: "If the actual usage of butter was less than 600, customers may not be happy, because they may feel that they did not get enough butter." ( OpenStax) In a shop, that same gap can mean portions are being cut, or it can mean the records are wrong. Check the records first.

Check these causes before you decide the count is good news:

• Recorded sales that were never made. A duplicate ring-up, a refund for an item that never reached the line, or an item entered under the wrong code raises predicted use above what was actually prepared. Compare the register detail with the tickets.
• Unlogged deliveries. Product that arrived and went onto the shelf without a receiving entry makes the closing count look high, so the actual use looks low. Check the delivery paperwork against the receiving log.
• Counts that were too high. A closing count that includes product already used, moved, or thrown away will make use look lower than it was. Recount the items with the largest gaps before you change any standard.
• Portions that shrank without a decision. Lighter servings, whether from a new team member or a busy shift, show up as less use. Compare recent portions with the standard, and ask whether customers have noticed a change.
• Recipe or portion changes not written down. If the team now uses less for each unit on purpose, the predicted number should change too. Update the standard and note the date of the change.

6. Talk to the people who handled the product

The count tells you what is on the shelf. The people who cooked, poured, and received the product can tell you what happened to it. Talk to them before you write a cause down, and talk to them as people who are trying to solve the same problem, not as suspects.

Ask open questions and let them answer in full. Useful starting points include:

• What was made or sold during the period that you did not expect?
• Was anything thrown out, dropped, or sent back?
• Did any product go to another location, to staff, or to a prep area without a note?
• Did the way a dish or drink is portioned change, even slightly?
• Did any orders get rung up differently, voided, or entered twice?

Write down what each person says, and what evidence they can point to. Their answer is a lead to check against the records, not the end of the review. A person who says they used exactly the standard may be right, and the record may still be wrong. A person who explains a gap may be honest and mistaken. Keep the conversation about the process: a question like "what made the scoop go over?" gets a more useful answer than "who used too much?"

Keep the staff who count in the loop too. The people doing the count will be asked to explain the gap, so tell them what the comparison is for and how it will be used. When they understand that the goal is a better standard, they are more likely to tell you what really happened.

7. Record the finding and update the standard

Once you have a cause for each gap, write a short record. Include the item, the period, the predicted use, the actual use, and the gap in the same units. Then add the cause you confirmed, what you checked, and what you changed. Keep it short enough that someone can read it in a minute, and complete enough that someone else can rebuild the reasoning.

Attach the source documents. Sales reports, receiving records, transfer slips, waste logs, and count sheets are what you will need if someone asks later why the number moved. Paper and digital records both work, as long as they can be found when someone needs them. Store the record where the next person doing a count will look first.

Share the record with the team that did the count, not only with management. People who see the result of their work are more likely to keep the next count careful, and they may spot the same kind of problem sooner.

Then decide what to change. If the cause was a real change in how the item is made, update the amount for each unit you wrote down in step one, and note the date of the change so the old and new figures can be compared. If the cause was a mistake, fix the process that allowed it: the receiving form, the ring-up code, the count sheet layout, or the transfer log. Then run the comparison again on the next count. If the gap comes back, the investigation starts again, now with a clearer picture of what to test. See inventory adjustment checks before updating the stock record.

Keep the response proportionate. A small gap on a low-cost item can be noted and watched on the next count. A large gap on an expensive item, or one that is easy to take, deserves a fuller review and a manager's sign-off before the standard changes. The goal is not to find someone to blame. The goal is a number you can explain, and a count the next person can trust.