Self-Guided Showing Security Checklist for Property Managers
A practical checklist for scheduling, identity verification, temporary access, audit trails, incident handling, and human oversight in self-guided tours.
Secure self-guided showing is a coordinated workflow, not a lockbox feature. Identity, time-bound access, property readiness, communication, and an audit trail must work together.
Define eligibility for the showing workflow
Before offering a self-guided tour, document which properties and time windows are appropriate for unattended access. Consider occupancy, building rules, local requirements, staff coverage, known maintenance conditions, and whether a property has a safe and unambiguous entry path.
Keep showing-access verification separate from rental eligibility decisions. The purpose of an identity or access step should be clearly disclosed, limited to securing the visit, and reviewed with qualified counsel for the markets where you operate.
Before the visit
- Confirm that the listing, unit, address, availability, and showing instructions match.
- Collect only the information required for the disclosed showing and access purpose.
- Use an appropriate identity-verification process before issuing access when your policy requires it.
- Generate a unique, time-limited code for the scheduled visitor rather than sharing a reusable code.
- Set the code window narrowly enough to limit exposure while allowing reasonable arrival variance.
- Send safety, parking, entry, occupied-area, and support instructions before the appointment.
During the visit
- Record code issuance and access events in the same prospect and property history.
- Provide a clearly visible support channel for entry problems and urgent conditions.
- Avoid exposing master codes, staff-only notes, alarm details, or information about other occupants.
- Use escalation rules for repeated failed entry, access outside the scheduled window, or a reported safety issue.
- Make the exit and lock-up instructions as clear as the entry instructions.
After the visit
- Expire access automatically; do not depend on staff remembering to revoke it.
- Confirm whether the visit occurred before starting the appropriate follow-up.
- Keep a searchable record of the prospect, property, scheduled window, code lifecycle, and access result.
- Route damage, lock, safety, or unauthorized-access reports to a defined incident owner.
- Review failed and unusual access patterns regularly and update the workflow when a pattern repeats.
Questions to ask a smart-access vendor
- Can each prospect receive a unique code with a precise start and expiration time?
- Does access continue to work if the property has unreliable internet service?
- Which events are logged, how quickly do they appear, and how long are they retained?
- How are lost devices, compromised codes, dead batteries, and emergency access handled?
- Can the access event stay attached to the same lead, tour, and property record?
- Which roles can issue, view, revoke, or override codes?
Treat security as an operating system
A lock can control a door, but it cannot decide whether the surrounding process is safe. Property managers need a repeatable system that connects disclosure, scheduling, verification, code issuance, visit support, expiration, follow-up, and audit history. Review that system after incidents and near misses, and keep a human escalation path available throughout the visit.