retention line

A retention line is a text entry placed into an airline reservation system or GDS (Global Distribution System) that postpones the automatic archival of a booking record. When a passenger books a flight, the reservation lives in the active database. After the flight departs, systems automatically move old bookings to archive storage to manage database size and performance. A retention line, typically containing a date or flag, tells the system to hold that specific booking in the live environment instead.

Retention lines serve operational purposes across airline and travel agency workflows. Accounting departments use them to keep bookings visible while reconciling payments or handling refunds; customer service teams retain bookings for frequent flyers who may dispute charges or request repeated documentation; legal holds may require certain reservations remain accessible for investigations or audits. Without a retention line, a travel agent looking back two months to investigate a complaint finds only an archived record that requires separate retrieval procedures.

How retention lines work in practice

Most GDS systems allow retention lines to be added as free text fields or via specific retention functions. An agent might enter a date, such as "RETAIN UNTIL 31DEC2025", or attach a code flagged for legal review. The system checks this instruction before executing its nightly archive routine. Some airlines configure automatic retention based on ticket type: group bookings held for 12 months, corporate contracts for 18, or disputed charges until resolution. The line occupies minimal database space and does not change the booking's operational status; the passenger is not aware of its presence.

Problems arise when retention lines are not cleared after their purpose expires. A booking retained indefinitely accumulates in the active system, slowing queries and inflating database bloat. Conversely, if a retention line is mistakenly deleted or expires before required documentation is gathered, archived bookings become harder to locate. Some systems offer audit trails that log when retention lines were added and by whom, helping track whether the hold was legitimate.

The term reflects its function: the line of text literally retains the booking in place. It sits alongside other booking metadata like ticket number, passenger name, and fare rules, but unlike those fields, it has no revenue or operational consequence. In smaller travel agencies that use basic systems, retention lines may be managed manually through file notes or spreadsheets rather than GDS fields, making the concept less formalized but the need equally real.