Overview
Locations are the foundation of Mobaro. A well-structured Location setup makes it easier for staff to complete Checklists, for managers to review Results, and for admins to maintain the system. A poorly managed one causes confusion, duplicate work, and inaccurate reporting. This article covers best practices for creating, naming, and maintaining Locations.
Why this matters: Locations are a central building block — Schedules, Assignments, Results, and access all hang off them. Time spent structuring them properly upfront saves significant rework and prevents errors later, when Schedules and Dashboards are already layered on top.
Best practices for creating Locations
Use clear, descriptive names
Names should immediately tell staff where a Checklist applies — Lazy River, Main Entrance, Kitchen — Café 1. Avoid generic labels like Pool 1 when you have several pools.
Best practice: Name Locations from the perspective of new staff. If they can't instantly recognize the place from the name, rename it.
Map Locations to physical areas
Each Location should represent a distinct physical area or attraction. Don't overload one Location with multiple spaces — use North Arcade and South Arcade, not just Arcade.
Heads up: If two areas share one Location, it becomes much harder to track issues and compliance accurately.
Avoid duplicates
A single physical place should exist only once in Mobaro. Duplicates cause double reporting and Checklist errors.
Organize with Location Groups
Use Location Groups to organize related Locations (Pools, Retail, Food & Beverage). Groups make it easy to assign one Checklist to many Locations and to grant access at scale. See How to create Location Groups.
Align with your organizational structure
Large operators may want to reflect sites, parks, or departments in naming — for example Resort A — Wave Pool and Resort B — Wave Pool.
Best practices for maintaining Locations
Keep the list clean and current
Archive or rename unused Locations rather than leaving them active, and review the list regularly so it reflects your current operation.
Standardize naming conventions
Decide on a consistent format (e.g. Attraction — Section or Building — Floor — Room) and apply it everywhere.
Note: A consistent naming convention matters most when multiple admins are creating Locations.
Consider reporting needs
Think ahead about how you'll analyze data in Dashboards. If you want to compare across sites or departments, structure your Locations and Groups accordingly. For attribute-based reporting, also tag Locations with Location Properties.
Benefits of following best practices
Clarity for staff — they always know which Checklist to complete where.
Efficiency for admins — fewer duplicates and errors to manage.
Accuracy in reporting — clean Location data means more reliable Results and insights.
Frequently asked questions
Q: Should every room or attraction be its own Location?
A: Not necessarily. Focus on areas where inspections or reporting need to be tracked separately.
Q: Can I restructure my Locations later?
A: Yes, but it may require updates to Schedules, Checklists, and Dashboards. Plan carefully before big changes.
Q: What's the difference between a Location and a Location Group?
A: A Location is a single place where work happens. A Location Group organizes multiple Locations together for reporting, scheduling, and access.