A service writer working by hand in a typical independent shop handles about 10 to 12 repair orders a day before something breaks: estimates go out late, approvals sit, and the phone rings into voicemail. With the repeat work automated, the same person can carry 18 to 25 a day without working longer. The number is not about how fast somebody types. It is about how many minutes of lookup, parts sourcing, approval chasing and phone tag are buried inside every ticket. Cut the minutes per RO and the daily count goes up on its own. That is the whole math.
What is a realistic number of repair orders per service writer?
Start with the day you actually have. A writer is on the floor roughly 9 hours. Take out lunch, two interruptions you cannot plan for, and the end of day cleanup. Call it 420 usable minutes.
Now divide by your real minutes per RO. That single number tells you your ceiling.
| Minutes per RO | ROs per day, one writer | What that shop looks like |
|---|---|---|
| 40 | 10 | Paper habits, phone heavy, estimates built from scratch |
| 30 | 14 | Software in place but lots of tab switching |
| 20 | 21 | Labor times, parts and approvals all inside the ticket |
| 15 | 28 | AI drafting the ticket, customer approving by text |
Most owners guess 20 minutes and are actually at 35. The gap is not laziness. It is five minutes here and seven minutes there that nobody logs.
Where do the minutes actually go on one ticket?
Break a single repair order into its parts and the picture gets uncomfortable fast.
- Intake and writeup: 6 to 10 minutes. Decode the VIN, find the customer, type the complaint, get the history.
- Labor lookup: 4 to 8 minutes. Open the guide, find the operation, make sure it is the right engine and trim.
- Parts sourcing: 6 to 12 minutes. Two or three suppliers, availability, price, call back on the one that is wrong.
- Building the estimate: 5 to 8 minutes. Line items, pricing, notes the customer will understand.
- Approval chase: 5 to 15 minutes spread across the day. Call, voicemail, call again, text, wait.
- Checkout and payment: 4 to 7 minutes at the counter.
That is 30 to 60 minutes of writer time on a job the tech may only touch for 90 minutes. The writer is the bottleneck, not the bay.
Which of those minutes can AI take off the writer's plate?
Not all of them. Nothing replaces a writer reading a customer's face when they hear the number. But the repeat work goes.
The ticket writes itself from a VIN and a sentence
Type the VIN and "pulling right, noise at highway speed" and the AI service writer builds the repair order: vehicle, likely causes, suggested operations, the lines you would have typed. You edit instead of starting from a blank screen. You can also talk to the RO and tell it what to change. That is 6 to 10 minutes back.
Labor times and parts live inside the ticket
MOTOR labor times and PartsTech parts ordering are in the same screen as the estimate. No second tab, no third login, no rekeying a part number. That is another 8 to 15 minutes back on a multi line job.
Approvals happen by text, not by phone tag
The customer gets the estimate with photos from the digital inspection and taps approve on their phone. Customer texting lives in the ticket, so the writer never loses the thread. The 5 to 15 minutes of calling back gets replaced by a notification.
The phone stops owning the counter
The phone system with an AI receptionist sits inside the ticket. It answers when the writer is with a customer, takes the booking, and shows the call attached to the right vehicle. Every call the writer does not have to physically pick up is two to four minutes of recovered focus, and it happens twenty times a day.
Checkout moves off the counter
Text to pay through payments and financing means the customer settles up before they walk in. The handoff is keys and a thank you, not a card terminal and a receipt printer.
What do the numbers look like at shops already running this way?
Pista was built inside working South Florida repair shops by a founder who still operates shops on it. The platform has written 2,600+ repair orders and manages 3,200+ customers. Shops running Pista are at 68.9% gross margin on the work going through the system.
That margin number matters for the workload conversation. A writer buried in lookup work takes the first part price they find and quotes labor from memory to get the ticket out the door. A writer with time checks the part, uses the real labor time, and presents the inspection findings properly. Speed and margin move together when the speed comes from removing steps instead of rushing them.
Should you hire a second service writer or fix the minutes first?
A second writer is real money every month, plus training, plus the desk, plus the handoff confusion between two people on the same car. Before you post that job, do the arithmetic.
If your writer is at 35 minutes per RO and doing 11 a day, you are using 385 of 420 minutes. Nobody is slacking. But get to 20 minutes per RO and that same person clears 21 without a longer day. You just doubled counter capacity for the cost of software, and you did not add a person who needs to be kept busy in February.
The question is never "do we need another writer." It is "how many minutes does one repair order cost us, and which of those minutes is a human actually needed for."
Hire the second writer when your minutes per RO are already tight and the car count still exceeds the day. That is a real growth problem. Hiring to cover tab switching is just paying for inefficiency twice.
What else quietly adds to the writer's day?
Three things usually sit on the writer that should not.
- Booking: every appointment taken by phone is five minutes. Online scheduling on your shop website moves those to self service.
- Review requests: asking at the counter is awkward and gets skipped. Google review requests fire automatically after the ticket closes.
- Follow up on declined work: the writer never gets to it. Retention and campaigns does, and declined jobs come back as booked tickets.
Your customers also get a connected car app with your shop's name on it: health score, instant estimates, booking and rewards. The connected car app answers the "how much and when" questions before they ever become a phone call at the counter.
What to do this week
- Time ten tickets. Have your writer note start and finish minutes on ten repair orders, start to checkout. Average them. That is your real minutes per RO.
- Divide 420 by that number. Compare the answer to the car count you actually wrote last week. The gap is your capacity problem or your demand problem, and you need to know which.
- Count the phone calls your writer picked up in one day. Multiply by three minutes. That number alone usually pays for the software.
- Run the numbers on pricing. Pit Crew is $149, Full Track is $299 and fits most shops, Podium is $499 per shop per month. Unlimited users, 30 days free, free migration. Setup runs 24 to 48 hours.
- Book a call. Bring your minutes per RO number to the call and a Pista expert will show you exactly which steps come off the ticket.