What is cycle time for a maintenance vendor?

Cycle time is the average number of calendar days from the date a work order is assigned to a vendor to the date it is completed and closed. The passing threshold used by property managers and institutional clients is 5 days or fewer. Cycle time above 7 days is considered a fail and is the most common reason vendors lose accounts.

What is first-time fix rate in property management?

First-time fix rate (FTF) is the percentage of work orders completed without a return trip for the same or related issue within 30 calendar days. A rate of 80% or above is the passing threshold. Between 70–79% is at-risk. Below 70% indicates a systematic diagnostic or quality failure.

What is a good callback rate for a maintenance company?

A callback rate of 5% or below is the passing threshold for most property managers. Between 5–8% is at-risk. Above 8% is a fail. A callback rate above 10% typically triggers volume reduction discussions regardless of other performance metrics.

What survey score do property managers expect from vendors?

A survey score of 4.0 or above on a 5-point scale is the passing threshold. Between 3.5–3.9 is at-risk. Below 3.5 is a fail. Survey scores are pulled from post-service resident surveys and feed directly into monthly vendor performance reports.

What documentation do vendors need to provide for property managers?

At minimum: a before photo (condition on arrival), an after photo (completed repair), a root cause note (what was wrong and why), and a scope note (what work was performed and what materials were used). All four items must be attached at work order closeout. 95% compliance is the passing threshold.

How is vendor performance scored?

Vendor composite score = (Cycle Time score × 20%) + (First-Time Fix score × 20%) + (Callback score × 15%) + (Survey score × 15%) + (Scope and Pricing score × 15%) + (Documentation score × 10%) + (Estimate Accuracy score × 5%). Scores above 85 are in the preferred vendor range. Below 55 typically results in account loss.

How do I improve my first-time fix rate?

Implement a 10-minute diagnosis rule before starting any work. Require techs to write down the root cause before picking up a tool. Establish a scope confirmation step with the occupant before beginning work. Build diagnostic checklists for the five job types with the highest return rate.

How do I reduce my callback rate?

Implement a pre-departure test protocol: run the repaired system under real conditions for five minutes and have the occupant confirm before leaving. Set a parts quality floor — no lowest-cost aftermarket parts on units under seven years old. Build a 30-day callback root-cause log to identify patterns.

How do I improve cycle time for my maintenance company?

Stock the 25 most-replaced parts on every truck to eliminate parts-wait delays. Implement a next-step rule: before leaving any property, the tech must have scheduled the next action. Run a daily review of all work orders open more than three days.

How do I improve documentation compliance for my techs?

Define a photo and note standard for each of your top ten job types. Implement a work order closeout gate — no WO can be marked complete without required photos and notes attached. Run a weekly spot audit of five random closed WOs per tech and share results publicly.

Reference — vendorlogix KPI Framework

The seven KPIs property managers use to grade maintenance vendors

Every month, your clients pull a performance report on every vendor in their roster. These are the seven numbers on that report — what they measure, what the thresholds are, how they're scored, and what each one costs you when it's in the fail zone.

Source: vendorlogix Scoring Rubric v1.0 · vendorlogix.net · hello@vendorlogix.net

Composite score formula

Composite = (CT × 0.20) + (FTF × 0.20) + (CB × 0.15) + (Survey × 0.15)
+ (Scope × 0.15) + (Doc × 0.10) + (Est × 0.05)

All individual KPI scores run 0–100. Composite is the weighted sum, rounded to the nearest whole number. A composite of 85+ puts a vendor in the preferred range. Below 55 typically results in volume reduction or account loss within one to two review cycles.

Cycle Time

20%

First-Time Fix

20%

Callback Rate

15%

Survey Score

15%

Scope & Pricing

15%

Documentation

10%

Est. Accuracy

Work Orders Completed

Throughput & capacity indicator · Context metric, not in composite

The total number of work orders closed in the measurement period. Clients use this to gauge whether a vendor can absorb additional work or is already running at capacity. A flat or declining count signals capacity constraints or dispatch reliability problems before any other metric flags it.

