Multi-venue bookings: enquiries, diary and run sheets

Use one enquiry handled centrally and delivered at a named venue. Change a guest count or date, then ask both teams to find the current booking and run sheet. Encore covers the enquiry, diary and handover workflow. Confirm combined views, per-venue access and the supported configuration rather than assuming every location shares all information.

Use the same number of venues, users and contract period in each proposal. Include onboarding, booking migration, training, hardware, payment charges and ongoing support when required. Keep Encore bookings, My Venue screen content and Solo POS counter sales as explicit line items. Use written terms and a representative branch demonstration before committing to a group rollout.

Use a stable booking reference together with the venue, date and area in the handover. Create two fictional events with the same name at different locations and ask staff to find the right one. The location-specific context should remain clear in the diary, run sheet and any export the team relies on.

Review the new space, availability, operational owner and customer agreement before treating the move as complete. Check both locations’ run sheets so the original team does not continue preparing the event. Confirm the supported Encore workflow and assign any manual handover needed for payments, screens or external suppliers.

Define the point at which the local manager must acknowledge a change and how that acknowledgment is recorded. Rehearse a fictional guest-count or timing change shortly before service. A central record update is useful only if the receiving team can identify the latest agreed instruction and knows who will resolve conflicting details.

Prepare the roles of a central coordinator, a local manager and a staff member who only needs service information. Test the actual views and actions offered in the proposed configuration. Record gaps explicitly rather than assuming every organisation has the same cross-venue visibility or that each location can edit all bookings.

Use a centrally handled enquiry delivered at a named venue. Include a changed detail and ask both teams to find the current booking and run sheet.

Give representative central and local users defined tasks. Confirm the supported visibility and permissions in the proposed configuration rather than assuming every site shares all records.

Move a fictional event and have the responsible teams review the affected venue and time. Verify the current operational details through the demonstrated workflow.

Compare a combined view with the underlying venue records for the same period. Confirm which statuses and locations the proposed report includes.

Review site, date, customer, guest count and operational details with each source diary. Name the local approver for the opening booking position.

No. Agree the confirmation decision and handover responsibility. Demonstrate the supported states and local acceptance process before rollout.

Specify the intended provider, verification and local responsibilities. Encore's booking purpose does not establish every multi-venue deposit configuration.

List Encore bookings, My Venue content and Solo POS requirements explicitly. Confirm any intended handoffs and avoid assuming one product automatically includes the others.

Select a site that tests a different operational requirement and confirm its configuration. Use pilot evidence and remaining exceptions rather than expanding solely because the demo looked convincing.

Review missing enquiry details, handover corrections and time to prepare the current run sheet. Compare similar events and keep the source records behind the results.