Consider a hypothetical traveller, call her Ms A, holding a one-way ticket to Baku on Azerbaijan Airlines. At the departure desk she is asked for proof of onward travel. She has a hotel booking but no exit document. This case study sets out what documents an agent and an officer may reasonably review, and how a dummy ticket, also called an onward ticket, being a real PNR booked for visa or border-check purposes without paying for the flight, fits the file.

The scenario

Ms A is a fictional holder of a passport that, for this example, requires certain pre-arrival formalities for Azerbaijan. We do not state those formalities here. They are matters for the Azerbaijani authorities and for the traveller's own government guidance.

The facts that matter for documentation are simple. She has a one-way fare. She has accommodation for part of the stay. She has no confirmed departure. The desk agent must decide whether to board her.

The primary sources she should consult first

Before any document is assembled, the entry position should be read from official channels. The UK government maintains an entry requirements section within its Azerbaijan foreign travel advice. Travellers of other nationalities should consult their own government's equivalent.

Airlines separately rely on the Timatic database administered through IATA, described on the IATA Timatic page. The agent sees a summary produced from that system. The summary, not the full regulation, drives the question put at the desk.

Where neither source states a requirement for onward travel, the file should record that fact. Absence of a stated rule isn't evidence of a waiver.

Documents in the file

A prudent file for a case of this type contains the following, in order of importance:

  1. Passport. Valid for the period the destination expects, as shown by the official source.
  2. Entry authorisation. Any visa or electronic authorisation that applies to the traveller's passport, held in the form the authority specifies.
  3. Evidence of departure. A reservation showing a flight out of the country, in the traveller's exact passport name.
  4. Accommodation. The booking for at least the first nights, consistent with the dates above.
  5. Funds. Whatever evidence the traveller can reasonably present, without overstating.

The third item is the subject of this study. Its quality depends on four attributes: name, date, route and verifiability.

Assessing the departure document

Name. The surname and given names must match the passport. A discrepancy of one letter can defeat a lookup.

Date. The departure must fall after arrival and within the permitted stay. A date that exceeds the stay undermines the document.

Route. The itinerary should be one an airline actually operates. A route that does not exist invites follow-up questions.

Verifiability. The record locator should return a booking on the airline's own manage-booking page. A document that cannot be verified is, for practical purposes, decoration.

A held reservation can lapse on the airline's timetable. For that reason, verification should occur close to the date of travel and again at check-in. Our compliance-style analysis of what the record shows in a dummy ticket versus a real ticket sets out the differences in the underlying record.

Common defects observed in files of this kind

Several recurring defects weaken otherwise sound documents. First, a name entered in a different order from the passport. Second, a departure date that precedes the arrival date, usually through a data-entry slip. Third, a reservation that was valid at purchase but lapsed before travel. Fourth, a screenshot with the locator cropped out. Each is avoidable with a final review on the day of travel.

A reviewer should also confirm that the departure airport and the arrival airport are distinct, and that the carrier named on the document operates the route shown.

Outcome of the hypothetical

In the example, Ms A presents the reservation. The agent searches the locator, finds the booking, and notes the date. The desk check is satisfied. Nothing about this outcome binds the Azerbaijani border officer, who retains discretion on arrival. The document answers the airline's question. It does not answer every possible question from the authorities.

This distinction matters. A reservation demonstrates an intention to depart. It's not a visa, not a guarantee of admission, and not a substitute for any authorisation the destination requires.

The record should also note what was not done. If the traveller did not book accommodation beyond the first nights, the file should say so, because an officer's questions will track the file. Silence on a gap invites a doubt that a plain statement would have closed.

Lessons for the file

The following points generalise:

  • Read the primary source first and record what it says.
  • Prepare for two audiences, the airline and the officer.
  • Keep every document consistent with every other.
  • Verify, then verify again.

This analysis is general information. It is not legal or immigration advice, and it does not describe the position of any particular traveller. The officer's decision on arrival is final.

For a verifiable departure document prepared to the standard above, obtain a reservation for your itinerary.