Multi-location waivers with a shared operating standard

Adding a second location exposes decisions that were easy to handle by memory at the first. A short template name, an informal review rule or a shared login can become confusing when several teams work at once. A consistent structure helps each location operate clearly without pretending every activity is identical.

Name locations for the people using them

Use recognizable location names and decide how they relate to your activities and events. Staff should be able to confirm where they are working without decoding an internal abbreviation. Keep location details accurate and review them before sharing links or launching kiosks. If a guest can attend more than one site, define how your organization determines which form applies rather than assuming a form signed at one place automatically covers another.

Standardize the parts that should match

Agree on common field labels, naming conventions and desk checks. Then identify differences that genuinely require a distinct form or instruction, such as a different activity or an approved document change. Avoid creating separate templates merely because each manager prefers a different name for the same question. Conversely, do not force different activities into one form when your approved process calls for specific information or wording.

Give each team the right access

Use individual accounts and the roles supported by your workspace. Review permissions against actual responsibilities, especially for publishing templates, managing members and exporting records. Do not infer a location-level restriction from a role name; confirm the available controls and how they behave in the current product. A shared operating standard should include who can change the common setup and how another location learns about that change.

Test an arrival at the new site

Before launch, open the public link, complete a realistic submission and have the new desk team find the record. Check the intended location context, event details and check-in result. Repeat the test with a returning guest and a guardian where those cases apply. Keep a short exception process for someone who has a record associated with another visit or activity.

The Growth plan includes unlimited locations and unlimited waivers. Use the pricing page for current billing and SMS details. A plan's location allowance does not settle your operating policies, so make the workflow decisions alongside the account setup rather than treating a plan upgrade as the entire rollout.