Resident Water Leak and Emergency Access Checklist for Property Managers

Use this before sending any AI-assisted resident reply

STOP AUTOMATION: do not send, summarize, promise entry, authorize a vendor, mention credits, assign blame, or describe habitability/insurance outcomes until a manager has checked emergency policy, entry-notice rules, source records, photos, shutoff status, vendor availability, and local/legal review requirements.

Do not invent whether the condition is an emergency, whether entry is authorized, or whether a resident must stay/leave.
Do not promise repair times, remediation scope, rent credits, insurance coverage, hotel reimbursement, deposits, or liability outcomes.
Do not let AI diagnose the cause of a leak; route source, safety, and damage questions to the approved maintenance/manager path.

Source card fields

Resident / unit / channel: resident name, unit, timestamp, official channel, callback number, and whether the resident reports active water, standing water, ceiling bulge, electrical risk, or access issue.
Emergency access source: lease/emergency-entry policy, notice rule, attempted contact log, authorized staff/vendor, key/lockbox method, and who approved entry.
Water control status: water source if known, shutoff attempted, common-area or unit-specific issue, adjacent units affected, and utility/vendor ticket reference.
Evidence: resident photos/videos, maintenance photos, location, time, severity notes, prior work orders, and any owner/insurance-sensitive documentation path.
Repair and resident update owner: vendor/maintenance dispatcher, manager review, next allowed update time, temporary mitigation, and what cannot be promised yet.
CRM label: water_leak_active, emergency_access_review, vendor_dispatch_pending, damage_claim_review, or resident_update_needed.

Copy/paste resident-safe snippets

Active leak acknowledgement

Thanks for reporting this. We’re treating the water issue as time-sensitive and will verify the source record, access path, and maintenance/vendor routing before promising timing or scope. If water is still actively entering the unit or you see electrical risk, reply through the official channel now and follow any posted emergency instructions while the manager reviews the next step.

Emergency access / entry update

Before we confirm entry or vendor timing, we need to verify the emergency-access policy, contact attempts, approval owner, and entry method. We’ll keep the update source-backed and avoid promising access, completion time, credits, or damage outcomes until the manager/vendor record is confirmed.

Damage, credit, or insurance-sensitive question

We received your note about possible damage. Please share photos through the official channel if you have not already. The manager will review the maintenance record and documentation path before any statement about cause, responsibility, credit, reimbursement, or insurance-sensitive next steps.

AI audit prompt

Review this draft resident reply for water-leak, flooding, emergency-access, repair-timing, damage, credit, reimbursement, insurance, or habitability risks. Flag invented promises about entry authority, vendor arrival, completion time, cause, liability, credits, alternate housing, insurance coverage, or safety conclusions. Rewrite it as a source-backed acknowledgement with manager/vendor review, resident-safe evidence request, and STOP AUTOMATION guardrails.

Why it connects to Local Lead Rescue

Local Lead Rescue System includes practical intake, follow-up, CRM-label, and human-review patterns for local-service and property-management teams. This free worksheet is a narrow example of the same source-card approach for high-risk resident maintenance messages.

See Local Lead Rescue System Start with the free missed-lead checklist