| Employee belongings | Many employees use lockers during shifts, often with daily assignment changes. | Fast badge or card access, simple self-service assignment, clear occupancy status, and administrator controls. | Estimate peak simultaneous occupancy, not just total headcount. Include space for bags, coats, and personal protective equipment where needed. | Can staff use existing access credentials? How are forgotten items, lost credentials, and unclaimed lockers handled? |
| Tools and shared equipment | Items are checked out and returned by multiple users, with a need to know who had access and when. | User-linked access logs, item-level RFID identification where suitable, return confirmation, and alerts for overdue or missing items. | Confirm that tagged items fit within compartments and that the chosen RFID setup can reliably read the intended tags in the actual locker environment. | Do you need to track access to a compartment, the specific item inside it, or both? What is the process for damaged or unreturned equipment? |
| IT devices and mobile equipment | Laptops, tablets, radios, or other devices are distributed, returned, or stored between shifts. | Access permissions, transaction history, configurable compartments, and charging provisions where devices must charge while stored. | Check device dimensions, ventilation, power capacity, cable management, and electrical safety requirements before specifying charging lockers. | Are devices assigned to individuals or shared? Should access records connect to an existing identity or asset-management system? |
| Uniforms and workwear | Garments are issued, exchanged, or collected regularly, sometimes across multiple shifts or locations. | User authentication, item or compartment tracking as required, replenishment reporting, and integration options for workforce or inventory processes. | Allow for garment size, return capacity, laundry workflow, and the time required to restock compartments. | Is the main goal controlled distribution, proof of return, inventory visibility, or a combination of these? |
| Deliveries and parcel pickup | Packages are placed in compartments for later collection by employees, tenants, or customers. | Recipient notifications, one-time or time-limited pickup access, delivery records, and compartments in several sizes. | Use delivery volume and package dimensions to plan capacity. Include a procedure for oversized, damaged, or uncollected parcels. | Who can deposit packages? How are recipients notified, and how long may parcels remain before escalation? |
| Visitor or contractor access | Temporary users need limited access during a visit, service call, or short-term assignment. | Temporary credentials, configurable access periods, audit records, and a straightforward check-in and credential-revocation process. | Plan for credential issuance, visitor support, and access removal when a visit ends or a credential is lost. | Can temporary access be granted without creating a permanent user account? Who is responsible for issuing and disabling credentials? |
| Multiple sites or departments | Different locations or teams need consistent rules, with local administration and centralized oversight. | Role-based administration, centralized reporting, location-level settings, and documented integration and data-export options. | Standardize policies where possible while checking local network, power, space, and operating requirements at each site. | Which reports are needed across sites? What happens to access and records during network or system outages? |
| Auditability and controlled access | The business needs traceable access, defined permissions, and consistent procedures for sensitive or valuable items. | Individual authentication, tamper-aware event records where available, permission management, and retention settings aligned with company policy. | Define who may view records, how long they are retained, and how exceptions are reviewed. Assess privacy and security requirements before deployment. | Which events must be recorded? How are administrator actions protected, and can records be exported for review? |