How to Plan a Van Route: Catchments, Dwell Time and Peak Windows

A van route plan is a written day schedule that lists, in order, the catchments a vehicle will visit, the time window it will be in each, the dwell duration at each stop, and the transit legs between them. It is not a map line and it is not a distance target. The distinction matters because the two produce completely different campaigns.

A distance-led plan optimises for kilometres and ends up moving through empty roads at speed to hit a number. A catchment-led plan optimises for time-in-place and accepts fewer kilometres in exchange for being present where the audience is. Everything else in route planning follows from that choice.

The plan should also carry the constraints explicitly: restricted-entry corridors, silence zones where audio must be switched off, no-parking stretches, and any hours during which heavy vehicles are barred from a road. Written down at planning stage, these are design inputs. Discovered on the day, they are a driver improvising, and improvisation is what breaks the link between the plan and the report.

A catchment is a place where the target audience predictably concentrates: a wholesale or retail market, a transport node such as a bus stand or a station approach, a mall or high-street frontage, a residential cluster at the hour people return home, a college or institutional gate, an industrial or IT campus at shift change, a hospital precinct, a weekly market ground. Begin by listing the catchments that match the brand's audience, then rank them, then build the route to connect the top ones. Working the other way round - picking a road because it looks busy on a map - produces routes that spend the shift in traffic between the places that mattered.

Ranking should use the brand's own distribution data where it exists. If the sales team can name the twenty outlets that carry the SKU and the ten that should, those addresses are the route. This is also the step where a brand should decide what it is not covering, because a route that tries to include every zone in a city covers none of them with enough frequency to register.

Dwell time is how long the vehicle stays within a catchment, either parked at an agreed position or circulating slowly through it. It is the most consequential number in the plan and the one most often left undefined. A van that passes a market at road speed is seen by whoever happens to be facing the road at that moment.

A van that holds a position at the market entrance for thirty minutes is seen repeatedly by everyone entering and leaving, gives promoters time to work the footfall, and produces photographs worth reporting. In our deployments the pattern that works for a printed vehicle is a smaller number of substantial holds rather than many brief passes, and for an LED vehicle the case is stronger still, because a screen needs a stationary audience to deliver a full loop. Assign dwell explicitly per catchment in the written plan - this many minutes, at this position - and treat transit as whatever time is left. Plans built the other way round consistently underdeliver on the catchments that mattered most.

Timing decides whether a dwell slot is worth having. Across our deployments the reliable urban pattern is an early-to-mid morning window when neighbourhood markets, vegetable vendors and daily-needs shopping are active, a quieter middle of the day, and a strong evening window from roughly 6 pm to 9 pm when both retail footfall and residential return coincide. Weekends shift the curve, with afternoon activity in malls and high streets that weekdays do not produce.

Institutional catchments run on their own clocks: campus gates peak at entry and exit hours, industrial areas at shift change, transport nodes at commute times. The planning move is to align the highest-ranked catchments with their own peaks rather than with a convenient slot in the route. If the priority market peaks at 7 pm and the route reaches it at 3 pm, the route is wrong even though the market is on it. Where a campaign has more priority catchments than peak windows, the answer is more vehicles or more days, not a faster route.

Honest capacity planning prevents most route disappointments. A standard shift in our deployments runs eight to ten hours including breaks and refuelling, and once meaningful dwell is assigned to each stop, the number of genuinely productive positions in a day is smaller than most briefs assume. Dense metro cores reduce it further, because transit between catchments consumes time that lighter tier-2 traffic would not.

Vehicle class matters too: an e-rickshaw at ₹1,200 a day circulates a small area well but cannot link distant catchments, while a Tata Ace at ₹3,200 or a pickup can cross a city between holds. The correct response to a long catchment list is to add vehicles rather than compress dwell, because compressing dwell degrades every stop rather than dropping the weakest one. A useful test at plan sign-off: if a stakeholder asks to add one more location, ask which existing stop loses its time. If the answer is none, the plan is already overbooked and will fail quietly.

Campaigns with several vehicles need a coverage design, not several copies of one route. Split the city into zones and assign a vehicle to each, so the fleet builds frequency across a wide area rather than repeating impressions on one corridor. Stagger loop timings within a zone so a resident encounters the wrap at different points in the day rather than at the same hour each time, which is what turns exposure into recall.

Where an LED vehicle is in the mix, treat it as a hub asset serving the highest-crowd positions in the campaign while small-format vehicles seed the surrounding catchments and drive people toward it. Where promoters are deployed, keep the crew with the vehicle that has the longest holds, since sampling needs dwell and cannot work from a moving van. In our experience a zone-based grid of three or four vehicles covering adjacent municipal wards produces a materially stronger presence than the same budget spent on one large vehicle running a long city loop.

A route plan is only useful if adherence to it can be checked. Every Vehicle Branding van carries a 4G GPS unit, and clients receive a daily report showing the route actually driven against the route planned, together with time-stamped photographs taken on the ground. That report has two functions.

The obvious one is assurance, replacing the trust-based reporting that has long been the weak point of van advertising in India. The more valuable one is correction. When the log shows a vehicle sitting in transit for far longer than planned between two catchments, or reaching a priority market after its peak had passed, that is actionable information for the following week.

Brands that read the daily report as a compliance document extract the first function only. Brands that read it as route diagnostics extract both, and their week-three routes look noticeably different from their week-one routes. The report should be reviewed by whoever owns the campaign, not filed by whoever receives it.

No route survives contact with a real city intact, and the plan should assume revision rather than resist it. The natural review point is the end of the first week, once enough daily reports exist to show which holds worked, which windows were missed and which transit legs cost more than they returned. Typical corrections are small and high-value: shifting a market hold from afternoon to evening, dropping a catchment that photographed empty, extending dwell at a position that produced consistent crowd, or re-sequencing to avoid a corridor that jams reliably at the same hour.

Larger corrections - adding a vehicle, changing vehicle class, extending into an adjacent ward - need commercial sign-off, so the change process and who approves it should be agreed before the campaign starts rather than negotiated mid-flight. The brands that get the most from van advertising are not the ones with the best week-one plan. They are the ones that treat week one as measurement and are willing to rewrite the schedule on the evidence.