Cycle Count Plan & Count Sheet

A practical, ready-to-use cycle-count plan plus a printable count sheet template, step-by-step procedures, frequency matrix by SKU value and turnover, hold/recount rules, variance investigation flow, and reconciliation entries. Designed for short counts on high-velocity SKUs and deeper counts for high-value or high-variance items.

Why cycle counts matter

Full physical inventories are disruptive and rare; cycle counting keeps on-hand records reliable with smaller, repeatable routines. Accurate inventory makes ordering, costing, and food-cost decisions trustworthy and reduces shrink, stockouts, and hidden food-cost creep.

Quick orientation

This template includes: a frequency matrix to decide how often to count each SKU, a recommended cadence, clear step-by-step counting instructions, hold/recount rules, a variance investigation workflow, and reconciliation entry examples. Use the count-sheet table as a printable worksheet or as a model when creating an interactive count form in your systems.

Core principles

  • Count frequently enough that small errors are caught before they compound.
  • Prioritize by value and turnover: high-value and high-variance SKUs need deeper attention.
  • Use short, rapid counts for high-velocity, low-value items to minimize disruption.
  • Always record a clear variance reason and ownership for adjustments.

Frequency matrix (example)

Use SKU annual usage value (unit cost × annual usage) and turnover rate to set count frequency. Tweak thresholds to your business.

CategoryExample criteriaSuggested cadence
Tier A — High value / low turnoverTop 10–15% by inventory valueMonthly or bi-weekly deep count
Tier B — Moderate value / moderate turnoverNext 20–30% by valueMonthly short/deeper hybrid
Tier C — Low value / high turnoverFast-moving perishables, condimentsWeekly short counts
Tier D — Low value / low turnoverOccasional-use items, small equipmentQuarterly or semi-annual

Recommended cadence (sample schedule)

Design weekly and monthly counting cycles so that each SKU is counted at its target frequency across a rolling schedule. Example:

  • Weekly: All Tier C items (short count)
  • Bi-weekly: Rotating subset of Tier B
  • Monthly: All Tier A and remaining Tier B (deeper counts)
  • Quarterly: Tier D and spot-checks

Stepwise count instructions

  1. Prepare — Print sheet or open digital form; confirm count schedule and assigned counters; close receiving window for the area being counted to prevent live changes.
  2. Segregate — For the duration of the count, isolate the shelf/pallet/bin being counted; tag it "COUNT IN PROGRESS" where practical.
  3. Record system quantity — Note the expected system on-hand (from POS/inventory system) before physically counting.
  4. Count — Use consistent unit-of-measure rules (each, case, lb). Enter counted quantity and initials of counter.
  5. Calculate variance — Variance units = Counted - System. Variance $ = Variance units × unit cost.
  6. Apply hold/recount if threshold exceeded — If variance exceeds threshold (see rules), place item on hold and perform recount or escalation.
  7. Document reason — Choose from standardized categories (see list below). Record observations (damage, theft suspicion, mislabeling, receiving error, scale calibration, portioning variance).
  8. Reconcile — Enter approved adjustments following authorization rules (who can approve adjustments of various sizes).
  9. Log & follow-up — Create an investigation ticket for persistent or high-dollar variances and assign ownership.

Standardized variance reason categories (examples)

  • Receiving error
  • Sales/ring/void not recorded
  • Portioning/waste
  • Damage or spoilage
  • Mislabeling or wrong location
  • Theft or loss
  • Scale or measurement error

Hold / recount rules

Establish clear, simple rules so counters know when to stop and escalate.

  • Auto-recount: If variance units > X or variance $ > $Y, perform an immediate second count by a different counter.
  • Supervisor hold: If second count differs from first by more than tolerance or variance $ > $Z, tag item HOLD and notify supervisor for investigation.
  • Do not adjust system quantities until the hold/recount process is complete and an authorized approver signs off.

Variance investigation workflow (simple)

  1. Identify recurring variances—track by SKU and location.
  2. Check recent receiving records and invoices for matching receipts.
  3. Review sales/void logs and portioning records for similar time frames.
  4. Inspect storage area for misplaced stock, spoilage, or vendor substitution.
  5. If theft or systematic loss suspected, escalate to manager with evidence and CCTV review where available.
  6. Document root cause, corrective action, and a date for follow-up recheck.

Reconciliation entries and authorization (example)

When approved, adjustments should be recorded with clear metadata: who approved, reason category, date, and dollar impact. Example reconciliation entry fields:

  • SKU, Location
  • System Qty before adjustment
  • Counted Qty
  • Variance units
  • Unit cost and variance $
  • Reason code and short note
  • Counter initials, Reviewer initials, Approver initials

Printable Count Sheet (template)

Use this table as a physical worksheet or convert to a digital form. Repeat rows per SKU.

SKU Description Unit Location Par System Qty Counted Qty Unit Cost Variance Units Variance $ Reason Code Counter Initials
(row 1)
(row 2)
(add more rows or duplicate)

Short counts vs deeper counts

Short counts: designed for speed—used on fast-moving, low-value SKUs. Capture on-hand in a bin or shelf but do not unpack every case unless variance suggests otherwise. Deeper counts: open cases, weigh or measure when units are sold by weight, check lot numbers, and verify labels for high-value or high-variance items.

Common mistakes & tips

  • Not freezing activity in the counted area causes mismatches—coordinate with front-of-house and receiving.
  • Inconsistent UOM rules—record whether counts are in each, case, or weight and convert consistently.
  • Missing reason codes—without reasons, variances can’t be fixed.
  • Too many ad-hoc adjustments—require approvals tied to dollar thresholds.

How to tailor this template

Adjust thresholds, cadence, and role authorizations to match your menu, perishability, and risk tolerance. Keep the count process simple at first; automate and add detail as the team becomes disciplined.

Next steps & improvement ideas

1) Trial the frequency matrix for 30–60 days and track variance trends. 2) Create a weekly log of repeat variances and assign corrective owners. 3) Convert the printable template into a digital, repeatable form so counts are saved with timestamps and user info.

Suggested form fields for a digital implementation

SKU, Description, Unit, Location, SystemQty, CountedQty, UnitCost, VarianceUnits, VarianceDollar, ReasonCode, CounterID, ReviewerID, ApproverID, Notes, Timestamp.

Related governance

Document who can approve adjustments by dollar band (for example: counters can propose; supervisors approve up to $100; managers approve up to $500; finance approval for larger). Keep an audit log of all adjustments.

Image suggestion: employee doing inventory count in restaurant storage


Discussion

Comments and conversation will live here.