Guide
Client onboarding checklist for event businesses
Follow a practical client onboarding checklist from confirmation and deposit through gathering event details, building the timeline, and the final check-in.
A client saying yes is the start of the work, not the end of it. Between that yes and the event date there is a sequence of small steps that, done consistently, means nothing gets discovered for the first time on the day. Skip or reorder them and the gaps show up at the worst possible moment.

What should happen right after a client says yes?
Send a written confirmation before anything else. It does not need to be a contract — it needs to exist as a record both sides can point back to: the date, what is included, the price, and what happens next. A confirmation that only exists as a verbal agreement or a single chat message is easy to misremember on either side.
What goes in the confirmation message?
Enough that the client never has to ask "wait, what did we agree to?" three weeks later:
- The date and start time
- What is included, in plain terms
- The total price and the deposit amount
- What happens if either side needs to cancel or reschedule
When should the deposit request go out?
Immediately after confirmation, with a clear due date. The date is not properly held until the deposit is paid — see the full breakdown in the deposits post below. Waiting to ask for it "once things are more settled" is how double-bookings happen.
What details do you actually need to gather?
Whatever changes the plan for the day — and no more than that. For most event types this means: the venue and any access restrictions, timings for the parts that matter (ceremony, speeches, load-in), who the other vendors are and how to reach them, and any specific requests. Collecting more than this "just in case" usually means it never gets read back before the event anyway.
How do you build the day-of timeline?
Work backwards from the moment that cannot move — the ceremony start, the doors-open time, the speeches — and slot everything else around it with buffer, not back-to-back. A timeline with zero slack looks efficient on paper and falls apart the moment one thing runs five minutes long, which one thing always does.
What should the week-before check-in cover?
A short confirmation that nothing has changed: timing, venue, contact numbers, and the balance payment if it is not already settled. This is not a full re-briefing — it is a final check that catches the venue change or timing shift that happened after the original details were gathered and never made it back to you.
The onboarding checklist
| Step | When | What it produces |
|---|---|---|
| Confirmation sent | Same day as "yes" | A written record of terms both sides agreed to |
| Deposit requested | Immediately after confirmation | The date is actually held |
| Details gathered | Weeks out, not the week before | Venue, timings, contacts, requests |
| Timeline built | Once details are in | A day-of schedule with buffer |
| Balance requested | Ahead of the due date agreed at confirmation | No payment conversation on the day |
| Week-before check-in | 5-7 days out | Confirms nothing has quietly changed |
Can your public portfolio make onboarding easier?
Yes, before the enquiry is even submitted. A useful portfolio does more than show attractive work: it explains the services, typical projects, starting price, location or service area, and the next step. That helps potential clients find a relevant page in search and decide whether the business fits before beginning the onboarding process.
Write for the questions a real client asks. A photographer may need a page that clearly says "corporate event photography in Dubai" or "wedding photography in Manila," supported by real work and useful detail. A search title and description can help a search engine understand that page, but the visible proof is what helps the visitor choose it. Discovery starts the journey; clear expectations make the steps after "yes" easier.
What most people get wrong
- Gathering details too early or too late. Too early and things change before the event; too late and there is no time to react if something is missing.
- Treating the week-before check-in as optional. It is the cheapest possible way to catch a venue change before it becomes a same-day surprise.
- Building the timeline before the details are confirmed. A timeline built on guessed timings gets rebuilt anyway — do it once, in order.
- Losing the confirmation in a message thread. If the client has to scroll back to find what was agreed, it was not really recorded.
Gallurio does not send automated reminder emails or generate the confirmation for you — the writing and the sending are still yours. Its published portfolio can carry a configured search title, description, Gallery description, canonical URL, and social preview, while the booking workspace holds the client, gathered details, and timeline together. Those technical signals can help search systems understand the public page; they do not guarantee a ranking. Whatever you use to run onboarding, the sequence above is what matters, not the tool.
Related reading
- How much deposit should you take for an event booking — the deposit step in more detail
- Gallurio vs Notion — why a general-purpose workspace struggles to hold booking details reliably
- Gallurio vs Google Forms and email — what happens to gathered details once they land in an inbox
- How to build a portfolio page that gets found and books clients — improving the steps before the enquiry