Spare Unit Stock Policy: A Field Worksheet to Complete
A spare unit stock policy worksheet is complete when another facility team can identify which installed lock variants are covered, where usable units are held, who may release one, and what evidence must accompany every issue. It is not a list of products to keep in a cupboard and it is not a promise about replacement speed. It is the controlled bridge between the installed lock asset register and the field service replacement stock held by your organisation.
Direct answer. The one-line answer — spare unit stock policy worksheet is the working record for spare unit stock policy worksheet. spare unit stock policy worksheet is worthless until spare-unit-stock-policy is attached to it as evidence. A spare unit stock policy worksheet is the operating-life view. It starts after the invoice. spare unit stock policy worksheet is the first interval of spare unit stock policy worksheet to measure.
spare unit stock policy worksheet means here what spare unit stock policy worksheet sets out. It is a working definition of spare unit stock policy worksheet for this market and product. It is drawn from the evidence below, and it is not a general marketing phrase.
- Set the interval — define how often spare unit stock policy worksheet is inspected
- Set the trigger — name the condition that forces a change to spare-unit-stock-policy
- Track the number — keep one metric that shows setting policy boundary is healthy
- For spare unit stock policy worksheet, spare unit stock policy is what each step has to answer to.
Use this playbook after the lock award is complete and before routine service begins. Copy the tables into your own system, remove fields that do not apply, and have the named owner approve each blank. Leave policy values blank until your records support them. The worksheet deliberately separates usable stock, reserved stock, quarantine, components and returns so that a unit cannot be counted twice.
Establish the policy boundary and controlled outputs
| Controlled output | Required content | Accountable role | Evidence of completion |
|---|---|---|---|
| Portfolio policy worksheet | Scope, counting rules, stock calculation, approvals and review triggers | Facility Manager | Approved revision |
| Installed-base inventory | Door and unit identifiers, model, variant and interchangeability class | Asset owner | Reconciled asset register |
| Stock register | Usable, reserved, quarantined, in-transit and return-authorisation status | Stock custodian | Physical count and system balance |
| Issue and return log | Issue, fit, test, old-unit disposition and evidence links | Field service lead | Completed transaction record |
| Site annex | Location, custodian, release route and local operating notes | Site representative | Signed site annex |
| Review record | Changes considered, decisions and next review point | Facility Manager | Approved meeting or change record |
Do not count a complete unit as usable stock until its identity has been checked against the receiving record. Components, incomplete kits and units awaiting inspection remain in separate statuses. A stock total is meaningful only when every physical item maps to one status. The catalogue side of this is the smart door locks.
Prepare the policy header and approval route
| Header field | Entry required |
|---|---|
| Policy identifier | Unique reference for the controlled document |
| Portfolio and sites | Buildings, areas or operating locations covered |
| Installed-base snapshot | Date and source extract used for the baseline |
| Review period | Historical period used to measure replacement issues |
| Planning period | Forward period used by the buyer for stock planning |
| Product scope | Models, SKUs and variants included or excluded |
| Stock locations | Central, site, service-bench and field-kit locations |
| Policy owner | Role accountable for the complete worksheet |
| Stock custodian | Role responsible for physical custody and counts |
| Release approver | Role permitted to authorise a unit issue |
| Request channel | Agreed method for receiving replacement requests |
| Related records | Asset register, issue ledger, work register and supplier correspondence |
| Revision and approval date | Current revision, approver and approval record |
The final version must distinguish a routine issue from an exception. A routine issue follows the agreed workflow. An exception covers a mismatched variant, a disputed count, an unapproved transfer, an unidentified unit or a return that cannot be completed under the agreed route.
Build the installed population and interchangeability classes
Start from the installed lock asset register, not from the original purchase order alone. An asset register shows where the installed population is; a purchase record may describe what was ordered rather than what reached each door. Reconcile object identifiers against the field schedule so that a room label is never used as the only unit identifier.
For an existing building, use the Office Smart Lock Site Survey or the Smart Lock Retrofit Site Survey as an input where the survey scope matches the site. Record the survey reference and reconcile its observations to the installed-base inventory before using demand data in the stock calculation.
Create an interchangeability class only from attributes confirmed for the specific SKU. Confirm on the dated product page for the specific SKU before treating two units as interchangeable, transferring one into another location or ordering a replacement against the same class.
| Inventory field | What to record | Control question |
|---|---|---|
| Object identifier | Stable door or unit identifier | Can the same door be found in field and stock records? |
| Site and area | Physical operating location | Does the unit belong in this site’s demand pool? |
| Model | Name shown on the unit label or approved record | Does the record match the physical label? |
| SKU and variant | Supplier product reference and distinguishing variant | Is interchangeability confirmed for this exact SKU? |
| Door configuration | Handing, swing direction and relevant installation attributes | Could orientation affect the replacement? |
| Finish and appearance | Relevant finish or trim distinction | Has the visible variant been recorded accurately? |
| Installation attributes | Recorded power, component and configuration details | Is the entry taken from evidence rather than assumption? |
| Support status | In scope, planned removal or excluded | Why is this object included in the calculation? |
| Interchangeability class | Approved grouping used for planning | Who confirmed that the class is valid? |
| Evidence source | Asset export, survey, label check or site record | Can the source be retrieved? |
Do not collapse several variants into one class because their model names are similar. Separate them when finish, handing, component configuration, installation method or another recorded attribute affects the replacement decision. If the class remains uncertain, keep the units in separate planning groups until the evidence is complete.
Remove or separately classify units scheduled for decommissioning. Their presence in the installed population may explain a future removal, but it does not automatically justify keeping a like-for-like spare after the removal work is complete.
Create the movement and evidence ledger
| Ledger field | Record required |
|---|---|
| Transaction identifier | Unique issue, transfer, receipt or return reference |
| Date and time | When the stock movement was recorded |
| Door or unit identifier | Object schedule identifier, not a room name alone |
| Model and variant | Label or catalogue-derived identity |
| Symptom | Technician’s description of the condition |
| Measured observation | Reading, test result or visible condition supporting the symptom |
| Checks performed | Tests run in the order performed |
| Finding after each check | What the check ruled out or established |
| Unit issued | Identity and status of the replacement unit |
| Old unit retained | Identity and destination of the removed unit |
| Credential state | Before and after state where credentials were involved |
| Supporting evidence | Photo, reading or report reference |
| Balance update | Effect on usable, reserved, quarantined and return status |
| Approver | Role accepting the issue or exception |
Without a record of what each check ruled out, a visit record is only an action list. The sequence helps the next technician avoid repeating a completed test and gives the approver evidence for choosing a replacement.
Count only an issue as consumed stock when the unit has actually left the stock location under an approved transaction. Keep reservations visible, but do not treat a reservation as an issue. If a reserved unit is cancelled, record the release and update the balance before selecting another unit.
Retain the removed unit where the approved procedure requires it. Its identifier, condition and destination form part of the spare unit evidence chain. Where the unit is sent for return authorisation, the transition from quarantine to return-authorised status must be visible in the ledger.
Calculate demand and the target usable pool
| Calculation | Method | Source | Decision use |
|---|---|---|---|
| Issue rate by variant | Recorded replacement issues for the variant divided by the length of the selected review period | Issue ledger | Establishes the observed demand pattern |
| Planning-period demand | Issue rate multiplied by the buyer’s selected planning-period length | Issue ledger and policy header | Converts historical use into the planning basis |
| Approved works demand | Count of approved works expected to consume that variant | Work register | Adds known future demand |
| Contingency allowance | A buyer-selected value with a written risk rationale | Policy review | Covers uncertainty identified by the accountable owner |
| Target usable pool | Planning-period demand plus approved works demand plus contingency allowance | Completed calculation | Sets the controlled stock target |
| Allocated stock | Uncommitted usable stock plus reserved units plus confirmed inbound units | Stock register | Shows what is already covered by the target |
| Net action | Target usable pool minus allocated stock | Completed calculation | Establishes the quantity to obtain, transfer or redeploy |
Do not smooth away a concentrated fault pattern in the average. If one variant, site or failure mode generates most replacement issues, present that segment separately and determine whether the cause is technical, operational or environmental. The stock policy records the resulting replacement demand; it does not replace root-cause work.
Select the allocation model that matches the portfolio
The Multi-site Spare Unit Stock Policy: What Changes at Scale expands the allocation choices for larger portfolios. Use this worksheet to record the decision and its evidence rather than to reproduce a site-by-site policy.
| Allocation model | Suitable operating pattern | Main advantage | Control that must be present |
|---|---|---|---|
| Central pool | Sites draw from a shared controlled store | Stock can be allocated as demand changes | Transfer authorisation, dispatch record and destination receipt |
| Regional pool | Several nearby sites share a hub | Keeps stock closer to operating areas | Hub-to-site reconciliation and agreed issue route |
| Site-held pool | Each site controls a local cabinet | Local custodian can release stock directly | Named custodian, cabinet access and site count record |
| Service-bench stock | Spares sit with the team doing installations | Physical checking is close to the work | Issue-to-door transaction and technician custody |
| Field-kit holding | A limited quantity travels with the technician | Supports planned and authorised call-outs | Issue, return and non-issued-kit reconciliation |
Record the chosen model, rejected alternatives and reason in the policy. For a hybrid arrangement, identify which units remain central and which are site-held. State whether site demand is drawn from its local pool first or whether every request is approved centrally.
Do not distribute stock merely because one site asked for it. Match the allocation to recorded demand, the approved interchangeability class and the ability to return unused stock. A site that cannot reconcile a transfer or produce an issue record should not receive an untracked pool.
Define physical locations and custody
| Location or container | Contents permitted | Custody record | Return condition |
|---|---|---|---|
| Central stock store | Approved complete units grouped by variant | Store ledger and location label | Same status and balance as the ledger |
| Site cabinet | Units approved for that site or authorised transfer | Site annex and local count sheet | Reconciled to the central register |
| Service bench | Units undergoing fit, check or preparation | Technician or bench checkout record | Returned, issued or quarantined with evidence |
| Field kit | Units issued for a defined work item | Kit checkout and door assignment | Used unit, unused return or quarantine entry |
| Quarantine area | Unusable, unidentified or pending-return units | Separate quarantine register | Released or returned through an approved decision |
| Return route | Units authorised for shipment or supplier collection | Return record and handover evidence | Receipt confirmed by the receiving party |
Apply the supplier’s handling and storage instructions for each SKU and the site’s own operating conditions.
Label every location with its controlling document, approved contents and custodian role. Keep the physical location code identical in the asset system, stock register and count sheets. If a unit moves without a transaction, it becomes an unresolved variance rather than an informal transfer.
Protect access to the stock without recording sensitive credential information in the stock ledger. The stock record needs unit identity, status and custody; credential issuance, revocation and recovery belong in the controlled credential process.
Control issue, fit and return transactions
Replacement should follow the fault evidence and the approved decision path. The Spare Unit Stock Policy: Decision Tree for Field Teams provides a companion decision aid, while this worksheet defines the records that must survive the decision.
flowchart TD
A[Receive replacement request] --> B[Match door and unit identifiers]
B --> C[Run approved fault checks]
C --> D{Replacement decision supported?}
D -->|Yes| E[Approve release and issue unit]
D -->|No| F[Record findings and escalate]
E --> G[Fit unit and restore service]
G --> H[Update ledger and retain evidence]
Use the following sequence for each request. The named owner may combine steps only when the resulting record still contains the same evidence.
| Step | Responsible role | Required record | Stop condition |
|---|---|---|---|
| Receive request | Service desk or designated channel | Request identifier, door identifier and reported symptom | Door or unit cannot be identified |
| Review installed record | Technician or asset owner | Model, variant and relevant installation attributes | Recorded identity conflicts with the label |
| Perform checks | Technician | Checks in sequence and what each check ruled out | Evidence does not support replacement |
| Approve issue | Authorised approver | Approval identity, unit selected and stock status | Unit is reserved, quarantined or mismatched |
| Prepare unit | Custodian | Issue transaction, label check and destination | Physical identity differs from the selected record |
| Fit and test | Technician | Fitted unit, observed result and credential state where relevant | Door is not operable or the issue remains unresolved |
| Retain old unit | Technician or custodian | Removed unit identity and destination | Old unit cannot be traced |
| Close transaction | Stock controller | Ledger update and retained evidence links | Balance or location remains unresolved |
Record the date and time the fault was reported and the date and time the door was operable again. These timestamps belong to the buyer’s service record and support later analysis. The policy does not convert them into an external performance promise.
Update the stock balance only after the physical issue is confirmed. If the fitted unit fails acceptance, record the exception and move the unit to the appropriate review status rather than quietly returning it to usable stock.
Operate quarantine, return authorisation and the old-unit route
A DOA unit is a unit that fails before it is put into normal service. Define the precise boundary between failed on arrival and failed in use in the buyer’s agreement. Do not assume that every early failure belongs to the same transaction route.
| Quarantine category | Reason for hold | Required evidence | Exit decision |
|---|---|---|---|
| Identity uncertain | Model, SKU or variant cannot be confirmed | Label photograph and receiving record | Identify, return or dispose through an approved decision |
| Failed before service | Unit failed before normal service | Test record and agreed DOA classification | Repair, return authorisation or other approved disposition |
| Damage or condition concern | Physical condition prevents use | Photograph and condition description | Inspection or return decision |
| Diagnostic hold | Unit may be relevant to an unresolved fault | Fault reference and technician findings | Release as usable, repair or return |
| Awaiting return authority | Shipment requires authorisation | Written authorisation and handover record | Dispatch, cancel or alter the request |
| Non-issued field unit | Field custody cannot be reconciled | Kit checkout and technician statement | Locate, reconcile or escalate |
Before shipping anything, ask the supplier what may be returned, what evidence is required, how the unit must be packaged, which items must accompany it and what the receiving process expects. Ask separately whether the current supplier quotation or agreement defines any stockholding, replacement or credit treatment. Do not assume that a return request guarantees a particular commercial outcome.
CONFIRM-PER-SUPPLIER: Confirm current return-authorisation instructions, evidence requirements, packaging and any supplier-side stockholding or credit treatment for each specific SKU.
The RMA record must show what was authorised, what was handed over and what the receiving party acknowledged. Record the carrier or collection reference where relevant, but do not assign freight responsibility or cost without the applicable agreement or written confirmation.
Run the stock replenishment review
Use this availability formula for each interchangeability class:
Available stock = usable on hand − reserved units
Keep confirmed inbound units separate until they are received and accepted. Quarantined units remain outside usable stock. A physical count variance remains outside the calculation until the variance is resolved or an accountable owner records the treatment.
| Review input | Evidence source | Review question |
|---|---|---|
| Current usable balance | Reconciled stock register | Does the physical count agree with the ledger? |
| Approved works | Work register | Which units are already committed? |
| Recent issue pattern | Issue ledger | Has demand shifted between variants or sites? |
| Confirmed inbound | Purchase or transfer record | Which units are genuinely expected, and where will they be held? |
| Quarantined population | Quarantine register | Has any held unit become eligible for use? |
| Replacement candidates | Return and disposition records | Should a returned unit re-enter stock? |
| Net action | Completed calculation | What quantity must be obtained, transferred or redeployed? |
A replenishment decision can be “no change.” Record it so that a low stock balance is not mistaken for an unexamined shortage. If the calculation produces a transfer rather than a purchase, use the same identity, custody and reconciliation controls as any other movement.
Do not combine variants to avoid a separate action. If a class is not stocked, record the approved alternative and the operational effect. If a class is stocked centrally, record how the request reaches that pool and how the receiving site accepts the transfer.
Reconcile physical stock with the ledger
| Category | Definition | Reconciliation action |
|---|---|---|
| Usable | Identity confirmed and available for issue | Match to an approved stock record |
| Reserved | Committed to an approved work item | Match to the reservation and release condition |
| Quarantined | Held because use or movement is uncertain | Match to quarantine evidence |
| In transit | Moved but not yet accepted at destination | Match both dispatch and receipt records |
| Return-authorised | Approved for the return route | Match to the return and handover record |
| Unidentified | Identity or location cannot be established | Investigate before any count is approved |
| Variance | Physical and recorded balance do not agree | Record cause, owner and corrective action |
Repeat a count of an unresolved location before the next approved stock action if the discrepancy could affect a release. Do not adjust the ledger merely to make the count agree. The adjustment must identify the transaction or evidence that explains the difference.
Review, change and retire the policy
A change record should state the reason, affected sites, affected variants, recalculated stock effect, proposed control change, approver and implementation date. A minor clerical correction and a change to the stock target are different changes; label them differently so the approval route remains proportionate.
At each review, test whether the records still work:
- Can every issued unit be traced to a door, approved work item or authorised return?
- Does every physical unit have one current status and location?
- Are models and variants still separated according to confirmed interchangeability evidence?
- Are reservations, inbound transfers and quarantine balances visible in the review?
- Do the issue records contain the checks performed and what each check ruled out?
- Are removed units accounted for under the agreed retention or return process?
- Does the target still reflect the buyer’s current installed population and planning period?
Record any lesson from field use as an evidence-backed change. Do not convert a local observation into a general product claim. Model identity and fit must still be confirmed on the dated product page for the specific SKU.
Complete the final approval checklist
| Completion check | Pass condition | Evidence reference |
|---|---|---|
| Scope boundary | Sites, installed population and exclusions are stated | Policy header |
| Variant classes | Each stocked class has confirmed identity evidence | Dated product page and asset record |
| Demand baseline | Review period, issue source and calculation are visible | Calculation sheet |
| Target rationale | Planning demand, approved works and contingency are documented | Approval record |
| Allocation | Location and allocation model are selected | Site annex |
| Custody | Every location has a named custodian role | Stock register |
| Release route | Request, approval, issue and fit records are defined | SOP workflow |
| Evidence standard | Required observations and test findings are listed | Issue ledger template |
| Quarantine and returns | Entry, review and exit controls are assigned | Quarantine register |
| Replenishment | Inputs, owner and review interval are recorded | Review template |
| Reconciliation | Physical and recorded balances use the same status definitions | Count sheet |
| Supplier evidence | Current written confirmations are attached where required | Correspondence log |
| Approval | Policy owner and authorised roles sign the revision | Approval page |
Use the Spare Unit Stock Policy for Installed Smart Locks: A Buyer and Operator Guide to brief the people who will operate the approved worksheet. Give them the decision boundaries, forms and evidence expectations rather than an informal summary.
Before approval, search for blank fields, conflicting names, duplicate unit identifiers and unexplained status changes. Resolve these through the source record. A blank entered as a dash can hide a missing decision, so use “not applicable” only when the policy explains why.
Publish the controlled policy and preserve the evidence
Publish one approved revision and mark earlier drafts as superseded. Distribute the site annexes and current forms to the people who receive, issue, fit and reconcile stock. Keep withdrawn copies available for audit, but prevent their use for current transactions.
The practical counterpart to this point is sl 6301 mechanical key access. That is the same question spare unit stock policy worksheet has to answer here.The Spare Unit Stock Policy Documentation Set provides the companion record structure for the worksheet, stock register, issue ledger, quarantine list and count sheets. Match each form to a named owner and storage location.
Send the approved SKU list and open questions to the supplier for written confirmation. Include the question, the specific SKU, the dated product page consulted and the response received. This creates a usable evidence trail without turning an assumption into a catalogue fact.
CONFIRM-WITH-LOCAL-SITE: Confirm the applicable access, security, insurance, transport and disposal requirements with the site authority and the buyer's insurer before stock is released.
Ask for the offer against the same requirement: request a quote.

