The Complete Guide to Running an Auto Repair Job Board

Walk into almost any independent auto repair shop at 10 a.m. and you will see the same scene. Keys on hooks, a stack of repair orders on the counter, a technician asking whether the parts for the silver sedan arrived, and a service advisor on hold with a supplier while a customer stands at the desk asking if their car is ready. None of those people are doing anything wrong. The shop is simply running on memory and interruptions instead of on a shared picture of where every job stands. That shared picture is what a job board provides, and it is the single most useful operating tool a shop can adopt, whether it lives on a whiteboard, a spreadsheet, or a screen in the bay.

This guide covers the whole subject from the ground up. We start with why the board matters more than any individual feature, then walk through the statuses that actually reflect how work moves, the approval step that decides whether a day goes well, and the customer communication that flows from a good board almost for free. We finish with roles and routines, the handful of numbers worth watching, and an honest comparison of whiteboards, spreadsheets, and dedicated software. We build software in this space, so we have opinions, but we have tried to keep the advice useful no matter what tool you end up using.

Why the Job Board Is the Operating System of the Shop

A repair shop is a flow problem. Cars arrive, get inspected, wait for parts or approvals, get worked on, get checked, and leave. Every one of those handoffs is a place where a car can quietly stall, and the shop rarely notices until a customer calls. The job board exists to make those stalls visible. When every vehicle in the building is represented by one card in one lane, the advisor does not need to walk the lot, the tech does not need to ask what is next, and the owner can glance at the board and know whether the day is on track. That visibility is worth more than any single feature, which is why we treat the board as the operating system and everything else as an app running on top of it.

The most common alternative is not a bad board but no board at all. Work lives in a stack of paper repair orders, in the advisor's head, and in a management system that tracks invoicing but not progress. That setup works until the shop gets busy, and busy is exactly when it fails. Cars get forgotten in the back lot, parts get ordered twice, and the advisor spends the afternoon answering the question every customer asks: is it done yet? The article on running a repair shop job board smoothly goes deep on the daily mechanics, but the short version is that the board replaces dozens of small interruptions with one place everyone looks.

Skeptical shop owners often ask whether a board is worth the effort of keeping it updated. The fair answer is that it depends on discipline, not on the tool. A board that is updated once a day is a decoration. A board that is updated at each handoff, in the moment the handoff happens, pays for itself in fewer phone calls, fewer walkbacks to the bay, and fewer cars that sit an extra day because nobody noticed the parts came in. We looked closely at how much time a live status board saves, and the honest finding is that the savings show up in the front office first, because that is where the interruptions land, and in bay throughput second.

Designing Statuses That Match How Work Actually Flows

The statuses on your board are the vocabulary the whole shop uses to talk about work, so they deserve more thought than most shops give them. A good status answers one question: what is this car waiting on right now? If the answer is a person, the status should name the role. If the answer is a thing, like a part or an approval, the status should name the thing. Statuses that describe a vague state, such as In Progress, hide exactly the information the board is supposed to surface. Our article on which job statuses a shop board should track daily lays out a full set, but the principle is more important than the list.

For most independent shops, a workable set looks something like this: Checked In, Diagnosing, Waiting on Approval, Waiting on Parts, In Bay, Quality Check, Ready for Pickup, and Picked Up. Some shops add Waiting on Sublet for work sent to a machine shop or glass installer, and some split In Bay into a couple of stages for large jobs. The temptation is to keep adding statuses until the board captures every nuance. Resist it. Every extra lane is one more decision the tech has to make when moving a card, and the more decisions you ask for, the less consistently the board gets updated.

The trickiest transitions are the ones from waiting to ready, because that is where cars get lost. A vehicle that is Waiting on Parts should move the moment the parts are checked in, not when a tech happens to notice the box. A vehicle that is Waiting on Approval should move the moment the customer says yes, even if no bay is free yet. We cover the mechanics of moving cars from waiting to ready without losing track in a dedicated article, and the core idea is that each waiting status needs an owner and a trigger. The owner is the person responsible for checking that lane, and the trigger is the event that moves the card.

