To track hospitality completeness, define the required fields for each guest, give every field a status of pending, provided or verified, report the percentage complete by group and day, chase gaps on a fixed rhythm and set a cut-off for exceptions. The number tells you how ready you are long before arrival day.
What completeness means
Hospitality completeness is the share of required information that you hold for your guests, and that has been checked. It answers a simple question: of everything we need to know to look after these people, how much do we actually know? If you need ID, a flight, a room preference and a pickup for each delegate, then a delegate with all four verified is complete, and one with two is half complete.
The metric matters because the cost of missing information rises as the event approaches. A missing flight detail a month before is a reminder. The same gap on arrival day is a stranded guest.
Step 1: define the fields
Write the list of required fields for each type of guest. Not everyone needs the same things. A local delegate may need only a dietary preference. An out-of-town delegate needs flight, hotel and pickup. A speaker needs travel, accommodation, presentation and a profile. Group the fields by guest type.
| Guest type | Required fields |
|---|---|
| Local delegate | Contact, dietary, ID if needed |
| Out-of-town delegate | Contact, ID, arrival and departure details, room preference, dietary |
| Speaker | Above plus session details and special requirements |
| Companion | Linked to primary guest, own details |
| VIP | Above plus liaison officer and protocol notes |
Keep the list short and necessary. Every extra field reduces completion.
Step 2: use three statuses
Use consistent statuses: pending (asked, not answered), provided (answered, not checked) and verified (checked by the desk). The third status is the one that matters. A flight number typed incorrectly is provided but not verified. A verified record has been compared against a ticket, a PNR or another source.
Make each status visible to the team, and record who verified and when.
Step 3: report by group and by day
A single overall percentage hides problems. Break it down by:
- Group. Which delegations or zones lag?
- Field. Is the lack mostly flight details or ID?
- Day of arrival. Which arrival days are least complete?
- Owner. Which team member’s list is behind?
Produce a short report at a fixed rhythm, such as weekly in the early weeks and daily in the final week. Show the trend, not only the snapshot. A group that moved from forty to sixty per cent in a week is healthier than one that stayed at seventy.
Step 4: chase the gaps
Chasing is where completeness is won. Segment the pending list and send a message that fits each group. A reminder from the organiser’s office to senior delegates, a message from the family to relatives, a call from the delegation lead to a zonal team. Keep messages short, specific and kind: “We still need your arrival time to arrange your pickup. It takes one minute here.”
Use more than one channel. Some guests answer a WhatsApp message and ignore email. Some need a phone call. Track attempts so the team does not chase the same person three times in a day.
Step 5: set thresholds and a cut-off
Decide the levels at which you act. For example: at four weeks to go, completeness should reach a stated level; at one week, higher. Set a hard cut-off for submitting details, after which changes go through an exception process. Share the cut-off with guests so they know the deadline is real. After the cut-off, the desk handles late cases individually, and the numbers stop shifting.
Step 6: verify against sources
Verification takes time. Reconcile arrival details against ticket copies, PNRs or airline information. Check rooms against the hotel’s list. Resolve mismatches. Prioritise senior guests and large groups, since their problems are costly. Leave low-risk checks, such as dietary notes, to the last.
Step 7: use the numbers to make decisions
If completeness is low a week before the event, you have choices: extend staff on the desk, send a personal call to the missing, or plan for more exceptions on arrival days. If it is high, you can reduce staffing for the final days or put the effort into experience details. Report the number to the organiser’s leadership with a short note on what you are doing about the gaps.
A worked example for a three-hundred-delegate conclave
Imagine a conclave with 300 delegates in six groups. Four weeks out, the overall completeness is below half, and one group lags far behind. The team sends targeted messages and calls the group’s lead. Three weeks out, the number rises. At two weeks, the desk starts verification and finds that some flight numbers do not match the dates. At one week, completeness is high, and the remaining items are mostly verification. At the cut-off, a short list of exceptions is handed to the desk.
The example is illustrative. Your thresholds and the speed of progress will depend on your audience.
Common reasons guests do not respond
Understanding why people ignore a request helps you design a better one.
They do not see it. The request is buried in a message among many others. Fix: use one clear channel and a distinct reminder.
They do not know the answer yet. Flights are not booked. Fix: allow a provisional answer and set a date by which it must be final.
They think someone else is doing it. An executive assistant or a travel desk handles the booking. Fix: ask who the right contact is and add them to the record.
They find it intrusive. The form asks for too much. Fix: cut fields and explain purposes.
They are not comfortable with the app. Fix: offer a call or a family member’s help.
Each cause points to a different remedy, so look at the pending list and sort the reasons before sending another generic reminder.
Escalating without annoying
Escalation should rise gently. First, a reminder. Second, a message from someone the guest knows. Third, a call. Fourth, for senior guests, a note to their office. Keep a record of each step so that the team knows what has been tried. Avoid language that sounds punitive. Guests are not at fault; the process is the organiser’s responsibility. A friendly tone gets more answers than a stern one.
What to do with the final report
After the event, keep the completeness history. It shows how quickly information arrives, which groups are slow and which reminders worked. Compare it with the number of exceptions on arrival days. If exceptions were high despite high completeness, your verification may have been thin. If exceptions were low, your process worked. Share a short summary with the organiser and keep the data in the reusable configuration for next year. Over several events, you will know the normal curve for your audience, and be able to spot trouble earlier.
How Sociana handles this
Sociana’s operations workspace lists each participant’s requested and provided information, such as ID, PNR, flights, rooms, pickups and drivers, and shows each field as pending, provided or verified, with the verifier recorded. Team members open the same sheet with permissions, so a hotel desk, a transport lead and a liaison officer see their own slice. An exception flag marks a record that no longer matches. These states are the basis of Sociana’s hospitality-completeness metric. Reports and exports deliver hospitality data for the team.
At the GCOO Conclave 2026 in Jaipur, delegates split across two hotels, and the workspace was used for PNR and arrival reconciliation. Read the case study. Related: executive conclaves, hospitality completeness, hospitality status states and pnr.
Frequently asked questions
What is a good completeness target?
It depends on the event, and no universal number applies. Set targets by week with your team, based on how many exceptions the desk can handle on arrival days.
What is the difference between provided and verified?
Provided means the guest has submitted the information. Verified means the desk has checked it against another source, such as a ticket.
Who should see the completeness report?
The hospitality lead, the organiser’s senior contact and group leads who can chase their own people. Restrict personal details to those who need them.
Can we export the data?
Yes. Hospitality data is part of the occasion reports and exports, so the team can share summaries or work in a sheet.