Guides
Moving Company Quality Control: Four Monthly Sources
Moving company quality control is a monthly audit of four sources: ride-alongs, surveyed-to-actual hours, claims, and post-move callbacks.
What to take away
- Moving company quality control is measured after the fact from four sources: the ride-along, the variance between surveyed and actual hours, the claims ledger, and the post-move callback.
- Reviews are the least useful of the available signals. They arrive late, they are written by the angriest and the happiest, and they say nothing about the jobs in between.
- The audit is run monthly and by crew lead, because quality in this trade is a property of the crew that showed up, not of the company name on the truck.
- Fix the estimator before fixing the crew. Most "crew" problems are surveys that missed the stairs.
The four sources
| Source | What it measures | How often | Who runs it |
|---|---|---|---|
| Ride-along scorecard | What the crew actually does at the door, on the ramp, and at placement | One job per crew lead per month | Owner or operations manager |
| Survey-to-actual variance | Whether the estimate matched the job | Every job, reviewed monthly | Office |
| Claims ledger | What broke, on whose job, and how it was handled | Every claim, reviewed monthly | Office |
| Post-move callback | What the customer noticed that they did not write down | Every job, within a week | Office |
None of the four is sufficient alone. The ride-along sees one job; the variance sees hours but not care; the claims ledger sees only what broke; the callback sees what the customer noticed. Together they see the crew.
Four Quality Sources
Ride-along scorecard
- What it measures
- Crew actions at door
- How often
- One job per lead monthly
- Who runs it
- Owner or ops manager
- Blind spot
- Sees one job only
Survey-to-actual variance
- What it measures
- Estimate vs actual
- How often
- Every job, monthly review
- Who runs it
- Office
- Blind spot
- Hours, not care
Claims ledger
- What it measures
- What broke
- How often
- Every claim, monthly review
- Who runs it
- Office
- Blind spot
- Only what broke
Post-move callback
- What it measures
- What customer noticed
- How often
- Every job, within a week
- Who runs it
- Office
- Blind spot
- Only what was said
The ride-along scorecard
The auditor rides with the crew and scores the checkpoints from the daily SOP, not a general impression. Items to score, each as done, partly done, or not done:
- The crew lead confirms the job scope, customer priorities, and access notes before work begins.
- Pre-existing damage and items excluded from the move are noted before handling.
- Floor, wall, and doorway protection is in place before carrying starts.
- Furniture is padded or wrapped before it reaches the truck.
- Suitable equipment is selected for the items and access conditions.
- Walkways, the elevator approach, and the truck ramp are kept clear.
- Fragile and priority items are identified and loaded accordingly.
Ride-Along Scorecard Checkpoints
- Pre-trip inspection recorded before departure
- Pad count taken and written
- Arrival walkthrough done room by room
- Pre-existing damage noted and photographed
- Customer cartons inspected and unsafe flagged
- Floor and door protection down first
- Every piece padded before leaving room
The scorecard is not a surprise inspection. The crew knows the checkpoints because the checkpoints are on their sheet; the ride-along confirms they are being run when the customer is watching and the elevator is late.
Survey-to-actual variance
For every job, compare the surveyed hours with the actual hours by phase. The monthly review sorts the variance two ways:
Flag any phase where actual hours exceed surveyed hours. That is a review trigger, not proof of crew failure; check the job notes for access, dispatch, scope, or work-method causes before assigning responsibility. Look for recurring patterns before deciding on corrective action.
Sorting Survey-to-Actual Variance
Which jobs run over surveyed hours?
Sort by estimator: missing access hours or under-counted volume
Sort by crew lead: pace or method problem, check ride-along
- By estimator.An estimator whose jobs run consistently over is missing access hours or under-counting volume. That is a pricing problem wearing a crew's uniform.
- By crew lead.A lead whose jobs run over on correctly surveyed work has a pace or a method problem, and the ride-along is where to look.
The dispatcher's calendar decisions also show up here. Record whether elevator access was confirmed, the access window, and any wait that affected the job; compare that time with surveyed phase hours so a scheduling cause is not assigned to the crew. The sequence in how to schedule moving company routes without delays exists to remove that variance at its source.
The claims ledger
Every claim, however small, is logged with the job number, the crew lead, the item, the cause where known, whether the carton was customer-packed, and the resolution and its date. The monthly read asks four questions:
Monthly Claims Ledger Questions
- Which crew lead's jobs exceed yard average claims?
- What fraction involve customer-packed cartons?
- How long did resolution take?
- Which items recur as equipment or method problems?
- Which crew lead, route, or access condition is associated with repeat claims?
- What equipment or handling method was involved, and was the appropriate item available—for example, an appliance dolly, piano board, or moving pads?
- Are outcomes and resolution dates recorded, and do repeat issues remain open?
For interstate moves, the claims process is a quality signal and a regulated obligation. Under 49 CFR Part 375, household-goods carriers must provide the booklet Your Rights and Responsibilities When You Move. 49 CFR Part 370 sets requirements for processing claims.
The FMCSA Protect Your Move glossary explains terms used in interstate household-goods moves. Read the claims ledger against the federal requirements, not against the yard's own standard alone.
The callback
Within a week of every move, someone from the office calls the customer. They ask three open questions: what went well, what did the crew do that surprised you, and is there anything you noticed afterward.
The third question finds the scratched floor the customer decided not to mention. It finds it before the review does. Log the answers by crew lead alongside the claims ledger.
The callback is also the only source that reports on the ordinary job, the one that produced no claim and no review. Most jobs are ordinary. Quality lives there.
Acting on the audit
The monthly read produces a short list: one estimator issue, one crew lead issue, one equipment or method issue, one dispatch issue, in that order.
The estimator comes first on purpose. A survey that misses access makes a good crew look slow and a fair price look wrong. The operations and workflow guide covers the monthly review meeting where the list is worked.
Where a market is being added, the audit is the evidence that the standard travels. A second yard whose ride-along scores match the first is ready; one whose claims ledger tells a different story is not, whatever its bookings look like. The expansion and market guide uses the same four sources as its readiness test.
Keep the audit record
Scorecards, variance sheets, the claims ledger, and callback notes stay with the job files. IRS Publication 583, Starting a Business and Keeping Records, explains business recordkeeping for income and expenses. The variance sheet supports the labor-cost side of that file.
The rest of the audit record is for the owner. It turns a bad month into a specific fix, not a general worry.
Common questions
How many ride-alongs a month?
One per crew lead. Fewer, and a lead can go a quarter without being seen; more, and the owner is a mover again.
Should crews see their own scores?
Yes, the same week. A score the crew never sees changes nothing.
What if the claims ledger is empty?
Either the crews are excellent or claims are arriving as reviews and phone calls that nobody logs. Check the callback notes before believing the first explanation.
Can reviews replace the callback?
No. Reviews are written by a small, unrepresentative group, and they arrive after the chance to fix the job has passed.
