The Wait Tag: an auto shop bottleneck tracking sheet with the common causes listed

The wait tag is three moves, in the same order as the video:

1. Tag the waits. For two weeks, every time a car waits, someone writes down why: the estimate, an approval, a part, a lift, a person.
2. Fix the biggest one. Count the tags by cause and work on the single largest pile. Leave the rest alone for now.
3. Check your own desk. Look for tags that point at you, because approvals that need the owner are a wait like any other.

Below is the sheet itself, the list of common causes already filled in, and how to run the two weeks without turning it into a second job.

Who this is for

Owners and service managers of one shop or a few, who feel that cars take too long but can't say where the time goes. You need no new software. A clipboard by the dispatch desk works, and so does a shared spreadsheet. If your shop system stamps status changes, use those times as a cross-check.

It is not a technician speed test. AutoVitals, a shop-software vendor, makes the point that delays rarely come from one big problem and show up instead as small waits, such as a car sitting before its estimate or a tech pausing for an approval. The sheet records those waits. It never records how fast someone turns a wrench.

What you need before day one

• One owner for the sheet. Usually the service manager or lead advisor. They don't write every tag, but they check it at lunch and at close.
• A short list of stages. Checked in, inspecting, estimate in progress, waiting on approval, waiting on parts, in repair, final check, ready for pickup. AutoVitals recommends a clear status on every repair order, because an unclear status is where jobs go missing.
• Two weeks on the calendar. Pick two normal weeks. Skip the week before a holiday if your car count swings.
• A two-minute talk with the team. Tell them what is measured and why. Say plainly that nobody is being timed.

The sheet

Copy this table onto a clipboard or into a spreadsheet. One row per wait, not per car. A car that waits three times gets three rows.

RO	Stage when it stopped	Waiting on	Start	End	Initials
8812	Inspection done	Estimate not started	9:40	10:10	PR
8812	Estimate sent	Customer approval	10:10	1:00	PR
8812	Approved	Part ordered, no ETA	1:00	next day	LV

The rows above are a made-up example from a demo shop, not real data. Write the start time when the car stops moving and the end time when the next person picks it up. Rough times are fine. Ten minutes either way won't change which cause wins.

The common causes, already listed

Use these labels so two people write the same wait the same way. Add your own only when none of these fits.

1. Estimate not started. Inspection is done and nobody has begun the quote.
2. Estimate waiting on a question. The advisor needs a price, a labor time or a tech's note before sending.
3. Customer approval. The quote is out and there's no answer yet.
4. Part ordered, ETA known. The part is coming and you know when.
5. Part ordered, no ETA. The part is coming and nobody knows when. Chase these first.
6. No free lift. Work is approved but every bay is full.
7. Waiting on one certified tech. The job needs the one person who does electrical, alignments or diagnostics.
8. Owner sign-off. A discount, a goodwill repair, a sublet or a price exception that only the owner can approve.
9. Sublet out. The car or a part is at another shop.
10. Ready, customer not told. The car is done and the customer doesn't know yet.

How to run the two weeks

1. Morning. The sheet owner puts a fresh page on the clipboard with the date.
2. During the day. Whoever notices a car stop writes the row. Advisors catch most of them, techs catch the lift and part waits.
3. At lunch. The owner of the sheet scans for rows with a start and no end. Those cars are still waiting.
4. At close. Fill in missing end times from memory or the shop system, and file the page.
5. On day fourteen. Add up the hours by cause. A spreadsheet pivot does it in a minute; a pencil does it in twenty.

Fix the biggest one only

The total by cause is the whole point. One or two causes will usually stand out. Work on the largest and leave the others. The Lean Enterprise Institute describes the theory of constraints, from Eliyahu Goldratt's 1984 book The Goal, as an approach that focuses on removing or managing the constraints that hold an organization back. In a shop that means the building finishes only as many cars as its slowest stage allows. Speeding up any other stage just builds a longer line in front of it.

What a fix looks like depends on the cause:

• Estimate waits. Standardize how inspection findings are written so a quote can be built fast, and set a target time from inspection to estimate sent.
• Approval waits. Send the estimate with photos while the car is still on the lift, and agree on when a second contact attempt happens.
• Part waits. One person owns parts status and every ordered part gets an ETA written on it. A part with no ETA is the one to chase today.
• Lift or tech waits. Check whether the real limit is lifts, or one tech who gets every job of a kind. Cross-training is slower than a new lift but often the better answer.

Then run the sheet again for one week. If the total for that cause dropped, keep the fix. If it didn't, the fix was wrong, not the method.

Check your own desk

This is the tag owners skip. Shop4D, another shop-software company, lists the owner as a bottleneck when every decision needs their sign-off. If advisors can't approve a small discount, a goodwill fix or a sublet without reaching you, the approvals stage runs at your pace, and your pace includes every hour you're on the phone, at the parts counter or out of the building.

Count the "Owner sign-off" rows on your own. If they add up to more than any single tech's waits, write a simple rule: a dollar limit or a list of fixes advisors may approve alone, and a weekly review of what they approved. That one rule often moves more cars than any change on the floor.

What to watch out for

• Tags written late. If the team fills in the sheet at close from memory, short waits disappear. Lunch checks catch most of this.
• Blame. The moment a tag reads like a complaint about a person, people stop writing them. Tag the cause, never the name.
• Too many causes at once. Changing three things in the same week tells you nothing about which one worked.
• Reading tech numbers alone. In the Ratchet+Wrench 2024 survey, 18% of shops did not track technician efficiency at all and 27% reported it below 80%. Low efficiency can come from waiting rather than slow work, so read the wait tags before you coach anyone.

How to tell it worked

Run the sheet again a month later for one week. You should see three things. The biggest cause from the first run is smaller. Cars that came in the same day leave sooner than before. Advisors spend less time answering where a car is. If your shop system reports stage times, compare the same weeks there too.

Software can keep this going once the habit exists. Shopmonkey's 2024 post on AI lists identifying repairs that take longer than expected as one use of analytics, and RevvOS's daily operations view shows each repair order's stage, age and owner, with delayed parts and aging orders on one short list. Neither replaces the two weeks of tags. The tags are what tell you which wait matters.

For the longer explanation of where shops lose time, read auto shop bottleneck detection. For the messages that cut approval waits, see repair status automation.