Overview
Location Properties are tags you assign to Locations to describe their characteristics — ride type, equipment present, area of the park, regulatory category. Once assigned, they let a single Checklist behave differently across Locations by showing or hiding questions and elements based on each Location's Properties. This article explains the concept; for the step-by-step setup, see Creating and assigning Location Properties.
Why this matters: Without Location Properties, every variation in your operation needs its own dedicated Checklist. Properties let one Checklist adapt — track inspections appear only on coasters, water-quality questions only on water rides — so you maintain fewer Checklists with less drift.
What are Location Properties?
Properties are attributes, organized into Categories, that you assign to Locations. They ensure only relevant Checklist content appears for a given Location. For example, a question about Indoor Fire Extinguishers shows only for Locations that have the Indoor Fire Extinguisher Property.
Category | Example Properties |
Indoor Checks | Indoor Fire Extinguisher, Ventilation System |
Ride Types | Coaster, Tower, Flat Ride |
FEC Categories | Arcade/Play Areas, Climbing Wall, Laser Tag |
Note: A Location can hold multiple Properties across different Categories — for example Ride Type: Coaster and Indoor Checks: Indoor Fire Extinguisher on the same Location.
Key benefits
Dynamic Checklists — content adapts automatically based on a Location's assigned Properties.
Streamlined operations — use one Checklist across many Locations while keeping each one relevant.
How Location Properties work
Dynamic Checklist behavior
Checklists show or hide questions and elements based on the Location's Properties. You wire this up with conditional logic on the Checklist — see Using Location Properties as Checklist logic.
Operational flexibility
Maintain standard Checklists across all Locations while still addressing Location-specific needs — no duplicate Checklists per variation.
Example: one Checklist, two ride types
Scenario
A single Checklist inspects different ride types.
Location 1: Coaster, Indoor Fire Extinguisher.
Location 2: Tower.
Logic applied
A Track Inspections question shows only for Locations with the Coaster Property.
A Structural Stability Checks question shows only for Locations with the Tower Property.
Result
Each Location sees only the questions that apply to its ride type, keeping the Checklist relevant and streamlined for operators.
Frequently asked questions
Q: What happens if a Location has no Properties assigned?
A: Any Checklist content not gated by Property logic still shows. Only Property-conditional content is affected.
Q: Can one Location have multiple Properties?
A: Yes — for example both Indoor Fire Extinguisher and Coaster.
Q: Do Location Properties affect existing completed Results?
A: No. Properties only take effect through logic added to Checklist questions or elements going forward.
Q: What happens if I remove a Property from a Location?
A: Any Checklist content gated by that Property is no longer limited by it for that Location. Review affected Checklists before changing Properties on production Locations.