Humanitarian Supply-Orchestration Architect

The mandate

Consortium members independently book similar emergency supplies through common hubs, but demand priority, cargo readiness, transport documents, sanctions checks and destination acceptance are not visible at the moment shared capacity must be allocated. A proposed 4PL risks becoming another reporting layer or an unelected programme controller. The defined problem is to design neutral orchestration that can combine movement and evidence while keeping needs assessment, beneficiary selection, donor accountability and country acceptance with member organisations.

The named deliverable is a Humanitarian Supply-Orchestration Architecture covering demand signal, cargo readiness, stock and procurement status, consolidation, capacity allocation, transport mode, multimodal data, electronic bill-of-lading and Single-Window interfaces where corridors support them, customs, sanctions, security, country acceptance, proof of delivery, cost attribution, provider governance, activation, step-down and exit. It includes decision rights, corridor archetypes, playbooks, commercial schedules and member data rules.

Five milestones govern six months. Week four reconstructs eighteen emergency journeys across six corridors. Week nine establishes member-retained authority, data minimums and allocation principles. Week fourteen concludes corridor laboratories for air bridge, ocean-to-road, regional stock and inaccessible final mile. Week nineteen runs four country and two governance simulations. Week twenty-four delivers the accepted architecture, service catalogue, provider requirements, funding model, transition plan and twelve-month activation backlog.

Acceptance rests jointly with the secretary-general and Member Operations Council; country directors, programme leads, customs specialists and security officers retain accountable judgments. Work is accepted only when three member teams can submit and amend unseen needs without surrendering ownership, the orchestration cell can allocate constrained capacity transparently, documents follow multimodal handoffs, destination acceptance is confirmed, costs reconcile by member and no delivered metric substitutes for beneficiary or programme outcome.

The client consortium provides de-identified emergency orders, stock and booking histories, provider contracts, donor restrictions, customs failures, corridor maps, security protocols, member data rules, cost records and exercise participants. Consultants will not prioritise beneficiaries, procure goods, book live cargo, obtain customs release, approve sanctions positions, direct country programmes or select the 4PL. Live implementation and technology build are excluded; unavailable country judgments remain explicit operating dependencies.

Why this is external work

Members need shared leverage and visibility but will not delegate their humanitarian mandate to a logistics intermediary. Existing provider proposals begin with platforms and shipment volume. Independent architecture can start from constrained capacity, lawful documents and country acceptance, designing a federated service whose authority and exit remain legible during crisis rather than only in normal procurement.

What you will own

• Reconstruct eighteen journeys from programme need and cargo readiness through allocation, booking, multimodal transfer, customs, receipt and member acceptance.
• Segment corridors by access, mode, document maturity, security, customs, lead-time tolerance, local capacity and recovery alternative.
• Define authority among members, orchestration cell, suppliers, carriers, hubs, brokers, country teams, donors and security owners.
• Design transparent scarce-capacity allocation, change, appeal and escalation routines tied to programme consequence and cargo readiness.
• Specify multimodal document and event handoffs, including eBL and Single-Window use only where counterparties can act on them.
• Exercise sudden-onset demand, port closure, sanctions hold, insecure route, destination refusal and member-priority conflict.
• Deliver the accepted service catalogue, governance, provider schedules, funding method, data rules and phased activation plan.

Candidate qualifications

• Has designed or led multi-agency humanitarian logistics across emergency air, ocean, road and regional stock networks.
• Can evidence shared capacity allocated transparently without centralising needs assessment or country programme authority.
• Understands humanitarian demand, donor restrictions, multimodal documents, customs, sanctions, security, hubs and proof of delivery.
• Has worked with electronic trade data and Single-Window environments while preserving workable degraded and paper fallbacks.
• Can distinguish expressed need, cargo readiness, allocated capacity, border release, member acceptance and programme outcome.
• Has left federated member organisations with usable activation and exit mechanisms beyond a common dashboard.

Non-negotiables

• Can complete six corridor laboratories, four country simulations and two member-governance exercises within six months.
• Will not choose beneficiaries, direct country programmes, book cargo, make sanctions determinations or select providers.
• Brings direct crisis logistics orchestration across multiple agencies; commercial control-tower design alone is insufficient.
• Will preserve unmet need, unready cargo, denied allocation, customs holds and destination rejection in service evidence.

1. 49 words maximum. Which shared humanitarian-capacity rule remained legitimate when demand exceeded every available mode?
2. 49 words maximum. When did an electronic trade document improve action, and when was a degraded fallback essential?
3. 49 words maximum. How did you protect member programme authority inside a common logistics service?