How to Block Lunch, Admin, and Drive Time on a Service Calendar (2026)

TL;DR

Yes, a scheduling system can block lunch, admin, and drive time automatically, and it does it with four mechanisms working together: buffers that pad each job with travel and reset time, recurring blackout blocks for lunch and paperwork, working-hours rules that define when each technician is bookable at all, and accurate service durations so a job's real length is reflected on the calendar. As of July 2026 this is the difference between a calendar that describes an achievable day and one that quietly sells your lunch break to a customer at 12:00 because nothing told it otherwise. This guide covers the four kinds of time to protect, how to set buffers without strangling capacity, per-technician versus company-wide blocks, and how to hold a genuine emergency slot without letting routine work eat it. It pairs with our guide on reducing no-shows, because a schedule nobody can actually keep produces its own kind of no-show.

Why an unprotected calendar overbooks itself

An online booking page is a very literal machine. It offers whatever is not already occupied. If your calendar shows a 60-minute job ending at 12:00 and nothing after it, the page will offer 12:00, and a customer will take it, because from their side it looks available. Nobody did anything wrong. The calendar simply had no way to know that 12:00 is when your technician eats, or that the next address is 35 minutes away.

The damage compounds through the day. A job booked with no travel allowance starts late. The technician skips lunch to catch up, which works once and not twice. The 2pm arrives at 2:40, the 4pm arrives at 4:55, and the invoicing that was supposed to happen at 5 happens at 8 that night. By Thursday the crew is tired and the customer texts are apologies. None of that shows up as a software problem. It shows up as burnout and one-star reviews about lateness.

The fix is not discipline. It is making the calendar tell the truth about what a day contains, so the booking page can only sell time that genuinely exists.

The four kinds of time to protect

Lunch

A real break, at a real time, every day. Thirty minutes is the practical minimum for a mobile technician and forty-five is more honest once you count getting somewhere to eat. Set it as a recurring daily block, not as something you defend by hand each morning. If your crew genuinely eats at different times, block it per technician rather than company-wide.

Drive and travel time

This is the biggest and most commonly ignored one. In a field-service business, travel is a structural part of the day, not an exception. If your average hop between jobs is 30 minutes and you have five stops, that is two and a half hours of your working day that is not available for work. A calendar that does not account for it is overstating capacity by roughly 30 percent.

Measure it instead of guessing. Take ten recent jobs, compare the booked start time with the actual arrival time, and take the realistic average, not the best case. On Pro plans, live GPS gives you real arrival data over time so the estimate gets more accurate rather than staying a hunch. Our route optimization guide covers how to reduce total travel once you have measured it.

Admin and invoicing

Every completed job produces work after the work: the invoice, the photos, the follow-up call, the part to order, the note in the customer record. If you never block time for it, it happens at 9pm. Thirty to sixty minutes near the end of the day, blocked as unbookable, is usually enough, and it is the single change most owners report getting their evenings back. Software reduces how much of this you need — automated invoicing and reminders shrink the pile — but it never reduces it to zero.

Emergency buffer

If you take urgent work, an emergency has to land somewhere. Without a reserved window it lands on top of a scheduled customer, and now you have two unhappy people instead of one. Hold a window, keep it off the public booking page, and give it a release rule so it is not wasted. More on that below.

What a protected day looks like

Here is a realistic eight-hour field day for one technician, unprotected on the left and protected on the right.

Both columns contain about the same amount of billable work. The difference is that the right-hand column is achievable, so the customer promises hold, the reviews stay good, and nobody works until 9pm to catch up on paperwork.

Buffers: the mechanic that does most of the work

A buffer is padding the system adds automatically around an appointment. Before-buffers cover travel and setup. After-buffers cover cleanup, paperwork, and the job that runs long. The booking page treats buffered time as occupied, so a customer simply cannot book into it.

Two rules keep buffers useful. First, set them per service type, not globally. A quick rekey and a full system installation do not need the same padding, and a single global buffer either strangles your short jobs or under-protects your long ones. Second, review them monthly against reality. If jobs consistently finish inside their buffer, you are leaving billable capacity on the table and can tighten it. If they consistently overrun, the buffer is too small or, more likely, the service duration is wrong.

That second point matters more than the buffer itself. Buffers are a patch on inaccurate durations. If a service is booked as 60 minutes but genuinely takes 85, no buffer setting will save the day, because the error repeats at every stop. Fix the duration in your scheduling settings and the buffer only has to absorb travel and variance, which is what it is for.

Recurring blocks, working hours, and per-technician rules

Three distinct settings do different jobs, and mixing them up causes most of the confusion.

Working hours define when a technician exists on the calendar at all. If someone works Monday to Thursday, Friday should not be bookable, ever, for anyone. This is the outer boundary.

