•

Locker Allocation Register Template for Workplaces

An open grayscale locker still contains a bag, while a returned key rests separately below.
What’s in this article?

    Separate a locker’s assignment from its readiness for the next person. Use linked records, a clearance gate and a worked example to keep occupied or unresolved storage out of the available pool.

    A colleague returns a locker key on Friday. Reception marks the locker available. On Monday, the next assignee finds someone else’s belongings inside. The key handoff was recorded, but the space was never released.

    This locker allocation register template is for facilities coordinators managing exclusive workplace lockers. It includes a locker inventory, an assignment record and a release checklist, all available inline. Copy the headers and record into a restricted spreadsheet or your existing record system; there is no separate download to obtain.

    The operating rules below are recommendations to adapt with your site owner. They do not authorize opening a locker, removing belongings, charging employees or changing access rights. Follow your approved workplace policies for those decisions. Bank safe-deposit lockers, shared occupancy and hourly bookings are outside this resource.

    Define the allocation rules before using the register

    Name a locker coordinator, a backup and a facilities decision owner. The coordinator maintains the authoritative record; the backup takes over explicitly rather than editing a second copy. An assignee confirms receipt and reports problems, while an authorized reviewer verifies clearance.

    Real workplace processes distinguish allocation from access support. In its blended-working FAQs, LSE describes numbered lockers assigned by an office manager and an identity and allocation-list check before opening a locker after a forgotten code. That is LSE’s process, not a universal workplace rule. Your register should identify the current allocation and link to your own authorized access procedure.

    • Scope: one person has exclusive use of one locker during an allocation. If your policy permits someone to hold two lockers, record two allocations with separate approval references.
    • Identity: use a site-qualified locker ID, such as CHI-A-L024. “Locker 24” is ambiguous across buildings.
    • Timing: record date-times with the site time zone. Fixed-term use needs an end date-time; continuing use needs a review date.
    • Eligibility: reference the approved allocation policy and any necessary approval. Do not put medical details or the reason for an accommodation in the shared register.
    • Control: keep lock combinations, reset secrets and master-key details outside the allocation sheet. Link only to a restricted access-control record.

    Template 1: maintain one inventory row per locker

    Start with a physical check by locker ID. An apparently unused locker is not automatically available: confirm its assignment history, condition and authorized access readiness first. Unknown occupancy goes on hold until resolved.

    Locker ID,Site and zone,Local description,Inventory state,Blocking assignment ID,Hold or repair reference,Verified empty at,Condition check and evidence,Access readiness reference,Last verified by,Last verified at,Next action owner,Next action due
    Inventory fields and validation
    FieldRule
    Locker IDRequired, unique and permanent. Keep the identifier when an assignee changes; never reuse a retired ID for a different unit.
    Site, zone and descriptionRequired location that a coordinator can find. Record useful physical attributes without sensitive occupant information.
    Inventory stateExactly one: Available, Reserved, Assigned, Clearance hold, Maintenance hold or Retired. Use the transition rules below.
    Blocking assignment IDRequired for Reserved or Assigned. Retain it during Clearance hold when a prior assignment is unresolved. Never overwrite it with the next person.
    Hold or repair referenceRequired for either hold state; identifies the issue, responsible owner, next action and deadline.
    Empty, condition and access checksRequired before Available: actual checks, evidence references and verifier. An access check can reference a completed key recovery or authorized lock reset; do not store secrets here.
    Verification and next actionRecord who checked what and when. Every hold and reservation needs a named owner and due date-time.

    Keep detailed damage or belongings information in an appropriately restricted case. A status board for general users should show availability, not other employees’ identities or private circumstances.

    Template 2: create a record for each allocation cycle

    Use a new assignment ID whenever a locker is assigned to a new person. Keep completed records so the inventory can point to its current cycle without erasing the previous one. Use this copy-ready record for a request, reservation, handover and eventual clearance.

    Assignment ID: [unique reference]
    Locker ID / site / zone: [inventory reference]
    Assignee: [work name / internal ID / work contact]
    Request and policy version: [references]
    Allocation type: [Fixed-term / Continuing]
    Purpose or eligibility confirmation: [non-sensitive reference]
    Approval: [decision / authorized person / timestamp / reference]
    Planned start: [date-time / time zone]
    End due (Fixed-term): [date-time / time zone]
    Review due (Continuing): [date / time zone]
    Reservation expires: [date-time / time zone]
    Record state: [Requested / Reserved / Active / Clearance pending /
                   Closed / Cancelled-before-handover]
    Handover: [actual date-time / issuer / assignee acknowledgement]
    Initial condition and evidence: [reference]
    Access handoff record: [restricted reference, not code or secret]
    Policy acknowledgement: [version / person / timestamp / evidence]
    Release requested: [by / date-time / intended end]
    Assignee removal confirmation: [date-time / evidence]
    Authorized empty verification: [person / date-time / evidence]
    Condition outcome: [Serviceable / Repair required / Unresolved]
    Access readiness outcome: [Cleared / Action required / Unresolved]
    Belongings, repair or access case: [reference / owner / next action / due]
    Closure: [reviewer / date-time / evidence / final inventory state]
    Change history: [old value / new value / reason / actor / timestamp]

    Make the required fields conditional on the decision

    A Requested record needs an assignee, proposed site, allocation type and eligibility reference; the specific locker can remain unselected until review. Before Reserved, require the locker ID, approval, planned start and reservation expiry, plus the end or review deadline. Before Active, require actual handover, condition evidence, access handoff and acknowledgement of the applicable policy.

    A receipt acknowledgement can read: “I confirm that locker [ID] was allocated to me on [date-time], that the recorded condition is accurate, and that I received the workplace locker policy [version] and the contact for reporting a problem.” This is an operational receipt, not a new waiver or authorization to search belongings.

    If the assignment needs an extension, record the approving person, old deadline, new deadline and reason. Do not backdate the change to hide an overdue period. Continuing assignments remain Active after a review becomes due; they need a review, not an automatic release.

    Use explicit states to decide what happens next

    Locker inventory transitions and blocking evidence
    StateMeaning and permitted next stepWhat blocks release or handover
    AvailableEmpty, serviceable and access-ready, with no blocking allocation. Coordinator may reserve it for an approved request.Missing verification, an unresolved case or a competing allocation.
    ReservedHeld for one approved assignment until its expiry. Handover makes the assignment Active and inventory Assigned.No acknowledgement, expired reservation or a newly discovered condition/access problem.
    AssignedExclusive use has begun. A release request moves the record to Clearance pending and inventory to Clearance hold.A planned end date or returned key alone does not complete clearance.
    Clearance holdPrior occupancy or clearance evidence is unresolved. Keep the assignment linked and complete the release checklist.Belongings, unverified vacancy, condition concerns or unresolved access actions.
    Maintenance holdAllocation has been closed after vacancy and access clearance, but a documented repair prevents use.Repair completion and a fresh readiness verification are required before Available.
    RetiredRemoved from the usable pool by the authorized owner with a reason and date.Do not use retirement to conceal unresolved occupancy; resolve or explicitly transfer outstanding responsibilities first.

    If a defect appears while a person is still assigned, keep the assignment Active and flag the linked case; block further allocation. If that person must move, open a separate approved allocation and clear the original through its own cycle. Do not silently transfer their belongings or rename the old record.

    For an expired reservation with no handover, the coordinator confirms that no use began, records Cancelled-before-handover and rechecks readiness before returning the locker to Available. If someone may already have received access, use Clearance hold instead.

    Coordinate edits so two people cannot allocate the same locker

    A spreadsheet does not enforce exclusive allocation just because a status cell says Available. Use one authoritative file and one allocation writer at a time. The backup confirms the takeover with the coordinator. Immediately before reservation, the writer rechecks the locker row and all nonclosed assignment records, then records the assignment ID before notifying the requester.

    If two requests collide, stop the handover, preserve both request records and let the coordinator resolve the conflict. For simultaneous self-service use, specify and test an enforced uniqueness or reservation control in the chosen system; do not assume a form submission supplies it.

    Release checklist: a key return is only one input

    1. Coordinator: confirm the assignment ID, locker ID and authorized release request. Record when use is intended to end.
    2. Assignee: confirm removal of belongings through the approved handback process. A nonresponse is not evidence of vacancy.
    3. Authorized verifier: check that the locker is empty under the site’s approved procedure; record the person, time and evidence. If authorization is unclear, keep the hold and escalate to the facilities decision owner.
    4. Facilities: record condition as Serviceable, Repair required or Unresolved. Give repairs a case owner and deadline.
    5. Access owner: confirm the required key, lock or credential action is complete. Use the physical key control log for copy-level custody and losses; this allocation register is not a substitute for it.
    6. Reviewer: close the assignment only after vacancy and access readiness are verified and every remaining issue has an explicit disposition. Set Available only if serviceable too; otherwise use Maintenance hold with the repair reference.

    Belongings left behind need a restricted case and a decision under your approved property-handling policy. This template deliberately sets no disposal deadline or right of entry. Do not treat an overdue allocation as permission to open, empty or reassign a locker.

    Reconcile the inventory and review overdue work

    At a locally agreed review cadence, count unique locker IDs, not assignment rows. Review also at a departure, a site move or a reported discrepancy. These are suggested triggers, not legal retention or inspection intervals.

    Usable-pool lockers = Available + Reserved + Assigned
                       + Clearance hold + Maintenance hold
    Known lockers = Usable-pool lockers + Retired
    
    Reservation allowed only when:
    Inventory state = Available
    AND empty, condition and access checks are current under site policy
    AND no unresolved restriction exists
    AND no blocking assignment exists.
    
    Fixed-term follow-up due:
    now > End due AND assignment is not Closed or Cancelled-before-handover
    
    Continuing review due:
    review date has passed AND assignment remains Active

    “Usable-pool” includes temporarily blocked units; it is not the number ready to issue. Ready-to-allocate capacity is the Available count only. Keep the terms consistent in reporting, and show holds separately so a high total cannot hide low availability.

    Check that each Reserved or Assigned row links to exactly one matching assignment in Reserved or Active state. A Clearance hold may link a Clearance pending record. No locker may have two blocking cycles. A Maintenance hold should have a closed prior assignment and a live repair reference. Any mismatch becomes a coordinator-owned exception, not a manual adjustment to make the totals balance.

    For each overdue item, record the next contact or decision, owner and due date-time. Choose review and escalation intervals with the site owner. Escalation creates a decision task; it never automatically renews an allocation or clears the locker.

    Worked example: a returned key with belongings inside

    Fictional example: Northline Office has eight lockers: three Available, one Reserved, three Assigned and one Maintenance hold. Thus eight equals 3 + 1 + 3 + 0 + 1. Alex holds CHI-A-L024 under assignment A-117, ending November 20 at 17:00 America/Chicago.

    Completed release record for A-117
    EventRecorded result
    Alex hands back the key, Nov 20 at 15:30Coordinator records key-return reference K-882, release request and Clearance pending. L024 becomes Clearance hold, still linked to A-117.
    Authorized check at 16:00 finds a bagEmpty verification fails. Open case C-19, owner Morgan in Facilities, next action: contact Alex by Nov 23 at 10:00. Do not allocate L024 to the waiting requester.
    Alex collects the bag Nov 23 at 09:15Authorized verifier records empty at 09:20 and Serviceable condition. Access owner confirms the site-required access action at 09:30 with reference AC-73.
    Reviewer checks evidence at 09:40Close C-19 and A-117 with evidence; update L024 to Available. A new requester needs a new approved assignment, not an edit to A-117.

    During the hold, the counts are 3 Available + 1 Reserved + 2 Assigned + 1 Clearance hold + 1 Maintenance hold = 8. After verified release, they become 4 + 1 + 2 + 0 + 1 = 8. Returning the key changed custody; only the completed clearance changed available capacity.

    Where Workhint fits in the allocation process

    The static records remain usable without Workhint. When multiple teams handle requests and review, the Workhint Workflow Engine provides configurable request steps, role-based approval routing and requirements before work moves forward. Those capabilities are relevant to intake, allocation approval and clearance review.

    Workhint’s workflow automation software describes custom forms, process stages, owners and configured approval outcomes. The two registers above can serve as a requirements brief for that configuration. This is not evidence of a prebuilt locker system, lock-hardware integration or an automatically enforced exclusive-allocation constraint; verify those implementation requirements separately.

    Test the register before the first live allocation

    • Enter L024 at two sites: site-qualified IDs must distinguish them.
    • Try a second active allocation for one locker: stop and resolve the conflict; do not replace the first assignee.
    • Return a key without empty verification: inventory stays on Clearance hold.
    • Clear belongings but find a broken hinge: close occupancy only with access clearance and explicit issue disposition; keep Maintenance hold until repair and readiness checks pass.
    • Let a continuing-use review date pass: flag review due, not Available.
    • Have the backup allocate during a coordinator handover: confirm who owns the write before either sends a confirmation.

    Before rollout, replace the sample roles, site codes and deadlines, choose retention and access rules with the responsible owners, and walk one complete issue-and-release cycle with the backup. Archive records under that approved retention policy, not an arbitrary period embedded in this template.

    Frequently asked questions

    Is a locker allocation register the same as a key log?

    No. The register tracks exclusive use and readiness of a fixed storage unit. A key log tracks physical copies and custody. A keyless locker still needs allocation and clearance records.

    Can the locker become available when the end date passes?

    Not under this design. The end date triggers follow-up. Verified vacancy, serviceable condition, access readiness and resolution of blocking records determine availability.

    Can several people share one locker?

    This template assumes exclusive use. Shared or shift-based lockers need a different occupancy model, explicit overlap rules and a way to distinguish each person’s responsibilities; do not use one assignee cell to represent several people.

    Should codes and combinations appear in the spreadsheet?

    No. Keep access secrets in the separately approved restricted process. Record only the reference and completion evidence needed to confirm access readiness.

    Comments

    Leave a Reply

    Your email address will not be published. Required fields are marked *


    The reCAPTCHA verification period has expired. Please reload the page.