Prepare for Booking or Communication Tools to Go Offline

A booking page, shared document or internet connection can become unavailable just as guests arrive. Prepare a small fallback that lets the organizer make accurate decisions without exposing a full collection of personal information. The aim is continuity for the event, not an improvised replacement payment or registration system.

Choose the minimum information needed

Identify what the welcome team needs to confirm attendance and allocate supplies. This may be a current booking reference, a name or identifier, party size and reserved design. Avoid copying payment details, sensitive participant notes or unrelated customer records into a general printout.

Use the organization's established privacy and retention procedures for any offline copy. Keep it with the responsible organizer and decide how it will be recovered or disposed of afterward.

Prepare before the event

1. Export or print an appropriately limited current list if your system and procedures allow it.
2. Record the time of that snapshot.
3. Write down the coordinator and venue contacts through an approved method.
4. Prepare paper change notes or an approved offline record.
5. Tell helpers which decisions they may make and which must wait for the coordinator.

Do not assume an old screenshot shows current availability. Cancellations, substitutions and new bookings after the snapshot can make it incomplete.

Use one change log during the outage

• Time and booking reference.
• Issue or change requested.
• Decision made and person authorizing it.
• Supplies issued or place held.
• Follow-up needed when systems return.

For example, a guest arrives with confirmation not shown on the offline list. The welcome helper records the reference and asks the coordinator to check the available evidence and actual capacity. The helper does not automatically admit an extra painter or dismiss a valid booking because a printout is old.

Reconcile after service returns

Compare the offline log with the live system before making further offers or changing capacity. Resolve duplicate entries and unconfirmed admissions. Let the appropriate organizer handle payments or refunds through established channels; never ask guests to write card details on a fallback sheet.

Record what failed and whether the fallback was sufficient. Improve the next event's preparation without retaining extra personal information indefinitely.

Common questions

Should every helper have a complete attendee export?

No. Give people only the information needed for their assigned role and follow the organization's access rules.

Can registration continue during an outage?

Only if the organizer has an approved process that can confirm capacity and avoid duplicates. Otherwise pause new confirmations until the record is reliable.

Connect this with repeat-session records, capacity planning, the event checklist and host readiness.