Inventory Shrink Investigation Protocol & Sample Audits

Overview

This playbook helps teams move from suspicion to evidence-backed action. Use the protocol to identify where shrink is actually occurring, gather defensible data, test short corrective experiments, and measure whether interventions recover margin. Preserve staff dignity, avoid premature accusations, and focus on systems and processes first.

Phases at a Glance

1. Scoping — identify top-loss SKUs and likely loss areas using POS, inventory, and purchasing data.
2. Sampling & Observation Planning — pick times, locations, roles and sample sizes to observe real operations.
3. Evidence Collection — standardize what to record: receiving, prep, waste, transfers, voids, comps, and theft indicators.
4. Short Corrective Experiments — implement limited tests (e.g., locked storage, par changes) to validate hypotheses.
5. Measurement & Escalation — measure impact, decide whether to scale, and escalate if thresholds are met.

1. Scoping: Find Where the Loss Is

Start with the data you already have. The goal is to rank opportunities so investigative effort targets the biggest recoverable loss.

• Run an SKU-level shrink report (sales vs. inventory usage) for the last 30–90 days. Look for high-dollar and high-turn SKUs with unexpected variance.
• Cross-check purchase/receive records to see unexplained discrepancies.
• Identify suspicious patterns: time-of-day, shift, specific prep stations, or particular suppliers.
• Choose 3–8 priority SKUs or categories for the investigation (focus is better than a scattershot approach).

2. Sampling & Observation Plan

Design observations so they are representative and repeatable.

Sampling rules

• Time-of-day: include at least one peak and one off-peak period.
• Role-based: observe receiving, receiving clerk, expeditor, line cooks, bartenders, and closing staff depending on the SKU.
• Duration: observe short, frequent sessions (15–45 minutes) rather than a single long watch to reduce observer fatigue.
• Randomization: if practical, randomize days/shifts to avoid bias.

Observer guidance

• Use a neutral script: "We're checking processes and records to reduce loss; we're not blaming anyone."
• Record exactly what you see (actions, times, quantities). Avoid speculation in the data field.
• Capture contextual notes: lighting, equipment failures, menu specials, staffing gaps.

3. Evidence Collection: What to Record

Use consistent data fields to make records comparable. Below are suggested fields for the sample data collection sheet you can copy or convert into an interactive audit form.

Sample Data Collection Sheet (fields to capture)

1. Date
2. Observer name/role
3. Location/Station
4. Shift (breakfast/lunch/dinner/closing)
5. SKU or category observed
6. Activity observed (receiving, putaway, prep, portioning, waste disposal, comp, void, transfer)
7. Quantity involved (units/weight/portions)
8. What happened (brief factual description)
9. Immediate cause(s) observed (e.g., over-portioning, improper storage, damaged pack, unrecorded comp)
10. Likelihood this contributed to variance (Low/Medium/High)
11. Photo or reference to asset/evidence (if permitted)
12. Recommended immediate control or quick fix

Other evidence streams

• Receiving: count vs. invoice, condition, short- or over-shipments.
• Storage: unlocked doors, unlabeled product, temperature excursions.
• Prep & portioning: portion sizes, recipe deviations, trimming losses.
• Waste: disposal practices, undocumented composting, or food for staff.
• Transactions: frequent voids/comps, discount patterns, manual tickets.

4. Hypotheses & Short Corrective Experiments

Turn observed causes into simple, time-boxed experiments. Each experiment should have a clear hypothesis, intervention, owner, duration, and measurement plan.

Example experiments

• Locked high-value storage: Hypothesis — unauthorized access is causing shrink. Intervention — lock storage overnight with sign-in/out for access. Measure — inventory difference for 2 weeks.
• Par-level changes: Hypothesis — over-ordering and spoilage cause shrink. Intervention — temporarily reduce par for fast-turn perishables and track stockouts vs. waste.
• Portion control enforcement: Hypothesis — inconsistent portions cause variance. Intervention — require portioning tools and run daily portion spot-checks for 7 days.
• Receiving double-check: Hypothesis — receiving mistakes lead to incorrect inventory. Intervention — require a second signature or photo on every invoice for 10 deliveries.

Experiment design notes

• Prefer short (7–21 day) experiments that are safe and reversible.
• Define primary metric (e.g., shrink $ per week per SKU, inventory accuracy %) and at least one supporting metric (e.g., stockouts, measured waste weight).
• Keep a control when possible (one shift or one location without the intervention) to compare results.

5. Measurement, Decision & Escalation Flow

Decide in advance what outcomes will cause you to scale, modify, or escalate.

Suggested measurement cadence

• Daily: quick checks for compliance (e.g., sign-in logs, portion checks).
• Weekly: compute shrink $/SKU and compare to baseline.
• End of experiment: run a simple before/after comparison and capture lessons learned.

Escalation thresholds and flow

1. Minor variance reduction (<10% improvement): keep changes local, iterate controls, update standard work.
2. Moderate improvement (10–30%): expand intervention across shifts/locations; schedule training and update SOPs.
3. High-risk or evidence of intentional theft, repeated policy violations, or significant unexplained losses (>30% or a set dollar threshold): notify site manager, HR, and regional loss prevention immediately. Follow legal and HR protocols—avoid confrontational or accusatory actions without counsel.

6. Sustain & Scale

If an experiment succeeds, make gains permanent by:

• Updating SOPs and checklists
• Adding role-based ownership and daily/weekly checks
• Implementing lightweight dashboards to track SKU shrink over time
• Training staff and embedding the why into shift huddles

Investigator tips & ethics

• Separate systems issues from individual blame. Often shrink is the result of process gaps.
• Document carefully and keep records secure. Photographs and logs may be sensitive.
• When theft is suspected, follow HR and legal guidance. Protect employee rights and the organization's position.

Appendix: Quick Audit Checklist (copyable fields)

1. Audit date and observer
2. SKU / Location
3. Observed mismatch? (Yes / No)
4. Type of mismatch (receiving / storage / prep / waste / transaction)
5. Quantity discrepancy
6. Immediate corrective action taken
7. Recommended follow-up

Use this playbook as a repeatable protocol. Consider converting the audit sheets and experiment logs into interactive forms so data is stored, queryable, and available for dashboards and cross-location comparisons.