Knowella

Cycle Count Record Template

A cycle count that ends in an adjustment has corrected a number and left the cause running. The count is worth doing because discrepancies point at something specific: a picking error, a receipt not booked, a location mislabelled, product moved without a transaction. Adjusting the balance closes the record and guarantees the same discrepancy next quarter.

KnowLogisticsRecordLOG-013Pinned in navigationFull guide
Purpose
Find causes, not correct balances
Measure
Location accuracy, not net value

Summary

In short

  • Count to find causes. An adjustment without a cause leaves the mechanism producing the discrepancy fully intact.
  • Measure location accuracy rather than net variance. Compensating errors cancel in the aggregate and hide the error rate entirely.
  • Count frequency should follow value, velocity and error history rather than treating all stock alike, which is the principle behind ABC classification.
  • Recount before adjusting. A large discrepancy is more often a counting error, a location error or an unposted transaction than actual missing stock.
  • Discrepancies cluster: by location, by product, by shift, by operator, by process step. The pattern is the output and it requires the counts to be recorded in a way that allows aggregation.
  • A count performed by the person responsible for the area has an incentive problem that is easy to remove and frequently is not.

What it is

What it is

What is a cycle count?

Counting a subset of inventory on a rolling basis, so that all stock is counted over a period without halting operations, rather than counting everything at once during a shutdown.

Why measure by location rather than by value?

Because compensating errors cancel. Two locations, one over by ten units and one under by ten, produce a net variance of zero and a location accuracy of zero percent. Net value is the finance measure; location accuracy is the operational one and it is far less flattering.

When to use it

When to use it, and when not to

This records a count and its outcome. Inventory management and the transactions themselves sit elsewhere.

Use it for

  • Rolling counts of inventory by location, product or classification
  • Investigating discrepancies to identify the cause rather than adjusting the balance
  • Verifying inventory accuracy for reporting and for order promising
  • Following a change in process, layout, system or staffing that could affect accuracy
  • Targeted counts where a discrepancy pattern has been identified

Not for

  • Full physical inventory, which halts operations and serves a different purpose
  • Goods receipt and despatch transactions, which this verifies
  • The inventory adjustment itself, which is an accounting entry following the investigation
  • Stock condition and shelf life checks, which examine the product rather than the quantity
  • Traceability exercises, which follow a batch rather than verify a balance

Standards

What it is built against

Inventory accuracy sits under property control and operational planning requirements.

ClauseRequirementWhere it lands
ISO 9001 cl.8.5.4Preservation of outputs during production and service provision, including identification and handlingHeader
ISO 9001 cl.8.1Operational planning and control, including determination of resources neededMethod
ISO 9001 cl.10.2Nonconformity and corrective action, including determining causes of discrepanciesOutcome
ISO 9001 cl.7.5.3Control of documented information, including inventory recordsRelated records
21 CFR 117.140Preventive control management components including monitoring, where inventory affects controlRelated records
BRCGS Issue 9 cl.3.9Traceability, which depends on accurate identification and location of stockRelated records
ISO 9001 cl.9.1Monitoring and measurement, including the accuracy measures chosenAccuracy
21 CFR 211.196Distribution records where pharmaceutical inventory control appliesRelated records

What it does not cover

  • Full physical inventory, which halts operations and serves a different purpose.
  • Receipt and despatch transactions, which this verifies.
  • The inventory adjustment, an accounting entry following investigation.
  • Stock condition and shelf life checks, examining the product rather than the quantity.
  • Traceability exercises, following a batch rather than verifying a balance.

Filling it in

Filling it in well

Recount before adjusting, record the cause, and measure the number that hurts.

Recount before you conclude

A large discrepancy is more often a counting error, a mislabelled location, product in an adjacent bay, or a transaction that has not posted than it is missing stock. Recounting first, ideally by a different person, resolves a substantial proportion of variances before anyone investigates a theft that did not happen.

Record the cause, not just the variance

Picking error, putaway to the wrong location, receipt not booked, despatch not confirmed, damage not recorded, unit of measure confusion, system timing. Use a fixed list so causes aggregate. A variance recorded as a number and adjusted teaches nothing; a variance recorded as a cause identifies a process defect.

Measure location accuracy

Each location counted is right or wrong, with no tolerance for compensating errors. This is the number that predicts whether a picker finds what the system promised, and it is considerably worse than net value accuracy in almost every operation, which is why net value is the one usually reported.

Separate counting from responsibility

Where the person counting is accountable for the area's accuracy, the incentive is obvious and it does not require dishonesty to operate. Rotating counters, or counting areas other than your own, removes it at no cost and is a straightforward design choice.

Audit findings

Common audit findings

Cycle count findings concentrate on what happens after the variance.

FindingClauseWhat fixes it
Variances adjusted without a recorded cause.ISO 9001 cl.10.2The cause is the output; adjusting the balance leaves the mechanism running.
Accuracy reported as net value rather than location accuracy.ISO 9001 cl.9.1Compensating errors cancel in aggregate; location accuracy is the operational measure.
No recount before investigation or adjustment.ISO 9001 cl.10.2Recount first; most large variances resolve without being real.
Count frequency uniform across all stock.ISO 9001 cl.8.1Follow value, velocity and error history rather than treating all stock alike.
Counting performed by the person accountable for the area.ISO 9001 cl.9.1Rotate counters; the incentive operates without requiring dishonesty.
Causes not recorded against a fixed list, so they never aggregate.ISO 9001 cl.10.2Use a controlled cause list; free text does not trend.
Discrepancy patterns by location, shift or operator not analysed.ISO 9001 cl.9.1Clustering is the finding; individual variances are noise.
Counts performed with the system view visible to the counter.ISO 9001 cl.8.1Blind counting removes the anchor that makes a counter see what they expect.
Traceability affected by location errors not treated as a food safety matter.BRCGS 3.9Stock in the wrong location undermines the trace as well as the balance.
Adjustments authorised by the same person who performed the count.ISO 9001 cl.10.2Separate the count from the authorisation to adjust.