What it measures

Total closed work orders in the trailing 30-day or 90-day period

Data source

Work order management system export or manual dispatch log

Why it matters

Tells clients whether a vendor has capacity for more work. A vendor with growing completed volume and strong KPIs will receive increasing allocation. Volume that is flat or declining alongside good metrics may signal staffing constraints.

Composite role

Not scored in the composite. Shown as a context metric alongside the scored KPIs.

Cycle Time

Days from assignment to close · Composite weight 20%

Pass ≤5dRisk 5–7dFail >7d

Cycle time is the single most-watched metric in maintenance vendor management. It is the most common reason vendors lose accounts — not price, not relationships, not quality. The number. Every day above the five-day threshold is another day the client considers who else to call.

Definition

Average calendar days from assignment date (when WO was dispatched to the vendor) to completion date (when WO was closed).

Scoring formula

min(100, round((5 ÷ actual_avg) × 100))
A 4.2-day average scores 100. A 7.5-day average scores 67.

Excluded from calculation

Permit-required jobs, documented client holds, client-supplied material delays. Exclusions must be documented at the time of the delay — not claimed retroactively during an audit.

Range	Status	Client response
≤ 5.0 days	Pass	Within preferred standard. No concern.
5.1 – 7.0 days	At Risk	Flagged in ops reviews. Volume may shift.
> 7.0 days	Fail	Volume reduction or reassignment likely within 1–2 cycles.

How to improve

Stock the top 25 parts — parts-wait is the most common cycle time driver and the most fixable. Identify the 25 most-replaced parts across all job types and stock them on every truck.
Next-step rule — before any tech leaves any property, they must have scheduled the next action: return date, parts ETA, or follow-up call. Nothing stays open without a scheduled next step.
Daily aging review — every morning, review every WO open more than three days. Call the tech. Get a status and a hard close date. Remove whatever is blocking it.
Category analysis — pull cycle time by job type. Two or three categories are almost always dragging the average. Fix those specifically rather than applying a blanket process change.

Time to improve: Parts stocking and next-step rule show results in 30 days. Full cycle time improvement visible in 60–90 days of data.

First-Time Fix Rate

% resolved on first trip · Composite weight 20%

Pass ≥80%Risk 70–79%Fail <70%

First-time fix rate measures whether the vendor's technicians are diagnosing correctly and completing the repair fully on the first visit. Every failed FTF is an additional truck roll the client pays for. At below 70%, clients begin questioning whether techs are diagnosing correctly — not just missing occasionally.

Definition

Percentage of closed work orders where no return trip was required for the same or related issue within 30 calendar days.

Formula

(WOs with no callback ÷ total WOs) × 100

What counts as a return trip

A new WO at the same address for the same system or component within 30 days of the original close date.

Valid exclusions

Client-caused damage documented at departure. Manufacturer warranty defect with evidence. Entirely unrelated system at the same address.

Range	Status	Score
≥ 80%	Pass	80–100
70–79%	At Risk	70–79
< 70%	Fail	0–69

How to improve

10-minute diagnosis rule — spend 10 minutes on diagnosis before picking up a tool. Write down the root cause before starting work. If you cannot write it clearly, you have not diagnosed it.
Scope confirmation — before starting any repair, state the scope to the occupant and get verbal confirmation. This eliminates scope-related returns.
Job-category checklists — identify the five job types with the highest return rate and build a diagnostic checklist for each one.
Pre-arrival protocol — review unit age, prior service history, and reported symptoms before arriving. Call the occupant to confirm access and gather context.

Time to improve: FTF improvement appears in the data after a full 30-day period of consistent execution — typically 60–90 days from implementation.

Callback Rate

Return trips within 30 days · Composite weight 15%

Pass ≤5%Risk 5–8%Fail >8%

