Training/Building a floor plan
How do I reuse part of a floor plan in another event?
Select the objects you want, then either copy and paste them into the other plan or send them straight there with Copy to another diagram. The staging, the bars and the dance floor travel together; the plan you copied from is untouched.
From the course: Copying objects into another diagram · 1:07
The next event usually wants most of the last one. The staging package, the bars, the dance floor, the registration desks — all of it again, minus a few things, in a different room. Rebuilding that by hand is the single biggest waste of time in event diagramming, and it is the complaint people bring us most often about the tool they are leaving.
Three ways to reuse a plan
| You want | Use | Where |
|---|---|---|
| The whole plan again | Duplicate the diagram | Storage · row actions · Duplicate |
| Part of a plan, in a plan you have open | Copy and paste | Select · ⌘C · open the other plan · ⌘V |
| Part of a plan, in a plan you have not opened | Copy to another diagram | Select · right-click · Copy to another diagram… |
| The same setup every time, in the same room | A saved setup | … menu · Save as layout template |
Copying a selection into another plan
- Select what you want. Drag a box around it, or hold
Shiftand click each piece. - Right-click the selection and choose
Copy to another diagram…. - Pick the plan it should go to, searching if you have a lot of them.
- The objects land in the middle of that room, on their own layers, ready to move. Nothing about the plan you copied from changes.
Copy and paste also works across two tabs and survives a reload — copy here, open the other plan, paste. Use
Copy to another diagram…when you already know where it is going and would rather not open it at all.
What travels, and what changes
Every object carries its own dimensions, colour, height and chair count, so a copy is the same furniture, not a lookalike. A few things are deliberately adjusted on arrival:
| Thing | What happens |
|---|---|
| A table block | Travels as a block, so it still renumbers and still fills the way it did where you built it — never as loose tables |
| Layers | Matched to the target's layer of the same name, or created there if it has none |
| Position | Centred in the room it arrives in, because the coordinates from a 150′ ballroom mean nothing in a 60′ breakout |
| Table numbers | Kept as they were — check them against what is already in the destination |
Because the objects are real objects rather than a flattened picture, the seat count, the load list and Diagram Check all update in the destination the moment they arrive.
When to save a setup instead
Copying is for a one-off — this plan, into that plan, today. If you find yourself copying the same objects for the third time, that is a setup, and it belongs on the room so anyone on the team can start from it. Saving a setup takes about ten seconds and you can save a selection rather than the whole plan, which is how you end up with a staging package you can drop into any room.
Duplicating a whole diagram keeps it inside its event. If last year’s gala is this year’s starting point, duplicate it and move the copy into this year’s event rather than editing the original — the old plan is the record of what actually happened in the room.
Related
Updated September 23, 2026 · 26 articles in the knowledge base