A prepared working record
A draft work item with the original request, known details, missing information, and a named property-team reviewer.
Property management / A practical workflow
Prepare a non-emergency maintenance work item
A resident’s message describes a dripping faucet but omits the unit. The team needs the missing detail before assigning the work.
From input to handoffThe source stays
The source stays
with the work.
One possible workflow, with the preparation and review responsibilities made clear.
- 01 / The starting point
The original request, agreed property and unit references, permitted contact details, and the existing non-emergency intake rules.
- 02 / The right context
Match the property, flag the absent unit, and prepare a clarification draft. Potential emergency language takes the existing escalation path rather than waiting for ordinary classification.
- 03 / Prepared for review
A draft work item with the original request, known details, missing information, and a named property-team reviewer.
- 04 / A person decides
The property team confirms urgency, access arrangements, vendor assignment, and resident messages before action.
Tangible work
What the next person receives.
A clear review route
The property team confirms urgency, access arrangements, vendor assignment, and resident messages before action.
An agreed scope
This is not an emergency service. Emergency instructions must direct residents to the appropriate existing channel; AI triage cannot guarantee detection or safe response.
Agree what good looks likeA useful result
A useful result
can be checked.
The acceptance decision
A request that mentions water near electrical equipment surfaces that signal and the existing urgent escalation route for the property team.
Include the difficult case
Try a message first describing a minor leak, then mentioning water near electrical equipment. The ordinary draft must not hide that signal; the property team needs its existing urgent escalation route surfaced.
Keep the scope clear
This is not an emergency service. Emergency instructions must direct residents to the appropriate existing channel; AI triage cannot guarantee detection or safe response.
How we validate the work ↗A first conversationBring the job.
Bring the job.
We’ll shape the brief.
Start with a general outline of this workflow and the team that owns it.
Plan this workflow ↗Three useful questions
Which non-emergency request type and intake channel should the first scope cover?
How does your team confirm the property, unit, contact details, and access arrangements?
What existing escalation route should be surfaced when a message suggests urgency?
A few useful answers
Before we begin.
What does the reviewer receive?
A draft work item with known details, missing information, and a reviewer.
Who reviews the result before anything changes?
Property-team reviewer.
What stays outside this scope?
This is not an emergency service. Emergency instructions must direct residents to the appropriate existing channel; AI triage cannot guarantee detection or safe response.
Which difficult case do we test first?
Try a message first describing a minor leak, then mentioning water near electrical equipment. The ordinary draft must not hide that signal; the property team needs its existing urgent escalation route surfaced.
How do we know it works?
A request that mentions water near electrical equipment surfaces that signal and the existing urgent escalation route for the property team. Agree this acceptance check before work starts.