Set the booking interval from the time your lessons actually occupy, not from what looks tidy on a clock. If a 60-minute lesson regularly needs 15 more minutes for notes, handoff, or setup, its clean block is 75 minutes. A 15-minute start grid can place the next same-location lesson at 10:15 after a 9:00 booking. A 30-minute grid must wait until 10:30, leaving 15 minutes that nobody can book.
The interval is only a rounding rule. It does not replace travel time, service buffers, instructor breaks, vehicle availability, or the student’s eligibility. Calculate those constraints first. Round the surviving start time to the next permitted interval last.
What an appointment interval actually controls
A booking interval—sometimes called a start-time interval or slot interval—controls which clock times customers may choose. With a 30-minute interval, starts might appear at 9:00, 9:30, 10:00, and 10:30. With a 15-minute interval, 9:15 and 9:45 become possible too.
It does not mean the lesson lasts 15 or 30 minutes. A 60-minute lesson can start on either grid. The interval decides how far the system must round forward after everything else has made an earlier start impossible.
Use this calculation:
Earliest feasible start = prior end + prior after-buffer + travel + travel margin + next before-buffer
Offered start = earliest time on the permitted grid that is not earlier than the feasible start
Stranded time = offered start − earliest feasible start
The formulas are simple. The inputs are where bad schedules hide. A pickup change alters travel. A different service may have another buffer. A protected break cannot be used as travel time. This is why an appointment interval belongs after the fuller driving-school availability check, not before it.
Same 60-minute lessons, two different grids
Consider an example day with four 60-minute lessons at the same meeting point. Each lesson also reserves 15 minutes afterward for the student handoff and notes. These are demonstration numbers, not an industry standard.
Each booking therefore occupies 75 minutes:
60 minutes teaching + 15 minutes fixed follow-up = 75 occupied minutes
| Lesson | 15-minute grid | 30-minute grid | Time stranded by 30-minute grid |
|---|---|---|---|
| 1 | 9:00–10:15 occupied | 9:00–10:15 occupied | 0 minutes |
| 2 | 10:15–11:30 occupied | 10:30–11:45 occupied | 15 minutes before start |
| 3 | 11:30–12:45 occupied | 12:00–1:15 occupied | 15 minutes before start |
| 4 | 12:45–2:00 occupied | 1:30–2:45 occupied | 15 minutes before start |
Both schedules deliver four hours of instruction. The 15-minute grid finishes at 2:00 p.m.; the 30-minute grid finishes at 2:45 p.m. Three forced round-ups create 45 minutes of stranded time.
That does not prove every school should use 15-minute intervals. If your true occupied blocks are 90 or 120 minutes, a 30-minute grid may align perfectly. The point is to test the remainder created by your own lesson duration and fixed buffers.
Travel creates a second rounding loss
Now keep the first 60-minute lesson and its 15-minute follow-up, but move the next student to another pickup. Assume the route estimate is 17 minutes and the school adds an explicit eight-minute travel margin.
9:00 start + 60 lesson + 15 follow-up + 17 travel + 8 margin = 10:40 earliest feasible start
- On a 15-minute grid, the next offered start is 10:45. Five minutes are stranded by rounding.
- On a 30-minute grid, the next offered start is 11:00. Twenty minutes are stranded by rounding.
The route estimate and margin are separate inputs. Google’s current Routes API documentation says traffic settings can affect both route selection and estimated duration, and distinguishes traffic-aware options from calculations that exclude traffic. It also notes that some richer traffic data carries a higher billing rate. See Google’s traffic options documentation, last updated September 10, 2026.
A route estimate is not an arrival guarantee. Your school still decides how much uncertainty to tolerate. The scheduling system should apply that policy consistently and should not treat a missing route as zero travel. The deeper two-sided pickup test explains why the proposed lesson must also leave enough time to reach the appointment after it.
Choose the interval with a one-week worksheet
Use last week’s common lesson types and calculate this before changing the booking page:
| Input | What to record | Why it matters |
|---|---|---|
| Teaching duration | 60, 90, 120 minutes, or the actual service length | The customer is buying this time |
| Before-buffer | Vehicle check, pickup handoff, or preparation | It occupies the instructor and car before teaching begins |
| After-buffer | Notes, parent handoff, cleaning, or recovery | It delays the next departure |
| Travel | Time between the actual prior endpoint and next pickup | It changes with the two locations and departure time |
| Travel margin | The school’s separate allowance for uncertainty | It keeps the route estimate from becoming a promise |
| Grid rounding | Minutes from the feasible time to the next allowed start | This is the waste controlled by the interval |
For every real transition, calculate the offered start using both candidate intervals. Then total only the grid-rounding minutes. Do not count a required break, travel, or note buffer as “waste.” Those minutes perform a job.
If a 15-minute grid saves meaningful capacity without offering awkward starts your staff cannot explain, test it. If most blocks already land on the half hour, keep the 30-minute grid. If several service lengths behave differently, use service-specific intervals when the software supports them—or choose the smaller common interval and limit which starts are displayed through actual feasibility rules.
Do not solve visual clutter by hiding usable starts
A finer grid can produce a long booking list. That is a presentation problem, not a reason to discard workable capacity. First remove starts that fail the student, instructor, vehicle, pickup, service-area, travel, buffer, or break rules. Then present the valid choices clearly.
Before enabling a new interval for customers, run four tests:
- Place same-location lessons back to back using the full occupied block.
- Place a pickup-based lesson between two existing commitments and check both travel legs.
- Change the pickup and confirm that old availability is recalculated.
- Protect a real lunch or rest break and confirm that it cannot be borrowed for travel or rounding.
RouteOS publishes this guide and sells driving-school software, so this is a disclosed product perspective. RouteOS’s scheduling architecture is designed to combine permitted start cadences with pickup, route, buffer, instructor, vehicle, and existing-commitment checks. The September 2, 2026 code review supports that design description; it does not prove a particular school has every setting enabled. Review the current RouteOS scheduling overview and ask to see your interval worksheet tested with demonstration addresses.