Variance should start a review, not an accusation
A shift variance report can show that product movement does not match expected usage. It cannot, by itself, prove intent. Counts may be wrong, recipes may be unmapped, transfers may be missing, and comps or waste may not have been recorded.
Managers should treat variance as an operating signal that deserves evidence, not as a shortcut to blame.
Review the evidence in layers
Start with opening and closing count coverage. Then check mapped sales, recipe accuracy, waste logs, comps, voids, transfers, and receiving. Only after those layers are reviewed should employee-level patterns be discussed.
- Opening and closing counts
- POS or sales import mapping
- Recipe and modifier accuracy
- Waste, breakage, comps, voids, and transfers
- Bartender assignment and manager notes
Use notes to protect the team and the business
A good manager note explains what was reviewed and what action was taken. That may be a recipe correction, retraining on ringing modifiers, a draft-system check, or a follow-up conversation.
The written trail matters because it keeps the process consistent and fair.
Put the guide into practice
Try the BMS sample bar before loading your real data.
Explore inventory setup, storage areas, ordering, invoices, recipes, reporting, and shift variance in The Manager's Table BMS.