Events and function spaces

Who this is for: Owner, Manager — reading the pipeline needs pos.event.read; moving an event along it needs pos.event.manage, and placing a hold on a space needs pos.space.hold. Where: Point of Sale → Events & Spaces

A function space is a room you let rather than sleep in: a ballroom, a meeting room, a terrace. An event is one piece of business that occupies one or more of them — a wedding, a conference, a board day.

The screen is a pipeline board with the function spaces listed underneath it. Each column is a stage, and an event moves left to right.

The pipeline, and the rooms it is competing for. A card's column is the commercial state; the hold underneath it is what actually stops somebody else selling the room.

How an event moves#

Stage	What it means	What it does to the space
Enquiry	Somebody has asked. Nothing is promised.	Nothing, until you place a hold
Option	The space is being held, with a deadline	Holds it. The deadline is real — see below
Confirmed	Contracted. A master account is opened for it	Holds it, with no deadline
Executed	It has happened	Holds it
Closed	Billed and finished	—

Two more stages exist off to the side: lost and cancelled. An event can only move along the edges of that path — nothing jumps from enquiry to executed, so a sale cannot be recorded as delivered without having been sold.

Start an enquiry#

1. Select New enquiry.
2. Name it as your team will look for it — the host's name, the company, the occasion.
3. Select Create.

The card lands in enquiry. Nothing is held yet: at this point the event is a note, and the ballroom is still sellable to whoever asks next.

Create a function space#

1. Select New space.
2. Name it.
3. Select Create.

Spaces are listed as tags under the board rather than as a table, because at this size the useful question is "do we have one called that" rather than "what are its dimensions".

Divisible rooms#

A space can be a part of another — Ballroom A and Ballroom B inside the Grand Ballroom — and when it is, holds compose in both directions: letting the whole ballroom makes both halves unavailable, and letting one half makes the whole unavailable. You do not have to remember to block the parent.

This is set up when the space is created rather than from this screen, so a house with divisible rooms should expect to model them once, deliberately, rather than as it goes.

Confirm an event#

1. Find the card in enquiry or option.
2. Select Confirm.

Confirming does three things at once: every option hold on the event is promoted to a confirmed hold and stops expiring, the card moves to confirmed, and — if the event has bedrooms attached as a group booking — a master account is opened for it.

That master account is the destination the rest of the module bills into. A bar tab settled to Master account (event) at the terminal, and the catering itself, both land there, and the whole thing is billed once as a receivable rather than as a stack of dockets. See receivables.

Ghi chú

An event with no group booking attached confirms without a master account, because there is nothing for the account to hang off. Nothing warns you; the symptom appears later, when a settle to the master account is refused. If the event will carry bedrooms, attach the group before you confirm.

How a hold works — and why it cannot be double-sold#

This is the model shared by function spaces and by the scheduler, so it is worth reading once.

A hold is a resource plus a span of time. The resource is a ballroom here and a therapist or a treatment room there; the span runs from the start of setup to the end of teardown, not from the start of the party. And the rule is enforced in the database itself, as a constraint on the table, rather than by a check the application runs before it writes:

two holds on the same resource cannot overlap. Not "should not" — cannot.

Two consequences follow, and both are the point:

• A race cannot corrupt anything. Two people confirming the same ballroom for the same afternoon at the same instant do not produce a double booking. One of them wins; the other is refused cleanly and can go and find another room.
• There is no repair procedure, because there is no state to repair. You will not find an overlapping pair to untangle, so nothing in this section offers a tool for untangling one.

An option that lapses releases its space#

An option hold carries an expiry, which the card shows as a badge. When a lapsed option is swept, its holds are dropped and the event goes back to enquiry — the card moves back a column and the room is sellable again, without anyone deciding to release it.

Quan trọng

Nothing runs that sweep on a timer today. The release is an operation somebody invokes, not a clock. So a passed expiry date on a card means "this option is no longer being honoured", not "this room has already been released" — the hold is still sitting on the space until the sweep runs, and until then the room reads as unavailable to everybody else.

Read the badge as a diary entry to act on, and expect to sweep deliberately — at the end of the week, or as part of the night's routine — rather than assuming lapsed options have already cleared themselves.

What this screen does not do#

The pipeline and the spaces are here; several things behind them are not:

• No calendar. There is no spaces × time grid on this screen — the holds exist, and the board does not draw them.
• No hold controls. Placing and releasing holds, and setting an option's expiry, are not done from here.
• No banquet event order. The BEO — the run sheet and the priced catering lines that are the billing basis for the event — is versioned in Nerve and is not authored from this screen.
• No setup styles or capacities. A space carries theatre/banquet/cabaret capacities; the tag list does not show them.

So today this screen is where you read the pipeline and move an event along it, not where you plan the event.

What's next#

• The resource scheduler — the same hold model, applied to people and treatment rooms.
• The terminal — settling a bar tab to an event's master account.
• Settlement and close — where an event's takings land in the day.