The All-Shops Check: a definitions sheet for multi-location auto shop reporting

This is the sheet from our video on multi-location auto shop AI. It follows the video's three parts:

1. Same words. Every shop agrees on what each stage means and when a repair order closes.
2. One screen. Only what an owner can act on, like stale estimates and late parts, each with its source and update time.
3. Honest gaps. When a shop's feed is down, the screen says unavailable. It never carries last week's numbers forward.

The definitions sheet below is the part most groups skip, so fill it in first.

Why the third shop goes quiet

The second shop is usually fine because you're still in it most days. Somewhere around the third, you start hearing about problems after the customer does. The usual reason isn't the people. It's that each shop counts differently, so the numbers you get can't be lined up.

Tekmetric, a shop-management vendor, listed what it saw shops need for multi-shop growth: a standard inspection template across locations, shared customer history, unified reporting and a way to test a campaign at one shop before scaling it. Read as a list of what breaks, it's the same problem: processes drift between locations and reports come shop by shop.

It's common to inherit that drift. In collision repair, Focus Advisors reported the five largest operators ran 3,836 shops and added 319 in 2024. That's collision, not general repair, but every group that buys a shop also buys its habits.

Part 1. Same words, the definitions sheet

Many shops don't track the basics in the first place. In the 2024 Ratchet+Wrench survey, 18% of shops didn't track technician efficiency and 22% didn't track productivity. Before you compare anything, agree on the words. Copy this sheet, fill in the right-hand column with your managers, and pin it in every shop.

Term	Write your group's definition
Estimate sent	sent how (text, email, in person) and recorded where
Stale estimate	no recorded answer after how many days
Approved	approved by whom, recorded how
RO closed	closed when (paid, picked up, or end of day)
Week	which day the week starts and ends
Aging RO	in one stage longer than how many hours or days
Late part	past the ETA by how long, or no ETA recorded
Callback owed	promised to whom, by when
Car count	what counts (diagnosis only, warranty, comebacks)

Two rules make the sheet stick. Every shop uses the same week and the same closing rule, or weekly numbers can't be compared. And a term only goes on the shared screen once all shops define it the same way.

Part 2. One screen, what an owner can act on

Keep the all-shops screen to things you can act on in a few minutes. A good layout is one column per shop and these rows:

1. Feed state. Current, needs review, or unavailable.
2. Stale estimates. Using the sheet's definition.
3. Aging repair orders. Orders sitting in one stage past your limit.
4. Late parts. Past the ETA, or no ETA recorded.
5. Callbacks owed and pickups waiting.
6. Open capacity. Bays or lifts free today, so you can see where work could shift.

Every cell carries two things under the number: where it came from and when it was last updated ("shop system, 8:10 AM"). A number with no source and no time is a rumor.

Where AI helps here is the reading and sorting. Shops often run different systems, and software can pull each feed into one table with the source attached, point out a shop with far more stale estimates than usual, and draft the next step for a named person to approve. Shopmonkey notes that analytics can surface patterns such as repairs taking longer than expected. Across locations, the same idea shows which shop's repairs run long.

Part 3. Honest gaps, when a shop's data is missing

This is the test for any multi-shop tool, including ours. Say one location's feed has been down since Tuesday. A weak tool keeps showing last week's numbers or fills the hole with an average, and you make a decision on fiction. A good one marks that column unavailable, leaves the cells empty, and tells you since when.

Ask every vendor these three questions and write down the answers:

1. What does the screen show when a shop's connection is down?
2. Does every number show its source system and last update time?
3. Can a manager see and correct their own shop's numbers?

What stays local

The all-shops screen is for seeing. Most decisions should stay at the shop. Hiring, pricing within your guardrails, customer conversations and whether an old estimate is worth chasing belong to the manager who knows the town and the customers. Shop4D names the owner as a bottleneck when every decision needs their sign-off. Give managers clearer information, and keep the decisions with them.

How to tell it's working

After a month, three things should be true. You can read every shop's row in the same few minutes each morning. Nobody argues about what a number means, because the sheet settles it. And when a feed drops, you see "unavailable" the same day instead of finding out from a stale number a week later.

Where RevvOS fits

RevvOS's multi-location view is an all-shops matrix with each location's feed state, stale estimates, aging work, callbacks, parts and capacity. It works alongside your existing shop systems, keeps the source and last update visible, marks a shop unavailable when its connection is down instead of guessing, and prepares drafts for a named manager to review. For the rollout side read AI for automotive service groups, and for the bigger picture see multi location auto shop AI.