Sao Paulo traffic for field service: planning a technician's day
Installers and repair technicians in Sao Paulo lose hours to the Marginais, rain and plate rotation. How to split the city, order jobs and check the roads each morning.
Part of the guide Location intelligence automation
Sao Paulo traffic for field service teams is less a daily surprise than a set of known patterns: the Marginais and the main corridors slow badly in the morning and evening peaks, summer storms can flood underpasses in an hour, and the number plate rotation keeps each car out of the expanded centre at peak times one weekday a week. Technician days work best when they are planned around those patterns. Give each technician one compact zone, keep jobs that cross a river or a corridor out of the peaks, and check closures, live road speeds and the afternoon rain before vans leave.
This article is for operations managers at internet and pay-TV installers, lift and air-conditioning maintenance firms, appliance repair networks and other businesses with technicians on the road in Greater Sao Paulo. It covers the city's patterns, how to split the work, a morning check that takes no one's time, an invented week, and an AI employee that prepares each day.
The patterns every dispatcher already knows
- The rivers and the Marginais. Crossing between zones means a bridge and often a stretch of Marginal Pinheiros or Marginal Tiete, the two roads that jam first.
- Plate rotation. On one weekday each vehicle, by the final digit of its plate, cannot drive in the expanded centre during the peaks. A van routed through it on the wrong day collects a fine.
- Summer storms. Heavy afternoon rain from roughly December to March floods low streets and underpasses and turns a 20-minute drive into an hour.
- Building access. Many jobs are in condominiums with gatehouses, booking rules and service lifts, so stop times are long and fixed.
Split the city before you order the jobs
The biggest saving is not the perfect route but keeping a technician on one side of the river all day. Split by territory shares the day's jobs between your technicians by area, as compact zones of about the same size, and names each zone by its direction from the middle. Route planner then orders each technician's jobs from their start, such as home or a base, with the kilometres and minutes between stops. Routes are planned from typical travel times, not live ones.
The morning check
Three readings, taken around 6:30, cover most of what changes overnight.
- Traffic incidents checks around each job for road closures and roadworks, and adds the nearest one with its distance.
- Traffic Flow measures the bridges and corridor junctions your zones depend on: live speed, free-flow speed and a jam factor from 0 to 10. It is a snapshot and does not count vehicles, so take it close to departure.
- Weather forecast gives the rain expected at each job that day, so afternoon jobs in low areas can move to the morning.
An invented week for an installer
Say an internet installer has six technicians and about 40 installs a day. The example is made up to show the habit, not measured.
| Day (example) | What the morning check found | What the dispatcher changed |
|---|---|---|
| Monday | Roadworks near three Pinheiros jobs | Moved them after 11:00, when the crew is finished |
| Tuesday | Bridge on the west zone reading Heavy at 7:00 | West technician starts on the near side, crosses at 10:00 |
| Wednesday | Heavy rain forecast from 15:00 | Low-lying afternoon jobs moved to Thursday morning |
| Thursday | Nothing unusual | Nothing |
| Friday | Closure on the access road to a big condominium | Customer called, slot moved to the afternoon |
Invented events. Real runs give the closures, speeds and rain for your own jobs.
Most days the check finds little. Its value is the one morning a week it saves a technician two hours in a queue and a customer a missed slot.
What to keep in mind
- Traffic Flow gives speeds and the jam factor, not car counts or history. Keep each reading in a sheet if you want your own record by weekday.
- Incident positions are accurate to about 150 metres, close enough to judge a street, not a single gate.
- Where visitors come from is measured in Sao Paulo, month by month, in Mobility Footfall, but that is for shops and sites, not for planning vans.
An AI employee for the dispatch desk
An AI employee can prepare the day every morning and send each technician only their part.
- Schedule at 6:15 on weekdays.
- My data or New rows brings in today's jobs with addresses.
- Split by territory gives each technician a zone; Route planner orders it.
- Traffic incidents and Weather forecast add closures and rain to each job.
- xMap LLM writes a two-line note per technician: start here, avoid this, rain after 3 pm.
- A message per technician, and a summary to the dispatcher.
The Road closures and storms at today's install sites template does the morning check, and Weekly home services ops brief sums up the week. For more on field teams, read the guide to AI employees for field operations.
Questions
What time should technicians leave in Sao Paulo?
It depends on the zone, but starting the first job before the morning peak and keeping river crossings out of the peak hours saves the most time. Your own readings over a few weeks show when each bridge clears.
Can the flow handle plate rotation?
Yes, if your job or van table has the rotation day. A Filter or Branch can move jobs in the expanded centre away from a van on its restricted day.
Does the route planner use live traffic?
No. It orders stops from typical travel times. Live speeds and closures come from the morning check, which you read before vans leave.
Can it warn about storms?
Yes. The Weather forecast block gives rain expected at each job, so afternoon jobs in flood-prone streets can move earlier.