Overview
Every Location has a readiness color: green when it's ready for operation and red when something needs attention first. The Header Color settings in Configuration › Location Overview decide what turns a Location red, for your whole organization.
These settings don't only color the dashboard. The same rules decide whether a Location is Ready in the mobile app, whether it can be opened, and whether RideOps shows it as ready. This article explains each setting and how to combine them.
At a glance |
|
Who can do this | Super Users, or a Role with Organization › Administrate |
Where | Configuration › Location Overview › Header Color |
Works on | Backend (web). The result also shows in the mobile app and RideOps. |
Availability | All organizations |
💡 Why this matters: Readiness colors let leaders and floor staff scan dozens of Locations in seconds, and they gate whether a Location can open. If the rules don't match what your operation calls "ready", green stops being reassuring and red stops being actionable, or rides get blocked for reasons that don't matter.
Where readiness colors show
The organization's Header Color settings drive the readiness color everywhere Mobaro shows it:
Dashboard: the header of each Location in the Location Overview widget.
Locations page: the Ready for operation / Not ready for operation status dot.
Mobile app: the Ready / Not ready state on the Operations tile. See Managing Downtime and uptime from the mobile app.
RideOps: whether the Location is ready for operation.
🛑 Critical: A red Location can't be opened. In the mobile app, Open location and Start Downtime are disabled while it shows Not ready, and in the Backend a red Location can't be switched to open. Changes here apply to every Location immediately, so a new red condition can block rides from opening. Plan changes outside operating hours and tell your team.
Color | Meaning |
Green | None of the red conditions is true. The Location is ready. |
Red | At least one red condition is true, or a critical Checklist is outstanding. The Location isn't ready. |
Gray | Dashboard widget only: nothing turns it red, but no Checklists are counted for it in the widget's time range and filters. |
Open the Header Color settings
1. Open Configuration
In the Mobaro Backend, go to Configuration.
2. Select the Location Overview tab
Select the Location Overview tab. The readiness rules are in the Header Color panel.
3. Change the settings
Tick or untick the options described below, then click the save icon (Save) at the top of the Header Color panel. Changes aren't applied until you save. Mobaro confirms with Location overview settings successfully saved.
The Header Color settings
Critical-for-operation Checklists always count toward red, whatever you choose here. The options add further red conditions or refine what counts as done:
Setting | Default | What it does |
Color is only affected by approved results | Off | A Checklist that counts toward red (critical, or missing while Red if one or more checklists are missing is on) stays counted until its Result is approved, if the Result requires validation. Results that don't require validation clear it as usual. |
Red if one or more checklists are missing | On | Any Checklist on the Location that ended without a Result (a Missing Result not yet approved or rescheduled) turns it red, critical or not. When off, only critical Checklists count. |
Red if one or more active high priority assignments exist | On | An open high-priority Assignment on the Location turns it red. |
Red if one or more active overdue assignments exist | Off | An open Assignment on the Location that's past its deadline turns it red. |
Red if a blocking downtime is active on the location | On | A blocking Downtime on the Location turns it red. Open Assignments created from a Downtime also count. |
Allow access to color explanation dialog for everyone | Off | Lets every user open the explanation of a red Location from the Location Overview widget. When off, only Super Users can. |
⚠️ Heads-up: Red if a blocking downtime is active on the location also keeps a Location red on the dashboard, the Locations page and in the app while any Assignment created from a Downtime is still open, even after the Downtime itself is closed or if it was never blocking. Resolve the Assignment, or turn the option off if that's not what you want.
For how critical Checklists turn a Location red in each mode, see Schedule criticality and Location operational status. To track down why a specific Location is red, see Troubleshooting red statuses in location overviews and the location review dashboard.
See why a Location is red
In the Location Overview widget, click a red Location's header to open its color explanation. It has two tabs, Checklists and Assignments, listing what's keeping the Location red. Blocking Downtime isn't listed there; click the Location's operational status bar to see its Downtimes.
The explanation only opens for red Locations. Super Users can always open it; other users can only if Allow access to color explanation dialog for everyone is on. On the Locations page, clicking a red status dot opens the same explanation.
Example: a ride operations setup
A theme park shows the Location Overview on a wall display in the operations center. Leadership wants red to mean "this ride can't open yet" and nothing else. They set:
Color is only affected by approved results: off. Submitted opening checks should clear the color without waiting for review.
Red if one or more checklists are missing: off. Only critical opening Checklists should block a ride; a missed weekly cleaning audit shouldn't.
Red if one or more active high priority assignments exist: on. Maintenance uses high priority for safety issues.
Red if a blocking downtime is active on the location: on. A ride in blocking Downtime isn't ready.
Allow access to color explanation dialog for everyone: on. Supervisors can click a red ride and see why.
Result: green rides are ready and can be opened in the app; red rides are blocked, and supervisors see at a glance whether a Checklist or an Assignment is the cause.
Best practices
Turn on only the red conditions that genuinely mean "don't operate" in your organization. Every extra condition is a reason a ride can't open.
Use criticality on Schedules for Checklists that must be done before opening, rather than relying on Red if one or more checklists are missing for everything.
Turn on Allow access to color explanation dialog for everyone so frontline supervisors can fix what's blocking a Location without calling a Super User.
Change these settings outside operating hours and tell your team, because they apply to every Location at once.
Frequently asked questions
Why is my location still red when the checklist is done?
Something else still counts: an unapproved, unrescheduled Missing Result (any Schedule while Red if one or more checklists are missing is on), a Result awaiting approval (when only approved results count), an open high-priority or Downtime Assignment, or a blocking Downtime. See Schedule criticality and Location operational status.
What decides whether a location is red or green in the app?
The same Header Color settings on this page. The mobile app's Operations tile shows a Location as Ready only when it's green; otherwise it shows Not ready and Open location is disabled.
Why does my location show gray on the dashboard?
Gray means nothing turns the Location red, but no Checklists are counted for it in the widget's time range and filters. Widen the time range or filters, or schedule Checklists on the Location.
Does a high-priority assignment stop a ride from opening?
Yes, while Red if one or more active high priority assignments exist is on (the default). The Location is red, so it can't be opened until the Assignment is resolved. A Location that's already open isn't closed automatically.
Can non-super users click a red location to see why it's red?
Yes. Turn on Allow access to color explanation dialog for everyone. Without it, only Super Users can open the explanation from the Location Overview widget.
Does a checklist score below 100% turn the location red?
No. Scores don't affect the readiness color. Only the conditions on this page and critical Checklists do. To act on a failed answer, use a trigger to create an Assignment. See Adding triggers to a checklist.