The room types this property sells. The three below are the GM’s own, read off his room bookings. Another property replaces them outright.

Everything a quote charges that is not a venue, a room or a menu — the liquor licence and bar counter, the Extras tab’s list, corkage and the hall-surcharge rounding step. Sports and their equipment have their own tab. Where it is used decides which screen a row appears on. An empty price reads “not set” on the quote, never ₹0.

Which activities raise a notification on the booking’s Overview by themselves. Every typed message is a notification already; these are the ones the system adds when something happens — a payment, a quote, a stage. Switch each on or off, say who it is for and how urgent it is. A raised notification never carries an amount.

The decision tree — each stage’s Next steps. For every stage: its own notification (too long in the stage, at a priority — management can silence it for one booking), and each row — the button’s words, what the tile says after the press, where it goes (a stage, the same stage, Reject / Cancel, or a tab) and the timer that then runs. When the timer runs out without a next press, its to-do goes to that department at that priority. A quote or a payment logged on Billing is a row too. Every press asks first and is logged on the booking’s Activity; Undo last step on the Stages list reverses it.

Watchers — not tied to a button. Each rule is on or off, is for one or more departments or for everyone, and has the numbers it works from — days at a stage, hours to reply, the share of the quote that counts as paid. The starting numbers are estimates: change them here and the list follows. A rule’s weight multiplies its place in the order (1 is normal, 2 is twice as pressing).

How the list is ordered and shown. Each to-do scores its points — days overdue plus how soon the event is — lifted a little for a bigger quote and multiplied by its rule’s weight; the highest comes first. A rule weighted at or above the “Important” setting can turn red and cannot be put off with Later. The Later choices, how many items show before “Show all”, and the Dashboard’s look-ahead are here too. Saved with the rules above.

Why a booking was cancelled — the reasons the cancel box offers. A picked reason can be counted later; a typed one cannot. “Other” still lets the person type. The list is a proposal from how venues track lost business; edit it to Firefox’s own words.

How a payment is made — the modes Billing offers. Every mode counts towards what has been received.

The rulebook — payments and tax. Each rule in plain words, with the settings it reads as they stand today and the places in the app that ask it. The numbers are edited in the table below; what a rule does is changed by talking it through with Claude.

The settings. One row per value. A row for an event type overrides the “Everything else” row for bookings of that type; the “Everything else” row always stays. A value outside its range is refused.

Event types. The kinds of event the enquiry form offers, and what a setting can apply to.

What each department checks before and during an event. Every confirmed booking’s Pre-event and Event tabs are built from these rows: an item is ticked once for the booking, or once for every event day, function or meal, and only when it applies. “Days before” sets when a pre-event item is due — the starting numbers are estimates. “Client signs” asks the client to sign on the screen. “From” says whose item it is.

Every vendor the resort has worked with, across all bookings. A vendor is added here, or from a booking’s Event preparation tab when it is first used. Bookings counts the events it was on, Last event is the latest, and Reliability tallies how it was rated on each booking.

The kinds of vendor. Decorators, outside caterers, car services, ironing services — the list a vendor is filed under.

The services this system runs on, what each one costs and where its ceiling is. Measured figures are collected every six hours (Apps Script, Slack, the API key) and the Google Cloud cost arrives from the budget itself about every forty minutes. A row with no figure has nothing that can be measured — the ceiling is still worth knowing. Amber at the warning threshold, red at the limit.