Tineo home

Settings

How do you share plans without sharing booking codes?

Tineo Editorial Team Last updated 5 min read

Share the plan, and keep the booking codes with the people who are allowed to open or change the reservation. The plan is the time, the place, the carrier and flight or train number, and the name a host will answer to. A record locator, a ticket number, a barcode, and a manage-booking link are keys. What a PNR is explains the locator as the handle for an airline record, and why travelers treat it like a key. This page is the list of what still belongs in the group thread once that key stays put.

What the thread needs

People who are meeting you need facts a stranger could follow. Date, local time, and the zone if anyone is reading from another country. Carrier and flight number, or train number. Departure and arrival stations, including the terminal when you know it. The lodging’s name and street address. A meeting point specific enough to find. The name a restaurant or a rental host will call.

Those facts are enough to show up. They are enough for someone at home to know where you meant to be. How to keep bookings from different sites in one place is the single note, the folder, and the calendar. Build that note from the fields above. When you paste a line into a family chat, paste from the note, not from the raw confirmation.

Flight numbers feel like secrets. They are not the booking. CBP’s passenger-name-record page lists the record locator, the names, the itinerary, ticketing information including the ticket number, and contact and payment data as separate categories a carrier may hold. Sharing the itinerary’s flight number does not, by itself, hand someone the locator. Sharing the email that contains both does.

What stays off the wide thread

Leave these out of any chat that includes people who should not change the booking or see payment data:

  • The record locator and any supplier confirmation code.
  • The ticket number.
  • A manage-booking link, especially one that already contains a token.
  • Barcodes and QR codes from a boarding pass or an entry ticket.
  • Passport numbers, full dates of birth, and card numbers, including the last digits if you can avoid them.
  • The unedited confirmation PDF.

CBP notes that a PNR may include payment and billing information and advance passenger information such as passport number, date of birth, and gender, when the carrier stored them. Not every booking contains every field. A locator is still the handle for whatever is there. What a PNR is says that on many airline sites the locator plus the passenger’s last name is enough to open the booking. If the site you use works that way, anyone with both can see the record. Treat a paste of the code into a twenty-person chat as a paste of that key.

United’s contract of carriage puts management in a practical frame: the name on the ticket has to be the passenger’s name, and tickets are not transferable unless the ticket said so at issue. A code in the wrong hands does not make a stranger the passenger. It can still let someone cancel, change a seat, or read the other names. The holder, defined in who should hold the reservation, keeps the code. Naming that holder before anyone pays is the sequence in how group trip decisions get made. A backup keeps it if the supplier will talk to them. Each traveler keeps the code for their own ticket, because check-in may demand it.

The hotel desk is the awkward case. The guest who will check in needs the confirmation the desk asks for. Send it to that person directly. The rest of the group needs the property name, the address, and the check-in time. They can stand in the lobby without the code. A restaurant name on a booking is useful. The credit-card guarantee number is not.

How to send the plan

Paste a short block written for humans. One block per day is easier to update than a thread of images. When a time changes, edit the block and say that the earlier time is replaced. How to tell a confirmation was updated is how you know which email is current before you paste.

Do not forward the supplier’s email to the group and call that “sharing the plan.” Forwarding carries the code, the links, and any personal data in the message. If you need a picture, crop it to the time and the place, then look at the image once more for a locator in a corner.

How to share a trip with someone who is staying home is a wider audience with a different need. They may deserve more than the group chat, including a way to reach a supplier if you asked them to do that job. Decide that on purpose. A default of “everyone gets every PDF” fails both the group and the household.

Keep the real files in the folder the bookings guide describes, named so the holder can find them. The thread is a copy of the plan. The folder is the booking. When they disagree, the holder checks the supplier, then corrects the thread.

Exceptions

Some groups are the passengers and nobody else. Two people on one reservation already know the locator. Repeating it in their private chat is ordinary. The discipline matters when the audience grows: cousins, a club, coworkers, a driver, a host.

A border form, a visa application, or an airline that asks for passport details will require those details through its own secure page. That is not a reason to drop the passport into the trip chat. Each traveler submits their own.

A code that has been replaced still opens something until the supplier says it does not. If a locator leaks, ask the supplier to secure the reservation, and watch for changes you did not make. Deleting the chat message does not pull the code back from phones that already downloaded it.

An illustrative paste

This message is illustrative. The locator is invented and should not appear in a real group thread.

A family chat of fourteen people needs to meet a flight. The useful paste is: “Thursday 4 June, flight AB123, arrives Alden Airport Terminal 2 at 16:40 local. Meet at the airport’s published arrivals meeting point. If you are later than 17:10, go to the hotel at 18 Market Street and send a message.” The version that fails is a forwarded email whose subject line is the record locator, with a manage-booking button and the traveler’s date of birth under the fold. The flight number AB123 is fiction. The method is the point. Fourteen people can find Terminal 2 without the six-character code that opens the booking.

The itinerary is the share

Share the trip with the people who should see times and places, and forward confirmations to [email protected], or paste them, instead of dropping the raw email into a wide chat. Notes can hold the meeting point, while locators stay with the people who may manage the reservation. A raw forward is still how a code leaks.

Frequently asked questions

Can you send the flight number without sending the confirmation code?

Yes. The flight number, the date, the airports, and the scheduled time are how people meet you and watch the flight. The record locator is the handle for the booking. CBP lists them as different categories of passenger-name-record data. Put the flight number in the group note and leave the locator with the traveler.

What if the hotel desk asks for a confirmation number?

The person checking in needs the number the desk uses. Everyone else in a large chat does not. Send it to the holder and to the guest who will be at the desk, through a channel you would use for a key, and keep it out of the trip-wide thread.

Is a screenshot of the booking email safe to forward?

Only if you cropped every locator, ticket number, barcode, and manage-booking link. Forwarding the original email forwards whatever was in it. Paste the fields you mean to share: time, place, and the name the table or the room is under.

Who should have the code?

The holder of that reservation, a backup the supplier will talk to, and anyone whose own ticket cannot be opened without it. The page on who should hold the reservation is that choice. A cousin who only needs to know where to stand does not need the locator.

Sources