Route preferences that stick: avoid highways, skip tolls, your rules

Mainstream navigation carries a hidden ideology: fastest is best, and every deviation is a concession to be re-requested trip by trip. Real families know better. The seventeen-year-old three weeks past her road test does not need the Cross Bronx at rush hour; she needs twenty calm minutes of surface streets. The kollel budget does not need four automatic toll crossings a week; it needs the free bridge and eight extra minutes. Preference routing is not a soft feature — for whole categories of drivers it is the difference between a tool that serves them and a tool that frightens them.

Who actually drives on preferences

• The new driver. The graduated licensing idea applies to routes, not just hours: surface streets first, highway merges later, expressways-at-night last. A parent who can set "avoid highways" as the standing rule on the new driver's device — rather than trusting a nervous teen to re-toggle it — has translated the family's graduated-trust ladder into asphalt.
• The toll-conscious household. Toll spend is a real budget line in the corridors this community drives — the crossings between Brooklyn and Lakewood, the turnpikes between simchos. A standing no-toll preference with a "unless it costs more than X minutes" judgment line is how households actually think; routing should speak that dialect.
• The anxious-passenger run. Bubby to the appointment, the carsick kid to camp: the smooth route with fewer merges beats the fast one with four. Preference profiles per trip type — not just per driver — match how families really move.
• The professional, inverted. The trucker's vehicle-aware routing is preference routing at its most consequential — where "avoid" means bridge strikes and citations, not comfort.

Set once, honored always

The engineering principle that separates serious preference routing from a checkbox: preferences are standing policy, defaults that persist, applied before the route is drawn — with the override being the per-trip exception, not the other way around. That inversion is native to a platform whose entire philosophy is that the device carries the household's standing decisions; the same architecture that holds a family's protection posture holds its routing posture. "Your fleet, your rules" is how the KolBo homepage frames the business version of this idea — households have fleets too, and KolBo Go is where their rules meet the road.

The craft of setting them well:

1. Name the profiles, not just the toggles. "Rivky's routes" (no highways, no night parkways), "budget trips" (no tolls under 15 minutes' penalty), "Sunday drives" (scenic bias). Profiles survive; toggles get forgotten.
2. Put the boundary in minutes, not principle. "Avoid tolls unless it saves 20+ minutes" is a rule a family keeps; absolute rules get abandoned the first rainy night.
3. Review at the season change — the standing rules that made sense for the summer van runs deserve a look before the winter yeshiva schedule, the same calendar-anchored review rhythm the luach-aware calendar already gives the household.

“Fastest is a preference too. It just never had to ask permission.”

kolbo.life

When to let the highway win

Preference routing done honestly includes its own limits. Three cases where the calm route is the wrong call: the closing window (the last Mincha, the candle-lighting margin — the Friday-wall math outranks comfort); the empty-road hour, when the feared highway at 6 a.m. is calmer than the surface streets at 8; and the skills plateau — the new driver who never meets a merge stays a new driver. The strong pattern for that last one is deliberate practice runs: the parent-accompanied highway leg on a quiet Sunday, graduating the profile the way every other trust ladder in the household graduates.

Frequently asked questions