When to use this
- A resident reports a dark parking lot, walkway, stairwell, hallway, garage, mailbox area, gate, or entry path.
- Someone reports a pothole, lifted concrete, broken curb, loose mat, wet area, uneven step, or trip/fall risk.
- A vendor ticket or work order needs source details before the manager promises a fix date or emergency dispatch.
- An AI draft is about to mention liability, injury status, rent credits, legal duties, security risk, police action, or reimbursement without verified source records.
Copy/paste source card
PARKING LOT LIGHTING / TRIP-HAZARD SOURCE CARD
Property / building / community:
Reported by:
Contact channel:
Date and time reported:
Exact location: [parking lot / garage / sidewalk / curb / stairs / hallway / entry / gate / mailbox / other]
Issue type: [light out / flickering / dark zone / pothole / uneven surface / loose mat / wet area / debris / other]
Photo/video/source attached? Y/N/Unknown
Injury, fall, threat, vehicle damage, or security concern mentioned? Y/N/Unknown
Immediate access/safety route affected? Y/N/Unknown
Prior reports or open work order? Y/N/Unknown
Vendor/maintenance ticket ID:
Vendor status verified? [not assigned / requested / scheduled / onsite / completed / unknown]
Resident-safe acknowledgement sent:
Manager/legal/insurance review needed? Y/N/Unknown
CRM label: lighting_outage / trip_hazard / common_area_safety / vendor_ticket_needed / injury_or_claim_review / owner_review / monitor_until_closed
Next human review step:
STOP AUTOMATION guardrails
- STOP AUTOMATION if injury, fall, vehicle damage, threats, police reports, insurance, legal claims, accessibility, habitability, or security concerns are mentioned.
- Do not promise repair timing, vendor arrival, safety status, rent credits, liability, reimbursement, enforcement action, or emergency dispatch unless the manager supplied the approved wording.
- Do not diagnose cause, blame residents/vendors, or say an area is safe from photos or an AI summary alone.
- Do not publish or share private resident, license plate, camera, access-code, medical, claim, or insurance details in AI tools.
- Use NEEDS MANAGER REVIEW if the source card lacks exact location, photo/source proof, vendor status, or escalation owner.
Resident-safe acknowledgement snippets
Lighting outage reported
“Thanks for reporting the lighting issue at {location}. We logged it for review and will verify the exact location and maintenance/vendor status before giving a repair update.”
Trip hazard reported
“Thanks for flagging this. We logged the common-area concern at {location} and are routing it to the property team for review. If there is an immediate safety emergency, please contact the appropriate emergency service directly.”
Photo/source request
“If you can safely send a photo of the area and the nearest building/parking marker, that can help us route the work order. Please do not put yourself in an unsafe position to take photos.”
Vendor ticket pending
“We have the report and are checking vendor/maintenance status. We do not want to guess at timing before the responsible team confirms the next step.”
AI review prompt
You are helping a property-management team review a parking-lot lighting outage or trip-hazard report before sending a resident reply. Use only the source card below. Draft a short acknowledgement that confirms receipt, asks only for safe missing details, and routes manager review when needed. Do not invent repair timing, vendor status, safety conclusions, liability, rent credits, legal advice, insurance outcomes, emergency status, resident identity, or camera/security details. If a STOP AUTOMATION rule is triggered, output NEEDS MANAGER REVIEW first.
Source card:
[PASTE SOURCE CARD]
CRM labels and follow-up metrics
- lighting_outage: exterior/interior common-area lighting issue needs work-order tracking.
- trip_hazard: physical surface or obstacle report needs location/source proof and manager review.
- common_area_safety: shared area may affect resident access, accessibility, or security perception.
- injury_or_claim_review: do not use AI autoresponse beyond acknowledgement; route to manager/legal/insurance process.
- monitor_until_closed: check vendor completion, resident update, and repeat reports before closing.
Weekly metrics to watch: report-to-acknowledgement time, work-order creation time, repeat reports by location, vendor completion proof, unresolved safety labels, and resident follow-up completion.
Product signal: if common-area safety content earns clicks, replies, or reuse, add a “common-area safety source card” mini-pack to Local Lead Rescue for lighting, trip hazards, access, snow/ice, camera requests, and vendor closeout updates.