Reconcile Rental Key Custody at Every Shift Change
Use a compact custody check for rental keys, lockbox devices, authorized holders, and unresolved access exceptions.
By PortfolioRental Editorial Team · · Updated 2026-09-14
Keys move between offices, vendors, showing staff, and secured storage. A shift reconciliation catches an unreturned item while the last handoff is still recent enough to investigate.
Quick Overview
List the property code, key or device identifier, storage location, authorized holder, checkout time, expected return, actual return, and exception status. Compare physical inventory with the lockbox inventory reconciliation. Use the access coordination plan for scheduled visits and resident notice requirements.
Count custody events
The log should show who accepted responsibility at each transfer. Do not write door labels or access codes where an exposed record could identify a property. When a key is late, record the last confirmed holder and escalate under the access policy. Do not quietly extend a checkout time to make the register balance.
The CISA physical security guidance offers general context for controlling physical access. Property procedures still need to match lease terms, local rules, and the owner's security policy.
Common Mistakes
Avoid shared holder names such as "maintenance." Do not treat a lockbox code as harmless because it can be changed later. Never mark an item returned until someone confirms its identity and location. Keep resident names out of the custody label unless the approved system requires them.
Common Questions Answered
If a vendor transfers a key directly to another authorized vendor, both sides should confirm the transfer. If the physical count disagrees with the register, freeze further release of the affected item and follow the incident process.
Ready to close the shift
The outgoing and incoming coordinators should agree on the physical count, open exceptions, and next escalation time. Sign-off means the discrepancy list is accurate, not that every discrepancy has already been resolved.