Callback rate is the inverse of first-time fix rate, scored separately because clients track callbacks independently as quality events. A callback rate above 10% is one of the most common triggers for volume-reduction decisions, regardless of how other metrics are performing.

Definition

Percentage of completed work orders that generated a return trip for the same or related issue within 30 calendar days.

Scoring formula

max(0, round(100 − (rate × 8)))
5% rate → score 60. 10% rate → score 20. 13%+ → score 0.

Spike rule

A month-over-month increase of 4+ percentage points is flagged as an escalation trigger regardless of whether the current rate crosses a threshold.

Range	Status	Score
≤ 5%	Pass	60–100
5.1–8%	At Risk	36–59
> 8%	Fail	0–35

How to improve

Pre-departure test protocol — run the repaired system under real operating conditions for five minutes before leaving. Have the occupant confirm the issue is resolved.
Adjacent systems check — inspect what is connected to the repaired system and document condition in the WO closeout note.
Parts quality floor — set a company standard: no lowest-cost aftermarket parts on units under seven years old.
30-day callback log — log every callback with root cause. At 30 days the pattern tells you exactly which techs or job types to address.

Time to improve: Pre-departure protocol shows results in 30 days. Full rate improvement visible in 45–60 days.

Survey Score

Resident & client satisfaction · Composite weight 15%

Pass ≥4.0/5Risk 3.5–3.9Fail <3.5

Survey scores are collected from residents or clients after every service visit and feed directly into the monthly vendor performance reports. Low scores are not attributed to a single bad day — they are read as a pattern and attributed to vendor quality. In portfolio management, survey scores are tied to lease renewal analysis.

Definition

Average satisfaction rating from post-service surveys. Typically a 5-point scale, though some clients use 10-point. Scores are normalized to 5-point for comparison.

Scoring formula

min(100, round((score ÷ 5) × 100))
4.0/5 → score 80. 3.5/5 → score 70.

What drives low scores

Tech communication failures, arrival time gaps without proactive contact, site condition at departure, perceived resolution vs. actual resolution, professionalism.

Score	Status	Client read
≥ 4.0/5.0	Pass	Residents satisfied. No concern.
3.5–3.9	At Risk	Pattern of below-expectation visits. Visible in monthly reports.
< 3.5	Fail	Resident dissatisfaction flagged as a vendor quality issue.

How to improve

Three-step closeout conversation — before leaving: (1) walk the resident through what was done, (2) confirm they agree the issue is resolved, (3) let them know they may receive a survey. Techs who do this score 0.4–0.6 points higher on average.
Arrival window accountability — if running more than 30 minutes late, call the resident before the window closes. That call converts a frustration into a professional touchpoint.
Site condition standard — clean up all debris, packaging, and materials before leaving. Residents rate cleanliness explicitly and it disproportionately affects the overall score.
Low-score response protocol — any score below 3.5 triggers a same-week manager outreach to the resident.

Time to improve: Behavioral changes show in survey data within 30–60 days.

Scope & Pricing Accuracy

Work order audit sample · Composite weight 15%

Pass ≥85%Risk 70–84%Fail <70%

Scope and pricing accuracy is assessed by reviewing a sample of 10–20 closed work orders and rating each on two criteria: whether the scope of work was appropriate for the reported issue, and whether the pricing was at or below market rate. Above-market billing doesn't just cost money — it raises questions about every other invoice the vendor has submitted.

How it's assessed

Auditor reviews 10–20 closed WOs. Each is rated: scope (Appropriate / Over-scoped / Under-scoped) and pricing (At market / Below market / Above market / Significantly above). A WO passes when both scope and pricing are acceptable.

Scoring formula

(scope-ok + pricing-ok points) ÷ (WOs × 2) × 100

Sample selection

Random or callback-weighted sample. Mix of high-cost and routine repairs, at least three work types. Must include any jobs that generated callbacks.

Score	Status
≥ 85%	Pass
70–84%	At Risk
< 70%	Fail

How to improve

