Proof of Travel
Consider a traveller with a Rwandan e-visa application open in one tab and an airline booking page in another. The visa form asks for the intended length of stay, and the airline desk may later ask for proof of departure. The two documents have to tell the same story. This case study unpacks how.
A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight. In this scenario it's the document that links the two checks together.
The scenario
The traveller is a named composite, Ms A., a UK passport holder planning two weeks in Rwanda before moving on to a neighbouring country. She has not yet bought a flight out. This is a hypothetical, built to illustrate the document logic, not a report of any real person.
Her documents on the day of travel are:
- A passport valid for the full stay.
- Entry authorisation for Rwanda, obtained under the rules that apply to her nationality.
- A hotel confirmation for the first nights.
- An itinerary showing onward travel.
The first three are routine. The fourth is where compliance questions arise.
Step one: establish the governing rule
Any compliance review begins with the primary source. For UK passport holders, the gov.uk entry requirements for Rwanda set out the current position, and other nationalities should consult their own foreign ministry and the relevant Rwandan authority.
The rule can change, and this article doesn't state a specific requirement as current fact. Ms A. should read the page on the day she books and again before she flies.
Where the guidance is unclear, the prudent course is to prepare an onward booking. The cost of preparing is small. The cost of being refused boarding is not.
Step two: identify who verifies the document
There are two verifiers, and each applies a different test.
The carrier checks at departure. Airlines rely on IATA's Timatic database to determine what a destination expects from a given passport. If it indicates that onward travel is expected, the agent will ask for evidence.
The border officer checks on arrival. That check is discretionary and tends to focus on consistency: the stated purpose, the length of stay and the next destination.
A document that satisfies the carrier does not guarantee that the officer will be satisfied, and the reverse is also true. The booking must work for both.
Step three: examine the document itself
An onward ticket is evaluated on four attributes.
| Attribute | Compliant | Non-compliant |
|---|---|---|
| Record locator | Exists in an airline or GDS system | Appears only on a PDF |
| Passenger name | Matches the passport exactly | Different spelling or order |
| Route | Departs Rwanda for another country | Ends inside Rwanda |
| Date | Falls within the declared stay | Predates arrival or lapses |
Ms A.'s booking passes on all four. She confirms this by entering the locator and surname on the airline's manage-booking page, which is the same lookup an agent would perform.
A reservation that cannot be retrieved there should be treated as unverified, whatever the PDF shows.
Where the carrier and the officer differ is in what each is entitled to ask. The carrier is concerned with its own liability: it does not want to transport a passenger who will be refused entry. The officer is concerned with the purpose of the visit. A compliance-minded traveller anticipates both and prepares a single consistent set of documents rather than separate stories.
Consistency also applies across time. If the visa application stated a two-week stay, the onward booking should not show a departure in six weeks. Any mismatch invites questions that the traveller must then answer unprepared.
Step four: preserve the document's validity
A reservation is not a permanent record. Some are held rather than ticketed, and a hold carries an expiry. If it lapses before departure, the agent sees no booking.
Ms A. therefore confirms the hold period with the issuer and selects one that covers her departure day with a margin. Our reference note on how PNR holds work behind an onward ticket describes the mechanics. She keeps a copy offline and records the locator on paper.
On arrival she answers the officer's questions briefly and consistently with the documents she holds. She offers the booking only when it is relevant.
Ms A. also reviews what she should not do. She does not alter a PDF, she does not present a document she cannot verify, and she does not offer more documents than the question requires. Each of these behaviours creates a risk that the underlying booking does not.
She keeps the correspondence from the issuer, because if a verifier queries the booking, a dated record of when and how it was made is useful. This is ordinary record-keeping, not a special measure.
Outcome and lessons
The case resolves without incident, because the documents agree with one another. The lessons generalise:
- Start from the primary source for your passport.
- Treat the carrier and the officer as separate verifiers.
- Use a booking that can be looked up, not a picture of one.
- Keep it valid through the border.
For a booking built for this check, book your onward ticket.