Cloning is useful when an event is similar to one you have already run. It gives you a starting point without rebuilding every participant type, payment method, catalogue choice, form setting, or branding detail by hand.
Good reasons to clone
- You are running the same venue again with similar participant setup.
- An event date is locked because activity already exists, and you need a new date instead of rewriting history.
- You want to preserve a proven application form, pricing setup, or branding layout.
- You need a new draft based on a completed event for next season or next year.
After cloning
Open the cloned draft
Check that the new name and dates are correct.
Review public wording
Look for old dates, venue notes, deadlines, arrival instructions, or seasonal text.
Check pricing and payment details
Update charges, VAT, bank transfer wording, PayPal links, or Stripe readiness if needed.
Check compliance and forms
Make sure required documents, questions, terms, and catalogue choices still apply.
Open only when ready
Treat the clone like any other draft.
Cloning saves setup time, but it does not remove the need for review. Re-check old dates, deadlines, payment wording, arrival notes, and terms before sharing the new event.
Need the rest of the event to use the same details?
Run applications, ticketing, payments, documents, transport, site plans, stage schedules and event-day work around the same event.
Related articles
Create an Event
Use the event setup flow to create the central event workspace before adding applications, tickets, stages, site plans, or transport work.
Enable Modules for an Event
Turn on Trader Manager, Ticketing, Stage Manager, Site Plan, or other event modules when an event needs those workflows.
Edit an Event
Update event details, module setup, participant setup, pricing, forms, payment methods, branding, and review settings after creation.