Inventory Cycle Count Schedule & Count Sheet

Purpose

Make inventory reliable without full monthly shutdowns. This toolbox gives you a velocity-based cycle count rhythm, a printable count sheet layout you can copy, counting rules, a reconciliation workflow with approval steps, common variance causes, corrective action categories, and practical steps to run counts during shifts with minimal disruption. Use it as-is or adapt it to your menu, POS, and stockroom layout. If you want to go digital, a recommended interactive form structure is included so your counts can be stored and tracked on the platform.

Why a velocity-based cycle count?

Counting items more often when they move quickly catches shrinkage and data errors before they distort ordering and food-cost decisions. Focusing effort where it matters reduces time spent on low-value counts while keeping accuracy high.

Suggested schedule by SKU velocity

• Fast movers (top ~10–20% SKUs by usage or dollar value): daily or every shift during low-volume windows.
• Medium movers (next ~20–30%): weekly.
• Slow movers (remaining SKUs): monthly or quarterly depending on spoilage risk and cost.

Tailor frequency by cost, perishability, theft risk, and supplier lead time. High-cost slow movers may still warrant weekly checks.

Count group examples (pick one mapping method)

1. By SKU velocity (recommended)
2. By storage location (fridge 1, freezer, dry store)
3. By recipe grouping (proteins, dairy, produce)

Printable count sheet (copy this table for each session)

Use a sheet per location or per counter. Add your logo/headers when printing.

Counting rules (standardize to reduce variance)

• Use the same unit of measure everyone knows (lb, each, case). Convert and note if needed.
• Count what's physically in the storage location (exclude items on hold or in transit unless instructed).
• When possible, use blind counts (system quantity hidden) to avoid bias.
• Record partial units consistently (round or use decimals per your system). Document the chosen rule on the sheet.
• If you can't access an item, label it and schedule a recount; do not estimate.

Cycle count procedure (step-by-step)

1. Prepare: print sheets for the session, bring pens, scales, calculators, and cold-storage PPE.
2. Assign zones and counters. Avoid duplicate counting by clear boundaries.
3. Perform counts using the counting rules above. Mark questionable items with a tag.
4. Record counts immediately and initial the sheet.
5. Submit sheets to the inventory lead for reconciliation within 24 hours.

Reconciliation workflow

1. Inventory lead aggregates counts into a reconciliation report (compare counted vs. system).
2. Apply a quick-check rule: for small variances (example guideline: within ±2% by quantity or <$25 value) flag as reviewed; for larger variances proceed to step 3. (Adjust thresholds to your business.)
3. For large or unexplained variances: recount the item (preferably by a different counter), verify receiving logs and portioning records, and check waste and prep logs.
4. Investigate causes (see common causes below). Document findings in the Notes/Action column and attach supporting evidence (receiving ticket, waste ticket, sales report snippet).
5. If variance is confirmed, create an approved adjustment in the system. Require manager approval for adjustments above your established dollar or percentage threshold.
6. Record corrective actions and assign an owner and due date (e.g., retrain staff, fix par levels, update recipes).
7. Track repeat variances and escalate recurring issues to operations leadership for process change.

Common variance causes

• Receiving errors (wrong quantity entered, cases vs. units)
• Incorrect or inconsistent units of measure
• Unrecorded waste, spills, or plate waste
• Recipe or portioning changes not reflected in system usage
• Unposted transfers between locations or prep areas
• Theft or misplacement
• Data entry errors in POS or inventory system
• Spoilage and unnoticed short-dated product

Corrective action categories (how to respond)

• Quick fixes: adjust a wrong UOM, correct a data-entry typo, post recent receiving.
• Operational changes: change par levels, improve labeling, reorganize storage locations.
• Training: retrain counters, receiving clerks, or cooks on portioning and documentation.
• Systems: update recipes, enable barcode scanning, integrate POS-to-inventory mappings.
• Security: limit access, install cameras, tighten receiving controls.

Counting during shifts with minimal disruption

• Schedule counts during natural lulls (pre-open, after midday rush, or post-close) and communicate windows in advance.
• Use short focused sessions (15–30 minutes) on high-value fast movers rather than long full-stockroom counts.
• Tag counted areas to prevent double-handling by other staff.
• For front-of-house items (condiments, disposables), pair counts with shift change duties.
• When counting in active prep areas, use a 'tag & hold' approach: tag items to be counted, continue service, then count tagged items in a quiet moment.

Implementation checklist

