The missed-arrival scorecard for garage door callbacks
Trace missed garage door arrivals to their real cause, measure each callback’s cost, and spot communication failures before they become repeat expenses.
A callback total cannot tell you what broke
A callback count belongs beside margin, cash, and growth, but it cannot explain itself. A missed garage door arrival is an incident type, not a root cause: a route change, no access, and a safety stop need different fixes.
Missed-arrival scorecard: a weekly record that codes each incident from evidence, prices the make-good once, and shows patterns by cause.
Classify the incident before assigning blame
Use review-time facts to assign one primary cause and, if needed, one contributing factor; do not use the catch-all “communication issue.”
| Cause bucket | Qualifying evidence | Common examples |
|---|---|---|
| Dispatch control | Promised window, route changes, contact record, and update log show an internal miss | Wrong time window, late route change, no customer update, bad phone number left uncorrected |
| Customer readiness | Job notes and contact attempts show the site or responsible person was unavailable | No access, site not ready, gate locked, homeowner absent |
| Documented exception | An outside trigger is recorded, along with discovery time and a timely update | Traffic closure, weather, safety stop, prior job overrun with prompt notice |
Keep cause separate from outcome: “rebooked,” “canceled,” “discounted,” and “refunded” say what happened afterward, not why. Use unknown when evidence is missing; forced coding creates fake precision and the wrong fix. ASQ’s root-cause guidance supports using root-cause work to target process changes.
Build the incident record that makes the scorecard credible
Use one record for every qualifying incident:
- Job/arrival: Job ID, booking date, promised window, status changes and owner, actual or final no-arrival time, rebooking reason, and outcome.
- Notification: channel, send time, delivery state, reply, sender/approver, corrected contact details, and Queue Up text log history.
- Readiness: access and prep notes, site and alternate contact, and pre-dispatch confirmation.
- Exception: trigger, discovery time, customer-update time, and manager approval for a changed route or promise.
- Evidence quality: complete (times, contacts, updates, outcome documented), partial (a key fact missing), or missing (no reliable cause code).
Keep text consent and privacy fields separate from performance scoring. If you retain SMS logs, record the message type, sending number, consent source and time where needed, and opt-out or suppression status as prudent operational evidence. The FCC notes that consent rules differ for commercial and informational texts, and customers can opt out in reasonable ways. Applicable consent and retention obligations depend on the message type, sending method, and other governing rules; this is not legal advice.
Calculate the cost without fooling yourself
Price incremental make-good work, not the original job twice.
Direct make-good cost = return labor + added truck cost + incremental parts/materials + third-party charges + one customer concession + other documented make-good spend
| Input | How to calculate it | Guardrail |
|---|---|---|
| Return labor | Incremental technician, dispatcher, and manager hours × one loaded hourly rate | Do not add benefits or payroll burden again if they are already in the rate |
| Added truck cost | Incremental incident miles × one vehicle-cost method | Use mileage proxy or actual vehicle costs, never both for the same miles |
| Parts and outside charges | Actual incremental parts consumed and third-party bills | Exclude parts already included in the original job |
| Customer concession | Discount, credit, refund, or waived invoice | Count one concession once |
Do not include both a warranty reserve or accrual and the payment for the same incident in the same scorecard period.
A loaded rate can include wage and benefit costs (BLS). For truck cost, use an approved mileage proxy—such as the IRS rate—or actual costs, not both.
([TK: return hours] × [TK: loaded rate]) + ([TK: added miles] × [TK: per-mile rate]) + [TK: parts] + [TK: one concession] = [TK: direct make-good cost]
Show lost capacity separately; do not add it when it duplicates direct labor and truck time. Tag results actual, estimated, or unavailable. ASQ’s cost-of-quality framework distinguishes rework from external failures.
Put five measures on the weekly owner-GM scorecard
Show volume and dollars together.
| Metric | Formula | Review question | Owner |
|---|---|---|---|
| Missed-arrival incident rate | Incidents ÷ scheduled jobs × 100 | Did the rate move with schedule volume? | GM |
| Preventable missed-arrival rate | Approved preventable incidents ÷ scheduled jobs × 100 | Which dispatch-controlled failure is growing? | Service manager |
| Average direct make-good cost | Direct make-good cost ÷ preventable incidents | Which cause costs the most per event? | GM |
| Complete notification-history rate | Incidents with complete logs ÷ all incidents × 100 | Can we trust this week’s coding? | CSR manager |
| Rolling cause share | Incidents in each cause bucket over four weeks ÷ coded incidents over four weeks | Which cause accounts for the largest share of coded incidents? | Service manager |
Set thresholds from your own baseline and capacity, then review the largest expense, the fastest-rising cause, and the weakest evidence. Cleaner KPIs make the next miss harder to repeat and protect margin with evidence.