The public classifier uses synthetic demonstration rules. In a production workflow, the score should be composed from visible factors, mapped to a response policy, and accompanied by the exact sentence or context that caused an escalation.
Hazard severity
Look for conditions that can worsen quickly or create immediate exposure: active leaks, electrical contact, gas language, entrapment, loss of heat, sewage, or blocked egress.
Resident impact
Consider whether the message describes an infant, older adult, disability, medical concern, inaccessible unit, or building-wide condition. These signals can change the response route without changing the trade.
Recurrence and spread
Repeated reports, multiple affected units, open related tickets, and a condition crossing systems or apartments should increase attention and may require broader building checks.
Example response bands
- Critical: immediate safety guidance and live first-response coordination
- High: rapid acknowledgement, assigned owner, and short escalation timer
- Medium: same-day review with resident and building context attached
- Routine: normal queue with a clear service expectation
Required explanation
- Which words or records raised the score
- What information remains uncertain
- Who should respond first and why
- What would cause the route to escalate or de-escalate
Safety boundary
A classifier cannot determine whether a condition is physically safe, replace emergency services, or authorize a contractor. Potential fire, police, or medical emergencies belong with 911; uncertain operational cases belong with a person.