Hotel technology

Sales and catering software: the function diary, options and banquet records in one place

This guide explains how sales and catering software holds the function diary, option dates and banquet event orders in one record. It shows how to test if a spreadsheet still works for your hotel.

  • 10 min read
  • AI Otel Editorial

AI draft · awaiting editorial review

Contents

Key takeaways

  1. A function diary is only useful if every entry carries a set-up, a turnaround time and a status, not just a client name in a cell.
  2. An option without an expiry date is a promise the hotel cannot keep; the system has to remind a person before the date passes.
  3. The banquet event order should be produced from the booking, so the kitchen, housekeeping and technical teams read one version of the event.
  4. The room block belongs in the same record as the event: release dates, pickup and the master folio are one commercial decision, not two.
  5. The test for whether a spreadsheet still works is spaces multiplied by events per week, not the size of the hotel.

Hotel sales and catering software keeps a hotel's event business in one place: a function diary of every space with its set-ups and turnaround time, tentative and definite bookings with option dates, banquet event orders produced from the booking, room blocks linked to the PMS, and deposit and final-number deadlines. It replaces the shared spreadsheet that double-books a ballroom.

Two sales managers, one ballroom, one Saturday in June. Both wrote the client's name into the shared sheet on the same afternoon, and neither cell said tentative. By the time the second client signed, the first had already printed invitations. This article explains what sales and catering software actually holds, how tentative bookings and option dates work, how a booking becomes a banquet event order and an event bill, and how to tell whether your hotel still gets away with a disciplined spreadsheet.

What does hotel sales and catering software do?

It holds every event space, every booking and every document the event produces in one record, so the diary, the contract, the banquet event order and the bill all describe the same event.

Sales and catering covers two halves of the same job. The commercial half runs from enquiry to quote, contract and deposit. The operational half runs from set-up to banquet event order, final numbers and the bill. One record carries both, which is the whole point: the person who sold the event and the people who run it work from the same facts.

The core objects are few. There are spaces, each with its capacities per set-up. There are bookings, each with a status and dates. And there is an event record holding times, menus, technical needs and billing instructions. Everything else is a view onto these three.

The difference from a calendar is what is stored. A calendar holds a name and a time; a diary holds what the room must become, how long that takes and who is responsible. The difference from the hotel management system (PMS) is the unit of sale. The PMS sells rooms by the night; the event business sells a space by the day-part, sometimes twice a day.

Several teams read the same record: sales, banqueting, kitchen, housekeeping, technical services and finance. Each needs a different view of one truth, not a copy of it. And note what the software does not do: it does not price for you. Package structure, day delegate rates and inclusions stay a commercial decision; the system stores the decision and applies it consistently. For how meeting packages are priced in the first place, see meeting packages: day delegate and residential pricing.

NoteTerms used in this article

Function diary: the calendar of spaces, not of people. Day-part: morning, afternoon or evening. Set-up: the physical arrangement of a room, such as theatre or banquet. Turnaround: the reset time between two events in the same space. Option date: the expiry date of a tentative hold.

Where does a shared spreadsheet fail?

A spreadsheet fails at the moment a second person writes to it, because it records a name but not a status, an expiry or a turnaround.

Two tentative entries land in the same cell block, and neither one expires, so the space is blocked twice and freed never. Status is invisible: tentative, definite, cancelled and lost look identical once the colour coding is lost on a printout or a forwarded copy. Turnaround is missing. A room used 09:00 to 12:00 and again 13:00 to 18:00 needs a reset in between; the sheet shows neither the reset nor the team that performs it.

The banquet event order is retyped in a word processor, so the kitchen's copy and the sales copy drift apart after the first change. Deadlines live in someone's inbox: option dates, deposit dates and the final guest count are remembered, not scheduled. And there is no history. After a dispute nobody can say who moved the date, when, or on whose instruction.

None of this is a criticism of the people. A spreadsheet is a symptom of volume crossing a threshold, and the threshold is measurable, which is why this article ends with a test rather than a verdict.

What belongs in the function diary?

Every space, every set-up that space can take, and the time needed to change between them.

The space record should carry what a planner asks on the phone: dimensions, ceiling height, natural light, door width, power, accessibility and the capacity per set-up. Set-up must be data, not a note in a cell. Once the diary knows the arrangement, capacity checks and turnaround times follow from it instead of from memory.

Turnaround is a property of the pair, not of the room. Banquet to theatre is a different reset from theatre to theatre, and the diary should hold both. Day-parts make a space sellable twice a day, but only when the turnaround fits between them. A morning and an evening event can share a room; two lunches cannot.

Divisible spaces need a lock. When the whole ballroom is sold, both halves must be unavailable, and the diary should enforce that rather than trust the sales manager to remember. Blackout time is part of the diary too: carpet cleaning, maintenance, an owner's annual gala. A space that is never blocked for upkeep will eventually be sold in a condition nobody wants.

For example, a diary might hold these four spaces:

SpaceTypical set-ups and capacitiesWhat the diary must hold
Ballroom A, divisibleTheatre 300, banquet 220, reception 350Half-room lock; 90-minute reset between banquet and theatre
Meeting room 1Boardroom 14, U-shape 12Fixed table; 30-minute reset
TerraceReception 120Weather-dependent; no wet-weather fallback recorded
Boardroom10No food service; bookable in two-hour blocks

How do tentative bookings, options and definite status work?

A booking moves through named states, and every state that holds a space carries a date, so the space is either held with a deadline or free.

The useful set is short: enquiry (no hold), tentative or option (held until a date), definite (contract and deposit in place), cancelled, lost and completed. The option date is the whole mechanism. A tentative booking without an expiry is a permanent block on the space and an invisible loss for the hotel.

