Key takeaways
- Every enquiry gets a stage, an owner and a next action date. If one of those is missing, the lead will be forgotten.
- Six stages are enough for most venues: new, qualified, quoted, provisional, confirmed and closed.
- A shared spreadsheet works up to a few dozen live leads; beyond that, or with several people quoting, a CRM pays for itself in time saved.
- Event leads are personal data. Collect what you need, protect access and only market to people where PECR allows.
Why event enquiries go missing
Most venues do not lose event business because the quote is too high. They lose it because nobody replied, the follow-up was forgotten or two people quoted different prices. Enquiries arrive by phone, email, the website, social media messages and in person at the bar, and they often land with whoever happens to be on shift. Without one place to record them, the events lead only sees part of the picture.
A simple CRM, which can be a well-organised spreadsheet, fixes that. It gives every enquiry a home, a status and a person responsible for the next step. It also gives you the numbers you need to know where bookings come from and which ones you lose.
Define the stages
Keep the pipeline short and give each stage a clear test for moving on. If staff cannot tell which stage a lead is in, the stages are too vague.
| Stage | What it means | Moves on when | Next action |
|---|---|---|---|
| New | Enquiry received, not yet contacted | You have spoken to or emailed the organiser | Reply the same day |
| Qualified | Date, numbers, budget and occasion confirmed | A quote is sent | Send the quote within one working day |
| Quoted | Written quote with package and terms sent | The organiser asks to hold the date | Follow up after three days |
| Provisional | Date held without payment | Deposit received | Release the hold if no deposit by the agreed date |
| Confirmed | Deposit paid, terms accepted | The event takes place | Final numbers and planning call |
| Closed | Won and delivered, or lost | Feedback recorded | Rebooking offer or lost reason logged |
Resist the temptation to add stages such as 'menu tasting booked' or 'awaiting final numbers'. Those are tasks inside the confirmed stage, and they belong in the event file or the run sheet. The pipeline should answer one question at a glance: where is each piece of potential business, and who is moving it forward? If you run several rooms or sites, add a column for the space rather than separate pipelines, so the events lead sees every enquiry in one view and can spot clashes before they happen.
Capture the right fields
Record enough to quote and follow up, and no more. Each field should earn its place.
- Organiser name, phone and email, and the company if it is a work event.
- Source: phone, website form, walk-in, venue finder site, social media, referral or repeat client.
- Event date, a second-choice date, start and finish times.
- Provisional numbers and the occasion.
- Room or space requested and the package quoted.
- Estimated value: minimum spend or per-head price times numbers.
- Owner: the person responsible for the next step.
- Next action and its date.
- Lost reason if it does not go ahead: price, date unavailable, no reply, chose another venue, cancelled.
Keep allergy and dietary details in the event file, not in the main CRM list, and only when an event is confirmed. They are health information about guests and should be visible to fewer people.
Set follow-up rules everyone follows
Reply within hours
New enquiries get a reply the same working day. The first useful response often wins the booking.
Never leave a blank date
Every live lead has a next action date. Sort the sheet by that column every morning.
Release holds on time
Provisional dates without a deposit are released on the agreed day, with a polite message. Held dates block other bookings.
Two follow-ups, then close
After a quote, follow up twice, a few days apart, then mark the lead lost with a reason.
Log every contact
A short note with the date: 'Called, asked for vegan menu, sending revised quote Thurs.' Anyone can pick up where you left off.
Read the numbers once a week
A weekly ten-minute review keeps the pipeline honest. Look at these figures:
- New enquiries this week, by source.
- Leads with no next action or an overdue date.
- Quotes sent and quotes won.
- Value of confirmed events for the next eight weeks.
- Lost reasons over the last month.
Example: a pub with a function room logs 40 enquiries in October. 30 are qualified, 24 receive quotes and 9 book. That is a 23% conversion from enquiry to booking and 38% from quote to booking. Lost reasons show 8 of the lost quotes never replied to a follow-up, so the pub adds a phone call before marking a quote lost.
Lost reasons are often the most valuable column. If many leads are lost on price for the same night, your minimum spend may be set too high for that slot. If many are lost for no reply, look at how quickly you respond. Compare large buyouts separately, using the method in full venue buyouts.
Turn the pipeline into a forecast
Once each lead has an estimated value and a stage, the sheet can tell you what the next two months look like. Give each stage a rough probability based on your own history, then multiply. A simple version is enough to plan rotas and food orders.
- Confirmed events: count the full value. These are your banked revenue.
- Provisional holds: count a share based on how often holds turn into deposits for you.
- Quoted leads: count a smaller share, based on your quote-to-booking rate.
- New and qualified leads: leave them out of the forecast until a quote is sent.
Look at the forecast by week. A quiet fortnight six weeks out is a prompt to contact past clients or local businesses now, while there is still time to fill it. A crowded week tells you to check staffing and room allocation early.
Handovers between shifts
Events leads rarely work every day, so the pipeline has to survive days off. Agree three habits. First, anyone who takes an enquiry enters it in the sheet before the end of their shift, even if it is just a name, number and date. Second, the events lead checks new entries at the start of each working day and assigns an owner. Third, nobody quotes a price that is not on the current package sheet; they promise a written quote instead. These habits stop the most common failure, which is a phone enquiry taken on a busy Saturday that nobody follows up until the client has booked elsewhere.
Mistakes to avoid
- Too many stages or fields, so the team stops updating the sheet.
- Leads with no owner, or owned by someone who has left.
- Holding dates without deposits for weeks, blocking paying bookings.
- Deleting lost leads instead of recording why they were lost.
- Copying contact lists into personal phones or spreadsheets outside the shared system.
Spreadsheet or CRM?
Start with what you will actually use. Free and low-cost software is how most hospitality businesses adopt new tools[1], and a shared spreadsheet is a sound first step.
| Option | Works well when | Watch out for |
|---|---|---|
| Shared spreadsheet | One or two people quote and there are fewer than about 40 live leads | Version clashes, no reminders, easy to share too widely |
| Booking system events module | Your table booking system has one and the team already uses it | Limited reporting, may not suit multi-room events |
| Dedicated CRM | Several people quote, you run several spaces or venues, or you want automatic reminders | Set-up time and keeping it updated |
Whatever you choose, make the phone part of it. Calls are where many event enquiries start, and they are the easiest to lose during service. Ava can answer those calls, capture the organiser's details, date and numbers, and log each call so it can be added to the pipeline.
Keep the data safe and lawful
Event leads are personal data, so the usual data protection principles apply: collect what you need, keep it accurate, keep it secure and delete it when it is no longer needed. Hospitality is a target for cyber attacks, though it is often less prepared than other sectors. In 2025, 30% of food or hospitality businesses identified a cyber breach or attack in the last 12 months, compared with 43% of businesses overall[2], and only 25% had sought external cyber security guidance, against 42% overall[3].
- Use individual logins for the CRM or shared drive, not one shared password, and remove access when staff leave.
- Turn on two-step verification for email and the CRM.
- Do not paste guest lists or allergy details into messaging groups.
- Set a retention period, for example deleting lost leads after a set number of months.
Marketing needs care too. Marketing emails and texts to individuals need their prior consent[4], although the soft opt-in lets you market similar services to people whose details you obtained during a sale or negotiation, as long as they were given a chance to opt out[5]. Record how and when each contact agreed, so your rebooking offers go only to people who can receive them.
Frequently asked questions
What is the best CRM for a restaurant events team?
The best one is the one your team will keep up to date. A shared spreadsheet works for one or two people and a few dozen live leads; a booking system events module or a dedicated CRM makes sense when several people quote or you run several spaces.
What stages should an event enquiry pipeline have?
Six usually cover it: new, qualified, quoted, provisional, confirmed and closed. Each stage needs a clear test for moving on and a next action with a date.
How long should we keep event enquiry data?
Only as long as you need it. Set a retention period for lost leads and past events, keep financial records for as long as tax rules require, and delete or anonymise the rest.
Can we email past event organisers with offers?
Usually yes under the soft opt-in, if you collected their details during a booking or negotiation, the offer is for similar services and they were given a simple way to opt out at the time and in every message.
References
Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