Lunch, Drive Time, Recovery Buffers Built Into Every Rep's Day
Most field-ops tools book appointments and call that scheduling. They show you 8 stops a day and call that "full." Then your reps arrive late to stop 4 because they hadn't accounted for the 40-minute drive from stop 3. Lunch is skipped. Stop 6 gets bumped because the rep burned out after back-to-back visits. Velocity X does time-blocking: when you plan a rep's day, the system auto-inserts a 30-minute lunch between noon and 2pm, calculates drive time between every stop, and adds a 15-minute buffer after each appointment. Your calendar shows the real day—not a fiction where humans are robots.
Here's what changes when time-blocking handles the boring stuff for you.
Why Naive Booking Fails
Assume a rep has 5 customer visits scheduled. The booking tool shows: 9am (Visit 1), 10am (Visit 2), 11am (Visit 3), 12:30pm (Visit 4), 2pm (Visit 5). Looks dense but plausible on a spreadsheet. Reality: Visit 1 is at the customer's site 12 minutes away from base. Visit 2 is in another suburb, 22 minutes from Visit 1. Visit 3 runs 15 minutes over (customer had extra questions). By 12:30pm the rep is 18 minutes late, rolling into Visit 4 at 12:48pm, skipping lunch entirely. Visit 5 gets canceled.
The root problem: scheduling tools measure appointments, not time. They don't know that "10am visit" doesn't mean your rep materializes there at 10am—it means they need to leave earlier. They don't know that after 3 hours of customer-facing time, your rep needs to eat or they'll flake. Velocity X flips this. It plans the rep's *time*, not their *stops*.
The Time-Blocking Algorithm
When you tell Velocity X "book this rep for these 5 jobs this Thursday," the system does this: it fetches the rep's address (or home base), then geocodes each job location. It calculates distance and duration between consecutive stops using the routing engine (Google Maps API + traffic model). Then it applies the time-blocking rules: (1) each appointment gets its duration plus a 15-minute buffer, (2) total travel time is inserted between stops, (3) a 30-minute lunch is auto-inserted between noon and 2pm if no lunch block exists, (4) no back-to-back appointments without a buffer.
The algorithm respects preferences: if a job is marked "40-minute visit" instead of the default 30, time-blocking reserves 40 + 15 buffer. If a rep has a known traffic hazard (e.g., school pickup at 3pm), that time is blocked. If a job is flagged "urgent—back-to-back ok," the buffer shrinks to 5 minutes. The calendar then shows the real timeline. Your rep sees: 8:45am travel to Job 1, 9am–9:30am Job 1, 9:30am–9:52am travel to Job 2, 9:52am–10:22am Job 2, 10:22am–10:44am travel to Job 3… all the way through 12pm–12:30pm lunch, then resume at 1pm. Eight appointments now looks like 7 because time is honestly allocated.
What the Rep's Calendar Actually Shows
In Google Calendar (or Outlook), the rep sees their day as a continuous ribbon of blocks, not discrete scattered appointments. Each job is a calendar event with the exact start/end time—no guessing. Travel blocks appear as "Drive to Job 3" events with the address and expected duration. Lunch is a named block: "Lunch" or "Break" depending on org preference. Buffers are labeled "Buffer" or "Recovery" so the rep knows they're protected time, not "free" time.
Click a travel block and you see: destination address, route (one-click to Google Maps), current traffic estimate, and a "notify dispatcher if delayed" button. Click a buffer and you see: "This block is reserved for travel prep, admin, or recovery. Do not book appointments here." The calendar is the source of truth. If a rep reschedules a job in Velocity X, all downstream blocks (travel, buffers) auto-adjust. If a job runs long and eats into a buffer, the next job's start time shifts automatically and the rep is notified in real-time.
Six Questions Your Team Will Ask
What if a job finishes early?
The buffer still exists in the calendar, but it's now *actual* free time. The rep can use it for admin, a coffee break, or prep for the next job. They can't be auto-booked into a buffer—it's protected. Dispatcher can't override it without the rep's approval.
Can the algorithm handle a 15-minute job in a 30-minute window?
Yes. If a quick assessment takes 15 minutes, time-blocking reserves 15 + buffer = 30. The next travel block starts 30 minutes after the job started, not 45 minutes. You're not wasting time; you're being honest about what's needed and padding for reality.
What about lunch for night-shift or international reps?
Lunch blocks are customizable. Set lunch hours to 1pm–3pm for a late-start team, or disable auto-lunch if reps eat between jobs. Time-blocking is a template, not a rule. You define the org's lunch window and buffer duration on a per-rep or per-team basis.
How does traffic prediction work?
Velocity X uses Google Maps' traffic layer for the day and time of booking. If you book a Thursday 8am slot, the system fetches "what's traffic at Thursday 8am near this area" and adds 30% margin for uncertainty. Historical data will improve this—after 100 jobs in a zone, the system learns "this route is always 8 minutes longer on rain days" and adjusts automatically.
Does time-blocking work for multi-day routes?
Absolutely. Multi-day routes apply the same rules per day. A 3-day regional tour auto-splits into three daily schedules with lunch and travel inserted. Hotel drive time from Day 1 to Day 2 is marked as travel, not a buffer, because it spans overnight.
What if I need to override the algorithm and book back-to-back?
You can. A button in the dispatcher UI says "Ignore buffers for this job." It marks the job as exception and notifies the rep: "This job has no buffer—you're back-to-back. Confirm?" They accept or push back. Managers can see how many exception-overrides happened in a week and adjust hiring/routing if overrides spike.
The Bottom Line
Honest scheduling is harder than fiction scheduling, but it's what makes field teams actually work. Time-blocking isn't about squeezing more jobs in—it's about knowing your rep's real capacity and respecting it. Fewer over-bookings, fewer missed appointments, fewer burned-out reps. Check pricing to see time-blocking in your team's workflow, or dive into how this connects to our two-way Google Calendar sync to keep dispatch and rep calendars in lockstep.