How to launch waivers at a second location

A second location is a good test of whether the first location's waiver process is documented or lives in one manager's memory. Reuse the parts that are deliberate and working. Inspect the assumptions that depended on a particular lobby, activity or staff team.

Compare the actual guest journeys

Walk through bookings, arrivals, guardians, events and returning participants at both sites. Identify differences in activities, equipment, programs and desk responsibilities. A shared brand does not automatically mean the same document or intake questions fit every visit. Have the responsible owner approve wording and workflow decisions for the new operation. Keep a short list of what is shared and what intentionally differs so staff understand the setup.

Set up location context carefully

Use the supported multi-location tools and check how location information appears in templates, invitations and records. Confirm the plan that covers the intended arrangement on the pricing page. Test the public link from a signed-out device. A guest should be able to recognize the correct organization and activity without knowing your internal location labels. Avoid reusing the first site's signs before checking their actual destinations.

Verify staff roles and record visibility

Invite staff through individual accounts and assign the supported roles needed for their work. Confirm what they can view or change across locations. Do not infer access restrictions from a location filter alone. If strict separation is required, resolve that requirement before opening. Give supervisors a clear owner for configuration changes so one site's attempt to fix a question does not unexpectedly alter a shared template used by the other.

Pilot the complete new-site process

Run adult, guardian and group scenarios that reflect the new location. Test the actual network, tablet placement, QR signs and booking messages. Have a staff member from the new site find each completed record without relying on the original site's manager. Inspect status, flags and the handoff to the venue's other admission checks. Document differences in the playbook rather than leaving them as verbal exceptions learned during a busy shift.

Establish a shared change routine

Choose who approves template revisions, updates shared instructions and informs both desks. Record which changes affect every location and which are site-specific. Review the first week's questions with both teams. A recurring issue at one desk may reveal a local setup problem; the same issue at both may point to the shared form. Keep product configuration, approved wording and staff training aligned as the organization grows beyond a single-location habit.