A year-end review for a multi-location auto repair, tire or quick lube business should line every store up side by side on the same ten numbers, calculated the same way, before anyone writes a 2027 budget. Five come from the shop system (car count per bay, ARO, effective labor rate, gross profit, comebacks) and five come from what actually happened in the bays (cars counted on camera vs tickets, time in bay vs hours sold, idle bay hours, cars waiting, work done but not billed). Then you sit down with each manager, one store at a time, with the table in front of you.
Most year-end advice for shops is written for one location: look back at the year, set goals, thank the team. That works when you are standing in the shop every day. With three, eight or twenty stores, the hard part is that every store's numbers look fine on their own. The review only becomes useful when the stores sit next to each other and the gaps show.
Quick answer
- Pull 10 numbers per store for the full year and the last quarter: 5 from the shop system, 5 from the bays.
- Use rates, not totals. A 4-bay shop can't be judged against a 10-bay shop on revenue.
- Put the stores in one table, then mark each number green, amber or red against that store's own trend and the group's middle store.
- Meet each manager with the table and the questions below. One fix per store goes into the 2027 plan.
- Set each store's 2027 target from its own baseline, not from the best store.
Why do a year-end review store by store?
Because a group total hides the store that's dragging it down. If the group's ARO went up, one store can still be flat while another carries it. If labor gross profit held, one store can be giving away hours while another is under-staffed and turning cars away.
Budgets make it worse. Most owners set next year's targets in December, often as "last year plus a percentage" for every store. That locks in the gap you didn't look at. Ten numbers, side by side, take a few hours to pull and change what you ask each store to do next year.
Which numbers should you compare across stores?
The shop system tells you what got sold. It can't tell you what came through the door and never got a ticket, how long cars actually sat in the bay, or which bays stood empty while cars waited outside. That's where the bay-side numbers come in. If you have cameras in the bays, most of them can be counted from video; if not, a week of manual counts per store still beats guessing.
| # | Number (per store) | How to calculate it | Source |
|---|---|---|---|
| 1 | Car count per bay per day | Tickets closed ÷ (bays × open days) | Shop system |
| 2 | Average repair order (ARO) | Total sales ÷ tickets closed | Shop system |
| 3 | Effective labor rate | Labor sales ÷ hours billed | Shop system |
| 4 | Gross profit % (labor and parts) | (Sales − cost) ÷ sales | Shop system, payroll, parts invoices |
| 5 | Comebacks per 100 tickets | Comebacks ÷ tickets × 100 | Ticket notes, warranty flags |
| 6 | Cars counted vs tickets | Cars that entered a bay − tickets opened | Bay cameras vs shop system |
| 7 | Time in bay vs hours sold | Minutes in bay ÷ (hours billed × 60) | Bay cameras vs shop system |
| 8 | Idle bay hours per week | Open hours with no car in the bay | Bay cameras |
| 9 | Cars waiting at peak | Average cars queued in the busiest hour | Lot or entrance camera |
| 10 | Work done but not billed | Cars or services seen in the bay with no matching line on a ticket | Bay cameras vs tickets |
Numbers 6 and 10 are the ones owners are most often surprised by. A gap between cars counted and tickets opened can be a reporting habit (tickets opened late, two cars on one ticket) or it can be work leaving without being rung up. Our car count vs tickets guide covers how to tell the difference, and the unbilled work guide covers the follow-up.
For the formulas behind the shop-system numbers, our KPIs by store guide goes through each one. For quick lubes specifically, see the quick lube KPIs post.
How do you make the stores comparable?
Three rules keep the table honest:
- Same definitions everywhere. Decide what counts as a car, a comeback and a billed hour, write it down, and apply it to every store's full year. If one store opens a ticket per service and another per car, fix that before you compare car counts.
- Rates per bay or per hour, not totals. Totals reward the biggest store.
- Two time windows. The full year shows the pattern; the last quarter shows whether a store is getting better or worse right now. A store that was weak all year but strong since September needs a different conversation from one that slipped in the fall.
Then colour each cell. Green means at or better than the group's middle store and not falling. Amber means below the middle store, or above it but falling for the last quarter. Red means bottom of the group and falling. You end up with a grid where the red cells tell you which conversation to have with which manager.
The side-by-side review table
Here's the layout, filled in with made-up numbers (made-up numbers, not real store data) for three stores so you can see how it reads.
| Number | Store A | Store B | Store C | What it suggests |
|---|---|---|---|---|
| Car count per bay per day | 7.8 | 6.1 | 8.3 | B is getting less out of its bays |
| ARO | $212 | $236 | $181 | C is busy but selling less per car |
| Effective labor rate | $118 | $121 | $104 | C is discounting or writing off hours |
| Gross profit % | 54% | 56% | 49% | C again |
| Comebacks per 100 tickets | 1.4 | 1.1 | 2.6 | C's speed may be costing quality |
| Cars counted − tickets (per week) | 3 | 2 | 14 | C has cars in bays with no ticket |
| Minutes in bay per hour sold | 72 | 65 | 81 | C's jobs take longer than they bill |
| Idle bay hours per week | 21 | 46 | 9 | B has bay time to sell |
| Cars waiting at peak | 2 | 0 | 5 | C is turning cars away at lunch |
| Services seen but not billed (per week) | 1 | 1 | 9 | Check C's tickets against the video |
Read across a row and you see where each store stands. Read down a column and you see the story of one store. In this example, Store C looks like the busiest shop in the group, and the shop-system numbers alone would make it look like a pricing problem. The bay numbers say something different: cars are going through without tickets and jobs are taking longer than they bill. That's a process conversation, and you'd want to watch a few clips before you have it. Store B has the opposite problem: good tickets, empty bays. That's a car count and marketing conversation.
A blank version of this table, one column per store and a "what it suggests" column, is all you need to print for the review meetings.
What should you ask each store manager?
Send the manager their column a few days before you meet, so the conversation is about causes and not about whether the number is right. Then ask:
- Which of these numbers surprised you, and which didn't?
- For each red cell: what happened, and when did it start?
- Where do cars go through the bay without a ticket, or with a ticket opened late? (If the gap is small, say so and move on.)
- Which hours of the week do your bays sit empty, and which hours do cars wait?
- What's one process you'd change if you could only change one?
- What do you need from me (staff, equipment, a price change) to hit next year's number?
- Which number do you want to be judged on each week next year?
Write down one fix per store. A list of eight fixes per store doesn't get done; one does. Our store manager accountability guide covers how to follow that fix through the year with a weekly scorecard.
How do you turn the review into 2027 targets?
Set each store's target from its own baseline, then nudge it toward the group's middle store, not the best one. A store at 6.1 cars per bay per day won't get to 8.3 in a year because you wrote it down. A target of 6.6 with a specific fix (fill the idle Tuesday and Wednesday afternoons) is something a manager can own.
Build the budget around the red cells:
- Cars counted vs tickets, or work not billed, in red: budget for a process fix and a monthly review of the gap before you budget for more marketing at that store.
- Idle bay hours in red: budget for car count (marketing, fleet accounts, appointment slots) at that store, not a new hire.
- Cars waiting in red: budget for staffing at peak hours or a faster process, before you add bays.
- Comebacks in red: budget for training, and check whether it's one tech or the whole store.
Then decide what you'll look at every morning in 2027, so next December's review isn't the first time anyone sees these numbers. Five or six of the ten, per store, on one screen, is enough.
Common mistakes
- Comparing totals. The biggest store always wins.
- Using last year plus 5% for every store. It locks in the gaps.
- Reviewing only the shop system. It can't show work that never got a ticket or bays that sat empty.
- Surprising managers in the meeting. Send the column first.
- Ten fixes per store. Pick one.
How Trilix fits
We build the owner dashboard that puts these numbers next to each other: tickets and repair orders from the shop system you already use, car counts, time in bay and idle bays from the bay cameras you already have, and the gap between the two flagged by store. It lands on one owner dashboard every morning, so the year-end review is a printout, not a project. If you want to see what that looks like at a quick lube, our cars never billed case study walks through one build.
Want your stores side by side before you set 2027 budgets?
We'll look at your shop system and your cameras and show you what the review table would flag at each location.
Before you sign anything, you’ll speak with businesses we already work with. No pitch deck, no pressure. If it’s not a fit, we’ll tell you.
