Travel & Tourism// definition

Enquiry-to-booking conversion: the metric that lies at six months

In short

Enquiry-to-booking conversion is only meaningful by cohort: take the enquiries that arrived in one month, follow that fixed set until it stops producing bookings, and divide. The ratio most operators report — bookings closed this month over enquiries received this month — mixes two unrelated populations, so it falls when volume rises.

Key takeaways

  • The denominator is a fixed set of enquiries that arrived in one month; it never grows or shrinks afterwards.
  • Bookings count against the month the enquiry arrived, never the month the booking closed.
  • The calendar-month ratio tracks your growth rate: it drops when enquiry volume rises, and jumps when volume collapses.
  • Report every cohort with its lag — a 4-month-old cohort is not comparable with a 12-month-old one.

Enquiry-to-booking conversion means one thing: of the enquiries that arrived in a given month, what share eventually became bookings. The denominator is fixed when the month closes and never changes. The numerator grows for as long as that cohort keeps closing, which in a tailor-made trip business is often 6 months or more.

The ratio most operators report is different: bookings closed this month over enquiries received this month. Those are unrelated populations. Almost none of this month's bookings came from this month's enquiries, so the number describes current volume against past volume, not how well anyone is selling.

Numerator and denominator, precisely

  • Denominator: qualified enquiries stamped with an arrival date inside the month. Fixed once the month closes. Spam, duplicates and enquiries for products you do not sell come out before it closes, never after.
  • Numerator: bookings from that same fixed set, counted whenever they close. A booking confirming 9 months later belongs to the month the enquiry arrived.
  • Neither side moves when a booking is later cancelled. Track cancellation separately — folding it in makes the metric change retrospectively, and nobody can reconcile a report printed last week.

The distortion, in one table

Here is the arithmetic, with round numbers chosen for legibility rather than to represent any real business. Every cohort converts identically: per 100 enquiries, 2 book in the arrival month, then 4, 5, 4, 3, 1 and 1 over the following 6 months. Each cohort ends at 20 per 100, a flat 20%, and nothing about sales performance changes anywhere in the table.

Only volume changes: 60 enquiries in January, then 80, 120, 160, 200, 240, and a collapse to 120 in July.

MonthEnquiries arrivingBookings closingCalendar-month ratioCohort rate
April1601710.9%20%
May2002311.3%20%
June2402912.2%20%
July1203327.8%20%
Same 20% cohort conversion in every row — only volume moves

June is the best month the business has had — 240 enquiries, 29 bookings closed — and reports 12.2%. July is the month the pipeline halved, and reports 27.8%, because July's bookings are mostly June's large cohort divided by July's small one. A manager watching the calendar ratio congratulates the team in the month the business started dying.

Three definitions the number depends on

A conversion rate is only as stable as the 3 terms underneath it, each written down before the first report runs.

  1. Qualified enquiry. One carrying enough to be worked: a destination, a dated window, a contactable person. Everything else is traffic. Apply the rule at arrival, because applying it later lets someone shrink a denominator after seeing the result.
  2. Quoted enquiry. One where a priced proposal reached the client. Quoted-to-booked is the consultant's number; enquiry-to-booked is the business's. Reporting one and calling it the other is how these figures get misread.
  3. Lost enquiry. A cohort member no longer a live prospect, under a rule that fires on its own rather than when someone tidies the pipeline.

Declaring an enquiry lost, on a rule rather than a mood

Without a cut-off a cohort never finishes: an 18-month-old enquiry books, the historic rate ticks up, and last year's reports quietly change. Two shapes are defensible — a fixed age since the last client-initiated contact, or a departure-window rule closing any enquiry whose dates have passed. Either way a lost enquiry that comes back is a new enquiry joining today's cohort, not a resurrection.

The other half is making booking state flow back to the enquiry record. Where it does not, the enquiry sits open in the report and open in the follow-up tooling, producing a wrong metric and the awkwardness in the chase sequence keeps emailing clients who booked.

Reporting a cohort that has not finished

You cannot wait 6 months to know anything, so report every cohort at a stated lag: this month at lag 0, last month at lag 1, and so on. Comparing April at lag 3 with January at lag 6 is the second most common error after the calendar ratio, and the one that makes recent months always look worse. Dates carry this hidden semantics throughout a trip business — the same trap where a day index is not a calendar date is in days are not dates in a trip model.

A cohort rate at lag 3 and one at lag 6 are different metrics with the same name. Label the lag or do not publish it.

Once cohorts are correct the breakdowns become worth having. Cohort rate by consultant separates skill from assignment, which every enquiry lands on the same consultant traces, and tells you whether the method in assigning enquiries by destination and load is working. None of it needs a warehouse: one enquiry table with an arrival date, a lag dimension and a view is a few days of product build work.

Two adjacent questions belong elsewhere: attributing a booking to a channel, and chase timing, which is derived from booking lead time rather than from this metric. Both sit in from enquiry to confirmed booking, with the rest of our travel and tourism work.

Frequently asked questions

Short answers to the follow-ups this page tends to raise.

What is a good enquiry-to-booking conversion rate for a tour operator?

There is no defensible external benchmark, because the number depends entirely on what you count as an enquiry. An operator counting every form fill and one counting only qualified briefs can differ by a factor of 5 while selling identically. The only useful comparison is your own cohorts at the same lag, with the qualification rule unchanged.

Should cancelled bookings be removed from the conversion rate?

No. Keep cancellation as a separate measure against the same cohort. Removing them makes conversion retrospectively mutable, so today's report disagrees with next month's copy of itself. What you want is 2 numbers against one cohort: the share that booked and the share that later cancelled.

How do we report conversion when a client enquires twice about the same trip?

Deduplicate into the earlier enquiry and keep the cohort of the first arrival. A second enquiry from someone already in the pipeline is a signal of interest, not a new opportunity, and counting it inflates the later month's denominator while the booking lands in the earlier cohort. Deduplicate before the month closes, on contact details rather than name and destination.

  • conversion
  • cohort reporting
  • sales metrics
  • enquiry data
// shipped work

The work behind this page

Builds from our portfolio that this page draws on.

Working on something in this space?

Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.

Start the conversation