Build a pricing matrix — define standard labor hours and typical material costs for the 20 most common repair types. Every tech should know what a repair costs before arriving on site.
Scope approval rule — techs address the reported issue and directly related findings only. Any additional work requires dispatcher approval before proceeding.
Quarterly market comparison — compare rates on top 10 work types to local market every quarter. Adjust where above market on routine work.

Documentation Compliance

WOs with required photos and notes · Composite weight 10%

Pass ≥95%Risk 85–94%Fail <85%

Documentation compliance is the fastest KPI to fix and the one most vendors underinvest in. If a work order isn't documented at closeout, it did not happen in any dispute, warranty claim, or billing audit. Clients cannot approve, defend, or verify work that wasn't recorded.

Minimum standard (all four required)

1. Before photo — condition on arrival. 2. After photo — completed repair. 3. Root cause note — what was wrong and why. 4. Scope note — what was done and what materials were used.

How it's measured

Random sample of ≥20 closed WOs per period. Each WO is pass or fail — partial documentation is a fail. Score = % of audited WOs that meet all four standards.

Scoring formula

Raw percentage of WOs meeting all four standards, capped at 100.

Range	Status	Reality
≥ 95%	Pass	Only 1 in 20 WOs has a gap — acceptable at volume.
85–94%	At Risk	1 in 8–12 WOs closing undocumented.
< 85%	Fail	More than 1 in 6 WOs undocumented. Systemic gap.

How to improve

Define the standard by job type — for each of the top 10 job types, define exactly which photos and notes are required. Post it in the truck and in the WO platform.
WO closeout gate — no WO can be marked complete without required documentation attached. Office reviews every WO within 24 hours and kicks it back if incomplete. Enforce for 30 days. Behavior change becomes permanent.
Weekly public spot audit — pull five random WOs per tech each week, score pass/fail, share results by name at the team meeting.

Time to improve: Fastest KPI to move. Documentation reaches 95%+ within 30 days of enforcing the closeout gate consistently.

Estimate Accuracy

Bids approved without revision · Composite weight 5%

Pass ≥85%Risk 75–84%Fail <75%

Estimate accuracy measures what percentage of submitted bids are approved without requiring revision. Every revision request adds days to the approval cycle and signals that the vendor's estimates require management overhead. At below 75%, more than one in four bids is generating friction before approval.

Definition

Percentage of submitted estimates that were approved without any revision or resubmission required.

Formula

(approved without revision ÷ total submitted) × 100

What counts as a revision

Any change to line items, pricing, or scope before approval. A clarifying question without a price change is borderline — auditor judgment required.

Range	Status	Score
≥ 85%	Pass	85–100
75–84%	At Risk	75–84
< 75%	Fail	0–74

How to improve

Never estimate before diagnosis is complete — most scope-change revisions come from estimating before the problem is fully understood.
Use the client's format — ask every active client if they have a preferred estimate format and use it. Format revision requests stop immediately.
Line item everything — labor (hours and rate), materials (itemized), permit fees, disposal — each on its own line. Never use "miscellaneous."
Read-as-approver check — before submitting, read the estimate as if you are the person who has to approve it. Answer any questions it raises before submitting.

Composite score ranges and what they mean

ScoreStatusClient response

85–100 Preferred Vendor receives increasing volume allocation. Relationship expanding. The vendors at this level are the ones property managers call first when new work opens.

70–84 Acceptable Volume is stable but not growing. One or two KPIs in the at-risk zone. The client is comfortable enough to keep the vendor but not confident enough to expand the relationship.

55–69 At Risk Volume may already be softening. Client is watching closely. If this range persists across two review cycles, a reallocation decision has likely already been made internally.

Below 55 Critical Multiple KPIs in fail zone. Volume reduction or account loss is likely within one to two review cycles. Immediate intervention required.

Find out where you actually stand.

The vendorlogix readiness audit scores your operation against these thresholds using your actual work order data. You'll see your composite, your gaps, and the exact priority order for moving the number.

Request an audit →