IT, MARKETING & AI
How to Set Appointment Lengths and Travel Buffers for a One-Person Service
Work out the time a customer sees and the time a solo operator actually needs. Test a two-stop route, a lunch boundary and the last booking of the day.
Little things.
Local knowledge.
plazaclass.

A freelance computer technician offers a 45-minute visit. Her last appointment ends at 11:45 in one building, so her booking page offers noon in another. On paper she has a quarter of an hour. In real life she still needs to explain the work, pack her kit, get to the car, travel and find the next unit. A calendar that fits two rectangles together has not necessarily fitted two jobs into a morning.
Build your schedule in three layers: the time promised to the customer, the private time needed around that work, and the rules for which start times may be offered. Use the fictional examples here to sketch a day before putting anything on a public calendar. The numbers are teaching examples, not estimates for traffic between Malaysian towns. For software options, see our appointment scheduling comparison for Malaysian businesses.
Five different settings that can all sound like duration
| Name | What it controls | Example for the worksheet |
|---|---|---|
| Customer appointment | Time spent on the booked service | 45 minutes of on-site assessment |
| Preparation | Private time that must fit before the customer start | 10 minutes to unload and set up |
| Wrap-up | Private time after the customer appointment | 15 minutes for notes and packing |
| Travel allowance | Movement between actual locations | Use a route estimate for the relevant time, then check access |
| Start interval | Which clock times appear as possible starts | Every quarter hour, only if the whole block fits |
These settings answer different questions. A 15-minute start interval does not turn a 45-minute visit into three services. A two-hour minimum notice does not give the operator two hours to drive between consecutive jobs. It governs how late a booking can be made. A limit on bookings per day may control workload without solving an impossible geographical pairing. Decide which problem you are trying to solve before changing the number.
Start the clock before you ring the doorbell
Take an empty sheet and list the last steps before a job: finding the correct entrance, signing in if required, unloading equipment and reaching the actual work area. Then list the steps after it: explaining what was completed, collecting the kit, recording any promised follow-up and returning to a place where travel can begin. Classify each as customer-facing time or private time. Do not count the same activity twice simply because the worksheet has two columns.
If the service promises a 45-minute assessment including explanation, keep that explanation inside the 45 minutes. If it promises 45 minutes of hands-on work and then an explanation, a 45-minute booking is misleading. Tighten the public description or reserve the additional time. Make the decision before comparing one app with another. No calendar product can infer from “standard visit” what you actually intend the customer to receive.

Work through one route by hand
Suppose the first customer appointment starts at 9:30 and ends at 10:15. The technician needs 15 minutes to finish private notes and pack, so she can leave at 10:30. For this fictional exercise, allow 25 minutes for travel and 10 minutes for setting up at the next location. She can start the next customer visit at 11:05, not 10:40. If starts are offered only at quarter-hour intervals, 11:15 is the earliest candidate, subject to everything else on the calendar.
Now suppose the second visit lasts 60 minutes and requires a 10-minute wrap-up. Beginning at 11:15 makes the customer finish 12:15 and the operator finish 12:25. If she has a fixed commitment at 12:15, the second appointment does not fit. Moving the start back to 11:00 does not fix it, because she cannot be ready then. The honest options are a different slot, a genuinely shorter service with clear scope or no booking on that route.
Decide where travel belongs
Some businesses reserve a fixed margin after every mobile appointment. That is easy to explain but can be wasteful for jobs in the same building or too short for different areas. Another arrangement is to group a small area into one session and use a named travel block between sessions. That works only if bookings really stay within those areas. A page saying “Klang Valley” is not a useful constraint if it accepts any address in the region back to back.
Pick one accounting convention. If travel is a separate calendar block between areas, do not also add the full journey to the outgoing and incoming appointment buffers. If the route is unknown until the customer replies, do not sell a precise immediate slot that depends on a journey you cannot yet assess. Offer a request for a time window and explain when the actual appointment will be confirmed. “Requested” and “confirmed” must mean different things to staff and customers.
Test the boundary, not just the middle of the day
| Boundary to test | Make this fictional request | Decide whether it should be offered |
|---|---|---|
| Opening | Customer chooses 9 am; preparation needs 15 minutes | Only if you are genuinely available from 8:45 |
| Lunch | A long service ends before lunch, but its wrap-up runs into lunch | If the break is protected, reject or move it |
| Different area | Second visit begins while the first route is still in progress | Do not offer the start merely because the first customer has finished |
| Closing | Final customer ends at closing time with work still to pack | Make room for the full private block or offer an earlier time |
| Remote session | Online advice follows an on-site job | Include a suitable place and time to reconnect, not just internet access |
Use all five tests on a non-public example calendar with fictional appointments. Pick one date and write your expected result before checking the booking page. If a start appears that should not, look first at service duration, the calendar checked for conflicts and the actual busy interval. If a valid start disappears, check whether you counted prep twice, marked an entire day as busy or chose a wider notice rule than intended.
See what the customer sees and what the operator sees
Microsoft’s service-availability guidance distinguishes time reserved around a booking from the appointment a customer is offered. This is a useful feature to investigate rather than assume. In your chosen tool, make a dummy 10 am appointment. Compare the appointment range in the customer preview with the busy period on the operator calendar. A customer who thinks a technician will be in their home for 90 minutes may be disappointed if the quoted visit was actually 45 minutes plus private travel.
Write the public wording in ordinary terms: “The visit is for a 45-minute assessment. Tell us your area before the slot is confirmed. We will contact you if the address is outside the planned route.” Use that wording only if it matches the process. Avoid showing the previous customer’s address or other appointments as evidence that the route is full. A person needs to know whether their own slot can be booked, not who else is on the calendar.

Plan for jobs that do not end on time
A buffer is not free service time to sell repeatedly. If nearly every standard visit uses its whole margin for ordinary work, the appointment description or duration may be wrong. Separate truly unpredictable overruns from a regular step you forgot, such as collecting a signature or waiting at a building entrance. For future planning, note the type of delay rather than a customer’s private details.
Consider a job that unexpectedly needs more work. Before extending it, check the commitments that follow. Can the issue be documented for a separate visit? Does a later customer need an update? A reminder sent automatically at the original time does not prove you will arrive then. Give a realistic update through the agreed channel rather than shortening the next customer’s paid appointment silently to recover a timetable error.
Choose the least complicated schedule you can keep
If you serve a small radius from one base, a simple service duration plus a conservative margin may be sufficient. If addresses vary greatly, offer neighbourhood sessions, provisional time windows or manual approval for outliers. An accurate modest schedule beats a beautiful page full of slots the owner must move by hand. If a customer comes to your shop rather than you travelling, build a separate service type; don’t charge every shop visit the time cost of a distant callout.
Keep one line in your weekly notes for what changed. For example: “More time now reserved for parking at high-rise sites; test both the morning start and the last afternoon booking.” Then run the boundary cases again. Customers with an existing booking should not be quietly moved simply because a default duration changed for future appointments. Confirm any change to their own arrangement separately.
Frequently asked questions
Should the travel allowance be the same for every address?
Only if the area and working conditions make that reasonable. When you cannot estimate a route reliably, ask for an area before promising an exact start or operate by a clearly explained service window.
Can I include lunch inside the buffer?
Do not rely on a variable gap to protect a fixed break. If lunch must be available, block it as unavailable and test a booking whose private work would overlap it.
Is the worksheet a recommendation for exact driving times?
No. The arithmetic shows how to combine different types of time. Substitute your own route, access arrangements, availability and customer promise.