Key & Access Control Log for Rental Properties
A key and access control log is the ongoing record of who has access to a rental property, what type of access they hold, when it was issued, and when it was returned, revoked, or replaced. Unlike a one-time key handover checklist, the log stays active throughout the life of the property and can cover tenants, managers, staff, contractors, cleaners, vendors, and temporary access.
The purpose is operational accountability. It should help you answer a simple question: who currently has authorized access to this unit, and what changed over time? Entry rights, notice requirements, privacy, lock standards, and tenant protections vary by jurisdiction, so the log should support—not replace—your legal access procedures.
Quick answer: what fields belong in an access-control log?
- Property or unit identifier
- Access item or credential identifier
- Access type: key, fob, card, remote, passcode, eKey, or other credential
- Name or role of the authorized holder
- Date and time issued
- Purpose or access scope when relevant
- Expected return or expiration date
- Date returned, revoked, or deactivated
- Replacement or loss notes
- Authorization or verification note
Why a key log is different from a key handover form
A Rental Property Key Handover Checklist records a specific event, usually at move-in or move-out. A key control log is the master history. It can show that two tenant keys were issued in January, one replacement was created in March, a contractor key was signed out and returned in June, and all tenant access was closed at turnover.
For one small rental, this may be a single page. For several properties, use one log per unit or a clearly structured portfolio log so access records do not become mixed together.
1. Give every physical key or device a non-sensitive identifier
A reliable log needs an identifier that connects the physical item to the record. That can be a key number, fob number, remote serial, or internal code. The identifier should be unique enough to distinguish one item from another.
Avoid attaching the full property address to a loose key when a lost key could then identify the door it opens. A coded system lets the internal record map the identifier to the unit without making the key self-explanatory to a stranger.
2. Track the holder, not just the quantity
“Four keys exist” is inventory, not access control. The useful question is who has each key. Record the person or authorized role, issue date, and the reason they have access. For temporary vendor access, add an expected return date or time window.
GSA Form 138, a long-standing government key-issuance record, uses fields for room, recipient signature, issue time, and return time. Residential property management does not need to copy that form, but the structure illustrates the core idea: every handoff should have a traceable beginning and end.
3. Separate permanent, tenant, staff, and temporary access
Not every credential has the same purpose. A useful log can classify access as tenant, owner or manager, staff, maintenance vendor, emergency, showing, or temporary. This makes it easier to see whether an old contractor key is still outstanding or whether a credential should have expired.
For physical keys, the control step is return or replacement. For electronic access, it may be deactivation or expiration. Record the actual action rather than assuming the end date on a calendar means access was successfully removed.
4. Record replacements without deleting history
If a key is lost, damaged, or replaced, keep the original entry and add a new one. Mark the old item’s status clearly. The log should show the sequence of events, because replacing one key can affect how you assess the security of the remaining copies.
The same principle applies to a smart-lock credential. If a code or eKey is replaced, record the old credential as revoked and the new credential as issued. Do not overwrite the record as if the old access never existed.
5. Use extra care with master keys and administrative credentials
A master key, building-level fob, property-manager credential, or smart-lock administrator account has broader consequences than a tenant key. Keep the record of who is authorized to hold or use that access separate from the credential itself. Do not print master codes or passwords in the log.
Limit the log to identifiers and status. Sensitive credentials belong in an appropriately secured system, not in a binder page that contractors, tenants, or other visitors may see.
6. Treat smart-lock activity logs as sensitive data
Some smart-lock systems can record timestamps, credential IDs, and unlock activity. That capability can be useful for maintenance or security workflows, but it can also create privacy concerns. Do not assume that because a platform can collect access history, every use of that history is appropriate or lawful.
Define why access data is being retained, who can view it, and how long it is kept. Use applicable law, building policy, and vendor documentation when setting the rules. The property access-control log can record credential status without becoming a surveillance log.
7. Reconcile access at every tenant turnover
Turnover is the point when the log should be audited. Compare access that was issued with what was returned, revoked, replaced, or deactivated. Check tenant keys, mailbox keys, fobs, garage remotes, parking credentials, and any temporary vendor access that may still be active.
Connect this step to the Rental Property Turnover Checklist Between Tenants. A turnover should not be closed while the access record still shows unexplained credentials.
8. Use the log for contractors and temporary access
Maintenance work often creates short-term access. Instead of handing a vendor an unlabeled spare key and relying on memory, record who received it, when, for which unit, and when it came back. If you use timed digital credentials, record the authorized access window and confirm expiration afterward.
For reservation-specific codes, use the Airbnb Key & Access Code Log. The maintenance record shows what work was assigned; the access log shows who was given the means to enter.
Audit the log periodically
Review the log for active credentials with no current holder, temporary access with no closure date, lost items without a recorded response, and former tenants or vendors still shown as active.
For broader property records, see the Property Management Binder.
Common key-control mistakes
- Tracking how many keys exist but not who has them.
- Labeling loose keys with the full property address.
- Deleting history after a replacement is issued.
- Leaving temporary vendor access open-ended.
- Writing master codes or passwords directly in the log.
- Forgetting fobs, remotes, cards, and digital credentials.
- Failing to reconcile access at turnover.
- Treating smart-lock event data as ordinary property notes without considering privacy.
Keep the log event-based and easy to audit
Record every issue, return, replacement, or revocation as its own event. Use consistent status values such as active, returned, revoked, lost, replaced, or expired. For temporary vendor access, add an expected return or expiration date and confirm closure after the work is complete.
Handle lost keys and turnover as separate events
If a key or credential is lost, record the report date, item, holder, and action taken. Keep the old entry and create a new entry for any replacement instead of overwriting history.
At move-out, compare the current log with what is physically returned or digitally revoked. This captures replacements and extra credentials issued during the tenancy and gives the next handover a clean baseline.
FAQ
Do I need a separate key log for every property?
Not necessarily, but each entry must identify the correct property and unit clearly. Separate logs are often easier to audit for small portfolios.
Should contractors be included?
Yes, if they receive a physical key, fob, remote, code, or other credential. Record issue and return or expiration.
What should I do with a lost key?
Record the loss and the action taken. Whether rekeying, fees, or other steps are required depends on the circumstances, lease, lock system, and local law.
Is a smart-lock event history the same as an access-control log?
No. Event history records activity generated by the lock. An access-control log records who is authorized, what credential they hold, and its status.