Use this before sending any AI-assisted resident reply
STOP AUTOMATION: do not send, summarize, fine, threaten removal, approve a grill, interpret fire code, or promise inspection/enforcement outcomes until a manager has checked the lease/addendum, community rules, local fire-code source, notice requirements, photo/evidence, accommodation/legal review, and approved resident communication path.
- Do not invent whether a grill, smoker, fire pit, propane tank, charcoal device, or outdoor cooking setup is allowed.
- Do not promise fines, towing/removal, lease violations, inspection timing, refunds, credits, or emergency response outcomes.
- Do not frame a resident as unsafe or noncompliant until the source record, photos, policy language, and manager/legal review path are confirmed.
Source card fields
- Resident / unit / location: resident name, unit, balcony/patio/common-area location, timestamp, channel, and whether the issue involves propane, charcoal, electric grill, smoker, fire pit, storage, smoke, odor, or visible flame.
- Policy and code source: lease clause, house rules, HOA/building rule, local fire-code/fire-marshal source, insurance or building restriction, and last approved resident notice wording.
- Evidence and inspection path: resident report, staff photo, inspection note, vendor/security report, prior warning, and whether any emergency or fire department contact exists.
- Resident-safe notice owner: manager/legal reviewer, approved notice template, allowed deadline/removal wording, exception/accommodation review path, and who may answer follow-up questions.
- Fee / violation / removal review: approved fee/fine policy, cure period, documentation requirement, owner/manager approval, and what cannot be promised or threatened yet.
- CRM label:
balcony_grill_review,fire_code_notice_needed,resident_policy_question,inspection_photo_pending, ormanager_legal_review.
Copy/paste resident-safe snippets
Initial acknowledgement
Thanks for reaching out about the balcony/patio grill question. We need to verify the lease/community rule, any fire-code or building-source requirement, and the approved notice language before confirming whether a device is allowed, must be moved, or needs manager review.
Possible violation / inspection notice
We’re reviewing the source record and any photos/inspection notes before sending a formal notice or promising enforcement timing. The update will be based on the approved community policy and manager review, not an AI interpretation of fire code or lease language.
Resident asks about fines, removal, or exceptions
Before we answer about fees, removal, exceptions, or next steps, the manager will confirm the applicable source record and review path. We do not want to guess about fire-safety rules, lease outcomes, credits, penalties, or accommodations without the approved source.
AI audit prompt
Review this draft resident reply about a balcony grill, patio fire source, smoker, propane/charcoal device, fire-code question, lease violation, fine, removal, or exception request. Flag invented claims about code compliance, allowed devices, emergency risk, fees, cure periods, inspections, legal outcomes, or accommodation decisions. Rewrite it as a source-backed acknowledgement with manager/legal review, approved policy references, resident-safe wording, 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 policy-sensitive resident notices.
See Local Lead Rescue System Start with the free missed-lead checklist