How Travel Time Affects Your Bookable Slots
AwardLettr uses real-time traffic for same-day bookings and historical traffic plus a sliding buffer for future days. Here is exactly how it picks (and blocks) slots, and where appraisers lose money if they get this wrong.
You'll learn
- How AwardLettr computes travel for same-day vs. future-day bookings
- Why between-appointment travel starts from the previous appointment, not from your home
- How the 15% sliding buffer (clamped 5 to 20 minutes) protects future-day estimates
- How max_drive_time_minutes silently blocks slots and how to tune it
Why this matters
You set max_drive_time_minutes to 30 to keep your day tight. The next morning, your booking page shows two open slots for the entire week. Or the opposite: you leave the defaults alone, accept a booking that looked fine on screen, and find yourself driving across town in rush-hour traffic to make an 8 AM inspection. Neither outcome is the system being broken. Both are the travel-time model doing exactly what you told it to.
If you do not understand how AwardLettr picks the origin point, when it uses live traffic versus historical averages, and where the max_drive_time setting silently blocks slots, you will spend an hour fighting the booking page, give up, turn off the constraints, and then take a booking that costs you half a day in windshield time. Worth ten minutes to read this once.
This article is for anyone who covers more than one metro area, anyone whose markets include rush-hour-sensitive corridors, and anyone who has ever looked at a confirmed booking and thought "wait, how did this slot even pass the filter?"
Travel time is the single biggest factor in which slots the opposing appraiser sees on your booking page. Get it right and you fill the day efficiently. Get it wrong and you either drive coast to coast between two inspections or you watch half your day go dark in the booking link because the math blocked it.
The two-mode rule
Mode 1: same-day bookings use live traffic
When the slot being evaluated is for today, AwardLettr calls the Google Routes API in TRAFFIC_AWARE mode. This returns the real-time drive time given current road conditions: accidents, construction, weather, the works. No buffer is applied because the number is already a live estimate.
A slot that was bookable yesterday might not be today
Mode 2: future-day bookings use historical traffic plus buffer
When the slot is for any future day, AwardLettr calls Routes in TRAFFIC_UNAWARE mode (which returns a historical average for the time of day and day of week), then adds a sliding buffer. The buffer is 15% of the historical drive time, clamped to a minimum of 5 minutes and a maximum of 20 minutes. Short trips get a small buffer; long trips get capped at 20 minutes so a 2-hour drive does not balloon into 2 hours 30 minutes.
| Historical drive time | 15% buffer | After clamp (5-20 min) | Effective time |
|---|---|---|---|
| 10 min | 1.5 min | 5 min (floor) | 15 min |
| 30 min | 4.5 min | 5 min (floor) | 35 min |
| 60 min | 9 min | 9 min | 69 min |
| 90 min | 13.5 min | 13.5 min | 103.5 min |
| 120 min | 18 min | 18 min | 138 min |
| 150 min | 22.5 min | 20 min (ceiling) | 170 min |
Where the trip starts (this is the gotcha)
The origin point depends on whether the slot is your first appointment of the day or a later one. This trips up new users who assume AwardLettr uses the opposing appraiser's address or the property address as the starting point. It does not.
Origin: your home
First appointment of the day starts from your home address (set in Profile)
Travel calc
Same-day: live traffic. Future: historical + 15% buffer (5 to 20 min)
First appt
Slot is bookable if travel fits inside max_drive_time_minutes
Travel calc
Same logic, but origin is now the previous appointment's address
Next appt
Each subsequent slot anchors off the appointment before it
Slot scenarios at a glance
| Situation | What AwardLettr does |
|---|---|
| First appointment, today | Live traffic from your home address to the property. No buffer. |
| First appointment, future day | Historical traffic from your home address plus 15% buffer (clamped 5-20 min). |
| Second appointment, same day as the first | Live traffic from previous appointment's address to the new property. |
| Second appointment, future day | Historical traffic from previous appointment's address plus the sliding buffer. |
| Slot where travel exceeds max_drive_time_minutes | Blocked. The opposing appraiser does not see it on the booking page. |
| Property outside all your zones | Falls back to the closest zone's availability windows, then runs the same travel math. |
| No home address on file | First-appointment travel cannot be calculated. Slot scoring degrades and slots may be miscategorized. |
The max_drive_time_minutes setting (read this carefully)
This profile setting is the hard ceiling. Any slot where computed travel exceeds it gets blocked from the booking page. The default is 60 minutes. Set it to match how far you are actually willing to drive between back-to-back inspections.
Do not set max_drive_time too low
Rush hour: a penalty, not a block
Slots that fall into rush-hour windows lose points on the slot score (so they show up lower in "Most Likely to Be Confirmed"), but they are not removed from the booking page. The opposing appraiser can still pick them. This is intentional: sometimes a 7:30 AM slot is the only thing that works for them, and you would rather accept than miss the appointment entirely.
When things go sideways
Diagnostic walkthrough
The booking page looks too empty. What is the most likely cause?
Common pitfalls
- •Setting max_drive_time_minutes too low. Blocks half the day before anyone sees the booking page.
- •Forgetting to update your home address after moving. First-appointment travel anchors off the wrong origin and slot scoring quietly degrades.
- •Assuming the booking flow uses the opposing appraiser's address as origin. It does not. It uses your home (for the first appointment) or your previous appointment (for everything after).
- •Expecting future-day travel to match what Waze tells you the morning of. Historical averages skew higher than a "no traffic" day, lower than a major incident. The 15% buffer absorbs normal variance, not chaos.
- •Treating rush-hour deprioritized slots as bugs. They are intentional. Slots score lower but stay bookable so a tight-deadline opposing appraiser can still grab one.
Next steps