The Northern Corridor connects Mombasa with inland destinations through a network of roads and border crossings. For a Mombasa–Kampala–Kigali run, plan the actual lane, border, documents, connectivity and driver arrangements before departure.
This guide lays out how corridor operators can keep the run — vehicle, documents, movement, fuel, and driver money — on one operating record from dispatch in Mombasa to closeout after Kigali.
This article is operational guidance, not legal or customs advice. Cross-border requirements change and differ by country, cargo, and lane. Confirm current rules with the relevant national authorities, the EAC, or a licensed clearing agent.
Why corridor trips break spreadsheet operations
A local delivery forgives weak records because the truck is back by evening. A corridor rotation does not. Between Mombasa and Kigali the operation absorbs pressures that a call-and-spreadsheet workflow was never built to hold:
- Runs measured in days, not hours — a truck can be away for a week or more per rotation
- Multiple jurisdictions on one trip: Kenya, Uganda, and Rwanda each with their own transport authorities
- Border and weighbridge stops where a missing or expired document halts the whole load
- Connectivity gaps between towns where phone-call dispatch simply goes silent
- Cash exposure that grows with distance — fuel, per diems, and en-route expenses across currencies
- Driver fatigue and welfare over long distances, with hand-offs that need a second driver on record
None of these are edge cases — they are the ordinary shape of cross-border work. The fix is not more phone calls. It is a trip record that starts complete at dispatch and stays alive for the whole run, so anyone in the workspace can answer where the truck is, what it is carrying, what has been spent, and what is still owed.
The corridor framework: what actually governs a cross-border run
Regional frameworks address different parts of the journey. NCTTCA describes the corridor network; the EAC Single Customs Territory addresses customs procedures; the COMESA Yellow Card provides regional third-party motor cover within its participating-country scope. Check each framework’s applicability to your lane and cargo instead of assuming one arrangement covers every crossing or every risk.
Kora does not clear customs or issue permits. It can help organise your trip and vehicle records alongside the references supplied by the responsible authorities and agents.
Dispatch corridor runs with the whole picture attached.
Kora ties the vehicle, trailer, driver, route, documents, fuel logs, and settlement records to one trip record — built for East African transport operators.
Documents that must not expire mid-run
The cheapest border delay is the one you prevented a month earlier. Cross-border work multiplies the paperwork attached to every vehicle and driver, and an expiry that would be an inconvenience in town becomes a stranded load at Malaba. The records worth tracking per truck and per run typically include:
- Vehicle registration and national inspection records for the truck and any coupled trailer
- Insurance for the home country, plus regional third-party cover such as the COMESA Yellow Card where applicable
- Cross-border operating permits and licences required on the lanes you run
- Driver licence, identity, and any border or port passes tied to the person, not just the vehicle
- Cargo and customs documentation prepared under the EAC Single Customs Territory procedures
- Speed governor, cargo, and route-specific certificates where national rules require them
Keep the relevant records against the vehicle or person, control access and assign a renewal owner. Kora can highlight recorded expiry dates and provide reminders. Check that the register is complete and notifications are configured; a reminder is not certification or a guarantee against delay.
Dispatch with the whole run in view
Corridor dispatch is where the operating record is born, and what it captures before departure decides what you can answer during the run. A dispatch fit for cross-border work assembles:
- A route record with origin, destination, distance, and the waypoints that matter — borders, weighbridges, fuel stops
- One vehicle record as the hub: the assigned driver, second driver, odometer, and coupled trailer all hang off it
- Rig composition confirmed at dispatch — which prime mover pulls which trailer for this specific run
- Cargo description, weight, and the billed client captured before departure, not reconstructed after
- An opening odometer captured when the driver starts the trip, and a closing reading when the trip is completed
- Scheduled departure and arrival windows the workspace can hold the run against
Articulated work makes the trailer question explicit. In Kora the dispatcher composes the rig when creating the trip — which prime mover, which trailer — so the coupled combination is part of the trip record, not tribal knowledge in the yard. After departure, operational control belongs to the driver in the field app; the workspace watches, and the record fills in as the run progresses.
The dispatcher can see the vehicle's last known odometer, but does not set the trip's opening reading. The trip records it when the driver starts, using a live tracker reading where available or a reading from the truck when it is not. Completion closes the trip with a final reading; later movement of the vehicle does not change that trip's distance.
Tracking across three countries — and the blackspots between them
Live tracking earns its keep on the corridor, but only if it is honest about coverage. Long stretches between towns have thin network, and a platform that shows a six-hour-old position as "current" teaches dispatchers to distrust the map. The useful standard is freshness you can see: a position marked live, delayed, or offline, so the operations desk reacts to reality instead of guessing.
Kora queues supported trip actions when the field device is offline, then attempts sync when connectivity returns. Fuel-accounting records belong in the workspace; per-consignment loading and delivery confirmations currently require connectivity. Use an agreed fallback, retain event times and verify that queued records reached the office.
Fuel discipline when the price changes at every border
Fuel budgets must account for the route, actual prices, currencies and expected duty. Preserve each purchase and payment reference so finance can reconcile the trip. Do not assume the platform supports every currency or exchange-rate workflow without a demonstration.
- Every fill logged at the pump: station, litres, cost per litre, odometer, and a receipt photo
- Fills reconciled against tank capacity and distance driven — not against a monthly total
- Automatic flags for excess fills, mileage mismatches, and rapid back-to-back refuels
- Suspected variances routed to a review queue for a human decision, with the evidence attached
- Tank-level readings from supported sensors where fitted, so paper claims meet measured reality
- Per-country price context, because a corridor fuel budget built on one pump price is fiction
The point is not to accuse anyone — it is to make variances visible while the trip is still warm. A flagged excess fill or a mileage mismatch lands in a review queue with the odometer readings, receipt, and history attached, and a human decides what it means. That is anomaly detection doing its job: surfacing the question early, on evidence, instead of burying it in a month-end total.
Driver advances and settlements without losing the plot
A week-long run needs money on the road: fuel top-ups, border expenses, per diems. The failure mode is familiar — cash handed over at the yard, a note that never reaches the office, and an argument at month end about what was advanced and what is owed. The durable pattern is records first.
Advances start as requests: the driver asks from the field app and names the trip, a manager approves or rejects, and the approved amount is recorded against the driver and the trip. The company then pays through its own M-Pesa or bank channels — Kora records the amounts and transaction references but never holds or moves the money itself. Money for the road — border fees, tolls, lodging — counts as a cost of the trip, next to fuel, so the trip's margin shows what the run really cost, and it is never taken out of the driver's pay. Money the driver draws for their own use is different: it is their pay, drawn early. On completion an agreed rate card — per kilometre, fixed trip fee, waiting allowance, per diem — turns the trip into a settlement due, any pay advance comes off it, and every approval and reference sits on an audit trail instead of in anyone's memory.
Close the loop when the truck comes home
A corridor rotation is only finished when the record is. Completion captures the final odometer and closing details once, and the trip becomes something the business can learn from: distance run against fuel burned, cost per kilometre on that lane, margin against the agreed rate, and the settlement it produced. Do that for every rotation and the corridor stops being folklore — you know which lanes pay, which trucks drink, and which runs deserve a better rate before you quote the next one.
A useful first check is the cost per kilometre for the truck. Count the empty return and keep missing odometer readings visible before comparing lanes.
A 30-day corridor readiness plan
You do not need to digitise everything at once, and you should not start with hardware. Start with the records that stop borders and month-end arguments, on one lane:
- Build one register of every truck, trailer, driver, and document expiry date that touches a cross-border lane
- Map your corridor routes as route records with distances, borders, and planned fuel stops
- Move fuel from monthly totals to per-fill logs with odometer readings on at least one lane
- Put driver advances through a request-and-approval record instead of shop-floor cash notes
- Define rate cards for corridor work — per kilometre, fixed trip fee, and per diem — so settlement maths is agreed before departure
- Pilot the full record on one Mombasa–Kampala rotation before rolling it across the fleet
One clean Mombasa–Kampala rotation on a complete record will teach you more than a fleet-wide rollout plan. When the pilot answers its questions — did the truck leave ready, did the record survive the blackspots, did the money reconcile — expand lane by lane.
Frequently asked questions
What is the Northern Corridor in East Africa?
The Northern Corridor links the Port of Mombasa with inland markets including Uganda, Rwanda, Burundi, South Sudan and eastern DRC. It is a network of routes and border crossings, not a single compulsory path through Malaba. Confirm the planned crossing and destination-country requirements for each trip.
What documents does a truck need for cross-border transport in East Africa?
A cross-border truck typically needs vehicle registration, valid national inspection, home-country insurance plus regional third-party cover such as the COMESA Yellow Card, cross-border permits for the lanes operated, driver licence and identity documents, and cargo paperwork prepared under EAC Single Customs Territory procedures. Requirements differ by country and cargo type, so operators should confirm current rules with the relevant authorities before each new lane.
How do you track a truck from Mombasa to Kampala or Kigali?
Use compatible tracking hardware and connectivity that covers the countries on the route. Check timestamps and distinguish recent from stale positions. Kora queues supported field trip actions, but fuel accounting is entered in the workspace and consignment handovers currently need a connection.
How do transport companies manage driver money on cross-border trips?
The workable pattern is records first: drivers request money that a manager approves and records against the trip, and the company pays it through its own M-Pesa or bank channels. Money for border fees, tolls and road charges is a cost of the trip and never comes out of the driver’s pay; money the driver draws for their own use is an advance on their pay. On completion the settlement is calculated from an agreed rate card — per kilometre, fixed trip fee, waiting allowance, or per diem — less any pay advance. Every amount, approval, and payment reference lives on the trip record instead of in a notebook.
Does Kora Fleet handle customs clearance or cross-border payments?
No. Kora Fleet is not a customs agent, clearing house, or payment service provider, and it never holds or moves funds on behalf of customers. It is the operating record around those processes: trip dispatch and tracking, document expiry visibility, fuel logs and anomaly review, and driver advance and settlement records — while customs clearance and actual payments run through your own agents and channels.
Official sources and further reading
Confirm current cross-border requirements with the relevant authorities before making operational or legal decisions.