Property maintenance vendor management: from assignment to review

A contractor can finish the repair at noon while the property manager still believes the job is waiting to start. The resident gets no update. By the time the invoice arrives, nobody in the office has reviewed the work.

The missing step is a handoff. Property maintenance vendor management starts with a request the contractor can accept, a confirmed access arrangement, and a named manager who can approve changes. Agree on the reply you need back before the next person can act. A vendor assignment begins that exchange. Manager review finishes it.

As a management company's vendor roster grows, contractors need to know which site contact can act on a request. Establish those handoffs before adding more providers. Decide who can approve work and who checks completion. This article follows a hypothetical dishwasher repair from the first assignment through close-out. The repair details are illustrative. The aim is to show where information can go missing and how a property team can keep it attached to the job.

Before dispatch: describe the work someone can accept

“Dishwasher broken, unit 214” leaves too much for the vendor to discover by phone. A stronger job brief includes the reported symptom and when it occurs, the location, and any relevant work already attempted. Include the appliance model if staff have verified it. A guessed model number can be worse than a clearly missing one.

For this example, the resident reports that the dishwasher stops during a cycle and leaves water inside. Staff have not diagnosed the cause. The brief says that explicitly. It also identifies the manager who can answer questions and approve a change in scope.

Ask the vendor to confirm whether they can take the job and what they need before attending. If an initial visit is diagnostic, say so. Do not imply that the price or completion date is settled when the cause is still unknown.

Site information deserves the same attention as the repair description. OSHA's recommended practices for host employers and contractors emphasize communication about hazards and coordination before work begins. That is a useful principle for planning a visit; this article does not determine which legal duties apply to a particular arrangement. OSHA guidance on communication and coordination.

Use the property's process to share relevant site conditions with the people who need them. A work order should not become a repository for unrelated resident information. The vendor needs to perform the assigned work, not browse a household's financial history.

Confirm the visit separately from the assignment

After assigning a vendor, staff still need to book the visit and confirm access. Track those steps separately so the person checking the schedule can see what remains unconfirmed.

In the dishwasher example, the vendor offers Tuesday from 10 a.m. to noon. The resident cannot be available then under the agreed access arrangement and proposes Wednesday afternoon. Staff confirm the revised window with the vendor and update the shared job record. Leaving Tuesday in the schedule would create an avoidable failed visit.

Access arrangements must follow the lease and applicable requirements. A digital scheduling response should not be treated as a substitute for whatever notice or authorization the situation requires. The practical aim is to record the arrangement accurately, including any information necessary for the visit, without asking the resident to repeat it to multiple people.

Have a plan for a missed window. Who contacts the resident if the vendor runs late? Who decides whether to reschedule? The answer should be agreed before a technician is standing outside the apartment with an incomplete phone number.

Avoid sending sensitive entry credentials through broad announcement channels or a job description visible to more people than necessary. Use the property's approved access process and limit information to the intended recipient.

Give scope changes a decision path

At the diagnostic visit, the hypothetical technician identifies a failed component and proposes a replacement. The original authorization covered diagnosis. The repair needs an additional approval.

The vendor should submit enough information for the manager to decide: the finding, proposed work, cost, and what happens if the repair waits. A photograph may support the explanation, but it does not replace it. The manager should know whether the quoted amount includes the diagnostic visit already completed.

Record the decision and any limit clearly. If the manager approves the quoted repair, the vendor should not need to infer that approval from “sounds good” in a separate text chain. If the scope changes again, use the same decision route rather than letting a growing invoice become the first formal notice.

The authorization policy belongs to the property team and its vendor agreement. It may vary by urgency and cost. Set a backup approver so work does not pause indefinitely when the usual manager is unavailable. Explain what the vendor should do if they encounter an immediate hazard through the established emergency process.

This is also where a seemingly slow vendor may turn out to be waiting on management. Keep that waiting time visible. A performance review that counts every open hour against the contractor can reward the wrong behavior and miss the approval bottleneck.

A submission is a request for review

After the repair, ask for a close-out account that can answer a future question. “Fixed” is too thin. For the hypothetical dishwasher job, the vendor records the component replaced, the test performed, and whether any further work is recommended. The level of detail should match the job, without demanding a report longer than the repair.

The manager then reviews the submission against the approved scope. Check whether the described work is complete and whether an additional inspection or follow-up is needed. Reconcile the amount with the approved quote and any documented change before using it in the property's payment process.

Keep resident billing separate from vendor submission. A contractor's statement of cost does not establish whether the resident owes that amount. Responsibility depends on the facts and the applicable agreement and rules. The manager should handle that determination through the appropriate process, with supporting records.

Once the work has been reviewed, provide a clear resident update. Explain what was done and how to report if the symptom continues. If the repair is only a temporary measure, say what remains and when the resident will hear more.

How do you review a vendor invoice against the approved work?

Suppose the illustrative diagnostic visit costs $95. The vendor then quotes a part and additional labor, with the diagnostic charge remaining payable. A small review ledger keeps the comparison attached to the job:

The arithmetic identifies a question; it does not establish wrongdoing or resident responsibility for the charge. Check for an approved addition or a charge excluded from the quote. If neither explains the difference, ask the vendor to check the submission for an error.

Ask for the explanation while the job is fresh. Record the answer with the work order. If an extra item was approved in a separate conversation, bring that decision into the record. If it was not approved, resolve the discrepancy through the vendor agreement and the team's normal process.

Now examine time. The technician finished Wednesday at 3 p.m. and submitted the write-up at 4 p.m. The manager reviewed it Friday at 10 a.m. The review wait was 42 hours. Calling the entire interval “repair time” would conceal that the physical work had finished. Keeping those events distinct points the improvement toward manager review.

Review vendors using comparable work

Aggregate cost alone is a poor way to choose a contractor. A vendor assigned difficult repairs may cost more because the work costs more. A specialist may have fewer jobs and a less stable average. Look at the category and scope of work before interpreting a difference as performance.

Response and resolution measures need the same care. Check which events start and stop the clock and whether time waiting on approval or access is included. Review a few underlying work orders before drawing a conclusion from a dashboard.

A small number of resident ratings also needs context. Two ratings do not describe every completed job. Low feedback volume should remain visible rather than being converted into a confident ranking. A manager may still learn something from the comments on an individual case, especially when they describe an issue the record can verify.

Use the review to choose a practical adjustment. Clarify the scope brief if vendors repeatedly need to call for missing information. Set a review time if submissions sit untouched. Address repeated missed appointments directly with the contractor. Keep the adjustment tied to an observed problem, then check whether it helped on the next comparable job.

How Talvi handles the vendor side of a job

Talvi's vendor portal shows assigned jobs with schedule and access information. Vendors can submit a solution write-up and an optional cost quote for manager review. That submission does not itself close the work order or decide resident billing; the manager retains the close-out decision.

The vendor view also limits the information exposed for the job. It is designed around the assigned work and the vendor's own submission rather than the manager's internal billing fields. Talvi's vendor scorecards show operational measures with sample information and permission-scoped access. Staff still need to interpret those measures against the work performed.

The $395 dishwasher repair provides a useful test when you review Talvi's vendor workflow. Ask how the manager would investigate a $430 submission and tell the resident what happened. Have a second coordinator pick up the review. They should be able to find the approval history without searching the first coordinator's personal messages or asking the contractor to reconstruct it.