Event postponement checklist: update buyers and check tickets
An event postponement checklist for a small workshop or event: pause sales, update buyers, track replies and check ticket validity before reopening.

An event postponement checklist starts with the people who already hold tickets. Pause new sales, establish what has changed and give every affected buyer a clear next step. A new date on the event page alone leaves old confirmations, payment requests and admission instructions unresolved.
For a single-date workshop, studio masterclass or small performance, keep a change record and a list of buyer replies. The workshop ticket sales checklist covers the original setup. Here the organizer needs to move the whole event after registration has begun.
Pause sales and preserve the existing orders
Assign one person to coordinate the postponement. Record the original date, the time the decision was made, the reason you can share and who approves the replacement arrangements. Keep the existing event and order references so staff can follow a buyer's purchase through the change.
Use your provider's supported way to pause sales. Check the public page without an organizer session and confirm that someone cannot buy the old offer. Review scheduled promotional posts and payment messages that could still invite a purchase. Pause or correct those messages through their actual sending tools.
Save a restricted copy of the current order list, including paid orders, free tickets, unresolved payments and active reservations. Keep private ticket links and QR credentials out of a shared planning sheet. Export only the fields the coordinator needs, and use the provider's live records when checking payment or admission status later.
Eventbrite's postponement guide separates changing event status, editing the date and emailing attendees. Check the equivalent steps for your provider before making a change. Its platform policies apply to its users; they do not establish the terms for an event sold elsewhere.
Write down what is confirmed about the replacement
If a new date is agreed, confirm the venue, instructor or performers, preparation time and participant limit before announcing it. Recheck access arrangements with the venue when the room or entrance changes. A new room may have fewer workstations even if it has enough chairs.
Record the agreed arrangements:
| Detail | Original arrangement | Replacement arrangement | Checked by |
|---|---|---|---|
| Date and time | Full date, start, finish and time zone | Confirmed full date and hours | Coordinator |
| Venue | Address, entrance and room | Verified location and access contact | Venue contact |
| Activity | Instructor, content and included materials | Any changes buyers need to assess | Session lead |
| Admission | Existing ticket instructions | Verified instructions for the new date | Ticketing operator |
| Buyer help | Original support route | Monitored route and named owner | Coordinator |
If the replacement is still undecided, state that plainly. Give buyers a date and time for the next update that the team can meet. If the platform requires a temporary internal date, follow its documentation and check that buyers cannot mistake it for a confirmed replacement. Do not advertise a guessed date to keep a page looking complete.
Check every deadline attached to the old date
The event start may be only one of several dates stored in the sales process. Review ticket sales opening and closing times, admission windows, scheduled reminders, calendar invitations and any reservation deadlines. Decide which need changing and verify the result individually.
MyVisito's organizer documentation describes a date-change option that can move related sales windows, admission deadlines and scheduled messages. That behavior belongs to MyVisito. Ask your own provider which fields move automatically and which remain unchanged.
For a reservation awaiting a bank transfer, read the instructions and deadline already given to that buyer. A date change should not quietly send a fresh request to someone whose payment is being checked. Use the manual-payment reservation workflow to investigate the existing payment and hold. Record any agreed change to that order separately.
Open an example of each affected message in the provider's supported preview or test process. Look for the old date in the subject, body, calendar attachment and payment instructions. Record the check rather than assuming that updating the main page also updated every saved message.
Contact existing buyers before promoting the replacement
Use the purchase records to identify recipients. A social announcement can help people notice the change, but it cannot show which affected buyers still need a direct update. Check whether the provider contacts purchasers, individual attendees or both. Someone who bought several tickets may need to pass the information to guests.
When the new date is not confirmed, adapt this operational message:
Subject: [Event name] on [original date] is postponed
Hello [buyer name],
[Event name] will not take place on [original date and time].
[Brief confirmed reason, if appropriate.]
The replacement date is not yet confirmed.
We will send the next update by [full date, time and time zone].
Your order reference is [reference], covering [quantity] places.
For help with this change or to discuss the available options,
contact [monitored route] and quote your order reference.
Current information: [public event update page].
[Organizer name]Before sending, add the options and information required by the applicable terms, provider rules and local requirements. Have the person responsible for those obligations approve the wording. This example supplies event details and a help route; it does not set a refund policy or a deadline for exercising a buyer's rights.
For a confirmed replacement, name both dates so the change is visible:
Subject: [Event name] moves from [old date] to [new date]
Hello [buyer name],
The new date for [event name] is [full date], [start] to [finish],
[time zone], replacing [original date].
Venue: [verified address, entrance and room].
Other changes: [relevant changes, or remove this line].
For your [quantity] places in order [reference]:
[ticket instructions verified with the provider].
Please reply through [monitored route] to tell us whether the new
arrangements work for everyone in your order or you need help.
You can discuss the available options through the same route.
[Organizer name]Fill the ticket line only after checking what existing holders must do. The confirmation message library covers initial paid, free and pending orders; a postponement update also needs the old date, the replacement and a route for unresolved responses.
Track replies separately from ticket and payment status
Use one row per order to coordinate buyer contact. Record the quantity covered by each reply. If an order splits because some guests can attend and others cannot, add ticket-level notes using the provider's references. Avoid copying private admission links into those notes.
| Field | What to record |
|---|---|
| Order reference and quantity | Which purchase and how many places the reply covers |
| Update delivery | Sent, failed or needs another supported contact route |
| Buyer response | New arrangements accepted, help requested or no reply |
| Ticket action | Existing access checked, replacement needed or unresolved |
| Payment action | None, under review, requested action or verified completion |
| Follow-up | Named owner, next action and review time |
An email marked delivered does not establish that the buyer read it or can attend. A request for help does not establish that a ticket was cancelled or money returned. Keep each status supported by its own record. If a refund is approved, track its actual execution through the original payment route and verify admission validity separately.
Work through 14 orders covering 24 people
Consider a fictional masterclass with twelve paid orders covering twenty-two people and two complimentary orders covering one person each. There are fourteen orders to contact and twenty-four issued admissions. No other reservations exist in this example.
After the first round of replies, the coordinator records:
| Response | Orders | Admissions covered |
|---|---|---|
| New date accepted | 9 | 16 |
| Help requested | 2 | 4 |
| No reply | 3 | 4 |
| Total | 14 | 24 |
The accepted group contains eight paid orders covering fifteen people and one complimentary order. The help requests cover four paid admissions. The unanswered group contains two paid orders covering three people and the other complimentary order.
Sixteen people have confirmed their plans, but twenty-four admissions still exist until verified ticket actions establish otherwise. The coordinator cannot offer eight more places by subtracting sixteen replies from twenty-four tickets. Assign the two help requests and three unanswered orders to named follow-ups. Reconcile each outcome before deciding how many new tickets, if any, can be sold.
Verify the buyer's access before reopening sales
Ask the provider whether the existing event can move with its orders intact or whether its supported process requires another event. Check whether original ticket links and codes remain valid, need refreshing or require replacement. Creating a second event without resolving old admissions can leave two conflicting sets of instructions.
Test through the supported environment using an existing test order. Open the buyer's current access, compare the displayed date and venue, and verify which event the admission process checks. If a replacement is required, confirm how the old credential becomes invalid. The door checklist covers admission exceptions on the day.
Before reopening, compare the public page, a newly issued confirmation and an existing buyer's instructions. Recount all active admissions and unresolved holds against the replacement's approved participant limit. Check the old venue's communication plan too, so someone arriving on the original date has a useful contact route.
If you are planning ticket sales with Skedful, contact the team with your country, event date and required change workflow to confirm availability and supported actions. Save the verified ticket instructions beside the response list, then give the door operator the current event details and the coordinator's contact.
About this article
Skedful is the publisher and corrections contact. Our editorial checklist covers product availability, source dates, worked examples and the limits of each claim.
About this articleWorked examples and sample calculations describe hypothetical scenarios. When an article cites research or customer results, follow the source for its context and limits.
Found an error? Send us the article link and the passage that needs a correction.
Report an error to SkedfulReminders come with every Skedful plan, on a schedule you set once. PricingSkedful vs Fresha vs Booksy