Layouts
A layout turns a room into a reusable plan: tables and individual seats define capacity, while stages, bars, dance floors and other fixtures explain the space around them. Save the plan once, then select it when an event needs assigned seating.
The library is at Layouts. Opening a card or choosing Create Layout takes you into the Layout Builder. A saved room, a browser-local draft and an event-specific copy are different records; confirm which one you are editing before saving changes.
Event Layouts
Start with the real venue dimensions and its permanent features. Position large fixtures first, add tables and seats, then review entrances, circulation and sightlines. A counted seat is not by itself a physically usable or approved place.

- Choose Create Layout for a new room, or open the intended saved card.
- Review floor width, depth, units and furniture sizes in Layout Settings. Defaults may not match your venue.
- Place seating and fixtures. Use readable labels and consistent numbering.
- Use the grid, snapping and spacing suggestions to inspect the arrangement. Review each warning against the physical room.
- Open the 3D view if it helps understand placement, then return to the plan for precise edits.
- Choose Save. For a new layout, enter a useful name and description, review any tags or location association, and complete the save.
- Return to the library, reopen the saved layout and confirm its geometry and capacity.

In the review, a new Garden jazz rehearsal seating plan was created from Cabaret, saved and reopened with 16 tables, 96 seats and one dance floor. The separate 17-table event plan was left unchanged. Neither plan was presented as physically approved: both still had spacing suggestions to resolve.
To use a room for ticket sales, select it during the event's layout-based setup and review the event's own tables-for-sale and ticket restrictions. Saving a layout alone does not create an event, issue tickets or make seats available for purchase.
Layout Templates
Templates supply starting geometry using the current floor settings. They help answer “how should I begin?” rather than replace measurement and review.
| Template | Starting arrangement |
|---|---|
| Banquet grid | Round tables of ten in a grid. |
| Theatre rows | Rows facing a stage. |
| U-shape | Rectangular tables around an open center. |
| Cabaret | Six-seat tables arranged around a social/performance space. |
| Pool hall | Pool-table arrangements. |
Open Templates in the editor, choose a suitable arrangement, and inspect the resulting counts and spacing. Our empty Cabaret draft produced 16 tables and 96 seats; another floor size or template can produce different results.

Templates are additive: applying one to an occupied floor can create overlapping or duplicate arrangements. Start from a new draft when comparing a different overall plan. The current Blank canvas choice closes the template chooser; it does not erase an existing room.
Reusable Layout Blocks
A saved block is a small group of selected tables that you can add again, such as two front-row tables or a repeated classroom pod. It preserves the tables' relative positions. The reviewed block implementation stores tables, not a complete stage-and-fixture package.
- Select the tables you want to repeat. In the reviewed desktop editor, Shift-selection added a second table to the selection.
- In Layout Settings → Saved blocks, choose Save selection.
- Enter a specific name, such as Two front-row tables, and confirm.
- Click the saved block to add a copy to the current floor.
- Position the new tables and check numbering, counts and spacing before saving the layout.

Blocks are stored locally in the browser profile for the active business/profile. They are not a shared cloud library and should not be assumed to appear on another computer. Use a saved cloud layout for the room arrangement the team needs to reopen.
Collaborative Layout Editing
The current collaboration feature shares presence and cursor positions for a saved layout. It helps teammates see who has that layout open. It does not automatically merge table moves or other geometry edits between people.
Open the same saved layout under the appropriate team accounts when checking presence. An event-only drawing session is a different context and does not establish the same saved-layout presence session. Opening another tab as the same user also does not prove that a second teammate is present.
Agree who is making and saving a room change. If local work differs from the saved cloud record, review the conflict choice deliberately rather than treating a visible cursor as protection against overwriting another edit.
Presence behavior is confirmed from the implementation; a two-account editing session and cross-device cursor delivery were not tested in this review. Do not rely on automatic multi-user geometry synchronization.
Find and manage saved plans
The library supports searching names, descriptions and tags, plus location and tag filters. Give reusable plans distinct names such as Main room — cabaret rehearsal so staff can distinguish them from a specific event copy.
Private and public layout visibility are separate choices. Review the plan and its labels before sharing publicly. A public layout is not the same thing as a public event or an open ticket sale.
Save and recover versions
Browser-local drafts protect work in progress, but they are not a substitute for a completed cloud save. Reopen the library record to verify persistence.
For an existing layout, saving geometry retains earlier versions; the implementation keeps up to ten. History lists those saved versions. A brand-new layout has no earlier version yet, which was confirmed after the rehearsal's first save.
Restoring a version loads its plan into the editor. Review it and save again if it should become the current saved arrangement. This review did not perform a history restore, so it does not prove recovery of a particular earlier floor or settings combination.
Troubleshooting
| Symptom | What to review |
|---|---|
| Template overlaps the current room | Templates append; begin a fresh draft or remove the unwanted geometry. |
| Saved block is missing elsewhere | Blocks are browser-local and profile-scoped, not cloud-synced. |
| History is empty | Save an existing layout's geometry to create an earlier version; the first save has no predecessor. |
| Presence is absent | Check that both people opened the same saved layout under different accounts and that realtime connectivity is available. |
| Teammate's moves do not appear | Presence is not shared geometry editing; coordinate saving explicitly. |
| Seat count is correct but spacing is poor | Correct scale, furniture dimensions and layout warnings against the actual venue. |
Continue with the detailed Layout Builder manual and Event ticket settings.