Worked case

Case in point: ninety-nine point six percent

A distribution centre reported inventory accuracy of 99.6 percent by value and had done so consistently for two years. Picking errors and short shipments continued at a level that generated regular customer complaints, and the two facts were treated as unrelated.

Recalculating the same counts as location accuracy, with each location counted as right or wrong, produced a figure in the low eighties. The value measure was netting overages against shortages across thousands of lines, and the net was close to zero because errors in a busy operation are roughly symmetrical.

Recording causes on the next quarter's counts showed that a large share of discrepancies came from one process step: putaway to a similar-looking location code in a single aisle where the labels differed by one character.

Definitions

Definitions and key terms

Cycle count
Counting a subset of inventory on a rolling basis without halting operations.
Location accuracy
The proportion of locations counted correct, with no tolerance for compensating errors.
Net variance
Aggregate difference by value or quantity, in which overages and shortages cancel.
ABC classification
Grouping stock by value or velocity so that count frequency follows importance.
Blind count
Counting without visibility of the system quantity, removing the anchoring effect on the counter.
Compensating error
Two errors in opposite directions that cancel in aggregate while both remain wrong.
Cause code
A controlled classification of why a discrepancy occurred, which allows causes to aggregate.
Adjustment
The accounting entry correcting a balance, which should follow investigation rather than replace it.

FAQ

Frequently asked questions

Why measure location accuracy rather than value?+

Because compensating errors cancel. Two locations wrong by ten units in opposite directions produce a net variance of zero and a location accuracy of zero percent for those locations. Net value is a valid finance measure and it reports that nothing is wrong in an operation generating a steady error rate, which is why picking errors persist alongside impressive accuracy figures.

What should happen when a variance is found?+

Recount, then investigate, then adjust. Recounting resolves a substantial share of variances before anyone concludes stock is missing, because mislabelled locations, adjacent bays and unposted transactions are more common than actual loss. Then record the cause against a controlled list, because that is the output the count exists to produce.

How should count frequency be set?+

By value, velocity and error history rather than uniformly. High-value and fast-moving lines warrant more frequent counting, and so do lines or locations with a history of discrepancies. Counting everything at the same frequency spends the same effort on stock that never moves as on stock that turns weekly.

Should counters see the system quantity?+

No. A counter who knows the expected figure is anchored to it and will tend to see what they expect, particularly at speed. Blind counting produces more findings, some of which will be counting errors, and the recount step resolves those. Visible quantities produce agreement rather than accuracy.

Who should perform the count?+

Someone other than the person accountable for that area's accuracy. The incentive to record agreement operates without requiring anyone to be dishonest, and removing it costs nothing beyond rotating who counts where. The same principle applies to authorising the adjustment, which should not sit with whoever counted.

The agents

What the agents do with it

The count checks a balance. What fails is the adjustment made without a cause and the flattering measure nobody questioned.

KnowLogistics

Drives count frequency from value, velocity and error history, requires a recount before adjustment, and records causes against a controlled list.

Ella

Aggregates discrepancy causes by location, shift, product and process step, so clustering surfaces as a process finding.

KnowQuality

Connects location errors to traceability, since stock in the wrong place undermines the trace as well as the balance.

KnowMaintain

Links scanning, labelling and equipment faults to discrepancy patterns, where the cause is technical rather than behavioural.

This template lives in KnowLogisticssupply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.

Meet KnowLogistics

Sources

Sources

  • ISO 9001:2015 clauses 8.5.4, 9.1 and 10.2
  • BRCGS Food Safety Issue 9 clause 3.9, traceability
  • 21 CFR 117.140, preventive control management components, FDA
  • ISO 9001:2015 clause 7.5.3, control of documented information
  • 21 CFR 211.196, distribution records (pharmaceutical)

KnowLogistics

Also in Inventory

6Browse the whole library
Record

Stock Count Variance Investigation

Investigates why a counted quantity did not match the system quantity, before anybody adjusts it. Raised on any variance above tolerance. Completed by the inventory controller. Adjusting without investigating turns a process problem into a monthly write off.

Record

Inventory Adjustment Authorisation

Authorises a change to a system stock figure, with the reason and the evidence behind it. Raised whenever stock is written on or off. Approved above the person requesting it. Unauthorised adjustment is the most common route for stock loss to be hidden.

Inspection

Stock Location Audit

Checks that what the system says is in a location is actually in that location, and nothing else is. Run per zone on a schedule. Carried out by the inventory controller. Location accuracy fails long before quantity accuracy does.

Record

Damaged Stock Record

Records stock damaged in storage or handling, how it happened and what was done with it. Raised when damage is found. Completed by the area owner. Damage written off without a cause is damage that repeats in the same aisle.

Checklist

Expiry and Rotation Check

Checks that stock is being rotated correctly and that nothing is approaching or past its date. Run per zone on a schedule. Carried out by the area owner. Rotation failures show up as customer complaints weeks after the mistake.

Record

Consignment Stock Reconciliation

Reconciles stock held on site but owned by somebody else, or held elsewhere but owned by you. Run monthly per arrangement. Completed by the inventory controller. Consignment is where two sets of books disagree quietly for a year.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.