EAC corridor decision control
Northern or Central Corridor: how Rwanda freight teams make and control the routing decision
A route-selection and shipment-control framework for Rwanda cargo moving through Mombasa or Dar es Salaam—based on operational readiness, not a generic promise that one corridor is always faster.
Route control points
- 1Cargo and supplier profile
- 2Port and sailing option
- 3Document readiness
- 4Border and inland plan
- 5Cost-at-risk review
- 6Route approval
- 7Exception ownership
Scope
Pre-booking and live-shipment decisions for Rwanda imports. This framework does not publish static transit times or prices because sailing, congestion, border, road and commercial conditions change.
Operating rule
Choose the corridor shipment by shipment, record the assumptions behind the choice, and preserve a switch deadline. Do not reroute live cargo because of anecdote without calculating document, carrier, customs and equipment consequences.
End-to-end workflow
What must happen, who owns it, and what proves completion
Demand definition
Describe the shipment before comparing corridors
Start condition
A purchase order or transport request needs a route.
Actions
- Record cargo type, container mode, origin, readiness date and required delivery window.
- Identify regulated, hazardous, temperature-controlled, abnormal or high-value requirements.
- Confirm Incoterm and which party controls ocean freight, clearance and inland transport.
- Set a business deadline and cost-of-delay rather than only a target ETA.
Evidence to retain
- Cargo profile
- Commercial terms
- Required-delivery window
- Constraint and permit register
Option build
Build a comparable Mombasa and Dar plan
Start condition
Cargo constraints and commercial ownership are confirmed.
Actions
- Compare actual sailings, transshipment risk, port cut-offs and equipment terms.
- Confirm agent and customs readiness at the port, transit borders and Rwanda destination.
- Map Northern Corridor border options and the Central Corridor Rusumo plan.
- Quote ocean, port, clearance, inland, border and equipment exposure on the same basis.
Evidence to retain
- Carrier option and validity
- Agent readiness confirmations
- Route plan
- Comparable landed logistics estimate
Risk decision
Score the failure modes, not just base cost
Start condition
Comparable route options are available.
Actions
- Test document readiness against the earliest filing and arrival milestones.
- Assess free time, likely inspection exposure, border handoffs and recovery options.
- Price delay exposure and equipment detention separately from normal charges.
- Choose the route and record why the alternative was rejected.
Evidence to retain
- Route scorecard
- Cost-at-risk estimate
- Approval record
- Switch deadline and decision owner
Live control
Manage the selected corridor by evidence
Start condition
Booking is confirmed and the route baseline is active.
Actions
- Track carrier, customs, port, road, border and destination states independently.
- Compare actual milestones to the approved baseline and explain every material variance.
- Use exception thresholds for documents, port release, stationary time, seals and border dwell.
- Feed actual outcomes back into the next routing decision without turning one shipment into a universal rule.
Evidence to retain
- Versioned route baseline
- Milestone timestamps
- Exception and resolution log
- Post-shipment corridor review
Shipment file control matrix
Route brief
Same cargo scope, origin readiness, delivery requirement and Incoterm for both corridor options.
Approved comparison baseline with version and owner.
Carrier option
Sailing, routing, transshipment, cut-offs, free time, equipment and quote validity confirmed.
Carrier or forwarder offer retained with assumptions.
Customs readiness
Port, transit, border and Rwanda destination responsibilities assigned before booking.
Named agents and filing prerequisites for each jurisdiction.
Landed logistics estimate
Compare equivalent inclusions and expose detention, storage, inspection and delay risk separately.
Cost model with currency, validity and exclusions.
Route approval
Decision states why the selected corridor fits this cargo and the date after which switching is no longer practical.
Approver, rationale, switch deadline and booking instruction.
Post-shipment review
Separate controllable failures from external variance and compare plan to actual by milestone.
Closed exception log and corridor scorecard update.
Exception playbook
Signal
Preferred sailing becomes unavailable
Response
Rebuild both end-to-end options from the new cargo-ready date; include document and equipment consequences.
Release condition
A new route baseline is approved before booking changes.
Signal
Documents miss the route cut-off
Response
Quantify whether correction fits the current sailing and pre-arrival window before rolling or switching.
Release condition
The approved document set and revised transport instruction agree.
Signal
Live corridor disruption
Response
Locate cargo and legal status first, protect customs and equipment obligations, then compare hold, recover or reroute options.
Release condition
A named authority approves the recovery plan and all actors acknowledge the revised handoffs.
Primary sources
Verify the live requirement before filing
This is an operations-control guide, not a substitute for a licensed clearing agent or a commodity-specific ruling. Procedures, tariffs and permits can change; use the linked authority for the current legal requirement.
Northern Corridor road network
Northern Corridor Transit and Transport Coordination Authority
Official Mombasa corridor routing through Uganda toward Rwanda.
Central Corridor overview and network
Central Corridor Transit Transport Facilitation Agency
Official corridor mandate and Dar es Salaam connection to Rwanda and other member states.
Central Corridor road network
Central Corridor Transit Transport Facilitation Agency
Official Dar es Salaam–Kigali routing through Rusumo.
Single Customs Territory
East African Community
Destination-state assessment and payment, customs-system interconnection and corridor-wide cargo movement.
Make every handoff traceable
InDataFlow keeps documents, reviews, releases, corridor events and client updates tied to the same shipment record.