The first reminder goes to the sales manager, not the client. Expiring options should surface every morning as a list, not as a surprise on the day. Expiry has a defined behaviour: the hold releases, the space returns to the diary, and the record stays for history so the enquiry can be reopened. A second enquiry on a held date is not a refusal. It is a waitlist entry, visible to the sales manager, who can then decide whether to chase the first client.

Conversion to definite should require the artefacts, not a click: a signed contract and a deposit date. Anything else is still an option with better manners.

Watch outVerbal holds and pencilled-in entries

An entry with no date, no owner and no status is not a booking, it is a hope, and it will cost the hotel a Saturday in high season. If the client will not accept an expiry date, the space is not held, it is hostage.

How does a booking become a banquet event order and an event bill?

The event is written once, and the banquet event order and the bill are produced from that record, so a change made in one place reaches the kitchen and the invoice.

The banquet event order is the operational instruction: times, room, set-up, menu, dietary notes, technical needs, billing instructions and the contact on the day. Every issue needs a number and a timestamp. The kitchen works from the latest issue, and superseded copies are visibly dead rather than quietly different. Distribution is part of the design: kitchen, banqueting staff, housekeeping, technical services, front desk and finance each receive what they need, not the whole document.

A changed guest count or menu must re-issue the order. A change whispered at the pass is how a kitchen prepares for the wrong number. Final numbers are a deadline, not a courtesy: the contract states the guaranteed count and the date it is due, and the bill uses the greater of the guarantee and the number actually served.

The event bill settles to a master account, with the deposit applied and any individual extras on separate folios. Corrections are voided and reversed, never deleted, so the money story can always be reconstructed. The banquet event order itself deserves its own read; see banquet event order: the one document that runs a hotel meeting or wedding.

How do room blocks and the PMS stay in step?

The event and the room block are one commercial deal, so the diary must show the block, its release dates and its pickup without anyone entering it twice.

A block is rooms held per night and per room type, with a rate and a cut-off date. Without the cut-off, the hotel holds inventory it can no longer sell. Pickup is the number of rooms actually taken from the block. The difference between the block and the pickup is what returns to general sale, and it should be a report, not a guess.

Staged release belongs in the contract and in the system: for example, half the unused rooms released thirty days out, the rest two weeks later, applied automatically. The classic mismatch is two numbers in two places: the diary says eighty rooms, the PMS shows sixty-two sold. The pickup report is the reconciliation, and it needs one owner.

The master folio keeps the group's charges together, room, meeting room and food and beverage, while individual guests settle their own extras on departure. Payment terms travel with the block: deposit dates, cancellation windows and release schedules are the same facts on the sales side and the finance side. For the group side in depth, see hotel group bookings: block, rooming list and master folio, and for congress business, congress groups and PCOs: room blocks, release schedules and payment terms.

When is a spreadsheet still enough?

A spreadsheet is enough while one person owns it, the spaces are few and no two events need the same room in the same day-part.

The test is arithmetic, not prestige: count the distinct spaces and the events per week. If one person can hold the whole diary in their head and no space is sold twice in a day, a disciplined sheet works. Discipline has conditions: one owner, one file, a status column with dates, a weekly review of expiring options, and a banquet event order template with version numbers.

The signals to move are specific: a second person writing to the file, a divisible ballroom, more than a handful of live tentative holds, deposit tracking living in email, a near-miss double booking. The cost of waiting is not the double booking itself. It is the client who books elsewhere after the apology, and the referral that never happens. Buying software before the discipline exists only moves the chaos. Write the fields down first, then look for a system that holds them.

ChecklistYou can stay on a spreadsheet if all of these hold

  • One named owner of the file
  • Every row has a status and a date
  • No space is divisible
  • Fewer than roughly ten live holds at any time
  • The banquet event order template is versioned and printed from the same file

ChecklistMove to a system when any of these appear

  • A second person needs to write to the diary
  • A tentative hold has no expiry date
  • You cannot answer "what is free on 14 June" in under a minute
  • Deposits are tracked in an inbox

What to do next

Before comparing any system, write down your spaces, the set-ups each one takes and the reset time between them, then count events per week and live tentative holds. That list is the specification: it tells you whether a disciplined spreadsheet still serves you, and if it does not, it tells you exactly which fields the diary must hold before you look at software.

Frequently asked questions

What is the difference between a function diary and a hotel PMS?

The PMS sells rooms by the night and runs the guest bill. The function diary sells event spaces by the day-part, with set-ups and turnaround. They meet at the group room block, which is why the block, its release dates and its pickup should be visible on both sides.

What is an option date in hotel event sales?

It is the date on which a tentative hold expires and the space returns to sale. Without it a hold is permanent and invisible. The system should list expiring options every morning so the sales manager, not the client, acts first.

What is a banquet event order and who writes it?

It is the operational instruction for one event: times, room, set-up, menu, dietary notes, technical needs and billing instructions. It should be produced from the booking record rather than retyped, and every issue should carry a number and a timestamp so the kitchen knows which copy is current.

Can a small hotel run events without sales and catering software?

Yes, under conditions: one owner of the file, a status column with dates, no divisible space, few live holds, and a versioned banquet event order template. The test is spaces multiplied by events per week, not the size or star rating of the hotel.

Who needs access to the function diary?

Sales and banqueting need to write. Kitchen, housekeeping, technical services, front desk and finance need to read the parts that concern them, usually through the banquet event order rather than the whole diary. Access should follow the task, and changes to a confirmed booking should be attributable to a person.

AI Otel EditorialEditorial team

Drafted with AI assistance from AI Otel’s published fact base. Not yet reviewed by an editor.

We can brief you on this topic.

If this topic touches your work, we can walk you through what is built and what is designed.

Request a briefing