The short answer
What to know first.
For a UK operator file, the two gorilla-permit systems share their discipline and differ in their rhythm. Uganda's UWA issues permits against passport identity and holds a date only on full payment under its date-lock terms, with certain wetter-month permits non-reschedulable; the DMC pays the authority, holds the park receipt on the file, and evidences it to the operator. Rwanda's RDB runs its own booking and payment terms, confirmed as current at booking, with the same absolute requirements on names and documents. On the NETT file both appear identically: pass-through park-authority lines at the authority's figure, never marked up, never estimated, collected on the authority's timetable rather than the invoice's. What a UK operator needs from its Uganda DMC is therefore three things: live availability before anything is promised, full compliance executed on time, and a confirmation-of-record that lets the operator's own file survive an audit. Tariff figures belong to the authorities' published schedules and are confirmed at booking, never quoted from memory.
At a glance
The planning brief.
Uganda's rhythm
UWA permits are held by full payment under date-lock terms, issued against passport names, with the receipt held on the file.
Rwanda's rhythm
RDB runs its own booking and payment terms, confirmed current at booking; the discipline of names and documents is identical.
On the NETT file
Permits appear as pass-through park-authority lines at the authority's figure, never marked up and never estimated.
Sail verifies
Current terms with both authorities for the actual dates, and returns a confirmation-of-record the operator can file.
01
Uganda's rhythm: pay in full, hold the date
UWA's system is built on commitment: a permit is held by full payment under the authority's terms, issued against the passport name, and locked to its date, with the named wetter-month windows carrying non-reschedulable terms. There is no deposit-and-decide; the date is real when the money has moved and the receipt exists.
For an operator this sets the file's tempo. Client funds for the permit line must be available at confirmation, which is why Sail raises the money-path conversation in the first design pass rather than at document stage, and why the permit line's deadline is printed beside it on every NETT quote.
02
Rwanda's rhythm: its own terms, same discipline
RDB administers Volcanoes permits under its own booking and payment framework, and the current terms are confirmed with the authority at booking rather than assumed from last season's file. The constants are the ones that never vary in either country: passport-accurate names, age eligibility, and documents that match the traveller who will stand at the briefing.
Operationally, Rwanda's centralised briefing system means the permit fixes a park rather than a sector, which simplifies the lodge question and leaves the trek allocation to the morning. The operator's file carries the same evidence either way: confirmation, receipt, and names reconciled character by character.
03
How the NETT lines should read
On a Sail NETT quote a gorilla permit is a pass-through line: the authority's figure, labelled as the authority's, with no margin inside it. The operator's own client pricing is the operator's business; the permit line is not where margin lives, and a quote that buries markup in a park fee fails the transparency that trade relationships run on.
Collection follows the authority, not the invoice cycle: where UWA's deadline lands before the operator's normal client-payment rhythm, the file says so early and plainly. The one conversation that cannot be improvised is the one about money already owed to a government desk.
04
The evidence pack
Every permit transaction on a Sail trade file produces its paper: the booking confirmation, the authority's receipt held by the DMC as the operator's agent, and a confirmation-of-record listing each traveller's name as booked. UK operators live under their own compliance and bonding obligations, and their East African files should be built to the same standard.
When something changes, a renamed passport, an ill traveller, a date under pressure, the answer is worked with the authority under its current terms and documented the same way. What Sail never does is promise an outcome the authority has not given; the desk's credibility is the product being sold.
Questions travellers ask
Useful answers, before you decide.
Who holds the UWA park receipt on a trade file?
Sail holds it as the operator's agent on the ground, and evidences it in the confirmation pack. The receipt is the proof the date is real, and it stays with the file through the journey.
Do UWA and RDB permits appear differently on a NETT quote?
No: both are pass-through park-authority lines at the authority's figure with the payment deadline shown. The difference between the systems is rhythm and terms, not how the line should read.
Can Sail quote current permit tariffs in this article?
Deliberately not. Tariffs are the authorities' to publish and they change; Sail confirms the current figures against the official schedules at booking, which is the only version an operator should file.