Vendor oversight resource

Property Vendor Review Checklist

A vendor review should compare a written promise with documented delivery, current property needs, and the cost of correcting or changing course.

By · Publisher: TRUSTPOINT STRATEGIC SOLUTIONS Published Updated

Decision area: Vendors and management selection

Illustrative scene: Property leaders reconciling a vendor contract, invoice, and service record
The core comparison

Scope, delivery, evidence, and consequence.

Frustration is a signal, not a finding. Start with the contract and turn concerns into specific, dated examples that can be checked against service records, invoices, communications, and property conditions.

A fair review protects both the property and the vendor relationship: it shows whether the issue is an unmet obligation, an unclear scope, an internal approval delay, a change in property needs, or a combination of these factors.

ScopeWhat was promised
ProofWhat was delivered
DecisionWhat changes now
Vendor scorecard

Measure what the property actually needs.

Contract alignment

  • Current agreement, amendments, renewal and notice dates
  • Defined deliverables, exclusions, frequency, and service territory
  • Required insurance, licenses, compliance, and reporting
  • Change-order and approval process

Service evidence

  • Work orders, inspections, logs, photos, and completion dates
  • Response and resolution times for priority issues
  • Quality checks, deficiencies, callbacks, and recurring failures
  • Communication record and escalation history

Financial discipline

  • Invoice-to-scope comparison and pricing schedule
  • Approved changes, allowances, credits, and out-of-scope work
  • Budget impact, forecast, and outstanding commitments
  • Comparable proposals when a market test is appropriate

Decision outcome

  • Corrective plan with service standard and deadline
  • Renewal, renegotiation, competitive bid, or transition path
  • Responsible owner and communication plan
  • Next formal performance review date
Review sequence

From concern to a defensible decision.

  1. Define the concernWrite the issue in observable terms: missed frequency, unacceptable quality, delayed response, invoice mismatch, or incomplete documentation.
  2. Check the obligationLocate the specific contract requirement, service standard, price term, exclusion, or approval condition.
  3. Collect the recordAssemble examples across a meaningful time period; include the vendor’s response and internal constraints.
  4. Assess materialityPrioritize safety, asset protection, resident impact, cost, recurrence, and ability to correct before deciding.
  5. Set the remedyAgree on measurable corrective actions, documentation, owners, dates, and escalation if performance does not improve.
  6. Re-evaluateReview proof at the agreed date, then decide whether the remedy, renewal, or transition path is justified.
Avoidable blind spots

Four errors that weaken vendor oversight.

Reviewing only the invoice

An invoice is not proof that scope, quality, frequency, or outcome was delivered. Compare it with the agreement and service record.

Using isolated examples

One poor event may matter, but patterns across dates, locations, conditions, and responses make a review more reliable.

Ignoring internal dependencies

Delays can arise from access, approvals, funding, site conditions, or unclear instructions. Account for these without excusing unmet commitments.

Waiting until renewal

Document performance throughout the term. Early correction creates options and avoids a rushed, poorly evidenced renewal decision.

← Return to all property insights

Working checklist

Vendor performance evidence checklist

Use this during the contract term and before renewal. Record a dated example for every material concern and give the vendor a fair opportunity to respond.

These rows define suggested controls, not completed property findings. Interpret each check against your actual property records, responsible role and acceptance evidence. See the review instructions and reuse terms.

18 checks shown

