A guest meets your event roughly thirty times before it ends. Map the touches and you can design them; leave them unmapped and they design themselves.
Hosts design the event; guests experience a sequence. Between the day a save the date arrives and the day a thank-you note does, a typical wedding guest interacts with your event somewhere near thirty times — and most of those touches happen nowhere near the venue. Each one either confirms the event's promise or quietly discounts it. This guide maps the full sequence, because a touchpoint you have named is one you can design, and an unnamed one gets designed by default — usually by a group chat.
| Touchpoint | What the guest actually experiences | The design decision hiding in it |
|---|---|---|
| Save the date | First contact; the event's register is set here and never fully reset | The identity's debut — timed and typed like you mean it |
| The search | They immediately look for your website | Have it live the same day; even one page beats a 404 |
| The invitation | The keepsake moment — held, photographed, displayed | Everything in the guide; and whether it greets them by name |
| The RSVP | Their first action — friction here colors everything | Named guests, real questions, two minutes end to end (the guide) |
| The dietary answer | Being asked properly, once — then never asked again | Free-text question, kitchen-readable answer, carried through to the caterer without the guest repeating it |
| The reminder | A nudge that knows whether they replied | Targeted to non-responders only — a broadcast nag punishes the prompt |
| Travel & logistics | Booking flights and rooms off your information | The details card + website answering before the questions form |
| The countdown message | Schedule, dress code decoded, weather-real advice, a week out | The single highest-gratitude message in the whole sequence — send it |
Notice what Act I is made of: paper twice, screens six times. This is why an identity that lives only on paper breaks exactly here — the guest has met your event eight times before seeing a single flower, and six of those meetings were on a phone.
| Touchpoint | What the guest actually experiences | The design decision hiding in it |
|---|---|---|
| Arrival & wayfinding | The first three minutes of mild social anxiety | Legible arrival — one alphabetical seating display, visible bar, someone saying hello |
| Finding their name | The escort card: proof they were expected | The highest-leverage small object of the day (seating guide) |
| The seat itself | Four hours next to whoever you chose | The politics and the kindness of the chart — one known neighbor each |
| The menu & place card | The paper held longest all event | Same world as the invitation; their name on it if you do one personal thing all day |
| The dietary keeping-of-the-promise | Their answer from Act I arriving as the right plate, unasked | Hospitality's quietest triumph — and pure information design |
| The schedule's honesty | Whether 6:00 meant 6:00 | Guests forgive almost anything except standing in heels for an unexplained hour |
| The one personal moment | A host's ten seconds of undivided attention | Not designable on paper — but protectable in the timeline; build the gap for it |
| Departure | The last impression: transport working, a favor worth keeping | End the evening on purpose, not by dissipation |
| Touchpoint | What the guest actually experiences | The design decision hiding in it |
|---|---|---|
| The morning-after message | Warmth while the glow holds — and the photo-sharing link | Drafted before the event, sent within a day or two |
| The photographs | Reliving it; sharing it; the event's public afterlife | One canonical gallery link beats forty airdrops |
| The thank-you note | Closure, in the event's own hand | Same design family as the invitation, within three months — ordered with the suite so it actually happens |
Print the three tables and do one pass with two pens. Circle every touchpoint that currently has an owner and a design; underline every one that would happen by default. Most events, honestly audited, circle the invitation and the table and underline nearly everything else — which is also the diagnosis of why events with spectacular rooms can still feel disorganized to the people in them: the room was designed and the sequence wasn't. The good news is the asymmetry: Act I and III touchpoints are cheap. A countdown message costs nothing. A morning-after message costs nothing. What they need is not budget but a system that knows every guest, remembers what each one answered, and speaks in the event's own voice each time — which is, not coincidentally, the thing we build.
Invitation, website, RSVP, reminders, seating, day-of updates and thank-yous — Evorrah carries a guest through every touchpoint in one identity.
Guest experience at Evorrah Start a commission
Not the flowers. Almost everything they remember is about being expected.
Three hundred invitations for three hundred people — what per-guest design changes.
Deadlines, questions worth asking, and chasing without nagging.