What this is
What is a stock count record?
What is a stock count record?
It is the reconciliation between what the spare parts register says a store holds and what a physical count actually finds. Each line captures system quantity, physical quantity, the resulting variance, and — where variance exists — a stated reason, so the count produces an explanation, not just a number.
What is the difference between a cycle count and a full physical count?
A full physical count checks every part on the register in one exercise, while a cycle count works through a rotating subset on a schedule so that, over the year, everything is counted without stopping the store for a single large exercise. A spot check is a targeted, unscheduled count of specific lines.
Why does the count need a stated reason for variance, not just the size of it?
A five percent shortfall caused by miscounting is a training issue. A five percent shortfall caused by parts issued without recording, or suspected theft, is a control failure that needs a different owner and a different response. Recording the variance without the reason erases that distinction.
Scope
When is a stock count record required?
This record is the reconciliation exercise itself. Using it to hold the master list of what should be in stock, or to judge whether critical spares cover is adequate, produces the wrong kind of record and breaks the count-to-register comparison it depends on.
Use this template when
- A scheduled cycle count, full physical count or spot check is due or under way
- Stores needs to reconcile physical stock against the spare parts register for one or more lines
- A pattern of variance needs a formal record before it is escalated as a control issue
- A new count is needed; each one gets its own ID in the form STK-2026-000
- A linked record needs this one to exist: links parts
Do not use it for
- Spare Parts Register, which is the master list of parts, locations and minimum levels this record is reconciled against, not a count in itself.
- Critical Spares Review, which judges whether the right critical spares are held for the assets that matter most, not whether the current count matches the register.
- Parts Issue and Return Record, which captures a single transaction moving stock, one of the possible causes a count variance traces back to.
- Storeroom Condition Inspection, which checks the physical state of the store itself rather than reconciling quantities.
- Anything outside KnowMaintain, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 55001 cl.8.1 requirements does this satisfy?
ISO 55001 cl.8.1 requires organisations to keep documented information with confidence that the processes an asset management system depends on have been carried out as planned, and to control the consequences of unintended change. A stock count is the mechanism that tests whether the spare parts register still reflects reality.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 55001 cl.8.1 | Verify, through a planned process, that documented stock information still reflects actual conditions | Header |
| ISO 55001 cl.8.1 | Record the outcome of the verification process at line level, not only in aggregate | Count results |
| ISO 55001 cl.8.1 | Review the consequences of unintended change, such as parts moved, issued or degraded without being recorded | Count results |
| ISO 55001 cl.8.1 | Control planned changes made to correct the register following the count | Result |
| ISO 55001 cl.8.1 | Maintain traceability between the count and the register entry it reconciles against | Related records |
| ISO 55001 cl.8.1 | Establish the schedule and criteria for when counts recur | Result |
What it does not cover
- Within Tolerance, which distinguishes a variance small enough to be normal counting noise from one that needs a stated reason.
- Variance Reason, which is what turns a number into an explanation stores and maintenance can actually act on.
- Uncontrolled Issue Suspected, which is the line that separates a training gap from a control failure needing a different owner.
- System Adjusted, which should follow an accepted reason, not substitute for one.
- Within Shelf Life, which catches expired stock a pure quantity reconciliation would otherwise wave through as correct.
Global
Stock Count Record requirements by country
ISO 55001 is voluntary everywhere, but a repeated, unexplained negative variance in a stock count carries weight beyond the standard itself, particularly where the missing stock could indicate theft or where the parts in question are food-contact items.
ISO 55001 cl.8.1
Voluntary, certifiable requirement to verify documented information against reality
A certification body reviewing the asset management system will expect count records to show a real reconciliation process, not a single closing figure.
Theft Act 1968, s.1
Defines dishonest appropriation of property belonging to another
A stock count record showing a consistent, unexplained negative variance with Uncontrolled Issue Suspected answered Yes is the documentary trail that turns a suspicion into a reportable matter.
21 CFR 117 (Current Good Manufacturing Practice, Preventive Controls for Human Food)
Requires maintenance and sanitation records to be verifiable
Where counted parts include food-contact spares, Within Shelf Life and Condition Acceptable feed directly into whether the plant can demonstrate its preventive controls were actually followed.
How to complete it
How to complete a stock count record, step by step
The count itself is arithmetic. The judgement calls below decide whether the finished record actually distinguishes a control failure from ordinary counting noise.
A small variance repeated on the same part across consecutive counts is a different problem to a one-off small variance, even though each individual line might tick Within Tolerance. The record needs someone comparing across counts, not just within one.
Answering No by default because nothing obviously points to theft understates the field's purpose. It should be answered Possibly whenever the variance reason itself is uncertain, not reserved for cases with direct evidence.
Adjusting the register the moment a physical count disagrees with it, before the reason is confirmed, destroys the evidence a repeat pattern would need. System Adjusted should lag behind an accepted Variance Reason, not run ahead of it.
A part can be present, in the right location, and still be unacceptable — corroded, past its shelf life, or stored somewhere unsuitable. Condition Acceptable is a separate judgement from Within Tolerance and needs treating as one.
What auditors find
Most common stock count record findings
These are the patterns that recur once stock count records are compared across cycles rather than read one at a time.
| Finding | Clause | What fixes it |
|---|---|---|
| Variance corrected in the system before a reason was recorded | ISO 55001 cl.8.1 | Sequence the workflow so System Adjusted cannot be set to Yes until Variance Reason is populated for the line. |
| Repeated small negative variances on the same part treated as routine each time | ISO 55001 cl.8.1 | Compare Variance Reason across the last three counts for a part before accepting Within Tolerance as the final answer. |
| Uncontrolled Issue Suspected left at No by default rather than assessed | ISO 55001 cl.8.1 | Require an explicit justification whenever a negative variance has no confirmed cause, rather than allowing No as the unexamined default. |
| Shelf-life-limited parts counted for quantity only, with condition unchecked | ISO 55001 cl.8.1 | Make Within Shelf Life and Condition Acceptable mandatory whenever a counted part is flagged shelf-life limited on the register. |
| Accuracy Percent reported without the line-level detail behind it | ISO 55001 cl.8.1 | Retain and surface the individual line variances alongside the summary figure, not just the aggregate percentage. |
| Action Required left at No despite a high main cause of variance being issued without recording | ISO 55001 cl.8.1 | Force Action Required to Yes automatically whenever Main Cause Of Variance is issued without recording or theft suspected. |
Case in point
Case in point: the count that closed too fast
A cycle count on fasteners and seals found six lines short against the register, all in the same aisle, all with a similar small negative variance. Each line individually sat close to the tolerance boundary, so stores marked each one Within Tolerance, recorded Miscount as the reason without much thought, and adjusted the system to match the physical count.
The next quarter's count found the same pattern, worse. Only then did anyone look at the six lines together rather than one at a time, and the shared aisle pointed to a specific issue path that had been bypassing the parts request process. The fix was not a new field on the form — it was reading Variance Reason across counts instead of within a single one.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- MNT-065
- Archetype
- Record
- Record ID
- STK-2026-000
- Scoring
- Accuracy percent
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 55001 cl.8.1
- Links
- Links Parts
- Tags
- Parts, Control
- Sections
- 4
- Fields
- 40
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 3
Header
11 fieldsCount ID*
Auto sequence. Format STK-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Count Type*
Full physical count, cycle count or spot check.
Area Counted*
Counted By*
Count results
Repeats10 fieldsPart Number*
System Quantity*
Physical Quantity*
Variance
Variance Percent
Within Tolerance*
- Yes3 pts
- Marginal1 pt
- No0 pts
In Correct Location*
- Yes3 pts
- No0 pts
Condition Acceptable*
- Yes3 pts
- Marginal1 pt
- No0 pts
Within Shelf Life
- Yes3 pts
- Expired0 pts
Variance Reason
Issued without recording, miscount, wrong location, damage, or theft.
- Issued without recording0 pts
- Miscount1 pt
- Wrong location1 pt
- Damage1 pt
- Theft suspected0 pts
Related records
1 fieldSpare Part ID
A part reconciled in this count.
Links to MNT-064 Register ID
Result
18 fieldsLines Counted*
Lines With Variance*
Accuracy Percent*
Value Of Positive Variance
Value Of Negative Variance
Net Adjustment Value
Main Cause Of Variance*
- None significant3 pts
- Issued without recording0 pts
- Miscount1 pt
- Wrong location1 pt
- Damage1 pt
- Theft suspected0 pts
Uncontrolled Issue Suspected*
Large negative variances usually mean parts are being taken without being booked out.
- No3 pts
- Possibly1 pt
- Yes0 pts
System Adjusted*
- Yes3 pts
- No0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Next Count Due*
Stores*
Signature*
Maintenance Manager*
Second Signature*
MNT-065 · record IDs look like STK-2026-000 · Links Parts
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The count itself is a few hours with a clipboard. Spotting the pattern across counts, and making sure a variance reason exists before the register gets adjusted, is the part that actually protects stock integrity.
Holds the stock count record against the spare parts register it reconciles, and keeps the two in step so a count actually corrects the record it is measured against.
Tracks recurring variance by supplier and part, surfacing whether a pattern traces back to receipt errors upstream rather than issue discipline in the store.
Picks up any CAPA raised from an unexplained variance or a suspected uncontrolled issue and keeps it linked back to the count line that triggered it.
Compares variance reasons across counts for the same part, flags a repeating pattern before it reaches a third cycle, and holds every write for your approval before it touches a record.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Stock Count Record definitions and key terms
- Cycle count
- A count of a rotating subset of stock on a fixed schedule, so the whole store is verified across a year without one disruptive full count.
- Variance
- The difference between what the register states as system quantity and what the physical count actually finds.
- Accuracy percent
- The proportion of counted lines that matched the register within tolerance, used as the headline measure of how trustworthy the register currently is.
- Uncontrolled issue
- Stock leaving the store without being recorded against a work order or parts request, the usual explanation for a persistent unexplained shortfall.
- Tolerance
- The pre-agreed margin within which a variance is treated as normal counting noise rather than something needing a stated cause.
FAQ
Frequently asked questions about stock count record
What is the stock count record template based on?+
It is built against ISO 55001 cl.8.1, the asset-management clause requiring documented information to be verified against actual conditions and unintended change to be reviewed.
What sections does the stock count record contain?+
There are four sections: header, count results, related records and result. Together they hold 40 fields, 27 of which are required.
How often is a stock count record raised?+
It runs quarterly or against a cycle count schedule, at the moment the physical count happens rather than reconstructed from memory afterwards. Each one is given an ID in the form STK-2026-000.
Which programme does the stock count record belong to?+
It sits inside Planned Maintenance, where planned work is completed on time and backlog age stays visible rather than being aggregated away.
How is a stock count record scored?+
Scoring is Accuracy Percent, where high is good. It reflects the proportion of lines that reconciled within tolerance, not just whether a count was completed.
Can the stock count record template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Planned Maintenance
Asset Register
Holds every piece of equipment, machine, vehicle and tool you track
Tool and Equipment Register
Holds portable tools, gauges, lifting accessories and small equipment that sit below asset level but still need control
Maintenance Request
Asks maintenance to look at a problem or carry out a job
Work Order
The main record for a planned maintenance job, covering what, where, who and when
Corrective Work Order
Covers a repair to fix something that has already failed or degraded
Emergency Work Order
Covers urgent work where equipment has stopped or become unsafe
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 55001 cl.8.1 — Operational planning and control
- ISO — International Organization for Standardization
- Theft Act 1968, s.1 (England and Wales)
- 21 CFR 117 — Current Good Manufacturing Practice, Preventive Controls for Human Food
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.