Leaving “15 minutes between calls” can sound like sensible advice. But it is only sensible if the drive, the close out work, the next customer’s promise, and the uncertainty in the job all happen to fit inside those 15 minutes. For a mobile service business, the time between calls is not a standard gap. It is a transition you have to plan.
Why a fixed gap usually fails
A calendar only shows the space between two appointment blocks. It may not show the work that connects them. If the first job runs to its stated end time but you still need to explain the repair, take payment, write notes, load up, drive across town, and park, the second job has already inherited a delay.
That does not mean every gap should be large. It means the gap should be tied to a real sequence. Microsoft’s field service documentation, for example, treats travel time as part of a technician’s working hours by default and models travel alongside bookings. That is evidence of how one scheduling system handles the constraint, not a universal rule for every service business. Read the Microsoft documentation.
Build the transition, not just the gap
Use this simple planning model between two jobs:
finish and close out at Job A
+ travel from Job A to Job B
+ parking / access at Job B
+ contingency for uncertainty
= transition time to protect
This is a PickTime planning model, not an industry standard formula. It is intentionally visible: once you can name each part of the transition, you can decide whether it belongs in every job type, only certain locations, or only days that need extra resilience.
A worked example
Assume a repair visit is scheduled to finish at 10:00 AM. The next customer has been promised a 10:30 AM arrival. You have confirmed the addresses and are estimating a normal transition, not claiming that these are average times.
The 30-minute calendar gap is 10 minutes short. You might change the promise for Job B, move another flexible job, reduce the contingency only if you understand the risk, or offer a later opening. The useful decision is not “should gaps always be 40 minutes?” It is “what would have to go right for this 30-minute transition to work?”
What changes the amount of time you need?
Travel and geography
Use the travel estimate for the actual order of jobs, not a rough average across your service area. A five minute move within one neighbourhood and a 25 minute move across town should not have the same gap. Account for the drive between adjacent jobs once, not once as the end of Job A and again as the start of Job B.
Job uncertainty
Diagnostics, first visits, difficult access, parts questions, and work you have not seen before often deserve more protection than a routine follow up. The goal is not to predict every surprise; it is to choose where a normal surprise should land without breaking the rest of the day.
The promise to the customer
An exact 10:30 AM appointment requires a tighter plan than a 10:30 AM–12:00 PM arrival window. Neither is automatically better. Use an exact time when the work is dependable enough to support it; use a window or daypart when that is a clearer, more realistic customer commitment.
Your own close out routine
The transition is not only driving. If you reliably need time for payment, a quote, photos, job notes, loading materials, or a customer handoff, that time belongs somewhere in the schedule. Ignoring it does not make it free.
How to set your starting buffer
- Review a small set of recent days. Pick completed jobs that resemble your usual work. Note the actual time from one customer facing commitment to the next.
- Separate the pieces. Estimate close out, travel, access, and contingency rather than writing down one unexplained gap.
- Create a few practical categories. You might plan differently for nearby follow ups, first visits, and jobs that require diagnostic work. Do not create so many categories that you cannot use them while taking a call.
- Test the plan against the next week. Look for commitments that depend on everything running perfectly. Adjust before customers are promised times.
- Review after disruptions. When you run late, ask which part of the transition was missing or underestimated. Improve the estimate rather than treating every late day as bad luck.
When a tighter day can still be sensible
A less dense schedule is not always a better schedule. Two known, nearby jobs with flexible windows may reasonably sit closer together than two uncertain jobs with exact start times. The test is whether the sequence is realistic and whether the remaining day can absorb a normal change.
This is the resilience part of scheduling. Maximum calendar density can look productive until one overrun turns into several late customers. Protecting a deliberate buffer may mean fewer apparent openings, while making the appointments you do take more reliable.
A quick check before you book the next call
- What must happen before I can leave the current job?
- What is the travel time for this actual sequence?
- Does parking, access, or setup need time at the next job?
- How uncertain are the jobs on either side?
- What exact time, window, or daypart have I promised?
- If the first job runs long, which commitment am I protecting first?
If you cannot answer those questions quickly, the slot is not ready to promise. Start with a wider option, then tighten your estimates as your own completed work gives you better information.
BUILD MORE REALISTIC AVAILABILITY
See the schedule behind the opening.
PickTime combines bookings, manual blocks, and imported calendar events in one schedule, and uses the customer address when checking booking availability.
Set up PickTimeRelated reading: How to Schedule Jobs by Location and The Complete Guide to Scheduling a Service Business.