Most vendor problems are not vendor problems; they are handoff problems. A work order that arrives without access instructions. A follow-up forgotten for a week. A status change nobody recorded. An invoice that does not match the job. Each one reads as a contractor failure but starts as an operator process failure. Good vendor coordination is mostly about what you hand the vendor and how you track the response.
Dwelon treats vendor handoffs as governed workflows instead of forwarded emails.
The complete work order
A work order is a contract of context. It should carry severity, issue summary, photos, location and access instructions, resident availability, approved spend limit, warranty notes, and a completion window, plus the permitted action and exception path. Vendors act on complete work orders without calling back to ask, and calling back is where the real time goes. Maintenance triage produces this context at intake; the coordination workflow carries it through.
The status contract
Define the statuses and who updates them: accepted, scheduled, parts on order, in progress, awaiting approval, complete, reopened. The workflow chases the missing update. A vendor who goes quiet past the expected window triggers a follow-up automatically. Residents see the right update at the right stage, and the manager sees exceptions, not raw statuses. The goal is not surveillance; it is that no job dies in silence.
The cost thresholds
Approval rules convert cost control from a negotiation into a policy. Jobs under the threshold route to approved vendors with an approved spend limit. Jobs over a selected threshold follow the configured notify, approval, or human-only path with the estimate attached. Recurring patterns, the same fault in the same unit twice, surface for a repair-versus-replace decision. The approval gate design applies the same structure to spend.
Invoice matching and the paper trail
The invoice arrives, and the workflow matches it against the work order, the approved spend, and the completion record. Mismatches surface for review instead of being paid into the void. Every action, from dispatch to approval to payment, leaves a record. The audit trail is complete because the workflow produces it as a byproduct.
Vendor network quality
Over time the record becomes the rating: average cost by trade, on-time completion, reopen rate, response latency. Renewal decisions about vendors should read that record the way renewal decisions about tenants read service history. For the STR portfolio where vendor speed compresses between bookings, see the STR back-office model.
The operator's new job
With handoffs complete, status enforced, and thresholds numeric, the operator's role becomes review: exceptions, overruns, and vendor patterns. Once per week, not per job. Coordination without micromanagement is not a management style. It is the output of a workflow that carries context and enforces visibility. Pick the trade you call most often and run one job through the full loop: complete work order, status window, invoice match. Count the callbacks you do not have to make; that number is what the workflow is worth.