Checklist

Cycle Count Routine & Exception Handling

A practical, repeatable cycle-count checklist with clear rules for scheduling, action thresholds, investigation templates (invoice vs physical vs POS consumption), corrective actions, and reporting cadence. Designed for regular use per item or per category and to capture structured investigation data for recurring issues.

Interactive Tool

Cycle Count Routine & Exception Handling

Purpose

Keep inventory accuracy high without running full physical inventories. Use this checklist each time you perform a cycle count for an item or small group of items. Capture counts, log variances, decide whether an investigation is required, and record corrective actions so problems get fixed and tracked.

Scope & When to Use

Use for daily, weekly, or monthly cycle counts by category (high-turn, high-cost, perishable). For bulk or batch counts use repeated submissions or upload a batch spreadsheet (see Capability Notes).

Roles

Counter: completes physical count. Verifier/Manager: reviews counts above thresholds and closes investigations. Inventory Owner: implements corrective actions.

Quick Guidance on Thresholds

As a starting rule, consider an investigation when any of the following occur: variance > 2% for high-turn items, variance > 5% for low-turn items, or absolute variance > 5 units for items normally stocked in small quantities. Adjust thresholds to your business and record them as part of local policy.

YYYY-MM-DD HH:MM. Use current date/time when possible.
e.g., Walk-in fridge A, Dry Storage - Shelf 3. Required.
Person who performed the physical count.
Choose the category that best reflects this item for scheduling and reporting.
Use the item name or SKU exactly as in your inventory/POS system.
e.g., each, lb, kg, case. Helps interpret thresholds.
Quantity shown in inventory/POS before this count. Enter 0 if not available.
Enter the physical count you observed.
Leave blank to let manager calculate. Prefer entering absolute difference (system - physical).
Record percent variance if you calculate it (e.g., 3%). Not required but helpful for trends.
Compare to local thresholds (see intro). If unsure, answer yes and manager will review.
Select 'Yes' when varianceThresholdExceeded is yes, when system anomalies exist, or when recurring variances are suspected.
Use these checks to structure the investigation: compare invoices, review POS consumption, re-count, check receiving records, check transfers, review waste logs.
Summarize what you found, attach reference numbers, invoice IDs, POS report snippets, or recount results.
Choose an action to resolve the root cause. If multiple actions required, summarize in notes.
Person responsible for implementing or closing the corrective action.
YYYY-MM-DD. Required if investigationRequired = yes and correctiveAction != no_action_needed.
How often should aggregated variance reports include this item?
IDs or filenames of supporting docs (invoices, photos, POS extracts), if stored elsewhere.
Final verification by the counter or verifier.
Manager confirms investigation complete and corrective actions logged.
Manager's comments, acceptance of action, or escalation instructions.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.