Managing Venue Spaces
Defining the areas of your property, with capacities and photos.
Venue spaces are the areas of your property you book separately — the ceremony garden, the barn, the bridal suite. Defining them is what lets the calendar catch a double booking and the Flow view show what is happening where.
Adding a space
Go to Settings, then Venue Spaces, and click Add Space. The panel asks for three things:
| Field | Required | What goes in it |
|---|---|---|
| Space Name | Yes | "Ceremony Hall", "Reception Ballroom" |
| Type | No | Ceremony, Reception, Cocktail, Outdoor or Other |
| Capacity | No | The most guests it holds |
Save with Create Space, or Save Changes when editing an existing one.
Type and capacity are both optional — a space with neither still works for booking and conflict detection. Capacity is recorded, not enforced: nothing stops you seating 200 guests in a room you marked for 150.
Photos
Each space takes up to three photos. The first one you upload becomes the cover, and the star on any photo makes it the cover instead. Delete the cover and the next photo takes over.
Those photos are not decoration. The cover image appears:
- on the calendar, when you open an event assigned to that space
- on the space's lane in the Flow view of a day-of timeline
- on the public review page a couple sees after the wedding
They do not appear in proposals or in the Guest Guide.
The list
Spaces show as a table — Space Name, Type, Capacity, Images and Actions — with a pencil to edit and a trash icon to remove. Drag the handle at the left of a row to reorder them; that order is what every space dropdown in the product follows, so put the ones you use daily at the top.
Deleting a space
Deleting asks first, and the confirmation says what happens: bookings, storage locations and assets that reference the space keep their data but lose the link to it.
The space is retired rather than erased — it stops appearing in dropdowns, and historical records that pointed at it stay as they are.
Where spaces are used
- The calendar blocks a space for the event that holds it, which is how a double booking gets caught.
- Weddings can take several spaces at once — ceremony in one, reception in another.
- The day-of timeline gives each space its own lane in the Flow view. An event with no space assigned does not appear on a lane at all.
- AssetSync turnaround and storage locations reference spaces if you run that module.
Practical use
- Define every space you book separately, even the ones you use twice a year. A space that does not exist cannot raise a conflict.
- Do not create a space for somewhere you never book on its own. The car park is not a space; it is part of the venue.
- Set capacities where you know them. They are a reference for whoever is building a proposal, even though nothing enforces them.
- Put a photo on the spaces you sell hardest. The couple sees it on their review page, and your team sees it on the calendar.
Frequently Asked Questions
How many spaces can I have? As many as you like. Order matters more than count — reorder so the common ones sit at the top.
Does capacity stop me overbooking a room? No. It is recorded for reference; nothing blocks a larger guest count.
What happens to old weddings if I delete a space? They keep their data and lose the link. Nothing is deleted from the wedding.
Can couples see my space photos? Only on the review page after the wedding. Proposals and the Guest Guide do not show them.
Keep reading
Still stuck? A person reads every email.
If a guide and the app disagree, the app is right. Tell us and the guide gets fixed.