ONEOS

Guide · Running the hotel

How to run weddings and conferences without double handling

By the ONEOS team7 min read

Answer in brief

You run weddings and conferences without double handling by keeping the enquiry, the function space, the bedrooms, the menus and the bill as one booking from first call to final payment. Double handling starts when sales works in a spreadsheet and operations works in the PMS, so every detail is typed twice and every change risks being missed.

Every change is typed twice

Events are some of the most valuable business a hotel takes, and some of the most fragile. A conference or a wedding touches sales, the front office, the kitchen, the banqueting team, housekeeping and finance, often over months. The details change constantly: numbers move, a dietary list arrives, the couple swaps the canapés, the company adds a breakout room.

In many hotels the sales office keeps the event in its own file and the rest of the hotel runs on the PMS. So the bedroom block is keyed once in sales and again at the desk, the menu is agreed by email and retyped onto the function sheet, and the final bill is assembled by hand from both. Each retyping is a chance for the versions to drift apart. Good coordinators hold it together through sheer attention, but that attention is the scarcest resource in the building on a wedding weekend.

How double handling shows up

A wedding enquiry comes in for a June Saturday. The ballroom is held provisionally while the couple decides. Three weeks later a conference asks for the same date and is turned away, because the hold is still sitting in the diary with no deposit and no follow-up. The wedding never confirms.

Meanwhile a confirmed conference grows from eighty to a hundred and ten delegates. Sales updates the contract, but the bedroom block in the PMS still shows the old number, and the kitchen's function sheet was printed before the change. On the day, the team solves it with goodwill and overtime, and the bill takes a week to settle. Nobody made a big mistake. The versions simply drifted apart, one small change at a time, until the day itself exposed them.

  • Provisional holds that block space long after they should have lapsed
  • Bedroom blocks that do not match the contract
  • Function sheets printed from an out-of-date version
  • Final bills assembled by hand from several sources

How to run events from one booking

Whatever system you use, the principle is the same: one live record that every department reads from, and clear rules that keep the diary honest. These steps help. The aim is for a change made once to reach everyone who needs it, without a second person retyping it.

  • Give every provisional hold an expiry date and release it automatically if it lapses.
  • Build quotes from your own packages so prices and inclusions stay consistent.
  • Ask for the deposit at confirmation and chase it on a schedule, not from memory.
  • Block the bedrooms and open the bill in the same step as confirming the event.
  • Send every department the same run sheet, and resend it when anything changes.
  • Track which enquiries tend to convert so sales time goes to the right ones.

What good looks like

When events run from one booking, the sales office and the operation stop working from different versions. The diary shows what is truly sold, the kitchen cooks for the right numbers, and the bill is ready when the last guest leaves. It also changes the sales conversation. A coordinator who can see real availability, quote from agreed packages and confirm in one step can reply to an enquiry the same day, which is often what wins the booking in the first place.

  • The diary shows held and sold space clearly, and holds let go on time
  • Confirming an event blocks bedrooms and opens the bill together
  • Every department works from the same, current run sheet
  • Deposits are requested and tracked without manual reminders
  • The final bill needs no assembly after the event
How ONEOS handles this

ONEOS Events keeps the enquiry, space, bedrooms and bill as one booking on one source of truth, with holds that release themselves and ticketed events built in. It is an add-on at around $1 a room a month.

See Events →

Key takeaways

  • Double handling comes from sales and operations keeping separate records.
  • Provisional holds need expiry dates, or they cost you real business.
  • Confirm once and let the bedrooms, bill and run sheet follow.

Questions

How long should a hotel hold function space without a deposit?

Long enough for a serious client to decide, and no longer. Many hotels use a short option period, with a clear date by which a deposit or signed contract is needed. When the date passes, release the space or ask the client to confirm. An open-ended hold is the most expensive booking in the diary.

Should event bedrooms be booked as a block or individually?

Usually as a block first, with a release date, then converted to named reservations as the organiser sends the rooming list. The key is that the block lives in the same system as the rest of your inventory, so it reduces availability everywhere and does not get sold twice.

Who should own the function sheet?

The events or banqueting coordinator should own it, but every department should read the same live version. The problems start when the sheet is printed and circulated, then changed. Keep one current version, and make sure any change reaches the kitchen, housekeeping and front office at the same time.

See Events running on your property.

A short walkthrough on your own property’s data, with no slides and no pressure.