Drive time at different times of day: usual traffic versus rush hour
A drive area drawn for usual traffic is a fair average, not a rush-hour promise. How to read live speeds at peak hours and shrink the area to match.
Part of the guide Location intelligence automation
Drive time at different times of day is best handled in two layers: a drive area drawn for usual traffic, which tells you the normal reach of a site, and live speed readings taken at the hours that matter, which tell you how much slower the roads around it get. If the roads keep only part of their usual pace at 18:00, a 15-minute promise at that hour covers roughly the area a shorter drive covers in usual traffic. That gives you an honest rush-hour picture without pretending to precision you do not have.
This is for anyone who sells or plans by drive time: delivery promises, service areas for repair and installation teams, clinic and dealership catchments, store expansion, school and event transport. It explains what a usual-traffic area is, how to measure the difference at peak hours, a worked example with invented numbers from Lima, mistakes to avoid and the AI employee that does the measuring. It belongs to the guide to AI employees for site selection.
What a usual-traffic drive area shows
The Travel area block draws the area reachable from a place within a travel time (up to 15 minutes for now) or a road distance (up to 10 km), by car, on foot or by bike, along the roads. Its times are for usual traffic, not the traffic at the moment the flow runs. Run it at 03:00 or 18:00 and you get the same shape.
That is a feature, not a flaw. A usual-traffic area is a stable answer you can compare across sites and over months. It is the right base for a catchment or a service territory. What it is not is a guarantee that a driver leaving at 17:45 on a Friday arrives in 15 minutes.
Measure how much slower the peak is
The Traffic Flow block reads the roads around a place at the moment it runs: current speed, free-flow speed, a jam factor from 0 to 10, a congestion percentage and the busiest road. Because it is live, the same flow run at 08:00, 13:00 and 18:00 gives three different answers. Read your site at the hours you care about, on weekdays, for a few weeks, and compare.
- Pick a quiet reference hour, such as 13:00 on weekdays, and the peak hours you sell into, such as 08:00 and 18:00.
- Read the roads within 1 km of the site at each hour for three or four weeks.
- For each hour take the median of current speed divided by free-flow speed: the share of free pace the roads keep.
- Divide the peak share by the reference share. That is the peak factor: 0.6 means the roads near the site move at about three fifths of their midday pace.
A worked example from Lima, with invented numbers
The figures below are made up to show the arithmetic. A home appliance repair firm in Lima promises a technician within 15 minutes' drive of its Miraflores base. It wants to know whether that holds at 18:00.
| Hour | Median speed kept near the base | Peak factor against 13:00 | Rough reach for a 15-minute promise |
|---|---|---|---|
| 13:00 | 0.82 | 1.00 | The 15-minute usual area |
| 08:00 | 0.61 | 0.74 | About the 11-minute usual area |
| 18:00 | 0.49 | 0.60 | About the 9-minute usual area |
Invented readings. Reach is 15 minutes times the peak factor, rounded down.
At 18:00 the 15-minute promise really reaches about as far as a 9-minute drive does in usual traffic. The firm draws two areas with the Travel area block, 15 minutes and 9 minutes, and tells customers in the outer ring that evening slots may take longer. Nothing about the base moved; the promise became honest.
Mistakes to avoid
- Treating a usual area as rush hour. It is an average shape, by design.
- One day of peak readings. A single wet Friday can halve speeds. Use weeks and medians.
- Comparing peak with free flow instead of with your reference hour. Free-flow speed is the empty road at night, which no customer ever drives on. Compare peak with a normal daytime hour.
- Applying one factor to a whole region. A city centre and a suburb slow down differently. Measure each base or store separately.
- Forgetting closures. A sudden closure is not rush hour. Check the Traffic incidents block before blaming the clock.
- Weekend assumptions. Saturday peaks can sit at midday. Measure the days you work.
Let an AI employee measure the peak
One flow collects the readings and another redraws the areas once you know the factor.
- Schedule: weekdays at 08:00, 13:00 and 18:00 in the local time zone, for four weeks.
- My data: your bases, stores or depots.
- Traffic Flow: every road within 1 km.
- Calculated field: speed_kept = speed_kmh / free_flow_kmh.
- Google Sheets: one row per site per run.
- After four weeks, the Data analyst block works out the median share by hour and the peak factors, and emails them.
- A second flow with Travel area draws the usual area and the shorter rush-hour area for each site, then Show on a map.
What lands is a note per site: the peak factor for each hour and two outlines on one map. Templates that use the same pieces: Who my warehouse reaches in 15 minutes, Road speeds around the airport, every hour and Road speeds around the stadiums. Teams in home services and e-commerce use it for delivery and visit promises.
Questions
Do drive-time areas change with the time of day?
Travel areas are drawn for usual traffic, so they stay the same whatever time the flow runs. Live speeds from Traffic Flow show how the roads near a site change across the day.
How do I estimate rush-hour reach?
Divide the share of free-flow speed kept at the peak by the share kept at a normal daytime hour, and multiply your promised minutes by it. Draw a usual area of that many minutes as a rough rush-hour reach.
Is this accurate enough to promise customers?
It is a sound rough guide. For promises, add a margin and check it against your own drivers' times.
Can it predict traffic next Friday?
No. Readings describe the roads when the flow runs. Weeks of readings at the same hours show the usual pattern, which is the best guide to the next Friday.