To replace hospitality spreadsheets, turn each column of the master sheet into a request the delegate answers in the app, keep one live workspace where the desk checks answers, and publish each person’s arrangements back to their phone. Every item moves from pending to provided to verified, so you see what is missing without scrolling.
Who this guide is for
You run the hospitality or travel desk for an event of 200 or more people and you live in a master sheet: one row per person, forty columns, three colour codes and four people editing it. It works until the week before the event. You want to know what to move out of the sheet, what to keep in it and how to switch without losing a day.
Why the master sheet breaks around 200 people
A spreadsheet is a single point of truth only while one person edits it. By the time the second coordinator joins, copies appear. Delegates send details in four formats and someone retypes them. The version emailed to the hotel is not the one the transport lead has. A colour code means one thing to the person who made it and something else to everyone else. And the sheet cannot answer the delegate’s question, “where is my room?”, so the delegate phones.
India’s events and exhibition market is cited in a recent IPO prospectus at US$5.23 billion in 2024, growing to US$7.80 billion by 2029, and the industry is said to employ more than 10 million people directly (prospectus cited by Multibagg, 2025). A large share of that work is coordination done in spreadsheets by people who would rather be hosting.
Sheet versus workflow
| Question | Master spreadsheet | Request, publish, verify workflow |
|---|---|---|
| Who enters the data | The desk, retyping | The delegate, in the app |
| How do you know what is missing | Scroll and colour | Filter by status |
| Who sees the final arrangement | Whoever you send it to | Each delegate, on their own card |
| Who verified an item | Unknown | Recorded in the workspace |
| Multiple editors | Version conflicts | One live sheet with scoped access |
| What changes when a hotel changes | Resend the file | Update the record; the card changes |
The three verbs
The model is simple. Request: ask each delegate for exactly what the desk uses. Publish: send each delegate their arrangement back. Verify: the desk checks provided items and marks them verified. Everything else is detail.
Step by step
Step 1: Audit the sheet and cut it
List every column. For each, ask whether someone acts on it. Columns nobody acts on go. Columns the delegate supplies become requests; columns the desk produces become published arrangements. A forty-column sheet usually becomes twelve requests and eight arrangements. The hospitality master sheet and hospitality data field checklist show a reduced layout.
Step 2: Import the people once
Bring the delegate list in with names, numbers and groups, so every request attaches to a real member. Use member imports so the same identity serves login, hospitality and attendance.
Step 3: Build requests from the delegate’s perspective
Each request is text, a choice, a date or time, or a document. Write the label as a delegate would say it: “Which flight are you arriving on?” not “Inbound carrier”. Group the requests into short tabs, such as Travel and ID.
Step 4: Run the sheet in parallel for 48 hours
If you are switching mid-planning, keep the old sheet read-only and copy its content into the workspace. Do not edit both. Name one day as the cut-over and tell everyone.
Step 5: Open the workspace to the team
Give the hotel desk, transport lead and liaison officer access to the slice they need. Each sees pending, provided and verified for their fields. See operations workspace.
Step 6: Verify, then publish
Verify documents and details first; then publish the arrangement to the delegate’s card: My Stay, My Flights, My Journey. At the GCOO Conclave, that is how delegates split across two hotels each saw one personal itinerary.
Step 7: Keep exports for those who need a file
Hotels and DMCs may still want a spreadsheet. Export the arrival list or rooming list when they ask, and connect Sheets or webhooks if you need a live feed. See webhooks, Sheets and Airtable.
Step 8: Measure completeness daily
Check hospitality completeness by group each morning. It is the share of required items that are provided or verified; it tells you where to chase.
What to keep in a spreadsheet
Not everything needs to move. Keep finance reconciliations, vendor quotations and hotel contracts in the tools your finance team already uses. Keep the rooming list that the hotel sends you as a file, and import it. Keep an export of the arrival list on paper at the hotel desk as a fallback. What moves into the workflow is the part that is about delegates: what they must tell you, what you must tell them and who has checked it.
A useful test is to ask whether a delegate or a delegate’s arrangement is the subject of the row. If it is, the row belongs in the workspace. If the row is about money or contracts, it belongs where it already lives.
Pitfalls
- Copying every column. Cut first.
- Running two live sheets. Choose a cut-over day.
- Asking for documents too early. Ask for the minimum first.
- Exports without versions. Date-stamp every export.
- Forgetting retention. Decide how long ID documents are held.
India and SAARC notes
Indian hospitality work carries terms the sheet should keep: pax counts, hospitality desk, travel desk, control room, liaison officer. A conclave of 150 CXOs and a partner meet of 1,000 dealers have very different tolerances for forms, so test requests with a sample of real delegates. If the event is outside India, keep passports and visas in a separate request. Rooming lists can arrive from hotels in Colombo, Dhaka or Kathmandu as files; import them by CSV or Sheets rather than retyping.
How Sociana handles this
Hospitality in Sociana is a two-way loop. Organisers create requests for text, choices, dates or documents such as ID proofs, PNRs, flight details and room preferences. Participants answer in the app. The operations team works in a live workspace with team sheet access, handles exceptions and companions and publishes individual arrangements back as My Stay, My Flights, Accommodation and My Journey. Each field moves from pending to provided to verified, which underlies the hospitality-completeness metric. Rooming lists can be imported by CSV or Sheets. Sociana is not a travel-booking tool and does not hold hotel inventory.
The GCOO Conclave 2026 is the worked example. See the hospitality request to My Stay demo and hospitality requests and My Stay.
FAQ
Do we have to stop using spreadsheets entirely?
No. Keep a spreadsheet for finance or a hotel that needs one. The point is that delegates answer in the app and the desk’s source of truth is the workspace.
What if a delegate will not use the app?
The desk can obtain the details by phone and ask the delegate to confirm in the app, or record them through the team’s process. Decide it in advance and keep the exceptions list short.
How do we keep the data safe?
Give each team access to its slice only, set a retention date for ID documents and review the trust centre for what is stored.
Can we see who changed an item?
The workspace records status progression with the verifier. For broader audit needs, agree the activity log requirements at kickoff.
Related reading
Glossary: request and publish workflow, hospitality status states, hospitality completeness, travel desk. Occasion hubs: executive conclaves, corporate annual meets, incentive travel.