It also helps to distinguish between statuses the shop controls and statuses the customer controls. Diagnosing and In Bay are yours. Waiting on Approval belongs to the customer, and a car can sit there for hours through no fault of the shop. Making that distinction visible on the board, with color or a separate section, keeps the team from feeling responsible for delays they cannot fix and helps the advisor know exactly which customers to nudge.

Approvals: The Step That Decides the Day

Almost every repair that goes over the original estimate hits the same wall: the technician finds something, the advisor has to reach the customer, and the car sits until the customer answers. The approval step is where the most time is lost in a typical shop, and it is the step most shops handle by phone tag. A board makes the problem visible, because cars pile up in Waiting on Approval, but visibility alone does not solve it. What solves it is a repeatable approval process that gets the customer a clear decision quickly, in the channel they actually respond to.

Text messaging is the channel that works for most customers, most of the time, because people can answer a text from a meeting or a school pickup line in a way they cannot answer a call. But the timing matters. Texting for approval on every small item creates fatigue and slows the job. Bundling findings into one clear message with a price and a recommendation gets a faster answer. Our article on when a shop should text a customer for approval on extra work walks through the judgment calls, including what to do when the customer is in the waiting room and when a phone call is still the right move.

From the advisor's chair, the goal is to shrink the gap between finding and decision. That means the tech documents the finding in a way the advisor can forward without rewriting it, the advisor sends a message with a clear yes or no ask, and the board reflects that the ball is now in the customer's court. When a repair needs customer approval fast, the advisor needs a short playbook: send the text, set a follow-up time, and know when to escalate to a call. We wrote a piece specifically on what a service advisor should do when a repair needs approval fast, and the theme is that speed comes from having the playbook ready before the busy day, not from hustling harder during it.

One last point on approvals: record them. A customer who approved work by text has left a timestamped record that protects both parties. A customer who approved by phone has left nothing, and if there is a dispute at pickup, the shop is relying on memory. Whatever tool you use, make sure the approval and the amount approved are attached to the job, not floating in someone's personal phone.

Keeping Customers Informed Without Burying the Front Desk

Customers do not get frustrated because repairs take time. They get frustrated because they do not know what is happening, and silence reads as neglect. The phone call at 2 p.m. asking whether the car is ready is not really a question about the car. It is a request for reassurance that the shop has not forgotten. Our article on why customers get frustrated waiting for status updates goes deeper on the psychology, but the practical takeaway is simple: a customer who knows what stage their car is in will almost never call to ask.

The good news is that a well-run job board makes customer communication nearly automatic. If the board already knows a car moved from Diagnosing to Waiting on Approval, that same status change can trigger a message to the customer without the advisor typing anything. This is the point where a board stops being an internal tool and becomes a customer experience. Not every status change deserves a message, though. Customers care about a handful of moments: the car was checked in, the diagnosis is done and here is what we found, we need your approval, the work is in progress, and it is ready. Anything more than that becomes noise. Our guide on keeping customers informed all day covers which moments matter and how to phrase them.

What goes into each message matters as much as when it goes out. A good status text identifies the vehicle, states the current stage in plain language, gives a realistic expectation for the next update or completion, and tells the customer how to reply if they have a question. It does not use shop jargon, it does not promise a time the shop cannot keep, and it does not require the customer to log into anything to understand it. We broke down exactly what a repair status text should include in a separate article, with examples for each stage.

A shared live status link takes this one step further. Instead of pushing every update as a text, the shop gives the customer a link that shows the current status of their vehicle whenever they want to look. The texts then become the exceptions that require action, like approvals, while the link handles the reassurance. Shops that use this pattern typically see the afternoon phone calls drop, because the answer to is it ready yet is already in the customer's pocket.

Roles and Routines: Who Updates What, and When

A board is only as good as the habits around it, and habits come from clear ownership. The single most common reason boards go stale is that everyone assumes someone else will move the card. The fix is to assign each transition to a role. The advisor moves cars into Checked In and into Waiting on Approval. The tech moves cars into Diagnosing, In Bay, and Quality Check. Whoever receives parts moves cars out of Waiting on Parts. The person who hands over the keys moves the car to Picked Up. Write it down, post it near the board, and enforce it for the first month until it becomes reflex.

