Rental Move-In Key Control Log

A move-in key log should show custody and exceptions without publishing access credentials. This PortfolioRental routine covers physical keys, fobs, remotes, and other issued devices at a process level. It does not prescribe security hardware or replace lease, legal, safety, or local access requirements.

Quick Overview

Assign each access item an internal identifier that does not reveal a usable code. Record the unit reference, item type, preparation check, authorized custodian, transfer time, acknowledgement method, exception state, and closeout owner. Store signatures and resident information in the approved protected system, not in a public or broadly shared checklist.

Common Mistakes

Avoid labels such as all keys ready when the count and test are unknown. Do not place lockbox combinations, alarm codes, or credential images in the log. Another failure is treating a vendor's possession as resident transfer. Each custody change should have its own dated record and authorized purpose.

Prepare before transfer

Reconcile the planned item list against the approved turnover and access records. Test devices using the authorized method and flag uncertain batteries, damaged remotes, or unmatched labels. Resolve whether old credentials must be disabled through the responsible property or security role. The person preparing the package should not infer authorization from a calendar entry alone.

Record custody clearly

At every handoff, capture from whom, to whom, when, what item identifiers, and the associated purpose. If acknowledgement is missing, keep the state pending. When an item is lost or does not work, follow the approved incident process and avoid recording assumptions about fault.

Close the move-in record

Reconcile planned and transferred items, retain the acknowledgement in the controlled file, and assign unresolved exceptions. A completed move-in does not automatically close a missing-device issue. Review recurring discrepancies by property or item type to improve preparation without exposing access data.

Common Questions Answered

Should the log contain key numbers or access codes?

Use only identifiers approved for the operational record. Keep usable credentials in the restricted system designed for them.

What if a device fails during transfer?

Record the observed failure, provide only the authorized fallback, and assign replacement or testing. Do not mark it delivered and working.

Ready to use

Connect this routine to the property access authorization review and turnover scope acceptance. Use CISA physical security guidance as general context while relying on qualified local procedures.

Published August 31, 2026. Test the log on one authorized move-in and review whether every custody change and unresolved exception can be reconstructed.