The Five-Blank Spec: an automotive workflow automation template with three shop workflows filled in

Who this is for

This template is for shop owners, service managers and operations leads who want to automate a repeated process, like chasing open estimates, and don't want to pay for software that hides the fact that nobody owns the job. It goes with our short video on the Five-Blank Spec and the longer article on automotive workflow automation.

The rule is the one from the video. Think of it like a repair order for the process: nobody starts work until the blanks are filled in. Anthropic's advice on building AI systems points the same way, recommending "the simplest solution possible, and only increasing complexity when needed". A plain rule beats an AI model for anything a rule can do.

What you need first

• One process that repeats every week. The quiet estimate is the usual first pick, because it happens daily and the cost of a miss is easy to see.
• Access to your shop-management system. Ratchet+Wrench's 2026 survey found electronic management system use at 59%, and that system is usually where the workflow's data lives.
• The person who will own it. Not a team, a name. If you can't name them yet, stop here and decide that first.
• Twenty minutes and this page. Fill in the five blanks before you talk to any vendor.

The five blanks, in order

Copy this into a document or print it, one sheet per workflow.

WORKFLOW: ______________________   LOCATION: ____________

1. TRIGGER  What event starts it?            ____________________
2. DATA     What does it read, from where?   ____________________
3. ACTION   What does the software do?       ____________________
4. OWNER    Which named person decides?      ____________________
5. EXIT     How do we know it's finished?    ____________________

If a field is empty, the workflow says so. It never guesses.
Ready to build? [ ] all five filled   [ ] owner agreed   [ ] baseline written down

1. Trigger

The event that starts the workflow, written so a computer could check it. "Estimate sent and no response in 7 days" works. "When a customer seems interested" doesn't, because no system records seeming.

Good triggers are a status plus a time: a repair order in one stage longer than your limit, an estimate past a number of days, a visit closed and paid.

2. Data

What the workflow reads and exactly where each field lives. For the quiet estimate that's the estimate date, status and amount, the vehicle, the customer's phone and any earlier declines, all from the shop-management system.

Check access before you go further. Tekmetric, for example, lists 70+ integrations in five categories and grants API access by application, so what an outside tool can read or write depends on the connection. Ask which fields move in which direction.

3. Action

What the software does when the trigger fires. Keep it to finding, drafting and queuing. For the quiet estimate: draft a follow-up that names the vehicle and the work, and put it on the advisor's list for the day. Nothing in these three examples sends, prices or diagnoses anything without a person reading it.

4. Owner

One named person who approves, edits or dismisses what the action produced. This is the blank most shops leave empty, and it's the one that decides whether the workflow lasts. "The team" means nobody. A tool can cover for a missing owner for a week, but not for a quarter.

Write the backup too: who owns it when that person is off.

5. Exit

How you know the workflow is finished for this item. For the quiet estimate: approved, declined with a reason, or marked do not chase. Without an exit the item keeps coming back, and people learn to ignore the list.

Three workflows, already filled in

Use these as written or change the numbers to fit your shop.

Blank	The quiet estimate	The stuck repair order	The finished visit
Trigger	Estimate open past your set number of days, no recorded response	RO in one stage longer than the limit you set for that stage	RO closed and paid
Data	Status, date, amount, vehicle, customer contact, prior declines	Stage, time in stage, assigned tech, parts status	Customer, vehicle, payment status, open complaints
Action	Draft a follow-up naming the vehicle and the work; add it to the advisor's list	Flag it to the shop manager with the likely reason and a draft status text	Hold the review request if a complaint is open; otherwise queue it for the next day
Owner	The service advisor on that RO	The shop manager	The advisor or office manager
Exit	Approved, declined with a reason, or snoozed to a date	Stage changes, or the manager records why it stays	Review requested, or skipped with a reason

Where these workflows break

Missing or late data. A workflow can only act on what the system holds. If repair orders are closed days after the car leaves, the finished-visit trigger fires late. If notes are blank, drafts come out generic. Decide in the spec what happens when a field is empty: the item should say so.

Texting rules. If the action sends texts from software to U.S. numbers, Twilio's documentation says senders on a 10DLC number must register for A2P 10DLC, and carriers penalize unregistered traffic. Keep consent records, and honor stop replies.

Voice. AI-generated voices on calls count as artificial under the Telephone Consumer Protection Act, per the FCC's February 2024 ruling. Keep outbound calling out of your first workflow.

Too much at once. Start with one workflow and one owner. Add the second only when the first has run for a month without anyone working around it.

How to tell it worked

Before you start, write down one number for each workflow you spec: how many estimates are open past your limit today, how many repair orders sit in a stage past theirs, how many closed visits got no review request. Check the same number after 30 days. Don't borrow improvement figures from a vendor page. Your own baseline is the only one that counts, and if nothing moved you want to know early.

A quick weekly check helps too. Ask the owner of each workflow two things: did anything come up that the spec didn't cover, and did you work around the tool at any point? Each yes is a blank to fix.

Where RevvOS fits

RevvOS is built around this pattern: it reads the systems you connect, raises an exception like an estimate open eight days with no recorded response, prepares a draft and shows it to a named person to approve, edit, defer or dismiss. It does not replace your shop-management system. See the order we suggest on auto repair shop automation, or book an assessment and bring your filled-in spec.