Metropolitan Microhub Network Redesign Architect

The mandate

Pilot microhubs reduced van kilometres in selected districts, but each relied on subsidised property, one cooperative carrier and unusually dense delivery rounds. Proposed expansion combines parcel, retail replenishment, returns and cargo bikes without agreed neutrality, cut-offs, kerb access or failed-item handling. The defined problem is to design a metropolitan network whose consolidation benefit survives normal carrier competition, seasonal peaks and neighbourhood operating constraints rather than moving dwell from streets to private loading areas.

The defined deliverable joins eight district plans into one Metropolitan Microhub Network Architecture. It must connect demand and parcel archetypes, catchments, carrier-neutral entry, inbound appointment, custody, sorting, cargo-bike and walking rounds, lockers, customer collection, failed delivery and returns with property, kerb, charging, data and closure rules. Dangerous and oversized freight remain explicit exclusions. Decision rights, service measures, commercial schedules, relocation triggers and a staged investment case make the design operable rather than a map of candidate premises.

For the opening month, the team shadows eighty freight journeys and records eight district failure patterns rather than proposing sites. Day 68 brings the first council choice: which catchment, property, kerb and neutrality assumptions survive evidence. Carrier and neighbourhood design laboratories occupy months three and four. In month five, two peak-day trials remove a node and overflow route without relaxing parcel custody. The sixth month is reserved for negotiated district dispositions, operating-licence needs, provider requirements, full-cost reconciliation and the twelve-month implementation queue.

Acceptance rests jointly with the city mobility chief and coalition council; planning, accessibility, traffic and carrier owners retain their judgments. Work is accepted only when two neutral operators can route unseen mixed demand through attributable custody and cost, peak overflow has a lawful destination, return and failed-delivery journeys close, neighbourhood impacts are measured at the hub boundary, and a carrier can enter or exit without losing customer parcels or proprietary data.

The client coalition provides anonymised shipment density, routes, service failures, kerb observations, property options, operating costs, carrier contracts, resident research permissions, planning conditions and controlled pilot access. Consultants will not award property, direct live deliveries, issue permits, choose carriers, set public policy or handle identifiable customer data. Procurement, construction, software build and ongoing hub operation are excluded; missing authority decisions remain explicit conditions.

Why this is external work

The city, carriers and property owners each control a dependency but none can credibly design neutral access alone. Previous pilots proved local possibility, not scalable economics or neighbourhood acceptance. Independent urban-logistics architecture can test the full network while leaving permits, competition, commercial and street decisions with accountable parties.

What you will own

• Reconstruct eighty journeys from carrier linehaul and hub receipt through sort, local round, failed delivery, collection and return.
• Segment districts by demand density, street geometry, property availability, carrier mix, accessibility, seasonality and overflow options.
• Define decision rights among city teams, property owners, hub operators, carriers, retailers, couriers and neighbourhood representatives.
• Build neutral entry, custody, charging, data-portability, overflow, closure and provider-exit rules for each node archetype.
• Run carrier laboratories and peak trials covering node loss, battery constraint, oversized item and failed-customer access.
• Quantify vehicle, kerb, labour, property, service, emissions and neighbourhood consequences without certifying public claims.
• Deliver the accepted architecture, eight district plans, commercial schedules, governance and costed rollout backlog.

Candidate qualifications

• Has designed urban consolidation, microhub or carrier-neutral last-mile networks at metropolitan operating scale.
• Can evidence a pilot changed after subsidy, property, overflow and failed-delivery costs were normalised.
• Understands parcel density, cross-docking, cargo bikes, kerb management, lockers, returns, property and carrier economics.
• Has aligned public authorities and competing carriers without awarding concessions or directing live delivery operations.
• Can distinguish parcel injected, hub accepted, round-ready, customer completed, return closed and neighbourhood outcome.
• Has delivered node and exit rules that independent operators executed without continuing consultant interpretation.

Non-negotiables

• Can complete eight district laboratories, six carrier sessions and two peak-day trials within six months.
• Will not issue permits, choose operators, acquire property, direct couriers or represent community consent.
• Brings direct carrier-neutral urban-network design; mobility policy or parcel technology advisory alone is insufficient.
• Will preserve overflow, failed delivery, returns, excluded items and displaced kerb dwell in every benefit calculation.

1. 49 words maximum. Which pilot assumption failed when a microhub moved from one cooperative carrier to neutral access?
2. 49 words maximum. How did you account for failed delivery and returns in a hub catchment model?
3. 49 words maximum. What acceptance test proves congestion was reduced rather than shifted around the node?