Guests and hospitality
Give guests one place to find the information they need
Editorial team · Reviewed
A guest information page should answer practical questions without exposing the private planning workspace. The best content is accurate, concise and easy to find on a phone during travel.
A practical sequence
- Publish confirmed event locations, local times and arrival instructions.
- Separate invitations to different events so guests do not infer an invitation they do not have.
- Include attire, transport, access and the right contact for questions.
- Review the page after every material change to the guest plan.
Work through an example
The rehearsal dinner is for a smaller group than the wedding. A general guest page can show the wedding schedule while the dinner invitation goes to its intended guests. The couple avoids an awkward correction caused by publishing every private event on one public page.
Where judgement matters
A hidden editing panel is not the same as private content. Preview the page as a guest and inspect exactly what is visible. Remove draft details, private vendor contacts and financial information before sharing the link.
Make it usable
Open the working tool and replace its sample assumptions with your own. Adapt the structured template to record the resulting decisions and handoffs. Review the finished version with the person responsible before it becomes an instruction to someone else.
Work the decision
A practice case
An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.
The wedding website shows a ceremony at 16:00, while a rehearsal dinner is restricted to a smaller group. A guest-facing hub should answer practical questions without revealing private events, supplier contacts or budgets. Treat each visible section as a permission decision rather than copying the planner’s entire runbook.
| Decision | Why it matters |
|---|---|
| Separate public information from invited-event details. | A convenient shared URL should not make every event visible to every visitor. |
| Put the latest practical answer in one maintained place. | Multiple PDFs and message threads can keep old transport instructions in circulation. |
| Name who owns guest updates. | A beautiful page becomes misleading when nobody is responsible for correcting it. |
Make one usable artifact
List the guest questions your hub must answer: where, when, transport, access contact, response deadline and who to contact. Mark each answer public or invitation-scoped.
Then test the difficult case
Change one pickup point after publication. Check an invited guest’s view and an outsider’s view, then confirm the outdated instruction is no longer presented as current.
Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.