Cycle Counting

What is Cycle Counting?

Cycle counting is an approach to inventory auditing where instead of verifying all assets at once, you check a small portion every day (or week, or month). Over a full cycle — typically a quarter or a year — every asset gets verified at least once.

Think of the difference this way: a full physical inventory is like a massive spring cleaning once a year (painful, time-consuming, and everyone dreads it). Cycle counting is like tidying up for 15 minutes each day (barely noticeable, easy to stick with, and the place is always in order).

Most companies that switch to cycle counting wonder why they didn't do it sooner. Less stress, higher accuracy, and no more "closed for inventory" signs on the door.

How Cycle Counting Works

The Basic Mechanism

1. Divide — All your assets or inventory are split into groups. The grouping criteria depend on the method you choose (by value, location, category, or randomly).
2. Schedule — Each group is assigned a counting date or period. High-value assets get counted more frequently, lower-value ones less often.
3. Count — On the assigned day, the responsible team member walks through and recounts or scans their group of assets.
4. Compare — The count result is compared against the system records.
5. Resolve — Discrepancies are investigated and resolved the same day or within the next few days.
6. Repeat — The next group is up the following day.

Example Schedule

For a company with 1,000 assets:

• A-items (200 items, high value): counted every month → ~10 items per day
• B-items (300 items, medium value): counted every quarter → ~5 items per day
• C-items (500 items, low value): counted once a year → ~2 items per day

Total: ~17 items per day. One person with a mobile scanner can verify 17 assets in about 30–45 minutes.

Types of Cycle Counting

ABC Analysis Method

Based on the Pareto principle (80/20). Assets are classified by value:

Best for: Organizations where value concentration is high — a few expensive items account for most of the portfolio value.

Random Sampling

Each cycle uses a random selection of assets. The system or a manager randomly picks N assets for verification.

Best for: Situations where all items have similar value, or when you want an unbiased statistical sample of overall accuracy.

Location-Based Counting

All assets at one specific location are verified in a single cycle. The next cycle covers a different location.

Best for: Multi-site organizations (multiple offices, warehouses, buildings). Logistically simpler — one person goes to a single site and checks everything there.

Control Group Method

The same group of assets is counted repeatedly until the process is fully dialed in. This is used when rolling out a new system or when data accuracy is very low.

Best for: New implementations — calibrating your counting process before scaling it.

Cycle Counting vs. Full Physical Inventory

Formula: Counting Frequency

Items per Day = Total Items in Category / (Days in Cycle × Working Days per Week / 7)

Example: 300 B-items need quarterly counting.

• 300 items / (90 days × 5/7) ≈ 300 / 64 ≈ 5 items per day

Real-World Example

A healthcare supply chain managed 4,200 items across a hospital and 3 clinics. Their annual full physical inventory:

• Required 12 staff members for 3 days
• Cost approximately $28,000 (labor + overtime + productivity loss)
• Disrupted clinical operations (some departments had limited access to supplies during the count)
• Achieved 94% accuracy on count day — but by month 6, estimated accuracy had dropped to ~82%

Switch to cycle counting:

• 1 supply chain technician spends 45 minutes per day counting 15–20 items
• High-value items (medications, surgical supplies): counted monthly
• Medium-value items: counted quarterly
• Low-value items (office supplies, cleaning products): counted semi-annually
• Annual cost: approximately $8,000 (salary portion dedicated to counting)

Results after first year:

• Average accuracy: 97.3% (maintained throughout the year, not just on one day)
• Discrepancies caught within 1–3 days instead of months
• Zero operational disruptions for counting
• 71% reduction in counting costs
• Stockout incidents for critical supplies: down 40%

Key Metrics

• Count accuracy rate — Percentage of counted items matching system records. Target: 97%+.
• Counts per day/week — Track that you're hitting your target count volume.
• Days to resolve discrepancies — How fast you investigate and fix mismatches. Target: < 3 days.
• Accuracy trend — Is your overall accuracy improving, stable, or declining month over month?
• Coverage rate — What percentage of your total inventory has been counted in the current cycle?

Common Mistakes

1. Setting too ambitious a schedule. If your team can't realistically count 20 items/day every day, they'll skip days, fall behind, and the program collapses. Start conservatively.
2. Not investigating discrepancies. Counting is only valuable if you act on the results. Finding 5 mismatches and just adjusting the numbers without understanding why is a waste of time.
3. Counting the same easy items. If counters get to choose what they check, they'll count what's convenient — not what's important. Use system-generated lists.
4. Ignoring C-items entirely. Low-value items still matter. If your C-items are never counted, you have no idea if hundreds of them are missing.
5. Not tracking metrics. Without data on accuracy rates and trends, you can't tell if the program is working or just creating busywork.

Best Practices

1. Automate the counting schedule. Let your system generate daily/weekly count lists based on your classification rules. Remove human decision-making from "what to count today."
2. Count at consistent times. Before operations start, during lunch, or at end of day — pick a time and stick to it. Consistency builds habit.
3. Use scanning, not manual entry. Every scan is a data point. Every manual entry is an error waiting to happen.
4. Review and adjust classifications quarterly. Items change in value and criticality. What was a C-item last year might be A-item this year.
5. Celebrate improving accuracy. When your team's accuracy improves from 89% to 96%, acknowledge it. Cycle counting is only sustainable if people see the value.

Related Terms

• Asset Audit — The broader process of verifying assets, of which cycle counting is one method
• Asset Reconciliation — Resolving the discrepancies found during cycle counts
• Inventory Management — The overarching discipline that cycle counting supports
• Reorder Point — Accurate counts ensure reorder points trigger at the right time
• Safety Stock — Buffer stock calculations depend on accurate inventory counts

Conclusion

Cycle counting is one of those ideas that sounds too simple to be powerful — but it is. Counting a small number of items every day, consistently, keeps your records accurate all year long. It replaces the stress, cost, and disruption of annual full inventories with a quiet daily habit that makes everything else in your supply chain work better.

Cycle Counting with UNIO24

UNIO24 supports cycle counting workflows with scheduled count tasks, mobile QR code scanning, and automatic discrepancy detection. Create counting schedules by category or location, assign tasks to team members, and track completion in real time. When a scan doesn't match the expected record, the system flags it immediately. Over time, your accuracy dashboard shows the trend — proving to management and auditors that your data is reliable.