The Work Order That Took Four People and Six Days to Close

A tenant submits a repair request on Monday morning. By Friday afternoon, the work order is closed in the PMS. In between: a coordinator reads and classifies the request, identifies a vendor, contacts them, confirms availability, notifies the tenant, follows up when the vendor is running late, logs the completion, reviews the invoice, and closes the record.

Four different people touched that work order (the tenant, the coordinator, the vendor, the coordinator again for invoice review). Six days elapsed. Most of those days were waiting — for responses, for confirmations, for someone to take the next step.

The repair itself took two hours.

The Work Order Lifecycle

Understanding where automation helps requires mapping the full lifecycle. A standard work order has eight stages:

1. Tenant submission
2. Triage and urgency classification
3. Trade identification and vendor selection
4. Dispatch and vendor confirmation
5. Tenant notification with scheduled window
6. Work completion and documentation
7. Invoice review and processing
8. PMS closure with full record

In most PM operations, stages 1 and 8 are automated (tenant portal submission; PMS logging when someone manually closes the record). Stages 2-7 are largely manual. That's where the six days go.

Automating Stages 2-4: Triage, Classification, Dispatch

These three stages represent the highest concentration of coordinator time and the most repeatable work. The logic is consistent: read the description, assign urgency, identify trade, select vendor from pool, send dispatch.

AI triage systems handle this automatically. The output of stage 2 (urgency classification and trade identification) feeds directly into stage 3 (vendor selection from a pre-configured pool) and stage 4 (automated dispatch with job details). For routine work orders — which represent 70-80% of the volume — no coordinator action is required to reach a dispatched state.

The coordinator receives a notification when dispatch is complete, not when it needs to happen.

Stage 5: Tenant Notification

Once a vendor confirms availability, the tenant needs to know when someone is coming. This is routine information delivery — the unit number, the vendor name, the scheduled window. It doesn't require judgment. It requires access to the dispatch data and a message template.

Automated tenant notification means the tenant hears within minutes of vendor confirmation, not hours. For tenants who submitted the request at night and are waiting to hear what's happening, this is a significant experience improvement.

Stage 6: Completion Documentation

Completion documentation has historically required either trusting vendors to log completion accurately or having a coordinator follow up. Neither is reliable at scale.

Modern dispatch systems require vendors to check in via app at the start of a job and upload photos and a completion note at the end. The system doesn't close the work order until those requirements are met. This creates accountability without requiring a coordinator to monitor each job individually — and creates a photo record for every completed work order, which matters for security deposit documentation and owner reporting.

Stage 7: Invoice Processing

Invoice review is where the automation usually stops in most PM operations — and where it shouldn't. The basic review of an invoice is a rules-based task: does the line-item total match the approved work order? Does the labor rate match the vendor's contracted rate? Are there charges for work that wasn't authorized?

AI invoice review can flag exceptions — invoices that don't match expected amounts, vendors billing for unapproved work, patterns of unusual charges — for human review, while processing clean invoices automatically. This doesn't require removing human judgment from the process; it requires applying human judgment only to the 15-20% of invoices that actually warrant it.

The Exception Handling Layer

End-to-end automation doesn't mean zero human involvement. It means human involvement only for exceptions. What constitutes an exception worth flagging:

• Tenant disputes the work or requests a callback inspection
• Invoice exceeds a defined threshold or doesn't match the work order
• Vendor fails to confirm or doesn't show up
• Completion documentation reveals an underlying issue requiring further assessment
• Emergency escalation requiring judgment about scope or tenant situation

In a well-configured system, exceptions represent a small fraction of total work order volume. The coordinator's role shifts from processing every work order to resolving the ones that genuinely require them.

The Documentation That Makes the Rest of Your Job Easier

The complete timestamp trail from an automated work order lifecycle has value beyond the individual job. Across a year of work orders, you have data on vendor response time, job duration, invoice amounts by trade, callback frequency by vendor, and maintenance frequency by unit or property. This is the operational analytics layer that manual management can't generate — and it changes how you make vendor, maintenance, and capital planning decisions.