A 220-room full-service hotel in Dallas held its largest ballroom for a pharmaceutical client’s regional meeting, tentative, for eleven weeks. No release date was set because the client was a good account and the director of sales expected it to firm. In week nine, a corporate group came in wanting the same dates with 180 room nights and a three-day meeting pattern, and the ballroom was unavailable. The hotel turned that group away. The pharmaceutical meeting canceled in week eleven, and the ballroom sat empty on the best three dates in the month.
That is a function space problem, not a guest room problem, and the two behave nothing alike. A guest room is one unit sold for one night at a rate. A ballroom is a flexible quantity of square footage that can be divided, combined, configured a dozen ways, and resold multiple times in a day, and it carries food, beverage, and audiovisual revenue that frequently exceeds the room rental itself.
Hotel function space management software exists because the property management system was built for the first problem and cannot represent the second. This covers how to measure space performance, how to hold and release it, how the banquet event order ties the hotel together, and what to do when a group wants both.
Because the inventory model is wrong in three ways at once.
First, the unit of sale is not a room, it is a room-time block. The same ballroom can be sold to a breakfast meeting, a lunch, and an evening reception on one day, which means the inventory is a calendar of occupancy windows rather than a nightly count.
Second, the space divides and combines. A ballroom with air walls might sell as one 6,000 square foot room, as three salons, or as two sections with the third held for a breakout. Booking one salon has to make the combined room unavailable, and a system that treats them as five independent rooms will double-sell within a month.
Third, the revenue is bundled. Space rental is often the smallest line on a group’s bill. Food and beverage, audiovisual, and service charges typically carry more revenue and more margin, and a space decision made on rental revenue alone will systematically accept the wrong business.
What the function space side needs that a property management system does not provide:
Most hotels solve this with a sales and catering system alongside the property management system, integrated so that group room blocks and function space live in the same account record while the inventory logic for each stays separate.
Not by occupancy, which is the trap. A ballroom that is busy every day at a low rate with no food and beverage attached is performing badly while looking excellent on a utilization report.
The measures that tell the truth:
Set a space-to-rooms discipline as well. A property with a large ballroom relative to its guest room count will have groups that want the space without filling the hotel, and those are legitimate business when priced accordingly. The error is pricing them as if the guest rooms were coming.
One further number worth tracking is turned-down business with the reason. Hotels record what they sold and rarely record what they declined and why. A quarter of lost opportunities attributed to space held on tentative is the exact finding that fixes the problem in the opening example.
Every tentative hold needs a release date set at the moment the hold is created. No exceptions, no good accounts, no “we will keep an eye on it.”
A workable status model runs: inquiry, tentative with a release date, definite with a signed contract and deposit, actualized after the event, and either lost or turned down with a reason code. The important mechanics sit around the tentative state.
How to run tentative holds properly:
That last mechanism is what hotels with disciplined space management use constantly and what hotels without it never deploy. When a second group wants held dates, the first group gets a short window to go definite or lose the space. It is a normal industry practice, clients understand it, and it converts stalled holds into either contracts or available inventory.
The cultural part is harder than the software part. A director of sales who releases space on a major account’s hold is making an uncomfortable call, and the only way that happens consistently is if the policy is the hotel’s rather than the individual’s.
Capacity is a function of configuration, and the system should hold a capacity figure per setup type per room rather than one number.
Rough planning allowances used across the industry: theater seating needs somewhere around 8 to 10 square feet per person, classroom setup roughly 15 to 18 because of the tables, banquet rounds around 10 to 12 per person, and reception standing considerably less. These are planning figures, and the governing number is always the occupant load your fire marshal has established for that room, which should be stored in the room record and treated as the ceiling.
Turn time is the operational constraint that sales teams underestimate. Striking a classroom setup and resetting the same room as banquet rounds with linens takes real labor hours, and a room sold at nine in the morning and again at noon in a different configuration may not be physically turnable. Build turn times per configuration change into the room record so the availability logic blocks what cannot be done rather than selling it and letting banquets discover the problem.
The underbooked space in most hotels is the awkward middle: rooms too large for a ten-person board meeting and too small for a hundred-person general session. Those rooms earn their keep as breakouts attached to a larger program, which means the sales approach is to sell the package rather than the room. A system that can show a planner the main room plus adjacent breakouts as a block is selling the building rather than its parts.

The banquet event order is the single document that tells the kitchen what to cook, banquets what to set, audiovisual what to install, and accounting what to bill. When it is wrong, every one of those departments is wrong in a way the client sees.
What a complete order carries: the client and account, the date and times including setup and strike, the room and configuration with a diagram, guest count guaranteed and set, every food and beverage item with timing, bar arrangements, audiovisual and technical requirements, linen and decor, signage, billing instructions and who has authority to sign, and the service charge and tax treatment.
Process discipline around the document matters as much as its contents:
Changes after the cutoff are the normal state of affairs with live events, so the system needs to handle them gracefully: a timestamped revision pushed to every department with the delta visible, rather than a new document that looks identical to the old one.
This is where the two inventories meet and where revenue management earns its salary. A group asking for 150 room nights and a ballroom is two decisions that have to be made as one.
Displacement analysis is the mechanism. The question is what the hotel would otherwise have earned from those rooms on those dates at expected transient demand, and whether the group’s total value exceeds it. On a high-demand weekend, a group at a discounted rate displacing transient business the hotel would have sold at full rate can be a loss even with substantial food and beverage attached. On a soft Tuesday it is almost always a gain.
What the contract has to pin down for the combined booking:
Attrition and cutoff are the clauses that protect the hotel and the ones most often left vague. A group that blocks 150 rooms, fills 90, and has no attrition obligation has cost the hotel 60 room nights it could have sold. The number should be negotiated, not omitted.
Service charge and gratuity treatment is worth a note too. The distinction between a mandatory service charge and a voluntary gratuity affects taxability and employee distribution, and the rules vary by state. Have your controller confirm the treatment rather than copying another property’s banquet contract.
Some business should be turned away, and a hotel without a framework for saying no takes it all and wonders why a busy quarter produced thin margins.
The patterns worth declining or repricing:
A group wanting the largest space on the highest-demand dates with minimal food and beverage and no guest rooms. This is pure displacement of better business, and the answer is either a rental rate that reflects the opportunity cost or a redirect to softer dates.
A single-day program that blocks space across a weekend because of setup requirements. Three days of inventory for one day of revenue only works at a price that accounts for all three.
A group whose room block pattern takes your peak nights and skips the shoulders, at a rate below what transient demand would have delivered. Negotiate the pattern or the rate.
Recurring business held at a rate set years ago, which quietly becomes the worst business in the building as the market moves. These accounts need an annual review, and the conversation goes better when you can show total revenue per group across comparable accounts.
Having those comparisons available is the practical case for running hotel function space management software properly, with status discipline, release dates, turned-down reasons, and revenue recorded by category. A property that can answer what each group was actually worth, and what it declined to take instead, prices the space well. A property that tracks only what it sold will keep accepting business that looks good on the booking report and poor on the profit and loss.
Service charge taxability, union labor rules, and occupancy limits vary by state and by local jurisdiction. Confirm the specifics with your controller, your legal counsel, and your fire marshal rather than relying on general guidance.
Reduce Your Fees, Upgrade Your Service, Guaranteed!
Your information will not be distributed
We received your request. A payments specialist will reach out shortly.