Duplicating an event

"Can I duplicate this event?" is one of the most common questions on the support inbox, and the honest answer is: not directly, but the thing you actually want is a template, and templates are usually a better fit anyway!

This article explains why 1pm doesn't have a one-click duplicate button, what to use instead for the three common reasons people ask, and the small bag of tricks for the cases where templates aren't quite right.

Why there is no "Duplicate" button

It seems like an obvious feature, and we thought about adding it. The problem is that "duplicate this event" means six different things to six different venues, and a single button can't do all of them well.

The annual conference planner wants every timeline item copied across, but with new dates and new crew assignments. (That's a template.)

The wedding planner wants every timeline item copied across, but the original event is for the bride and groom, and the duplicate is meant to be a different couple in a different venue. (That's a template.)

The corporate operations manager wants to copy yesterday's gala dinner because tonight's is the same shape but with a slightly different running order. (That's a template, with light editing.)

The venue that made a typo on event creation wants to throw away the original and start again. (That's just edit the existing event.)

The venue that has built a complex run of show for client A and wants to clone it as a starting point for client B. (That's a template.)

The venue that needs the exact same event to happen on a second date with the same crew, same venue, same details. (That's the closest thing to a true duplicate, and even then the crew assignments would almost certainly want a sanity check before you sent the links.)

Every one of these is best served by templates, which re-anchor to the new event's date and leave the run-specific clutter behind (the briefing fields tied to that particular booking, the attached files, the live share links, the requests, and the execution state), so you start from a clean reusable shape. A template does carry the crew assigned to each item across, so the one thing to sanity-check after inserting is that those people are actually on this event.

Use a template for "I want this shape again"

Templates are the supported path for almost every duplicate-event scenario. The flow:

1. Open the event you want to base the new one on. Click Save as template in the planner header. Give it a name that describes the shape ("Standard Saturday wedding", "One-day conference plenary", "Two-day intensive workshop"). Click Save.
2. Create a brand-new event the normal way: New event button, set the name, set the date, save. You're in a fresh planner with an empty timeline.
3. Click Insert template. Pick the template you just saved. Click Insert. The timeline fills in with the saved structure (every item, every time, every Where field, every Details block).
4. From here you assign crew, fill in the BEO/briefing fields specific to this client and venue, and you're off.

What is copied into the new event: every timeline item with its title, start time, duration, Where field, Details text, and the crew member assigned to it. The times are re-anchored to the new event's date.

What is not copied: the briefing fields (PAX, space, client, organizer, and the BEO fields), any attached files, the live share links, the requests, and the execution state (start/finish marks) from the original event. The new event keeps the date, status, and briefing fields you typed when you created it; inserting a template fills in the timeline without overwriting those.

See the Event templates article for the full walkthrough, including how to manage templates over time and the difference between saving from an event and building one from scratch.

Use a template once and discard, if you just want this event copied

If you have a one-off "I need this exact event again" case, you can still use the templates flow. Save the source event as a template, create the new event, insert the template, then delete the template if you don't expect to use it again. No harm done.

This is also the approach for the "moved my event to a new date and want to keep everything" case. Save as template, create the new event on the right date, insert. The timeline is identical to before, with the times intact and the date refreshed.

What about the briefing fields

Briefing fields (the BEO data: Service style, Setup style, PAX guaranteed, Dietary Requirements, the Menu picker and Menu notes, Bar package, Audio Visual & Technology, Access from, Vacate by) live on the event itself, not the timeline. Inserting a template does not fill them in, because they tend to be event-specific: a 150-pax plated dinner template is unhelpful if the next event is a 600-pax stand-up cocktail.

If the briefing details are the actually-stable part across your events (you always run plated dinners with the same dietary requirements), you can still pre-fill them quickly. The autocomplete on Service style, Setup style, and Bar package is per-owner, so as you fill these in on subsequent events, your previous entries appear in the autocomplete and you can pick instead of retyping.

What about crew assignments

Crew assignments do carry across when you insert a template: each timeline item keeps the crew member it was assigned to on the source event. For an internal, stable team (you always have the same banquet manager running plated service) this is a time-saver: the assignments are already in place.

The flip side is the one thing worth checking every single time. Crew availability changes by the day, so before you generate and send any share links, run an eye down the Responsible column and re-pick anyone who isn't on this event. Sending last quarter's photographer a link to tonight's wedding is the mistake to avoid, and a ten-second check after inserting prevents it.

Edge cases

• Same event, two days. Save as template, create the second event on the second date, insert. The same applies if you need the same event repeated weekly for a month (make four events from one template).
• Recurring monthly. 1pm doesn't have a recurrence engine. Use the template pattern manually each month. If you find yourself doing this often for a true recurring series, email [email protected] we'd want to hear about it.
• Backed up wrong, need to re-do. If you've made a mess of an event and want to start over while keeping the original as a reference, save the messy event as a template (even half-finished work makes a fine template), create a fresh event, and insert. You now have a clean slate. The original event is untouched.
• Want to share an event with another planner. Templates are private to your account. You can't directly export a template to share with someone else's 1pm account. If you have a use case for this, email [email protected].

When templates aren't enough

The genuinely hard duplicate case is when you want a one-click copy of every aspect of an event including crew, briefing, files, links, requests, and history. We haven't built that because the cost of getting it wrong is high (links sent to the wrong people, briefing fields copied from a different client). If you have a strong reason to want this, email [email protected] with the specifics; the more concrete the use case, the more usable the feature will be if we do build it.

A small workflow note

The biggest unlock for "I keep duplicating events" is investing fifteen minutes the first time to build the template properly. The second time you use it, you'll save twenty minutes. The fiftieth time, you'll save hours. Treat the template as the durable artifact and the events as disposable.