Same feature set, same brand, three genuinely different ways of working. Built against your own September BEO packet — real rooms, real sales team, real Chesapeake A/B conflict. Open each one, then tell us which way of working feels right and we take that one deep.
The availability timeline is the application. You open the day, you see what is free, you click a cell and a booking exists.
The hierarchy your team already knows — Booking → Events → Items — but on one scroll, editable in place, with no save button anywhere.
Opens on what needs you today. A pipeline you drag, a command bar that reaches everything, and call logging that never leaves the page.
These are not three different products. Every concept carries the same model underneath — the differences are entirely in how you move through it.
Chesapeake A+B blocks A and B. Booking A alone blocks A+B. Enforced at the data layer, not by a person remembering — so the Mahoney 50th never gets quoted a date that was already gone.
Accounts are typed Individual or Company. A bride is her own account with her fiancé, her mother and her planner as contacts — no 2026 RodNReel Weddings umbrella. You already do this correctly for the Miller Family; this makes it the rule.
Rebuilt field-for-field from BEO 5042: the header block, the event line table with Agr/Gtd/Set/Rental, the same seven sections in the same order, the red booking-type flag, and both approval lines.
Admins add fields at booking, event, item and account level. A new field appears on the record, in the filters, in reports and as a merge tag on the BEO and the contract — without a developer.
Calls in and out with notes and duration, emails, site visits, and the system's own audit rows — every field change, every BEO revision, every Sertifi event, on the account, the contact and the booking.
Shuttles and the charter fleet live on the same availability grid as the ballrooms. Two bookings wanting Shuttle 1 at 6:30 collide exactly like two bookings wanting Chesapeake A.
One row per thing your team does every day.
| The job | A · Space Grid | B · Record Desk | C · Sales Console |
|---|---|---|---|
| "Is the ballroom free Sept 19?" | It is the home screen. Scan the row. | Filter the bookings list by date and space. | ⌘K → type the room name. |
| Take a new enquiry on the phone | Click the free cell, four fields, done. | Three-step wizard: account, contacts, booking. | ⌘K → New booking, or approve the web request. |
| Log a sales call | From the account's activity timeline. | Log-a-call button on the booking or contact row. | Inline on the queue item — never leaves the page. |
| Build out a definite booking | Open the drawer, then the full booking page. | One long scroll, edit in place, sections collapse. | Composer view, all events stacked. |
| Move tentative → definite | Change status on the booking; grid re-colours. | Status chip on the record header. | Drag the card; it tells you what it will lock. |
| See what needs you today | Not the focus — read the week on the grid. | Saved views: contracts expiring, my bookings. | It is the home screen. |
The full sellable function-space list (we built from the rooms named on the September packet — Chesapeake A/B, Overlook, Atrium, Derby Suite, 4th Floor Conference, Lounge, 1936 Bar & Grill upper and lower, The Dock, Band Shell Beach, South Beach, the Chapter fleet and the shuttles), plus which rooms combine beyond A+B, and confirmation of the Sertifi account we integrate against.