A reliable dispatch workflow does not send every ticket straight to a contractor. It decides who must act first, what that person needs to confirm, and what evidence must return before the manager can approve the next action.
Super-first route
Use the building contact to confirm resident access, isolate the affected area, photograph conditions, and report whether a licensed trade is needed. This is useful when the reported condition is urgent but the exact scope is still unclear.
Direct trade route
Use a preferred licensed vendor when the failure and trade are already known, such as a boiler shutdown or a confirmed electrical fault. The packet should still name the on-site contact and define the required status update.
Dual-response route
Water near electrical equipment may require the super to secure access while plumbing and electrical support are prepared together. The approval view should explain why both trades were selected instead of presenting a silent score.
Minimum dispatch packet
- Property, unit, resident contact, and access constraints
- Observed condition, hazard language, photos, and source
- Assigned super, selected trade, vendor ETA, and backup route
- Required acknowledgement, arrival update, and completion evidence
Manager approval record
- Why this route was chosen
- Which source and portfolio rules were checked
- Who approved the tenant, super, and vendor messages
- When the incident escalates if no response is received
Operating boundary
The workflow should prepare and prioritize the route, not hide it. Emergency language, unavailable contacts, conflicting records, or an out-of-policy vendor should stop automation and present a clear exception for human review.