Recurring blocks carve protected time out of working hours: lunch every day at noon, a team meeting every Monday at 8, admin every afternoon at 4:30. Set them once as a repeating rule so they persist without weekly maintenance.

One-off blocks handle the specific: a dentist appointment, a vendor training, a half-day for a school event. These should be as easy for a technician to add on their phone as they are for the office to add on a laptop, because a block that is annoying to create does not get created.

Blocks need to work at both levels. Per-technician for individual needs, company-wide for things everyone observes such as holidays or a shutdown week. The common mistake runs in one direction: applying an individual's block to the whole company, which silently removes real capacity from people who did not need the block. When you audit a schedule that feels thin, look for company-wide blocks that should have been personal.

Once staff roles are in play on Pro and Agency plans, decide who can override a block. Someone must be able to, because a customer will occasionally be worth the exception. But it should be a deliberate act by an owner or admin, not a default anyone can do by accident.

Keeping an emergency slot genuinely open

Reserving emergency capacity has an obvious failure mode: if you hold two hours a day and only use it twice a week, you have thrown away a lot of billable time. If you hold nothing, urgent work lands on top of scheduled customers.

The workable pattern is a hold with a release rule. Reserve a defined window, keep it invisible to the public booking portal, and set a cutoff at which it converts to normal availability if unclaimed — for example, an afternoon emergency window that opens to regular booking at 11am. Emergencies almost always announce themselves in the morning, so by 11am you know whether you need it. Unused capacity goes back into the day instead of sitting empty.

The dispatch view is what makes this work in practice, because when an emergency does come in, whoever answers can see which technician is closest, what they are currently on, and whether the held window still stands. Pro and Agency plans add live GPS and traffic-based ETA on top, so the reshuffle produces an arrival window you can actually tell the customer. If most of your urgent volume arrives by phone while everyone is on a job, the KeyBot AI receptionist on Pro and Agency answers 24/7, qualifies the call, and routes genuine emergencies rather than letting them go to voicemail.

A short setup checklist

Set working hours per technician first, including days off. Add recurring lunch blocks and a daily admin block. Audit every service duration against three real recent jobs and correct the ones that are optimistic. Add travel buffers per service type based on measured drive times, not hopeful ones. Define one emergency window with a release time. Then watch two weeks of actual arrival times and adjust once, rather than fiddling daily.

Protecting time is the least glamorous part of scheduling and the part that most directly determines whether your promises hold. The Bureau of Labor Statistics tracks employment and hours across the skilled trades at https://www.bls.gov if you want a reference point for what a realistic working day looks like in your sector. GetTimePad includes the calendar rules described here on every plan starting at $79 a month, with a 14-day free trial and no credit card required; plan details are on the pricing page, and if you want the broader platform comparison first, see our field service management software guide.

Frequently asked questions

Can a booking app automatically block out lunch and admin time?

Yes. A scheduling system protects that time with three settings working together: recurring blackout blocks for lunch and admin, working-hours rules that define when each technician is bookable at all, and buffers that pad every job with travel and reset time. Once those are set, the booking page simply never offers those slots to a customer.

What is buffer time in scheduling software?

Buffer time is padding automatically added before or after an appointment so the next job cannot start the instant the last one ends. It absorbs drive time, parking, paperwork, and the job that runs fifteen minutes long, which is what stops one late morning appointment from pushing the entire afternoon off schedule.

How much drive time should I build into a service appointment?

Measure it rather than guess. Look at ten recent jobs, compare the booked start times with when the technician actually arrived, and use the realistic average for your service area. Most metro field-service businesses land somewhere between 20 and 40 minutes between stops, and a system with GPS lets you refine it against real data.

Can I block time for one technician without blocking the whole team?

Yes. Blocks should be settable per technician for individual needs such as a standing appointment or a shorter Friday, and company-wide for things everyone observes such as a holiday or a Monday morning meeting. Applying an individual block company-wide is a common mistake that quietly removes real capacity.

How do I keep an emergency slot open without wasting it?

Hold a defined window each day that the public booking page cannot see, and release it to normal booking at a fixed cutoff, such as 11am for an afternoon slot. That way emergency work has somewhere to land, and an unused reserve converts back into billable capacity instead of sitting empty.

How much does scheduling software with buffers and blackout blocks cost?

GetTimePad pricing is flat: Starter is $79/mo for one staff member, Pro is $199/mo for up to five staff and adds GPS with traffic-based ETA, Tech Mode, payments, and the AI receptionist, and Agency is $499/mo for unlimited staff. Buffers, blackout blocks, and working-hours rules are part of the calendar on every plan. See /pricing.