1. Map SKUs to velocity buckets using the last 4–8 weeks of usage.
2. Create count sheets for each zone and schedule them on a shared calendar.
3. Decide variance thresholds for auto-review vs. escalation.
4. Assign roles: counters, inventory lead, reconcilers, approvers.
5. Run a pilot for 2–4 weeks, track time spent vs. variance reduction, and adjust frequencies and rules.

Quick-start pilot (practical plan with metrics)

1. Week 0 — Setup (1–2 days): Map 50–100 SKUs into velocity buckets, create printed sheets, schedule sessions, assign roles.
2. Weeks 1–2 — Pilot (2 weeks): Run daily fast-mover counts and one weekly medium-mover session. Log time per session and record variances and corrective actions.
3. End of Pilot — Measure: look at average variance by SKU, number of adjustments, time per count, and % of variances requiring escalation. Target outcomes: reduce unexplained variance for fast movers by 50% and keep average time per fast-mover session under 30 minutes.
4. Adjust schedule and thresholds based on results and roll out to remaining SKUs over the next 4–8 weeks.

How to choose variance thresholds

Thresholds should balance effort versus business impact. Use combination rules that consider quantity, dollar value, and SKU importance. Example starting thresholds:

• Auto-review: variance <= ±2% by quantity or < $25 value
• Recount & investigate: variance between ±2% and ±10% or $25–$150 value
• Immediate escalation for single-SKU variance > ±10% or > $150 value

Adjust these based on your average order sizes and margins. Record your chosen thresholds in the implementation checklist so everyone follows the same rules.

Common mistakes to avoid

• Estimating instead of tagging and recounting inaccessible items.
• Not standardizing units of measure across receiving, recipes, and inventory.
• Making system adjustments without documented approvals and supporting evidence.
• Running counts inconsistently (same items must be counted to build trend data).

Tailor these recommendations

Every operation is different. Use the schedule and thresholds as starting points, then refine using real data. High-cost or high-theft items may need higher frequency or special controls regardless of velocity.

Next-step options (capability and tooling opportunities)

This template is ready to print and attach to counts. To modernize counting and capture data automatically, consider these platform-enabled steps:

• Build an interactive digital count form that stores submissions (so you can track history and trends) — this uses the platform's Interactive Form Rendering and Data Submission capabilities.
• Integrate count submissions with your POS/inventory system to auto-reconcile and reduce manual adjustments.
• Add scheduled reminders and dashboards that show variance trends by SKU and location, and surface repeat offenders for targeted improvement.

Recommended simple interactive form design (fields to implement)

Below is a concise, implementation-ready field list you can use to create an InteractiveForm on the platform. Keep field keys stable and use SchemaVersion when you implement.

When you create the InteractiveForm, set DataType to something like "inventoryCycleCount.v1" and use a stable SchemaVersion such as 1. Use the platform's submission API so entries are stored in hunContentItemData and available for dashboards and trend reports.

Capability Enhancement Notes

The platform already supports interactive forms and JSON storage (Interactive Form Rendering and Content Data Submission). Implementing the recommended form would let you:

• Collect count rows as structured submissions tied to ContentItemID so history is preserved and searchable.
• Compute variance and variance value automatically on submit or in a lightweight post-process to reduce human error.
• Build dashboards showing variance trends, repeat-offender SKUs, and time-per-count metrics to guide continuous improvement.
• Package this toolbox as an Adaptive Ownable Toolkit so teams can copy, tailor thresholds, and run local pilots while preserving the shared structure for enterprise governance.

Suggested platform capabilities to enable these improvements: Interactive Form Rendering (to present the form), Content Data Submission and JSON Storage (to save structured submissions), and Adaptive Ownable Domains (to package and distribute a reusable toolkit).

Implementation tips for the platform

• Start by creating the InteractiveForm with the fields above and a short pilot group of counters.
• Use hidden systemQty for blind counts, or present it when you want open counts.
• Map SKU codes to unit cost so varianceValue can be auto-calculated on submit.
• Use scheduled reminders and a shared calendar entry to trigger count sessions for each zone.
• Collect attachments or reference IDs (receiving ticket numbers, waste ticket IDs) in the notes field so reconciliations keep evidence together.

Next steps summary

1. Decide whether you will pilot on paper or implement the InteractiveForm immediately.
2. If digital: create the InteractiveForm using the field list above and enable submissions for this content item.
3. Run the 2–4 week pilot, measure the metrics listed, and refine thresholds and frequencies.
4. Roll out more SKUs and add dashboards to surface trends and repeat problems.

Use this toolbox as a living resource. Keep records of changes (par updates, threshold changes, training outcomes) so your inventory process improves predictably over time.