The garage diary is the product: where bay-hours are lost, and why

A garage sells hours on a ramp with a technician attached. That is the whole product. Everything else the business does exists to fill those hours, protect them, or stop them being wasted, and an hour that passes unsold cannot be recovered on a busier day.

Looking at a workshop that way makes the automation question much easier to answer, because every candidate has to justify itself against one test: does it fill a bay-hour, protect one, or stop one being wasted? Most of what gets marketed to garages does none of the three.

What we'll cover

• What you are actually selling
• The four ways an hour disappears
• The slot nobody filled
• The car waiting for an answer
• The car waiting for a part
• The job that was the wrong size
• Building it with CodeWords
• Measuring utilisation honestly
• The order to build in
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

What you are actually selling

Count the sellable hours in a week. Ramps times technicians times hours, minus the time nobody is going to sell anyway.

Then count what was invoiced against them. The gap between those two numbers is the whole opportunity in a workshop, and it is almost always larger than owners expect, because the workshop felt busy the entire time.

Busy and utilised are different states. A morning spent chasing a customer for an approval, ringing a factor about a part and rebooking two jobs feels like a hard morning's work. None of it was a sellable hour, and the ramp was occupied by a car nobody was working on.

The four ways an hour disappears

Nearly all of it falls into four categories, and they have completely different fixes.

The slot nobody filled. A gap in the diary, or a booking that did not turn up.

The car waiting for an answer. On the ramp, work identified, customer not contactable.

The car waiting for a part. Job started, part wrong or not there.

The job that was the wrong size. Booked for an hour, took four, and pushed three other jobs into tomorrow.

Worth spending a fortnight tagging lost time against those four before deciding what to build. Most garages are certain they know the answer and most are wrong about which is largest.

The slot nobody filled

Two different problems that look the same in the diary.

The gap that was never booked. Usually a demand problem, and the fix is the due-date list rather than anything clever: vehicles you have seen, with dates coming up, contacted with an offer of a time. A garage with a gap next Tuesday and 200 vehicles due that month has a communication gap, not a demand one.

The booking that did not arrive. A no-show costs the whole slot, and it is largely preventable. A reminder the day before with an easy way to move the appointment converts a no-show into a cancellation, and a cancellation with notice is a slot you can refill.

Which means making it easy to cancel is worth more than making it hard, however wrong that feels. The customer who cannot conveniently tell you they are not coming simply does not come.

Then there is the short-notice list: customers who wanted an earlier date. Keeping it by hand never happens on a busy morning, which is exactly why it is worth automating.

The car waiting for an answer

The most expensive of the four, because the bay is occupied while nothing is happening in it.

The clock starts when the technician identifies the work and stops when the customer answers. Everything in between is a ramp generating nothing. In most workshops the biggest single component of that wait is the time before anybody contacts the customer at all, rather than the customer's response time.

So the fixes are in order: send it the moment the inspection is done rather than at a convenient moment, send it in a channel that can be answered in thirty seconds from a desk at work, make it answerable in one word, and give unanswered estimates an owner and a cut-off so somebody rings rather than waiting.

A workshop that halves its approval wait has effectively added capacity without adding a ramp, which is the only free capacity a garage ever gets.

The car waiting for a part

The one automation helps with least and planning helps with most.

Most part delays are knowable before the car arrives. A vehicle booked for a cambelt has a predictable parts list; a vehicle booked for a diagnostic does not. Splitting the diary on that distinction, and ordering ahead for the first category, removes a large share of the problem before it exists.

For the rest, what automation can do is tell the customer quickly and rebook cleanly. A part that will not arrive until Thursday is a Thursday problem whatever you do; the avoidable damage is the customer discovering it at five and the slot sitting idle on Wednesday because nobody rebooked it.

Worth tracking which suppliers and which jobs generate the delays. That record is usually more valuable than anything else in this article, and almost nobody keeps it.

The job that was the wrong size

Booking accuracy is a scheduling problem that presents as a chaos problem.

A workshop that consistently books an hour for jobs that take two will run behind every afternoon, every day, and no amount of communication fixes it. The diary is simply wrong.

Two things help. Record actual time against booked time on every job for a month, which is tedious and is the only way to find out. And separate jobs you can size from jobs you cannot: a service and an MOT are known quantities, an intermittent electrical fault is not, and booking them as though they are the same thing is why the afternoon collapses.