Routines matter as much as roles. A short morning huddle in front of the board, five minutes at most, is enough to assign the day's work, flag any car that has been sitting too long, and agree on which jobs must go out today. A second look mid-afternoon catches the cars that stalled in a waiting lane. Shops that skip these check-ins tend to discover problems at 4:30 p.m., which is the worst possible time to discover anything. Our article on running a repair shop job board smoothly describes a full daily rhythm that works for one-advisor shops and for larger teams.

The technician's side of the routine deserves special attention because techs are often the least enthusiastic board users. From their perspective, updating a board is paperwork that pulls them away from the car. The answer is to make the update as close to zero effort as possible: a tap on a tablet mounted in the bay, a quick move on a phone, or a shout to the advisor who does it for them. If the update takes more than a few seconds, it will not happen consistently, and the whole board suffers. Moving cars from waiting to ready without losing track depends on this more than anything else.

Measuring Flow: The Numbers a Board Can Give You

Once a board is updated reliably, it becomes a source of data that most shops have never had. Every status change carries a timestamp, and those timestamps tell you how long cars spend in each stage. The two numbers worth watching first are cycle time, meaning drop-off to ready, and time in waiting lanes, meaning how long cars sit in Waiting on Parts and Waiting on Approval. Both are more useful than technician efficiency for diagnosing where a shop is losing days, because they point at the handoffs rather than at the individual.

Work in progress, or the number of cars in the building that are not finished, is the third number. A shop that takes in more cars than it can move through the bays does not get more done; it gets more waiting. Watching WIP on the board tells you when to stop scheduling drop-offs and when to push cars out. The article on how much time a live status board saves discusses how these measures show up in practice, and the honest summary is that the biggest gains come from spotting the two or three cars each week that would otherwise sit an extra day.

Do not over-instrument. A small shop does not need a dashboard with twenty metrics. It needs to know which lane cars get stuck in and whether that is getting better. If the board shows that Waiting on Parts is where days go, the fix is in parts ordering. If it is Waiting on Approval, the fix is in how and when the advisor asks for approval. If it is Quality Check, the fix is in who does the check and when. Choosing which job statuses to track daily and then watching the time in each one is the whole measurement program most shops need.

Whiteboards, Spreadsheets, and Software: Choosing and Rolling Out

Every shop starts somewhere, and there is no shame in a whiteboard. A whiteboard with columns for each status and a magnet for each car does most of what a board needs to do, at the cost of a marker. Its limits are visibility and history. It cannot be seen from the front desk if it hangs in the bay, it cannot be seen by the customer at all, and it forgets everything the moment a magnet moves. Spreadsheets fix the history problem and can be shared, but they are awkward to update from a bay and they do not talk to customers. Dedicated software adds timestamps, customer notifications, and a live status view, and it charges a subscription for the privilege. We compare these approaches in detail on our comparison page.

When you decide to move to software, the rollout matters more than the choice of product. Start with the statuses you already use, not the full list the software offers. Run the whiteboard and the software in parallel for a week so nobody loses a car during the transition. Put a screen where the whole shop can see it. Pick one person to be the board owner for the first month, with authority to nag. And resist the urge to turn on every notification on day one; start with check-in, approval, and ready, and add the rest once the team trusts the tool. Our article on running a repair shop job board smoothly has a rollout checklist you can adapt.

Finally, evaluate any tool on how it handles the moments that matter, not on the length of its feature list. Can a tech update a status in two taps? Does an approval request go out as a clear text the customer can answer with a single word? Does the customer have a way to check status without calling? Does the shop get a history of every status change with a timestamp? Those four questions separate tools that help from tools that get abandoned. Keeping customers informed all day is the outcome, and the board is the mechanism; choose the tool that makes the mechanism nearly invisible.

More guides on this topic

Further reading from the GarageTrackr blog, each answering one specific question in depth.

A job board is not a piece of software. It is a shared agreement about where every car stands and who moves it next, and any tool that supports that agreement will help the shop. Get the statuses right, give each transition an owner, handle approvals with a short playbook and a clear text, and let customers see status without calling. Do those four things and the rest, including the measurements and the software, follows naturally. The articles linked throughout this guide go deeper on each piece, and we will keep adding to them as we learn from the shops we work with.