Par & Cycle-Count Worksheet with Variance Escalation Flow

Purpose

This worksheet helps teams run regular par lists and cycle counts that are manageable, repeatable, and connected to clear investigation and corrective actions when variances occur. Use it to reduce over-ordering, spoilage, stockouts, and unexplained shrink.

What's included

• Par-list template per category
• Sample weekly/monthly cycle-count schedule
• Count sheet (expected vs actual) with fields to record context
• Automatic variance-flag guidance with suggested thresholds
• Root-cause checklist (receiving, recording, prep loss, theft, supplier)
• Escalation flow: who investigates, how, and corrective actions

Par-list template (use per category)

Cycle-count schedule (example)

Assign counts by category and frequency based on value, usage, and risk. Customize to your operation.

• High-value / high-turn items: weekly
• Moderate-value, fast-moving: biweekly
• Low-value or long-life: monthly or quarterly
• Critical allergens / special-order items: include in every count

Count sheet (one row per item)

Automatic variance flag guidance (suggested)

Use these thresholds as a starting point and adjust for your menu and item cost structure.

• Green — Variance ≤ 5%: no immediate action required; log and monitor
• Yellow — Variance > 5% and ≤ 15%: require supervisor review and recount within 48 hours; complete root-cause checklist
• Red — Variance > 15% or negative stock: immediate escalation to store manager, recount within 24 hours, and investigation started

Root-cause checklist (use when flagged)

Walk through the checklist to capture likely causes and corrective actions.

1. Receiving
   • Was the item received and verified against PO? (Y/N)
   • Were weights/quantities recorded in the system?
   • Action: Reconcile vendor invoice, locate receiving paperwork, interview receiver.
2. Recording / POS / Production entries
   • Were recent transfers or prep usages entered correctly?
   • Action: Verify prep logs, transfer slips, and POS comp/void entries; correct system records.
3. Prep loss & portioning
   • Was yield loss or trimming recorded correctly?
   • Action: Update yield factors; retrain on portion sizes; reweigh components.
4. Spoilage / storage conditions
   • Was product past use-by or exposed to temperature abuse?
   • Action: Inspect storage logs, review temp logs, and discard appropriately; revise par if needed.
5. Theft / unexplained shrink
   • Is shrink repeated, concentrated on a shift, or one-time?
   • Action: Check CCTV, restrict access, tighten receiving/stockroom procedures, document incidents.
6. Supplier issues
   • Was the delivered item substituted or short-packed?
   • Action: Contact supplier, hold invoice until reconciled, update approved vendor list if necessary.

Escalation flow (clear roles and timeframes)

Define who acts and when. Use the flag level to set deadlines.

1. Flagged by counter — Enter count, flag auto-generated (system or manual). If Yellow, notify shift supervisor; if Red, notify manager immediately.
2. Supervisor — Recount within 24–48 hours, complete root-cause checklist, and attempt local corrections (adjust entries, retrain, reconcile receiving paperwork).
3. Manager — If unresolved after supervisor steps or if Red-level: open formal investigation, review CCTV/receiving, notify operations or regional Inventory Lead.
4. Inventory Lead / Operations — Conduct deeper audit, run historical usage and PO checks, if recurrent escalate to HR (for theft) or Purchasing (for supplier issues). Implement systemic fix (SOP change, access control, or system correction).
5. Documentation — Record findings, corrective actions, and follow-up date. Track repeat occurrences as part of shrink KPI.

Sample short notification templates

To Supervisor (Yellow): "Yellow variance on [Item]: expected X, counted Y (-Z%). Please recount and complete root-cause checklist within 48 hrs."

To Manager (Red): "Red variance on [Item]: expected X, counted Y (-Z%). Recounted? [Yes/No]. Please investigate immediately and escalate to Inventory Lead if unresolved."

Implementation tips

• Use blind counts where practical (hide expected values) to reduce bias.
• Rotate counters and pair a counter with a verifier on critical items.
• Capture context: shift, deliveries that day, specials, known waste events.
• Adjust par levels seasonally and after menu changes; document reasons for changes.
• Train staff on how to count by unit (cases, eaches, kg) and how to handle partial units.

Suggested KPIs

• Count accuracy (% within Green threshold)
• Shrink rate (cost of variance / total cost of goods)
• Time-to-resolution for Yellow/Red flags
• Repeat variances by item and by shift

How to make this interactive (recommended)

Collecting counts with an interactive form makes variance detection, audit history, and escalation faster and auditable. Consider implementing an Interactive form for the count sheet that captures: Date, Location, Count Taker, Item, Expected, Counted, Notes, and auto-calculates variance and flag. Use the platform's data submission capability to store results, trigger alerts, and build dashboards.

Quick starter checklist

• Create par list per category and assign frequency.
• Train counters and run a blind-count pilot week.
• Set variance thresholds and publish escalation contacts and timeframes.
• Start logging counts in the Interactive form (or spreadsheet) and review KPIs weekly.

Use this template as a living tool: tune thresholds, schedules, and responsibilities to fit your menu, volume, and risk tolerance. When repeated problems appear, treat them as opportunities to change an SOP rather than only to correct a single count.