Before the planner presses send, the group form has already ticked copy to every site.
That tick is how a group produces two quotes for one Saturday. A shared alias does not stop it, because each site still writes its own answer. What the group owes, before anyone types, is a named owner and a calendar every site can already read.
A group that answers twice, or answers late because the file had no owner, loses the date before the visit. Organizers already look at several addresses for the same brief.
The Saturday that already has two owners
A planner looking for 80 seated in Manchester writes to the loft she found on Maps, then fills the group form. Two people open a file, with two deposits and sometimes two cancellation rules. The planner is comparing suppliers. She thinks she wrote to one group.
When both files become confirmations, the problem leaves the office. For a consumer booking, a wedding or a private dinner, the Consumer Rights Act treats every contract to supply a service as including a term that the trader must perform the service with reasonable care and skill. Confirming a loft already given to someone else is not that. A corporate off-site sits under ordinary contract. Two signed quotes are still two promises, and when one of them breaks, that is the expensive version of a double booking.
The same Saturday also breaks the client file. If Manchester and the city-centre brand are separate companies and they pool planner names in one tool, that is sharing between controllers. The ICO data sharing code covers the sharing of personal data between organisations that are controllers. Moving data inside one legal entity is not sharing. Pooling across companies is. If they jointly decide why and how that shared file is used, they are joint controllers and need a transparent arrangement, with the main points available to the individual.
Each site still keeps its own sheet. To know how many inquiries the group has open, someone phones every manager. The number is stale by morning. That is the point where a spreadsheet stops keeping up with the team.
The hour that owns the file
Routing is two fields on the file: who owns it, and by when.
The public teaser of Harvard Business Review's The Short Life of Online Sales Leads is blunt: most companies are not responding nearly fast enough. The house rule is simpler than a two-hour slogan. Acknowledge inside an hour while the desk is open. A proposal, or a clear next step, inside 24 hours. Name a deputy when the owner is walking a site. The older note on answering inquiries still applies; the clock is one hour, then the next day, not a two-hour house myth.
Write the criteria down: city, capacity, date and type of brief, then whether the client is already known and whether a framework account applies.
- A named city goes to the site in that city. Two venues there: capacity decides.
- Each site declares a comfortable range and a hard limit. The inquiry goes where the headcount sits in the comfortable range.
- A hold or a confirmation on the date moves the file to the second site in the area before anyone writes.
- A wedding, a residential retreat and a product launch do not belong in the same room. Each site lists what it accepts.
- A planner already in the file goes back to the last site, unless the city changes.
- A framework account stays with the central desk, even when the event is on a site.
- Anything that fits no rule goes to a named person. Never to an alias with no owner.
The hybrid model adds one step: routing. That step has to fit inside the same working hour. The site should receive a file with the date already checked and the client already identified. When routing slips, it adds a day. Measure the routing time the same way you measure the reply. Who does the routing is a sales-team decision, not a software setting.
Three desks, one calendar
Autonomous sites work when venues are few, far apart and different. Answers are fast and local, but nobody arbitrates, nobody proposes another site, and management flies blind.
A single commercial desk gives a consistent answer and a complete view. It also sits further from the floor. In peak months the desk saturates. Hybrid keeps one intake and written rules, then hands the proposal to the site. The desk does not write quotes. It qualifies, routes, settles collisions, consolidates. That is the usual shape between five and thirty venues. It only holds if someone wrote who does what.
| Setup | What the site still does | What the centre does | Fits when |
|---|---|---|---|
| Each site alone | Receives, prices, follows | Almost nothing | 2 to 4 venues, far apart |
| One commercial desk | Runs the event day | Qualifies, prices, confirms | 3 to 10 similar venues |
| Hybrid | Writes the proposal | Intake, route, arbitrate | 5 to 30 venues |
| Hybrid by region | Writes the proposal | One router per area | Several countries |
None of this works if the intake cannot see every calendar. Three states: open, hold with an expiry, confirmed. Check before routing. Otherwise the desk sends a file to a site already taken, the site sends it back, and the planner waits another day.
Holds need a group rule covering how long they last (seven to fourteen days in practice), how many a Saturday can carry at once, and who decides when two planners want the same date. A declined hold is cheap. Two confirmations are not.
Rates can differ between sites; the rules should not. Proposal structure. Deposit terms. Who may discount. A manager in Manchester should be able to quote a range for London without making the planner wait. Joinways is what those groups open before a reply goes out: every site's dates, holds and rates, in one place.
Amex GBT's 2025 Meetings and Events Forecast puts venue among the top three factors of a memorable attendee experience, with content and destination. Venue size, date and season weigh into the selection. A group that can offer a second site on the same Saturday is answering that search, provided the second calendar really is open.
The other address, in the same reply
Confirm the date is taken. Name one or two alternatives with capacity, distance and a price range. Offer a visit or a video slot rather than a vague line about other sites. Tell the second site before the planner hears the address. An alternative offered on a closed Saturday is a second collision.
Numbers the group can actually compare
Group management needs few numbers. They have to mean the same thing in Leeds and in Manchester.
Time to first reply. Confirmation rate: confirmed inquiries over qualified inquiries. Confirmed revenue per site, current and upcoming. Across the venues we set up, the confirmation rate on qualified inquiries typically sits in the 15 to 25 percent range. Under 10 percent is a signal: slow replies, weak qualification, or a price the brief never matched. The seven profitability figures stay the base, read site by site, then in total.
A site that confirms far fewer files than its neighbour, on the same mix, has a problem of speed, price or qualification. A site whose first reply regularly slips past the next day, when the group aims at the hour, has a load problem. None of that is visible while each site stares at its own sheet.
The definition has to travel. Qualified in Manchester must mean qualified in Leeds. Consolidated reports built from the same fields avoid the fake ranking. We described elsewhere how to run a venue on figures a site manager and a group director can both read.
The planner who already knows Manchester
A Manchester client organising in London is the test. If he has to introduce himself again, restate constraints and renegotiate what was already agreed, the group has thrown away the relationship one site built.
One client record at group level, with the events already run on other sites, the contacts, the notes. Every site feeds it. Every site reads it. A shared CRM attaches the London inquiry to the Manchester client without a second typing.
Tell the home site when its client organises elsewhere. Keep one name on the account, even when the event is on another floor. The tool does not do that part.
Questions groups actually ask
- From how many venues should a group centralise intake?
- From the second venue if both sit in the same city or take the same kind of brief. That is where duplicate files start. Two very different venues far apart can stay autonomous if they share one client record. From five venues, hybrid with written routing is what we see most often.
- Does the whole group need one email address?
- One intake simplifies routing. It is a house rule, not a legal duty, and it should not erase the local channel. A venue known on its street will keep getting direct mail. The useful rule: every inquiry, whatever the channel, enters the same tool and follows the same ownership rules. There can be several channels, but only one way of handling them.
- When do two companies in the group become joint controllers?
- When they jointly decide why and how a shared planner file is used. The ICO asks for a transparent arrangement and for the main points to be available to the individual. If they are one legal entity moving data from one site to another, that is not sharing under the code. The other UK GDPR duties still apply.
