The shortest path is a pedestrian path
Delivery drivers do one thing very well: they find the shortest route to the door. On most campuses, the shortest route crosses the quadrangle, runs along a colonnade full of people, or reverses across the walkway between the main car park and the largest building. Nobody chose that route on a drawing; it was chosen at eight in the morning by the first driver who turned in.
Left alone, that behaviour hardens into a de facto network of vehicle movement through the busiest pedestrian space on the site. The near misses accumulate quietly: a reversing van and a group of students, a courier idling across a crossing, a catering van blocking the fire route while it unloads. A delivery route plan exists to replace that accident of habit with a decision.
Map the flows before the rules
Spend a week counting. Note where delivery vehicles actually enter, stop, and leave, at what times, and how often. Note the pedestrian desire lines at the same hours. Overlay the two and the conflict points announce themselves: usually the campus entrance, the main crossing, and the service yards of the largest buildings.
With the flows mapped, the routing decisions become concrete. Which entrance serves vehicles, which serves people, where the timed windows are, and which route can genuinely carry a seven-and-a-half-tonne truck, including turning radii, surface strength, and overhead clearances. A route drawn without checking that a truck can physically make the turn produces a plan that drivers will ignore within a week.
Windows, not bans
Banning deliveries outright tends to fail, because the campus still needs feeding and stocking. Delivery windows work better: agree the hours when goods vehicles may enter, coordinate them with the pedestrian pulses such as class changes and lunch, and give each building a slot. A shared calendar, however simple, is the cheapest traffic management tool a campus owns.
The windows need an owner. Someone must hold the schedule, tell repeat suppliers about it, and turn away the van that arrives outside its slot. Without an owner, the windows decay into suggestions, and the campus reverts to first-come routing. The role is part of facilities management, takes minutes a day, and pays for itself in avoided incidents.
Design the stopping places
Drivers stop where it is safe to stop, and if the campus offers no designated place, they improvise. Marked bays, dock levellers, or a simple hatched standing area near each served building give the legitimate stop a home. The bay should sit off the pedestrian desire line, with a marked walking route from the bay to the goods entrance so the trolley run does not cross the quad.
Where the goods entrance faces a busy walkway, physical separation matters more than signage: a level change, planting, bollards, or a simple alignment that puts a reversing manoeuvre out of the main flow. Sightlines at the bay deserve a check too; a driver who cannot see the crossing they are reversing toward will reverse on trust.
Small vehicles are part of the plan
The routing debate usually fixates on trucks, but couriers on bikes and scooters, ride-hail drops, food delivery riders, and campus maintenance vehicles create the higher-frequency conflicts. Their arrival pattern is continuous rather than pulsed, which means they meet pedestrian flows dozens of times a day in small ways.
Give small vehicles their own logic: a clearly signed drop and collection point off the main desire line, marked cycle and scooter parking near the buildings they serve, and a rule for ride-hails that names the door and the waiting area. These measures cost paint and signs. They remove a large share of the daily friction without touching the freight route at all.
Safety behaviours and the marshal question
Large or awkward deliveries, equipment moves, and event logistics may need a marshal: a named person who walks the vehicle onto the site, controls the crossing, and stays until the vehicle leaves. The marshal rule is cheap insurance, and it belongs in the plan with a trigger, such as any reversing manoeuvre outside a dock or any vehicle over a defined size.
Brief the drivers as well as the staff. A one-page site map at the gate, a card with the windows and bay locations given to repeat suppliers, and a rule that first-time drivers report to reception costs almost nothing. Most drivers want to do the right thing; they simply have never been told what it is on this site.
The traditional reading of service thresholds
Traditional spatial practice keeps service movement at the edge of a compound, with the approach and threshold reserved for people and ceremony. Vastu carries the same instinct: heavy, routine, and utilitarian movement belongs away from the principal approach. A campus that routes its trucks around the perimeter and its people through the centre is following a very old spatial idea with very modern justification.
The reading is useful in design debates. When a new building's service yard is proposed on the main approach because it is cheaper, the traditional objection and the safety objection will say the same thing. Saying both strengthens the case and keeps the decision from being made by default on a cost line.
The plan and its upkeep
The deliverable is one page: the vehicle and pedestrian networks overlaid, the conflict points marked, the windows and bays listed, the marshal triggers, and the supplier briefing pack referenced. Circulate it to repeat suppliers, pin it at the gate, and review it whenever a building changes use or a new major tenant arrives.
Re-walk the site twice a year. Delivery patterns drift as suppliers change and as buildings fill, and the plan that is not updated silently stops describing reality. The half-day of observation that catches the drift is the cheapest safety work on the campus.
Campus delivery route checklist
| Item | What a pass looks like |
|---|---|
| Flow mapping | A week of observed vehicle and pedestrian flows with conflict points marked |
| Physical feasibility | The planned route verified for turning radii, surface strength, and overhead clearance |
| Delivery windows | Agreed hours per building, held by a named owner, shared with repeat suppliers |
| Stopping places | Marked bays off the pedestrian desire line with a defined trolley route to the goods entrance |
| Separation | Reversing manoeuvres kept out of the main pedestrian flow by design, not signage alone |
| Small vehicles | Signed drop and collection points, marked cycle and scooter parking, a ride-hail rule |
| Marshal triggers | Named situations requiring a marshal, with the role assigned in the plan |
| Supplier briefing | One-page site map and rules issued to repeat drivers; first-time drivers report to reception |
| Review cycle | The plan re-walked twice a year and after any change of building use or major tenant |
FAQ
Why not simply ban deliveries during the day?
Because the campus still needs stocking and the ban will be broken by whoever is most urgent. Timed windows with a named owner achieve the separation a ban promises while remaining workable for suppliers.
How do we know a truck can actually use the planned route?
Check the geometry before publishing the route: turning circles at every corner, surface loading, gate widths, and overhead obstructions such as canopies and cables. A route a seven-and-a-half-tonne truck cannot physically drive will be ignored by the second driver who tries.
What about food delivery riders?
Give them a named pickup point off the main desire line, marked on the map at the gate. Their arrival pattern is continuous, so a single well-chosen point removes dozens of small conflicts a day without affecting freight at all.
When is a marshal needed?
For reversing outside a dock, vehicles above a defined size, or deliveries during a pedestrian pulse. The rule belongs in the plan with a named person per trigger, and the marshal stays until the vehicle has left the site.
How do we get drivers to follow the plan?
Brief them at the point of arrival: a one-page map at the gate, cards issued to repeat suppliers, and a rule that unknown drivers report to reception. Drivers follow plans they were actually given; they improvise when nobody told them.
Does Vastu have a view on where service traffic belongs?
Tradition places heavy, routine, utilitarian movement at the edge of a compound, away from the principal approach. That matches modern separation of vehicle and pedestrian movement, and the two arguments reinforce each other in design debates.
How often should the plan be reviewed?
Twice a year, plus after any change of building use, a new major tenant, or a change of main supplier. Delivery patterns drift, and an unreviewed plan stops describing what drivers actually do.
What is the first practical step?
A week of observation. Count where vehicles actually enter, stop, and leave, and when the pedestrians move. The conflict points and the realistic windows come out of that week; everything else is drawing.
Sources and verification notes
The factual building-performance and safety statements above were checked against the following public references on 20 September 2026. Traditional interpretations are presented as interpretations, not measured causal claims.
- Health and Safety Executive: workplace transport safety
- US Government Publishing Office: 29 CFR 1910.176 materials handling
- US Access Board: accessibility standards for the built environment
- Project for Public Spaces: public space guidance
- US Occupational Safety and Health Administration: workplace safety resources