The Full Queue Check: a one-page board setup for auto repair technician scheduling

This is the board setup from our video on technician scheduling AI. It follows the video's order:

1. Propose the next job. For each tech, the board shows one proposed next job with the reason it was picked.
2. Flag the stuck car. Any car waiting on a part or an approval is flagged and held, so nobody walks over to a job they can't start.
3. The foreman approves. Nothing moves into a tech's lane until the foreman or service manager says yes.

You can run it on a whiteboard, a spreadsheet or the scheduling view in your shop system. The software part is optional at first. The rules are what matter.

Why an empty queue costs more than it looks

When a tech finishes a job and has to walk up front to ask what's next, the shop loses those minutes. For many techs it's also their own money. The Bureau of Labor Statistics notes that some repair shops pay technicians hourly, while others pay based on the amount of work completed. In a 2024 Ratchet+Wrench write-up of its survey, flat rate was 23% of shops and hourly plus commission another 23% (the article's figures add to 102% and cite two years of reports). For a tech paid on hours produced, a gap in the queue is a pay cut.

Consultant Cecil Bullard makes the same point about pay plans: if a shop only has 30 available hours a week, a bonus that starts at 40 hours can never be earned. The schedule is what makes the hours available.

What you need before you start

• One person who owns the board. In a Ratchet+Wrench profile of efficient shops, one used a shop foreman, a former top technician, who schedules work after the initial inspection. In a small shop it may be the service manager or the owner.
• A skills list. For each tech, the work they're certified or trusted for: diagnostics, electrical, brakes, alignment, maintenance.
• Today's work list. Every open repair order with its status: approved, waiting on approval, waiting on a part, in progress.
• Promised times. Which cars were promised for today, and when.

Step 1. Propose the next job

Set up one lane per tech with three slots: current job, next job, and on deck. The rule is that the next slot is never empty while there's approved work in the shop.

A proposal has three parts, and the reason matters as much as the job:

Field	Example (demo data)
Tech	Marcus, A-tech
Proposed next job	RO 5124, check engine light
Reason	free at 10:40, diagnostics certified, promised today

The inputs for the reason are the ones the video named: who's free, who's qualified and what's waiting. Add the promised time as a tiebreaker. A tool can help here. AutoVitals says scheduling software should at minimum track labor hours per job, and better tools also measure non-billable work such as training, dispatching and estimating. That's a vendor's checklist, so treat it as features to ask about, not proof of results.

Copy these proposal rules:

1. Promised-today cars first.
2. Match the job to the skill list, then to who frees up first.
3. Keep the next slot filled for every tech who is clocked in.
4. Show the reason in one line. If you can't write the reason, it isn't a good proposal.

Step 2. Flag the stuck car

A job only goes in a next slot if it can start the moment the tech gets to it. FenderBender's advice on labor hours puts it plainly: keep technicians in their stalls, with parts, supplies, approvals, tooling and training ready so they don't wait.

So every proposed job gets a readiness check:

• Parts: on the shelf, or the expected arrival time.
• Approval: customer approved, or still waiting.
• Bay and equipment: the lift or alignment rack free when the tech frees up.

Anything that fails goes to a held tray with a flag and a time ("struts, part arriving 2 PM"). It gets proposed again when the flag clears. A scheduling tool can't fix a parts delay, but it can make the delay visible before someone walks over.

Step 3. The foreman approves

The software proposes. The foreman decides. These are the calls that stay with a person, every time:

• Who gets the hard diagnostic. Training, certifications and trust are judgment calls.
• Fairness. Giving the best-paying jobs to the same tech every time affects pay and morale.
• Overtime and pay questions. Those come from the owner and the pay plan.
• What the customer is promised. The advisor says it, with the board as input.

Approving should be quick: the foreman reads each proposal and its reason, accepts it, swaps it or moves it. When a job finishes early or extra work gets approved, the board proposes a new next job and the foreman approves that one too, instead of working from the morning's guess.

The one-page setup

1. One lane per tech, three slots: current, next, on deck.
2. A skills list pinned beside the board.
3. Every open RO on the work list with its status and promised time.
4. Proposal rule: promised-today first, then skill match, then who frees up first.
5. Each proposal shows its reason in one line.
6. Readiness check before a job enters a next slot: parts, approval, bay.
7. Failed checks go to the held tray with a flag and a time.
8. The foreman approves, swaps or moves every proposal.
9. Re-propose when a job finishes, a part arrives or work is approved.
10. Before you close up, note every time a tech waited with no next job, and why.

How to tell it's working

Run it in suggest mode for two weeks and keep a short log. Each day, write down how many times a tech had an empty next slot and what caused it. You're looking for the log to get shorter, and for the causes to shift from "nobody staged it" to real constraints like a late part. Compare the proposals with what the foreman chose. Keep the rules that matched his picks and change the ones he kept overriding.

Hiring is hard, which makes the hours you already have worth more. The BLS projects about 66,200 openings a year for automotive service technicians and mechanics on average from 2025 to 2035. A full queue won't fix that, but it means the techs you have aren't waiting for work.

Where RevvOS fits

RevvOS isn't a dispatch board and doesn't assign technicians. It sits beside the shop system and calendar you already use, and its daily operations view puts aging repair orders, delayed parts and capacity in one short list, each with where it came from and when it was last updated. Proposals and drafts wait for a person. For more on the topic see technician scheduling AI and auto repair shop automation.