SNOW-ICE-SIDEWALK-HAZARD-CHECKLIST-READY
Why this deserves a worksheet
Snow and ice reports sound simple, but winter property messages can involve vendor schedules, changing weather, accessibility requests, documented injuries, municipal rules, insurance records, camera footage, owner budgets, and liability-sensitive wording. A rushed AI reply can accidentally promise a treatment time, say an area is safe, admit fault, deny responsibility, or discuss legal obligations before the manager has verified the record.
STOP AUTOMATION: do not let AI state that an area is safe, unsafe, negligent, compliant, inspected, treated, salted, cleared, liable, reimbursable, or legally required without manager/source review. Do not invent vendor ETAs, weather observations, camera findings, injury conclusions, insurance advice, accommodation decisions, fee/fine outcomes, or legal deadlines.
Copy/paste snow / ice hazard intake
Resident / property / unit: [name, property, unit]
Report type: [icy sidewalk / snowy stairs / slippery entry / parking lot / ramp / walkway / roof drip/refreeze / blocked access / fall or injury mentioned / other]
Message channel and timestamp: [portal / email / SMS / phone / in person]
Exact resident words: [paste without assumptions]
Location: [building / entrance / sidewalk segment / stairwell / ramp / lot / garage / common area]
Photos/video received: [yes/no + source]
Weather condition claimed: [resident claim only / verified source / not checked]
Immediate access/safety issue? [blocked exit / ramp issue / mobility concern / injury mentioned / emergency service access / no]
Vendor or maintenance record checked: [source + last service + next verified step if approved]
Lease/policy/municipal/insurance/legal question raised? [yes/no + manager/legal review]
Accessibility/accommodation concern raised? [yes/no + human review required]
Approved escalation owner / due time: [maintenance / manager / vendor / owner / legal / insurance]
CRM/PMS label: [snow-ice-hazard / sidewalk / winter-access / vendor-follow-up / injury-mentioned / accessibility-review]
STOP AUTOMATION until: [manager verifies site/source record, vendor status, and approved wording]Resident-safe acknowledgement snippets
Hi [Name], thanks for reporting the snow/ice concern at [location]. We logged it and are checking the site condition and maintenance/vendor record before giving a specific update.Thank you for the details and photos. I am routing this to [maintenance/manager/vendor coordinator] so we can verify the location, current condition, and approved next step. We do not want to guess about timing, responsibility, reimbursement, or safety status until the record is checked.Internal handoff: Winter hazard report for [property/location]. Type: [type]. Evidence: [photos/source]. Sensitive flags: [injury mentioned/accessibility/legal/insurance/vendor ETA]. Source records needed: [work order/vendor log/site inspection/weather note/policy]. Do not state fault, liability, safety status, treatment completion, reimbursement, or legal duties until reviewed.AI review prompt for managers
You are helping a property-management team summarize a snow, ice, sidewalk, stair, ramp, parking-lot, or winter access hazard report for internal manager review. Use only the verified fields below. Do not invent weather facts, treatment status, vendor ETAs, site inspection results, camera findings, injury conclusions, accessibility decisions, liability, legal duties, reimbursement, insurance advice, fines, or resident fault.
Return: 1) missing facts, 2) sensitive flags, 3) safe resident acknowledgement, 4) vendor/maintenance/manager questions, 5) CRM/PMS label, and 6) STOP AUTOMATION triggers before any resident-facing answer.
Verified intake:
[Paste intake fields]Fast QA before any answer goes out
- Does the draft avoid saying the area is safe, treated, inspected, negligent, compliant, or cleared unless the source record proves it?
- Does it avoid promises about vendor arrival, salt/sand, snow removal, reimbursement, insurance, fees, lease enforcement, or legal responsibility?
- Does it route fall/injury mentions, accessibility or accommodation concerns, emergency-access problems, and legal/insurance questions to a human owner?
- Does it keep the follow-up owner, due time, vendor/source record, and exact location visible?
- Does the resident get a useful acknowledgement while the source record is checked?
How this connects to the paid system
This checklist is a narrow example of the resident-message triage patterns inside Local Lead Rescue System. The broader kit helps small operators turn missed calls, portal messages, maintenance updates, owner handoffs, and resident requests into safer first replies and CRM follow-up labels.