The short answer
What to know first.
A gorilla permit is issued against a passport, checked at briefing against that same document, and unforgiving of clerical drift, which makes the advisor's data pack the quiet hinge of the whole file. What Sail asks for at confirmation, in one structured pack: passport scans for every traveller, names exactly as the document reads; dates of birth where age rules apply; dietary requirements in practical detail; medical and mobility disclosures that shape pacing and porter support; insurance details; and an emergency contact that answers. Sent once, cleanly, before permits are paid, it removes the two classic failures: the permit in a booking-form name, and the allergy discovered at dinner. Data is held for the file it serves and nothing else.
At a glance
The planning brief.
The permit truth
A gorilla permit is issued against a passport. Wrong data at confirm becomes a crisis at briefing.
One clean pack
Passport scans, dietary notes, medical and mobility disclosures, insurance and emergency contacts, sent once.
When it is due
At confirmation, before permits are paid: the authority's deadline is the real deadline.
Sail verifies
Every name character by character, and holds the data only for the file it serves.
01
Why the passport rules the file
The authorities issue gorilla permits against passport identity, and officials at briefing compare the document in the guest's hand with the permit in the ranger's. A name entered from a booking form, a transposed middle name, a maiden name the ticket still carries: each is a solvable problem at confirm and a crisis at the trailhead.
So the SOP is character-by-character: the advisor sends scans, Sail transcribes against the document, and any mismatch between passport, permit and flight ticket is reconciled before money moves. Boring is the standard; boring is what a trek morning should be, administratively.
02
The one clean pack
One structured pack at confirmation beats twenty emails across three months: passports, dates of birth where age rules bite, dietary needs written practically, allergies distinguished from preferences, medical and mobility notes as they genuinely are, insurance policy details, and the emergency contact who actually picks up.
Sail returns a confirmation-of-record so the advisor can verify every field their client will be served against. Corrections at that moment cost minutes; the same corrections at a lodge desk in Kisoro cost an afternoon of goodwill.
03
What each field actually does
Dietary notes reach every kitchen on the route before arrival, so the vegan guest is met with intention rather than improvisation. Medical and mobility notes shape pacing, porter counts and, where a sector allows, carried support, arranged ahead rather than negotiated on a slope.
Insurance details and the emergency contact sit quietly on the ops sheet until the day nobody wants, when they save an hour that matters. None of it is decoration; every field maps to an operational move.
04
Privacy and the white label
The data arrives under the advisor's brand and stays inside the file: used for permits, lodges, kitchens and safety, shared only with the suppliers who need each piece, and never marketed against. That restraint is part of the white-label promise, stated plainly.
When the journey ends, the file closes. The advisor keeps the relationship and the data story that protects it: their client's details were asked for once, used precisely, and respected throughout.
Questions travellers ask
Useful answers, before you decide.
When exactly do you need passport scans?
At confirmation, before permits are paid: the permit is issued against the passport, and the authority's deadline is the real one. Late scans are the single most common cause of avoidable permit drama.
What if a client renews their passport after booking?
Tell Sail immediately: names and numbers must match the document the client will carry. The rules for updating a permit's details are worked with the authority under current terms.
How is sensitive medical information handled?
It is held for the file, shared only where it operationally must be, under the privacy commitments Sail states plainly, and never used for anything else.