Covering the Workshop When Staff Are Off

August is the month the diary stops telling the truth. The bookings look normal, the bays look full, and then you realise the only tester you have is in Spain from the fourteenth and you have four MOTs booked for the fifteenth.

Nobody plans badly on purpose. What happens is that leave gets agreed in one place, usually a conversation in the bay or a message on a Friday, and work gets booked in another. The two never meet until the morning they collide. In a five person workshop that is not a rota problem, it is a visibility problem, and it is worth separating those two things because they need different fixes.

This post is about scheduling and cover. It is not about holiday entitlement or employment law, which is a separate subject and one where you want the actual rules rather than my summary. The government's holiday entitlement guidance is the right source, and ACAS has the plain-English version for anything contentious.

Approve leave against the diary, not against the calendar

The single change that fixes most of this is approving time off while looking at what is already booked.

Most garages approve leave against a mental model of a normal week. But the week someone wants off is rarely a normal week. It might be the week you have three courtesy cars out, or the week the fleet contract does its quarterly batch, or the week your other technician is already off. Saying yes to a request in isolation is how two people end up away on the same Tuesday.

You do not need software to do this. You need the leave request and the booked work in front of you at the same moment. What you should be able to answer before you say yes:

• Who else is already off in that window
• How many hours are already booked in it
• Whether the specific tickets that only one person can do fall inside it

That third one is where garages get hurt, and it deserves its own section.

Protect the roles only one person can fill

Every workshop has capabilities that are not evenly distributed. Usually it is the MOT tester. Often it is whoever is actually confident on diagnostics, or the one person who will touch an EV, or the only technician insured to drive the recovery truck.

General cover does not help you here. If your tester is away, another pair of hands does not get an MOT done, and a customer booked in for a test is not going to accept a service instead. Those bookings need to be either moved before they are taken or held back from the online booking page for that window entirely.

Worth writing down, once, which roles are single-cover in your workshop. Most owners have never listed it and are surprised by how short and how fragile the list is. Once it is written down, leave in those roles gets a different level of scrutiny to leave in roles where anyone can pick up the slack. That is not favouritism, it is just capacity.

Make away visible without making it personal

There is a wrinkle here that is easy to get wrong. The workshop needs to know somebody is not in. The workshop does not need to know why.

Sickness, a hospital appointment, a family matter, a funeral. All of these are reasons someone is away and none of them are the team's business. A board in the workshop that says "Dave, medical" is a small breach of your employee's privacy displayed on a wall, and in the UK health information is a special category of personal data under the ICO's guidance on special category data, so it is not merely bad manners.

The board should say away. That is all anyone scheduling work needs. Autera's time off feature works this way deliberately: the workshop board shows that someone is unavailable and never shows the reason, and the reason is not a field anyone is asked to fill in. It is a scheduling tool, not an HR record.

Stop the booking page selling hours you do not have

If you take online bookings, and you should, the leave calendar has to reach the booking page. Otherwise you spend August ringing customers back to move appointments you never had the capacity to accept, which is a worse customer experience than being honest about availability in the first place.

The mechanics are simple enough. Reduce the bookable slots for the days you are short, or close the service types that depend on an absent role, and let the page reflect the workshop as it will actually be. A customer who sees Thursday unavailable books Friday and thinks nothing of it. A customer who books Thursday and gets a call moving them to Friday has learned something about how organised you are.

This is the same discipline that stops no shows and missed bookings eating your week. Both are cases of the diary promising something the workshop cannot deliver.

Plan the year backwards from the pinch points

A small amount of forward thinking removes most of the pain, and it is not the same as a formal rota.

UK garages have predictable pressure points. Late March and late September for the MOT plate change. The run up to Christmas for everything. School holidays for whoever has children. If you know your own shape, you can decide in January which weeks are genuinely difficult, tell the team early, and let them plan around it rather than refusing requests in July and looking arbitrary.

Being explicit early also removes the worst version of this conversation, which is turning down a request because two other people already asked. If everyone knew in February which two weeks were tight, that conversation happens once, in advance, and without anyone feeling singled out.

What to actually put in place

For a workshop of three to ten people, this is enough:

One place where leave lives. Not a WhatsApp thread, not a wall planner in the office that the technicians never see. Somewhere both the person approving and the person booking work will look.

A rule that leave is approved against booked work. Ten seconds of checking prevents the collision.

A written list of single-cover roles. Tester, diagnostics, EV, whatever yours are.

Leave visible on the shop floor as away, without reasons.

Booking availability that follows the leave calendar, so the diary never sells an hour that does not exist.

We built time off into Autera along exactly these lines, and the design constraint was that it stays a scheduling tool. It tells you who is around so you can plan the work. It deliberately does not track allowances, accruals or entitlement, because that is payroll's job and doing it badly in a workshop system is worse than not doing it at all.

Whatever you use, the test is the same. Can the person booking a job on Tuesday see, without asking anyone, who will be standing in the workshop that day. If the answer is no, August will find you out.