To reconcile PNRs with arrival lists, compare each delegate’s declared PNR and flight with the arrival data you receive, mark matches as verified, send mismatches to an exception list with an owner and keep one live sheet for arrival day. Sociana’s operations workspace holds the sheet and updates the delegate’s card when a record changes.
Who this guide is for
You are the operations lead for a conclave, dealer meet or incentive trip where delegates fly in from many cities. Transfers, rooms and welcome desks depend on who actually lands and when. Your concern is the gap between what delegates declared and what happens at the airport.
Where PNR and pickup drift apart
Between a PNR typed three weeks ago and a delegate at arrivals, a lot can change. Flights are rescheduled, passengers rebook, a delegate travels a day early with a colleague or arrives by train instead. The PNR the delegate gave you belongs to a flight the delegate is no longer on. If nobody reconciles, the car waits for a flight that landed an hour ago, and the delegate waits for a car that left.
Reconciliation is the discipline of comparing three things: what the delegate declared, what the travel record shows and what has actually happened, and then correcting the record before the vehicle leaves.
The three lists
| List | Source | What it tells you | Reliability |
|---|---|---|---|
| Declared | Delegate’s own answer in the app | Intent | Good at submission, decays |
| Verified | Desk’s check against ticket or agent record | Fact at a point in time | Best at the time of checking |
| Arrived | Airport desk, driver or liaison team | Reality | Most current |
A reconciliation workflow moves each item from the first list to the second and, on the day, to the third.
Step by step
Step 1: Make sure the declared list is complete
Everything starts with the request. Use the hospitality request to collect PNR, flight number, arrival time and terminal. The 72-hour collection plan covers this. Completeness by group tells you where to chase.
Step 2: Define what “verified” means
Agree what the desk checks: PNR against the delegate’s name, flight against the schedule, ticket against the ID. Verified should mean a person looked. The workspace records who verified an item.
Step 3: Run a full reconciliation 48 hours out
Sort by arrival time. For each flight, count the delegates declared on it and compare with the travel agent’s list. Mark every match as verified and every mismatch as an exception. Do it again at 24 hours.
Do it in Sociana: the operations workspace lists every participant’s requested and provided information, with pending, provided and verified states and team sheet access.
Step 4: Log and assign exceptions
Typical exceptions: a different flight, a rebooked date, a missing PNR, a name mismatch, a plus-one who needs a room. Each gets an owner, a next step and a deadline. At the GCOO Conclave, itinerary corrections were traced from the identity match to the participant’s readback, so the delegate saw the corrected card.
Step 5: Group arrivals into waves
Create pickup waves by terminal and time window, and assign vehicles and a welcome desk to each. Publish each delegate’s wave to their My Journey card so they know where to stand.
Step 6: Run arrival day from one screen
Keep the sheet open and sort delegates into three working groups: landed, delayed and not yet heard from. The liaison team marks arrivals as they happen; the desk updates the card and sends a notification to the affected delegate or group.
Step 7: Chase quickly and politely
For a delegate who has not landed or is unreachable, the liaison officer calls first, the desk second. Do not broadcast to the whole group.
Step 8: Close the loop after the event
Export the final arrival list, the exceptions closed and any that remained open. The hospitality-completeness figure by group, with the date, belongs in your report.
Pre-flight checklist
- A named reconciler per shift, with a backup.
- Agent list received at least 48 hours out and again at 24.
- Terminal and wave published on each card.
- Driver contact on each card and on the sheet.
- A decision rule for a delegate who misses the wave: next wave, taxi or reimbursement.
Reading a reconciliation sheet
A good sheet reads left to right as a story: delegate, declared flight, verified flight, expected landing, pickup wave, vehicle, status. Sort by expected landing so the desk sees the next two hours first. Use a small number of statuses, such as verified, exception, landed and handed over, and use them consistently. If your team invents a status, add it to the list rather than typing it into a note field.
Review the sheet out loud with the liaison team before each wave. Read the names expected in the next hour, ask whether anyone has contact with a delegate who is delayed, and confirm that each vehicle has a driver and a contact. The ritual takes five minutes and catches most of the problems that would otherwise surface at the arrival gate.
Pitfalls
- Reconciling once. Do it at 48 and 24 hours, and on the day.
- Treating the PNR as proof of arrival. It proves a booking.
- Changing the sheet and the card separately. The card should update from the record.
- No rule for the missed wave. Decide it before arrival day.
- Sharing the sheet too widely. Give each team its own slice.
India and SAARC notes
Indian conclaves and dealer meets draw delegates from many cities onto a few flights, often to resort or tier-two destinations where airport transfers take hours. Inbound international delegates add passport and visa checks: India recorded about 9.15 million foreign tourist arrivals in 2025 (IBEF, 2025), and airports are busiest at the seasons when conclaves cluster. Names on PNRs follow the passport, not the visiting card, so a reconciliation sheet needs a column for the ID name. In Bhutan, Nepal and Sri Lanka, check the local entry rules for Indian and other nationals and add them to the request.
How Sociana handles this
Behind My Stay and My Journey sits the workspace the desk actually works in. It lists every participant’s requested and provided information, such as ID, PNR, flights, rooms, pickups and drivers, with each field pending, provided or verified. Team members open the same sheet with permissions, so a hotel desk, a transport lead and a liaison officer see their own slice. Exception handling covers the late change, the missing document and the plus-one who needs a room. When a record changes, the delegate’s card updates and a notification can follow.
The GCOO Conclave 2026 in Jaipur, with delegates split across hotels, used the workspace for PNR and arrival reconciliation. Open the PNR and arrival reconciliation demo and use the post-event reconciliation checklist to close the record.
FAQ
Does Sociana read PNRs from airlines?
No. Delegates declare PNRs and flight details, and the desk verifies them against your travel agent’s or the ticket’s record. The app does not book travel or integrate with airline systems.
Who can see the reconciliation sheet?
Named team members with scoped access. A hotel desk, a transport lead and a liaison officer each see their own slice.
What if a delegate changes flights after verification?
Update the record and verify the new details before you treat them as final. The delegate’s card reflects the change when the record changes.
Do we need a notification for each change?
Only for the people affected. Send it to the delegate or the affected group, not to everyone.
Related reading
Glossary: PNR, PNR reconciliation, arrival manifest, exception handling, liaison officer. Occasion hubs: executive conclaves, incentive travel, dealer and partner meets.