The Northern Corridor is East Africa's working artery: cargo lands at the Port of Mombasa and moves by road through Nairobi, across the Malaba border into Kampala, and on to Kigali. A truck on that route is away for days, crosses jurisdictions, and passes through borders and weighbridges where one expired document stops the whole load. Most fleets still run it on phone calls, notebooks, and a spreadsheet that stayed behind in the office.
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.
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:
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.
Three regional structures shape most Northern Corridor trucking, alongside each country's national transport rules. The corridor itself is coordinated by the Northern Corridor Transit and Transport Coordination Authority (NCTTCA), the treaty body headquartered in Mombasa that links Kenya with Uganda, Rwanda, Burundi, South Sudan, and the DRC. Customs clearance on the route runs under the EAC Single Customs Territory, in place since 2014, with joint border processing and one-stop border posts that the EAC credits with cutting truck turnaround times from weeks to days. And for liability, the COMESA Yellow Card scheme provides regional third-party motor cover recognised across member states.
A fleet platform does not replace any of that — no software clears customs or issues a permit. What it does is keep your side of the paperwork visible: which documents each truck, trailer, and driver holds, when each one expires, and whether the vehicle leaving on Monday is actually ready for the border it will reach on Tuesday.
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.
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:
Keep every document filed against the vehicle or person it belongs to, stored privately with controlled access, and covered by expiry alerts that fire well before the date — Kora raises them 30 days out. Document tracking is visibility, not certification: the operator remains responsible for meeting each country's current requirements, and the win is that nothing expires unnoticed while the truck is three borders from home.
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:
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.
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.
The same honesty applies to the driver's side. A field app built for corridor work keeps working without signal — fuel logs, trip updates, and issue reports queue on the phone and sync when coverage returns, so the blackspot between Eldoret and the border costs you nothing but a delay in the timeline, not a hole in the record.
Fuel is the largest controllable cost on a corridor run, and the hardest to police from a distance. Pump prices differ between Kenya, Uganda, and Rwanda; a driver fills in three currencies across a week; and by the time a monthly fuel total reaches the office, no one can say which fill was wrong. Corridor fuel control means per-fill discipline:
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.
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, 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. Settlements work the same way: an agreed rate card — per kilometre, fixed trip fee, waiting allowance, per diem — turns the completed trip into a settlement due, advances are recovered against it, and every approval and reference sits on an audit trail instead of in anyone's memory.
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.
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:
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.
The Northern Corridor is the transport route linking the Port of Mombasa in Kenya to Uganda, Rwanda, Burundi, South Sudan, and the eastern Democratic Republic of Congo, running through Nairobi and the Malaba border to Kampala and on to Kigali. It is East Africa’s busiest trade artery and is coordinated by the Northern Corridor Transit and Transport Coordination Authority (NCTTCA), headquartered in Mombasa.
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.
With a GPS tracking device on the vehicle reporting into a fleet platform that shows live position, speed, and trip progress. On corridor runs the practical detail is coverage honesty: a good system distinguishes live, delayed, and offline positions instead of showing a stale dot as current, and lets drivers keep logging fuel and trip updates offline so the record catches up when the network returns.
The workable pattern is records first: drivers request advances that a manager approves and records against the trip, the company disburses the money through its own M-Pesa or bank channels, and the settlement due on completion is calculated from an agreed rate card — per kilometre, fixed trip fee, waiting allowance, or per diem — with advances recovered against it. Every amount, approval, and payment reference lives on the trip record instead of in a notebook.
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.
Confirm current cross-border requirements with the relevant authorities before making operational or legal decisions.
Built for the lanes you actually run
Kora gives East African transport teams dispatch, live tracking with honest freshness, fuel logs with anomaly review, document expiry visibility, and driver advance and settlement records — from Mombasa to Kampala and Kigali.
