Every VP of maintenance has lived this sequence. A plumbing vendor confirms a Tuesday window. The resident arranges to be home. Tuesday passes without a truck in the parking lot, and nobody at the property finds out until the resident calls, frustrated, on Wednesday. The work order is now older, the resident is angrier, and a coordinator spends part of the next day rebuilding a schedule that should have held the first time.

The cost of that missed visit never appears as a line item. It shows up as backlog age, technician hours lost to chasing and rework, and resident sentiment. Tracing why no-shows persist even when qualified vendors are available points to a specific culprit: the coordination layer between the property and its vendor network.

Outside work is too big to run on informal coordination

Third-party work is not a marginal slice of maintenance. Research covering 385 communities and more than 73,000 apartment homes found that 87% of properties outsource at least part of their preventative maintenance work . Add reactive trades work (plumbing, electrical, specialty HVAC, flooring, abatement) and most portfolios depend on vendors for a meaningful share of total work order volume.

Yet in many operations, that outside work runs on the thinnest possible infrastructure: a site manager's email thread, a supervisor's cell phone, a note that says "vendor coming Thursday." Industry benchmarks show what execution looks like when coordination holds: the average work order completes in 3.88 days from creation, and 66% of work orders close within 24 hours . A vendor no-show does not just miss that baseline. It restarts the entire scheduling cycle: re-contact the vendor, re-secure a window, re-notify the resident, re-arrange access. Each restart can add days to a work order that the benchmark says should close in under four.

Delays compound at the portfolio level. Work order saturation, meaning open work orders divided by units, averages 5.98%, with 10% or less considered acceptable and 5% or less exceptional . Vendor-dependent work orders stuck in reschedule loops sit in that open count for days or weeks, quietly pushing a property from exceptional toward merely acceptable, and from acceptable toward a visible backlog problem.

The no-show is usually the symptom, not the disease

It is tempting to file no-shows under vendor accountability and stop there. Some vendors are unreliable. But the pattern behind repeated no-shows is usually a coordination bottleneck with three specific failure points.

Fragmented intake. Requests reach vendors through whatever channel is handy: a call from one property, an email from another, a text from a regional. The vendor has no single queue of your work, and you have no single record of what was requested, confirmed, or promised.

Unclear ownership. When each site coordinates its own vendors, nobody owns the confirmation step. Did anyone verify the vendor still plans to show on Tuesday? Did anyone confirm the resident granted access? When ownership is ambiguous, the answer is often "we assumed so."

Missing status context. After dispatch, the work order goes dark. The property learns about a no-show from the resident rather than from the workflow. Without live status there is no chance to intervene before the appointment fails, and no reliable record afterward of which vendor missed, how often, and why.

None of these failures is the vendor's fault alone. All three are within the operator's control.

What the ledger actually looks like

Priced honestly, a vendor no-show hits at least four cost lines.

Backlog and throughput. Every missed appointment adds a full reschedule cycle to a work order, against a baseline where two-thirds of work orders close within a day .

Coordinator and technician time. Hours spent chasing vendors, re-calling residents, and rebuilding schedules come out of a labor budget already under strain. NAA survey data shows expense levels rated a major concern across operators, with virtually all operators above 10,000 units calling expenses an extreme challenge . Larger operators are responding with internal teams focused on renegotiating vendor contracts and technology to offset growing costs , which only works if vendor performance is actually documented.

Vendor accountability gaps. Without standardized records of confirmations, arrivals, and completions, you cannot tell reliable vendors from risky ones, so pricing conversations and dispatch decisions run on anecdote.

Resident trust. The resident who took a morning off for a vendor who never arrived does not blame the vendor. They blame the property. That failed promise lands on review scores and renewal conversations, not on the vendor's ledger.

Standardize the outside work loop

Operators who run outside work well treat vendors as an extension of the team, held to the same standards. At Charles Dunn Co., where 95% of maintenance and engineering crews are contracted, the firm interviews every individual a vendor assigns to its buildings rather than letting vendors place staff unilaterally, and maintains long-standing vendor relationships built around alignment with its protocols . That is control at onboarding. Others centralize the back end: Greystar's centralized assistant managers oversee accounts payable processes such as paying vendors across several communities, part of a broader move away from property-by-property operational teams .

Federal O&M best-practice guidance points the same direction on the workflow itself. Effective maintenance management systems include outside service call and dispatch capability alongside work order generation, prioritization, and tracking . The guide's needs assessment asks pointed questions: do you have an effective way to generate and track work orders, verify the work was done correctly, and get notified on completion ? For vendor work, an honest "no" to any of those is where no-shows hide.

Consider an illustrative composite, not a documented case: a regional portfolio where each property books vendors independently. The same vendor serves six properties, misses appointments at three of them, and still gets first call at all six because no one sees the pattern. Centralize intake, confirmation, and status into one owned workflow, and the pattern becomes visible quickly. That visibility, more than any single saved reschedule, is where control over outside work starts.

Centralized execution, not another dashboard

The fix is not consolidation for its own sake, and it is not a reporting layer that tells you after the fact how many appointments failed. It is centralized execution: one standardized loop for outside work, with named ownership of confirmation and follow-up, running on top of your existing systems of record. This is where Accolade fits. It acts as the system of action connecting your property management systems to consistent vendor execution: vendor onboarding and records in one place, a centralized vendor inbox so requests and confirmations stop living in personal email, and vendor invoicing tied to the same work record, so completion and payment reconcile against what was promised and performed.

Vendor no-shows will never reach zero. But when intake, ownership, and status context are standardized across the portfolio, a no-show becomes a documented, escalated exception instead of a silent tax on throughput, technicians, and resident trust.