Tenant Lockout and Access Request Checklist for Property Managers

When to use this

Use this when a resident reports being locked out, missing a key/fob, needing a gate or door code, requesting emergency entry help, asking someone else to pick up access credentials, or disputing an access/lockout fee. The goal is not to guess the answer; it is to confirm policy, identity, safety, ownership, and after-hours routing before sending a promise.

Marker: TENANT-LOCKOUT-ACCESS-REQUEST-READY.

Copy/paste lockout/access triage card

Resident / property / unit:
Portal, phone, SMS, or email thread link:
Request received at:
Exact resident request, pasted without rewriting:
Access issue type: [lockout / lost key / fob / gate code / door code / package room / parking gate / guest access / after-hours / other]
Urgency/safety claim:
Identity verification path allowed by policy:
Lease / house rule / access policy checked:
Fee or deposit source checked:
Approved after-hours vendor or manager path:
Access credential involved: [physical key / fob / code / smart lock / vendor lockbox / none]
Who may receive access? [resident only / authorized occupant / approved proxy / manager review needed]
Known verified facts:
Unknowns that must not be guessed:
Resident-safe first reply needed? [yes/no]
Owner/team to route to: [manager / leasing / maintenance / security / locksmith/vendor / legal/accounting]
Next-check due time:
CRM / PMS label: lockout_request / access_device_issue / identity_review / after_hours_access / fee_review / manager_approval_needed
STOP AUTOMATION if: identity is unverified, emergency/safety risk is claimed, entry rights are unclear, police/security is involved, a minor/vulnerable resident is mentioned, access is requested for a third party, fees/deposits/refunds are disputed, or lease/legal notice language is needed.

Resident-safe reply snippets

1. Acknowledge and route without promising entry

Hi [Name], thanks for contacting us. We logged this as [ticket/thread]. Because this involves access to the property or unit, we need to verify the approved process before promising entry, codes, keys, fobs, fees, or timing. We are routing it to [manager/team] and will update you by [time/date].

2. Identity/source details needed

Hi [Name], to route this safely, please use [approved identity/process channel] and include [approved details]. We cannot send codes, keys, fobs, or lockout instructions from an incomplete message.

3. After-hours or safety-sensitive request

Hi [Name], this request has been logged. If this is an active emergency or safety issue, use [approved emergency channel] immediately. For non-emergency lockout/access help, we are checking the approved after-hours process before confirming options, fees, or timing.

4. Fee, refund, or policy dispute

Hi [Name], I can confirm we received the access/lockout question. A manager must review the lease, access policy, and account/source record before anyone promises a fee waiver, refund, deposit change, access exception, or third-party pickup approval.

AI review prompt

You are helping a property manager triage a tenant lockout or access request. Use only the verified source notes below. Do not invent identity verification, lease terms, emergency status, access rights, fob/key availability, vendor ETA, fee waivers, refunds, third-party pickup approval, lockbox/code instructions, legal notice language, or security/police guidance.

Return: (1) access issue type, (2) verified facts, (3) unknowns, (4) resident-safe acknowledgement, (5) owner/team to route to, (6) next-check due time, and (7) STOP AUTOMATION triggers.

Source notes:
[Paste resident message, lease/access policy excerpt, access-device log, approved after-hours process, manager decision, and vendor/security notes if any]

Human review rules

• STOP AUTOMATION: do not send AI-written lockout/access replies when identity, emergency status, entry rights, fees/refunds, legal/security issues, third-party pickup, or after-hours vendor approval is unclear.
• Do not invent: gate codes, fob status, key availability, vendor ETA, manager approval, locksmith coverage, fee waivers, refund eligibility, lease rights, access exceptions, or legal/security instructions.
• Keep the official channel: document the request, verified identity path, source policy, assigned owner, next-check due time, and final resident update in the PMS/CRM.