From enquiry to deposit: how a wedding venue's booking flow works

A wedding venue's coordinator does not manage weddings for most of the week; they manage enquiries. Each one is a couple with a date in mind, a rough number of guests, a budget they may or may not share, and a list of other venues they are also talking to. The venue's job is to move the couple from "interested" to "confirmed" without over-promising a date that someone else is about to confirm, and without losing a good couple to a slow reply. The flow below is common to most venues; the rules inside each step are where venues differ, and where any software scope has to start.

Step one: the enquiry

Enquiries arrive from the venue's own website form, from wedding directories and listing sites, by telephone and through social media messages. Each one carries some of the same facts: names, a preferred date or season, an approximate guest count for the ceremony and the evening, whether the ceremony itself is to be held at the venue, and a contact preference. A directory enquiry often arrives with less than that and a note that the couple has sent the same message to several venues.

The coordinator's first task is to get every enquiry into one place with the same fields, whatever channel it came through, and to check the date. A date that is already confirmed produces a reply offering alternatives. A date that is free, or held provisionally by someone else, produces a reply with the brochure, the next steps and an invitation to view. The speed and consistency of this reply is the first place venues compete, and it is why the enquiry record needs the date status visible on it at a glance.

Step two: the viewing

Most couples want to see the venue before they commit. The viewing is an appointment with its own diary: the coordinator or a member of the events team, a slot that does not clash with an event or another viewing, and sometimes a second visit with parents. During the viewing the coordinator learns what the couple actually wants (ceremony in the garden, dinner in the barn, a band in the evening) and notes it against the enquiry, because those details become the proposal.

After the viewing the venue typically offers a provisional hold on the date. This is the most important rule in the whole flow, and venues set it differently. Some hold for a fixed number of days. Some hold indefinitely until another couple asks for the date, at which point the first couple is given a short period to confirm or release. Some do not hold at all and confirm only on deposit. The rule is a business decision, and the software must apply whichever rule the venue has chosen, including the notification to the first couple when a second asks.

Step three: the proposal

The proposal turns the conversation into a document: the date, the spaces being used and when, the guest numbers it is based on, the package or the itemised elements (room hire, ceremony fee, catering per head where the venue caters, bar arrangements, accommodation), any minimum spend or minimum numbers, the terms, and the deposit required to confirm. Where the venue uses an outside caterer, the catering element is either a separate proposal from the caterer or a line the venue passes through, and the proposal says which.

Proposals are revised. Guest numbers move, the couple asks about a different package, a parent wants the ceremony elsewhere. Each revision replaces the last, and the venue needs to know which version the couple has seen and which one they eventually accept. A proposal that was sent and then changed is a dispute waiting to happen if both versions are in circulation and nobody can say which was agreed.

Step four: acceptance, the deposit and the confirmed date

The couple accepts the proposal and pays the deposit. At that moment three things happen at once: the provisional hold becomes a confirmed booking, the date is closed to every other enquiry, and the venue's own obligations begin (the contract, the planning timeline, the payment schedule). Many venues require the signed terms and the deposit together; some accept the deposit as acceptance of the terms sent with the proposal. Either way the record should show the proposal version accepted, who accepted it, when, and the deposit received against it.

The deposit is also the point at which the venue's financial calendar starts: a second payment at a set point before the wedding, final numbers and the balance a set number of weeks before the day, and any damage deposit or bar float. These dates are calculated from the wedding date and the venue's own schedule, and they generate the reminders the coordinator would otherwise keep in a spreadsheet.

The states an enquiry moves through

Where catering fits

Venues split three ways on catering. Some cater in-house, in which case the proposal carries the menu choices and per-head numbers and the kitchen needs final numbers and dietary requirements by a set date. Some have a list of approved caterers, and the couple contracts with the caterer separately while the venue needs to know who it is and what access they need. Some are dry hire, and catering is entirely the couple's affair. The booking flow is the same, but what the venue's record holds about catering is different in each case, and the proposal has to say clearly which elements are the venue's and which are not.

For the caterer, the same wedding is an enquiry of its own, with its own flow from enquiry to tasting to deposit, and its own dependency on the venue's final numbers date. The catering software service and the catering enquiry package describe that side; the venue's and the caterer's records meet at final numbers and dietary requirements, which is where a connection between them earns its place if both use software.

The rules that software has to carry

Scoping a venue system is mostly a matter of writing down the rules that sit inside each state. The hold rule: how long, what triggers a release, who is notified. The viewing rule: which slots, who hosts, how many viewings on an event day. The proposal rule: what is in the package, what is itemised, how long a proposal stands, what a revision does to the hold. The deposit rule: how much, whether it confirms on its own or with signed terms, what is refundable and when. The payment schedule: which dates are calculated from the wedding date and what reminders go out. The numbers rule: when final numbers are due and what happens if they fall below the minimum. Each venue has its own answer, and most have never written them down, because the coordinator knows them.

The consequence is that the first week of discovery for a venue system is a conversation with the coordinator, not a demonstration of screens. Once the rules are written, the screens follow: an enquiry list with date status, a viewing diary, a hold board for the year, a proposal builder with versions, and a payment schedule per booking. The wedding venue booking systems service and the wedding venue package are built around those five views and the rules behind them.

A labelled example

If your venue's flow matches this, the rules inside each state are what make yours different. Describe how you hold dates and take deposits and ask for a proposal; discovery starts from those rules.