Where a job cannot be sized, book the diagnostic time rather than the repair, and treat the repair as a second booking.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: the reminders, the estimate send, the short-notice list, and what happens when a job moves.
3. Authorize the connections to your garage management system, your diary, your parts supplier where they support it, and your WhatsApp Business Platform account.
4. Describe the exceptions: a customer waiting on site, a job on hold, a vehicle that cannot be released, anyone who has asked to be phoned instead.
5. Build one thing at a time and measure the bay-hours it recovered before building the next, because otherwise you will never know which of them worked.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Measuring utilisation honestly

Four numbers, none of which require new software.

Sellable hours available, per week, as defined above.

Hours actually invoiced against them.

Lost hours by cause, tagged to the four categories.

Average approval wait, from inspection complete to customer answer.

The last one is the most useful single number in a workshop and almost nobody has it. It is also the one that moves fastest when you change anything, which makes it a good early measure of whether a change worked.

Avoid the flattering measures. Messages sent, open rates and response times describe the automation rather than the workshop, and a garage can improve all three while selling the same number of hours.

The order to build in

Appointment reminders with easy rescheduling. Cheapest to build, protects slots immediately.

The estimate send and its cut-off. Attacks the largest category of lost hours in most workshops.

Due-date reminders with an offer of a time. Fills the gaps, using a list you already own.

The short-notice list. Converts cancellations into filled slots, which is free revenue.

Job updates. Reduces interruptions, which is real but indirect.

That order is deliberate. Everything above starts with the bay and works outwards, rather than starting with the message and hoping.

Making it survive

Check the job state before any send, since the diary moves constantly.

Give unanswered estimates an owner and a time by which somebody rings.

Record actual against booked time, permanently, not just for a month.

Keep the short-notice list current, because a stale one wastes the call.

Review lost hours by cause quarterly, since the largest category changes as you fix things.

Limits worth knowing about

No automation adds a ramp. A workshop at genuine capacity has a premises and staffing question.

Technician availability is the real ceiling, and it is harder to move than the diary.

Some jobs cannot be sized, and pretending otherwise is what breaks the afternoon.

Parts supply is largely outside your control. Communicating it well is not the same as fixing it.

A full diary is not the same as a profitable one. Hours filled with underpriced work are still underpriced.

What to build first

A fortnight of tagging lost hours against the four causes. No messages, no integration, just a sheet in the workshop where somebody records why a bay was not earning. Most owners are surprised by which category wins.

Two habits make the difference. Measure the approval wait, because it is usually the largest single block of dead ramp time and it responds fast to being attacked. And make cancelling easy, since a slot you can refill on Tuesday is worth a great deal more than a no-show you could not have prevented.

Frequently asked questions

What should a garage actually be measuring?

Sellable hours available, hours invoiced against them, lost hours tagged by cause, and the average wait from inspection complete to customer approval. Message statistics tell you nothing about the workshop.

Where do most bay-hours go?

Into unfilled slots, cars waiting on approval, cars waiting on parts, and jobs booked at the wrong size. Tag a fortnight before assuming which is largest, because the guess is often wrong.

Why is approval wait so important?

Because the bay is occupied while nothing happens in it. Halving that wait adds capacity without adding a ramp, which is the only free capacity a workshop gets.

How do I reduce no-shows?

A reminder the day before with an easy way to move the appointment. Making cancellation easy converts a no-show into a cancellation, and a cancellation with notice is a slot you can refill.

Is a short-notice list worth keeping?

Yes, and it is the classic example of something that never gets maintained by hand on a busy morning, which is exactly why it suits automation.

What helps with parts delays?

Ordering ahead for jobs with a predictable parts list, and tracking which suppliers and job types generate the delays. Messaging helps with communicating a delay rather than preventing one.

Why does the afternoon always run behind?

Usually because jobs are booked shorter than they take. Record actual against booked time for a month, and book diagnostic time separately from repair time for anything that cannot be sized.

What order should things be built in?

Appointment reminders, then the estimate send with a cut-off, then due-date reminders with an offer, then the short-notice list, then job updates. Start at the bay and work outwards.

Can automation increase capacity?

Only by recovering hours that were being lost. A workshop genuinely at capacity has a staffing and premises question, and no messaging changes that.

Is a full diary the goal?

A diary full of correctly priced, correctly sized work is. A full diary of underpriced jobs booked too short produces a busy, unprofitable workshop and a tired technician.

Related reading

• Estimates, approvals and authority
• MOT reminders and the due-date list
• Job updates and the customer who cannot see the car