PNR Health Check: Catch Ticketing Deadlines and Booking Errors Before They Cost You

Most booking mistakes aren't dramatic — they're small, easy-to-miss details that only become a problem days later. A ticketing deadline that quietly passes because nobody noticed there wasn't one on file. A 40-minute layover that looked fine on paper but isn't realistic once you account for a full concourse change. PNR Health Check is built to catch exactly these, automatically, every time you convert a PNR.

What It Actually Checks

Missing ticketing deadline

Every converted PNR is scanned for a ticketing element — TK OK/TK TL in Amadeus, TAW in Sabre, TKTL in Galileo/Worldspan. If none is found, you get a warning rather than silence. It might mean the booking is already ticketed, or that the deadline just wasn't included in what you pasted — either way, an unticketed PNR without a visible deadline is worth a second look before it auto-cancels without warning.

Missing frequent-flyer number

A quick flag if no loyalty number shows up in the booking — a natural prompt to ask the client if they have one to add before ticketing, since some fares only credit miles or allow upgrades if it's on file at booking time.

Impossible connections

If a later segment appears to depart before an earlier one arrives at the same airport, that's almost always a mis-typed date rather than an actual booking — flagged clearly so it gets caught before it reaches a client.

Different-airport connections

Some routings connect through two different airports in the same city — Milan's MXP and LIN, for instance. These aren't walk-through transfers; the passenger needs their own ground transport between them, and it's easy to miss on a quick read of raw PNR text.

Tight connections

Layovers are checked against typical minimum connection times — 45 minutes for domestic, 90 minutes for international — and flagged if they fall short. Actual minimums vary by airport, so this is a prompt to double-check, not a guarantee either way.

Why the Ticketing Deadline Warning Matters More Than It Looks

A ticketing time limit isn't a formality — when it lapses, most airlines release the held inventory automatically, with no notification sent to the agent who made the booking. On a high-demand route or during peak season, the exact fare class and seat availability that existed when the PNR was created may simply not be there anymore by the time anyone notices the deadline has passed. A missed TTL isn't just an inconvenience to fix; it can mean a real fare increase or a route that has to be rebooked from scratch at a worse price.

It's also worth being precise about what a missing-TTL warning actually means. It doesn't mean the deadline doesn't exist — it means no ticketing element was found in the text that was pasted. Many agents assume that silence means the booking is already ticketed or otherwise safe, when just as often it means the deadline is sitting elsewhere in the PNR's history and simply wasn't included in the copy-paste. The warning exists specifically to make that ambiguity visible instead of letting it pass unnoticed.

Group Bookings: Where a Missed Flag Costs the Most

The cost of an overlooked warning scales with party size. In a 15- or 20-passenger tour group, a single missing ticketing deadline or one tight connection buried in passenger twelve's segment is far easier to miss scanning by eye than the same issue in a single PNR — and because everyone in the group is usually meant to be on the same schedule, one bad connection doesn't just affect one traveler, it can affect the whole party's itinerary and the tour operator's plans on the ground.

PNR Health Check runs identically whether a PNR is converted on its own or as part of a batch — every booking in a batch conversion gets its own independent pass, with its own set of flags, rather than one summary check across the whole group. For a large group booking, that turns into a fast way to scan every sub-booking at once for the one passenger whose connection is six minutes under minimum, without opening each PNR individually in the GDS.

What PNR Health Check Doesn't Do (By Design)

It's worth being upfront about the limits, since overstating what an automated check catches is its own kind of risk. Health Check doesn't call the GDS live, so a segment that shows HK in the text you pasted could have since changed status without your knowledge. It doesn't check visa or travel-document requirements, doesn't verify current fare pricing, and doesn't guarantee minimum connection times — those vary by airport, terminal layout, and even by airline alliance, so the 45/90-minute thresholds it checks against are a reasonable general rule, not a hard fact about any specific airport.

None of this makes the checks less useful — it just means they're best treated as a second pair of eyes catching what's easy to miss on a quick read, not a live system that knows more about the booking's current state than you do. For anything time-critical, confirming directly in the GDS is still the last word.

Reading a Warning Correctly: What To Do Next

1. Ticketing deadline warningPull the PNR in your GDS directly and confirm the actual TTL date before assuming the booking is already ticketed.
2. Tight connection warningCheck the actual minimum connection time for that specific airport pair, and consider rebooking if the layover falls under it.
3. Different-airport connectionConfirm the passenger understands the ground transport needed, and build in extra buffer time.
4. Missing frequent-flyer numberFollow up with the client and add it before ticketing if the fare rules allow retroactive mileage credit.
5. Impossible connectionTreat it as a likely typo first — re-verify the dates against the original GDS record rather than assuming the routing itself is wrong.

Common False Positives, and How to Read Them

An automated check flags patterns, not intent, so a warning firing doesn't always mean something is actually wrong — it means the situation matches a pattern worth a human glance. A tight-connection warning on a 50-minute layover might be perfectly fine at an airport the agent knows well, with a passenger who packs light and knows the terminal. A different-airport connection warning between two airports that are, in practice, a five-minute shuttle apart reads very differently from one where the airports are an hour apart by taxi.

The point isn't that these warnings are wrong when this happens — it's that they're calibrated to typical cases, and a working agent's judgment about a specific passenger, airport, or airline still matters more than any automated flag. Treat a warning as a prompt to think for a second, not as an automatic red mark against the booking.

Why the Loyalty Number Check Matters Most on Partner Bookings

A missing frequent-flyer number is easy to shrug off on a domestic booking with a low-cost fare where mileage accrual barely matters to the client. It matters considerably more on an international itinerary flown on a partner airline within an alliance, where crediting depends entirely on the loyalty number being attached at the time of booking or ticketing — added after the fact, some partner carriers won't retroactively credit miles at all, even with a receipt and a polite request.

It's also relevant to upgrades: many airlines only open complimentary or mileage-based upgrade requests to passengers with a loyalty number on file, and a request submitted without one can simply be invisible to the system handling upgrade lists. A PNR Health Check flag on a missing loyalty number is worth treating differently depending on context — a quick nudge to the client on a partner-airline international booking is worth more than the same flag on a short domestic hop.

Where the Warnings Show Up

Right alongside the converted itinerary, with no separate step to trigger it — health checks run on every conversion automatically, on the main converter and inside batch conversions alike.