What this is
What is a parts issue and return record?
What is a parts issue and return record?
It's the transaction record for parts moving out of the storeroom against a job, or unused parts coming back in. It captures what was taken, whether it was booked at the time, whether the bin location and stock level are correct, and — separately — whether anything returned was inspected before it went back on the shelf as available stock.
How is this different from the Spare Parts Register?
The Spare Parts Register (MNT-064) is the master list of what a site stocks, at what reorder point, for which assets. This record is the transaction log against that master list — every issue, return, transfer or adjustment that changes what's actually on the shelf versus what the register says should be there.
Why does it score bookings, not just correctness of the count?
Because a correct stock count that took three days to reconcile after an unbooked issue isn't the same outcome as a count that matched because every transaction was logged when it happened. The score is on discipline at the point of transaction, which is the only point where an unbooked issue can actually be caught.
Scope
When is a parts issue and return record required?
This record covers the movement of parts against a specific transaction. Using it for work that belongs to a neighbouring storeroom record leaves either the register or the condition trail with a gap.
Use this template when
- A part is being issued against a job, returned unused, transferred, or adjusted in the count
- The transaction happens at a specific moment and needs to be booked at that moment, not reconstructed later
- A returned part needs an inspection decision before it goes back into available stock
- The outcome needs to flag a below-reorder-point or critical spare condition as it happens
- A linked record needs this one to exist: links spare parts register, stock count
Do not use it for
- Parts Receipt Inspection, which inspects incoming spare parts from a supplier for part number, damage and certification, before they ever reach the shelf.
- Storeroom Condition Inspection, which checks storage conditions, segregation and shelf life across the whole store, not a single transaction.
- Stock Count Record, which reconciles the physical count against the register periodically — this record is what a bad count is usually tracing back to.
- Spare Parts Register, which is the master list of what should be stocked, not the log of what actually moved.
- Obsolescence Review, which looks at whether a part can still be sourced at all, not whether a specific issue was booked correctly.
Compliance mapping
Which ISO 55001 cl.8.1 requirements does this satisfy?
ISO 55001 cl.8.1 requires operational control over activities that affect asset performance, and spare parts availability sits directly inside that control. The clause map below shows where each check actually lives in the form.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 55001 cl.8.1 | Each issue is booked at the time it happens, not reconstructed afterwards | Parts |
| ISO 55001 cl.8.1 | Bin location is verified correct at the point of transaction | Parts |
| ISO 55001 cl.8.1 | A below-reorder-point condition triggers a recorded reorder | Parts |
| ISO 55001 cl.8.1 | Unused returned parts are inspected before restocking as available | Returns |
| ISO 55001 cl.8.1 | Failed parts are retained for failure analysis where required, then scrapped correctly | Returns |
| ISO 55001 cl.8.1 | Out-of-hours issue process is followed and access is controlled | Control |
| ISO 55001 cl.8.1 | Unbooked issues are actively checked for, not just assumed absent | Control |
| ISO 55001 cl.8.1 | Cost of parts consumed is booked back to the asset it served | Returns |
What it does not cover
- A part booked out 'Later' rather than at time of issue, which is the exact gap where the shelf and the register stop agreeing with each other.
- A returned part restocked with no inspection recorded, which puts a part that has already been fitted and removed back into the critical spares pool as if it were new.
- An unbooked issue found during a control check, which confirms the out-of-hours process isn't being followed, not merely that it's at risk of failing.
- A critical spare shown below reorder point with no reorder raised, which is precisely the condition the critical spares review depends on this record to have already caught.
- Store access logged as 'Open access', which means the next unbooked issue is a matter of when, not a departure from an otherwise controlled process.
Global
Parts Issue and Return Record requirements by country
Spare parts control sits mostly inside asset management and quality standards rather than statute, but the consequences of an uncontrolled store reach further than most sites assume.
ISO 55001 cl.8.1
asset information must be traceable across the asset's life, including the parts consumed against it
a parts transaction record is an asset management record, not a warehouse convenience, and gaps in it are gaps in the asset's history
ISO 9001 cl.8.5.4, preservation
preservation obligations apply to product and its constituent parts for as long as they remain under the organisation's control
a returned part sitting unbooked and uninspected is, technically, outside preservation control until this record closes the gap
Sarbanes-Oxley Act s.404, internal controls over financial reporting
material inventory for a public company needs an auditable transaction trail, not just a periodic count
for a listed company's site, this record is what an auditor tests as an internal control, not just a maintenance nicety
How to complete it
How to complete a parts issue and return record, step by step
The fields are mechanical to fill in. The judgement calls are what stores or the maintenance manager actually decide before the record is treated as clean.
A single 'Later' booking on a genuinely chaotic emergency job is different from a pattern of 'Later' bookings from the same shift or the same store window. The judgement call is whether this instance is explainable or whether it's evidence the booking process itself is too slow to use in real time.
Ticking Yes on Returned Parts Inspected Before Restocking should mean someone actually assessed fitness for use, not that the part looked fine on a glance back onto the shelf. Stores has to decide whether the inspection that happened matches the claim being recorded.
Old Part Returned For Failure Analysis is optional, which means someone is deciding, transaction by transaction, whether this failure is routine wear or something worth understanding before it repeats. Skipping that decision by default, rather than by assessment, is where recurring failure modes go unnoticed.
Out Of Hours Issue Process Followed scores 'Partly' at 1, between full compliance and none. The maintenance manager has to judge whether that partial compliance reflects a genuine edge case or whether it's the normal state for every night shift, which changes what the finding actually means.
What auditors find
Most common parts issue and return record findings
Patterns that show up repeatedly when this record is reviewed across a store's transaction history.
| Finding | Clause | What fixes it |
|---|---|---|
| A recurring share of issues booked 'Later' rather than at time of issue, concentrated on one shift | ISO 55001 cl.8.1 | Treat repeated 'Later' bookings from the same window as a store-access finding, not a series of individual timing lapses. |
| Returned Parts Inspected Before Restocking ticked Yes with no inspection criteria ever recorded | ISO 55001 cl.8.1 | Add inspection criteria to the field's help text and require the inspector to be someone other than the person returning the part. |
| Critical spare flagged below reorder point with Reorder Raised left at No | ISO 55001 cl.8.1 | Auto-trigger a linked Critical Spares Review entry whenever Critical Spare is Yes and Below Reorder Point is Yes. |
| Cost Booked To Asset left at No on issues tied to a specific Work Order ID | ISO 55001 cl.8.1 | Require Cost Booked To Asset before Status can move to Complete whenever a Work Order ID is present. |
| Out Of Hours Issue Process Followed logged as 'Partly' as the routine answer for every night shift | ISO 55001 cl.8.1 | Trigger a CAPA automatically once 'Partly' or 'No' appears more than a set number of times in a rolling period. |
| Old Part Returned For Failure Analysis left blank on critical-spare failures | ISO 55001 cl.8.1 | Make the field required, not optional, whenever Critical Spare is marked Yes on the same transaction. |
Case in point
Case in point: a shelf that said one thing and a work order that said another
A critical spare bearing was issued against an emergency job at 3am. The technician fitted it, the line came back up, and the part was logged the next morning as booked 'Later' — inside process, technically, since the field allows it. Nobody flagged it, because a single late booking never does.
Three weeks later the same part number was needed for a different asset. The register showed one in stock. It wasn't — it had been issued that night and never actually decremented until the morning booking, which by then had been missed entirely in the shift handover. The Critical Spares Review had signed off the week before on a count that was never true.
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.
6 sections
- Reference
- MNT-095
- Archetype
- Record
- Record ID
- PIR-2026-000
- Scoring
- Bookings complete
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 55001 cl.8.1
- Links
- Links Spare parts register, Stock count
- Tags
- Storeroom
- Sections
- 6
- Fields
- 42
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 4
Header
10 fieldsRecord ID*
Auto sequence. Format PIR-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*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Uncontrolled Issue Is Why Counts Never Reconcile
Parts taken off a shelf at two in the morning and never booked out are the reason the critical spare shows as in stock and is not there.
Transaction Type*
Work Order ID
Links to MNT-002 Work Order ID
Issued To*
Parts
Repeats9 fieldsPart Number*
Description*
Quantity*
Booked At Time Of Issue*
- Yes3 pts
- Later1 pt
- Not booked0 pts
Bin Location Correct*
- Yes3 pts
- Wrong location0 pts
Stock Level After Issue
Below Reorder Point*
- No3 pts
- Yes1 pt
Reorder Raised
- Yes3 pts
- No0 pts
Critical Spare*
Returns
6 fieldsUnused Parts Returned*
- Yes3 pts
- Not applicable3 pts
- No0 pts
Returned Parts Inspected Before Restocking*
A part that has been fitted, removed and returned to stock as new is a future breakdown.
- Yes3 pts
- No0 pts
Returned To Correct Location*
- Yes3 pts
- No0 pts
Old Part Returned For Failure Analysis
- Yes3 pts
- Not required2 pts
- No0 pts
Old Part Scrapped Correctly
- Yes3 pts
- No0 pts
Cost Booked To Asset*
- Yes3 pts
- No0 pts
Control
3 fieldsOut Of Hours Issue Process Followed*
- Yes3 pts
- Partly1 pt
- No0 pts
Any Unbooked Issue Found*
- No3 pts
- Yes0 pts
Store Access Controlled*
- Yes3 pts
- Partly1 pt
- Open access0 pts
Related records
1 fieldSpare Parts Register ID
The part being issued or returned.
Links to MNT-064 Register ID
Result
13 fieldsItems Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
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
Stores*
Signature*
Maintenance Manager*
Second Signature*
MNT-095 · record IDs look like PIR-2026-000 · Links Spare parts register, Stock count
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures each transaction. Keeping the booking discipline consistent across every shift, and connecting a bad transaction to the register it affects, is what tends to slip once volume goes up.
Holds this record against the spare parts register and stock count, and flags issues booked 'Later' or returns restocked without inspection before they turn into a count discrepancy.
Tracks reorder triggers raised from this record back to the supplier relationship, so a below-reorder-point critical spare turns into a purchase order rather than a repeated finding.
Rolls Cost Booked To Asset from every transaction into the asset's running maintenance cost, so a part issued but never costed doesn't quietly disappear from the spend picture.
Coordinates the crew, rolls completion and exceptions into one view, 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
Parts Issue and Return Record definitions and key terms
- Booked at time of issue
- Whether the stock transaction was logged the moment the part left the shelf, versus recorded later from memory — the field that scores the control this record exists to enforce.
- Bin location
- The physical storage position recorded against a part number. Confirming it's correct at issue or return catches drift between where a part is supposed to live and where it actually does.
- Reorder point
- The stock level below which a part should trigger a replenishment order. Below Reorder Point and Reorder Raised are tracked as two separate facts because falling below the point doesn't guarantee anyone acted on it.
- Critical spare
- A part flagged as essential to keeping an asset running, where a stockout has outsized consequences — the reason its transactions get extra scrutiny in this record.
- Failure analysis retention
- Keeping a failed part rather than scrapping it immediately, so its failure mode can be examined before the same fault repeats on another asset.
FAQ
Frequently asked questions about parts issue and return record
Does every part movement need its own record?+
Each transaction — an issue, a return, a transfer, or an adjustment — gets its own line under the repeating Parts section, but they can be grouped under one header record for the same job or the same counter session.
What happens if a returned part fails inspection?+
Returned Parts Inspected Before Restocking would be marked No, which scores zero and should stop the part going back into available stock. The template doesn't dictate the disposal path from there — that's handled through the failure analysis and scrap fields separately.
Why is Critical Spare not itself scored?+
Because it's a classification, not a performance measure — flagging a part as critical doesn't reflect good or bad process. The scoring sits on what happens around that flag: whether the reorder point condition was caught and acted on.
Who signs off a parts issue and return record?+
Stores and the maintenance manager, with two separate signatures. That split exists so the person handling the transaction day to day isn't the sole check on whether the store's controls are being followed.
Does this record replace the periodic stock count?+
No. It's the transaction trail the stock count reconciles against. A store with clean transaction records should produce counts that match with minimal adjustment — a store relying on the count to catch problems is finding them too late.
Why does 'Not applicable' score the same as 'Yes' on unused parts returned?+
Because a job that consumed every part issued, with nothing left to return, is exactly as clean an outcome as a job that returned everything correctly. Both reflect a fully accounted-for transaction; only an unreturned, unexplained part should score zero.
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
More in Storeroom
Parts Receipt Inspection
Inspects incoming spare parts for correct part number, damage, certification and food grade compliance
Storeroom Condition Inspection
Checks storage conditions, segregation, shelf life and preservation of held spares
Obsolescence Review
Reviews spares and assets whose parts are no longer manufactured, and what the plan is before the last one is used
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 9001 cl.8.5.4 — Preservation
- Sarbanes-Oxley Act 2002 s.404 — Internal controls over financial reporting
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.