Vendor performance evidence checklist · October 18, 2026
Review areaCheckEvidence to requestDecision question
Contract Current scope Signed agreement amendments deliverables and exclusions Which obligation applies to the concern?
Contract Service cadence Required frequency seasonality and missed visits Was the agreed cadence met?
Contract Response standard Priority definitions response and resolution expectations Was the issue escalated under the right standard?
Contract Renewal window Expiry notice period and decision date When must the board act?
Contract Price terms Base fee escalation unit prices and allowances Which charge is contractually supported?
Delivery Work record Dated tickets logs photos and completion notes What was actually performed?
Delivery Quality inspection Deficiency findings rework and acceptance evidence Did the work meet the stated outcome?
Delivery Recurring failures Repeated location issue or callback history Is the remedy treating the root cause?
Delivery Resident effect Complaints service interruption and communication record What impact needs attention?
Delivery Vendor response Explanation corrective proposal and supporting evidence Has the vendor had a fair chance to respond?
Finance Invoice match Invoice line scope approval and work record Which charge cannot be reconciled?
Finance Open commitments Approved extra work credits and disputed amounts What cost remains uncertain?
Finance Market comparison Comparable scope qualifications and total cost Would a market test improve the decision?
Risk Coverage record Current certificate and contract insurance requirement Is required coverage documented?
Risk Safety controls Incident reports site rules and corrective action What safety issue needs escalation?
Risk Dependency Single provider exposure access and handover needs Can service continue if the vendor changes?
Decision Corrective plan Standard owner due date and proof of completion What measurable improvement is required?
Decision Renewal outcome Renew renegotiate bid or transition with rationale What decision best protects the property?
Working method

Choose the response that fits the evidence

An exception should lead to a proportionate action.

For an isolated documented miss, a corrective action with owner, deadline, and verification may be enough. For recurring failures, compare logs, work orders, site observations, resident impact, invoices, and contract service levels over a defined period. Distinguish poor execution from an unclear scope or unrealistic schedule before assigning fault.

If performance cannot be restored, evaluate replacement timing, continuity risk, notice requirements, and the handover of keys, records, inventory, and open work. The vendor contract renewal tracker helps preserve options before a notice window closes; the bid comparison matrix supports a fair comparison when competition is appropriate.

Need a neutral vendor or contract review?

Discuss your situation
Hypothetical worked example

An invoice repeats the contracted frequency

A fictional supplier bills for the agreed service frequency, but the service log has missing dates. The invoice establishes a claim for payment rather than proof of each visit.

Original fictional example · no completed client assignment or property inspection is represented.

From available records to a bounded decision
Record to obtainReview question or calculation
Executed service scheduleReconcile service dates to the agreed scope
Visit and acceptance recordsAsk for the missing evidence
Invoice period and disputed itemsDocument uncertainty and obtain advice for contractual payment treatment

Useful working output: A service-evidence exception with a retrieval owner and resolution path.

Adapt the record request to authorized access, governing documents and the actual property. The example does not verify any unknown input or replace a professional conclusion.

Property Invoice Approval and Payment Controls · More vendors and management selection examples

Before acting on this guide

Set the review boundary and the acceptance test.

When to use it

A supplier delivers work under a recurring agreement.

What the evidence does not prove

Do not use a paid invoice as proof of accepted service.

What to verify before acceptance

Compare agreed scope, service evidence, exceptions and corrective commitments before approving the next commercial step.

Original proposed coordination checks · adapt to authorized access, the actual obligation and the appropriate professional review. These are not findings about your property.

Follow the related handoff workflow · Read the review definitions

Put the guidance to work

Match payment to the service that was purchased

Sample an invoice against the approved scope, location, frequency, attendance record, inspection result, and any authorized change. A signed invoice does not prove the contracted work was delivered.

Assign one internal owner for each contract. Maintain a deficiency log with the relevant clause, dated evidence, vendor response, remedy, and verification rather than relying on informal complaints.

Review repeated exceptions before renewal and escalate safety, insurance, licensing, or access issues to the relevant qualified reviewer. Record whether a gap belongs to the vendor or the property’s own oversight process.

What evidence should support a vendor invoice?

Use the executed scope, authorized changes, service dates and locations, completion evidence, and relevant inspection results. Resolve missing or conflicting support through the contract owner before the payment decision.

Apply the next operating control

Find checklists and data definitions · Explore vendors and management selection

Read an operational indicator with its evidence

An indicator should define its unit, period, source and responsible reviewer.

Scroll horizontally to read all columns.

Decision guide
CriterionWhat to checkPractical implication
VarianceSeparate changes in price, volume, timing and service scope.A budget variance alone does not identify waste or explain performance.
CompletionDistinguish work reported complete, evidence received and acceptance confirmed.Closing a task in a system does not itself establish that the required result was delivered.