Hello Suburb guide

What is Hello Suburb and who is it for?

Hello Suburb is a practical delivery programme built for South African SME teams running estate and complex parcels. It is not designed for single-package couriers or businesses with a full 3PL stack. Instead, it fits growing dispatch and ops teams who manage real freight every week, often with a lean staff and a patchwork of tools. Most users work out of Gauteng, the coast, or a regional hub, and need suburb loops that survive load-shedding and Monday morning estate gates.

If your week is full of PDFs that never get read or shiny apps nobody trusts at the gate, you are in the right place. Hello Suburb fits where the ops lead still runs the show and where handovers happen in real time, not in a theoretical control room. It will not suit teams who expect a single digital dashboard or nightly system syncs.

How Hello Suburb works in practice

Instead of long manuals and abstract policies, Hello Suburb gives you a short, printable lane card and specific cues. Each pack includes local gatehouse notes, cluster sequencing, and soft-move backup options for when load-shedding or traffic throws out a plan. Every box and handoff note assumes the realities of South African business, closed mall counters, short-notice calls, and teams with part-time planners.

A typical week starts with a lane card that lists the suburb loop, estate rules, order of stops, and parking tips. Gate notes and return lanes are kept in one place, so you do not scramble for details when a supervisor changes on a Thursday. If customer handover is the main problem, a doorstep script is included to keep the handoff quick and professional. Hello Suburb windows and Hello Suburb handoff are linked to make sure every operator has matching info.

Who should use Hello Suburb, and who should not

Hello Suburb suits teams where the ops lead or owner still signs off the route and the courier arrives knowing where to park. If you rely on junior planners, dispatch bays in an industrial park, or last-minute changes from a city workshop, this card will save you hours. It is also for businesses in Polokwane, Bloemfontein, Durban and other cities with complex loops.

It is not suited to businesses who outsource every handover or operate only in single-building deliveries. If your team never interacts with estate security or never needs to leave a parcel with a cluster manager, you may be better off in a different move or lane. See Moves or Lanes for other fit options.

A short worked example from a Gauteng week

On a Monday, the ops lead at a Germiston office reviews the lane card for Edenvale and surrounds. Afternoon loops are planned to pick up after school traffic. The card notes estate gate hours, a pin-drop for a known tricky cluster, and backup contact numbers. The on-floor operator prints the checklist after load-shedding, keeping it ready for the driver even if the laptop goes flat.

During the run, the team tells us when a gate procedure changes, so the notes can be updated before the next hub hour. Nothing is lost if someone is off sick, as a fresh lane card is ready for the next operator. This is how the move survives real Gauteng weeks, not just theory.

What to prepare before you get in touch about your suburb

Before sending our contact form, take five minutes to name the main problem. Is it the suburb loop, the window schedule, or the handover procedure? List the city, which guide or tool you have already tried, and who in your team will own the decision list. You do not need perfect info, but be clear which leaf (guide, windows, or handoff) fits your route. If you do not have a named owner for the week, fix that first. This speeds up your pack and avoids double work.

• State your main problem in one sentence (e.g. 'Estate access after 3pm').
• List the delivery city and typical suburbs covered.
• Mention if you have used the guide, windows, or handoff leaves before.
• Who in your team will own the checklist and handoff?
• Share any unique timing quirks (load-shedding windows, school run peaks).

Common pitfalls and how to avoid them

Teams run into trouble when they skip the simple boxes or rely only on memory for gate notes. If your checklist relies on a single person, you lose days to sick leave or missed updates. Some try to widen scope too soon without linking the move to a lane, ending up with mismatched info. Others forget to send updates when the suburb changes its rules.

Avoid these by printing the checklist, naming a local owner, and keeping your notes fresh. Open Updates to check for language or rules changes before every Monday run. Use Checklists for a quick review if you suspect you have missed a detail.