Skip to main content

Configuring readiness colors on the Location Overview

Configure what turns a Location green, red, or gray on the Location Overview — based on Checklist completion, high-priority Assignments, Blocking Downtimes, and Result approval rules.

Written by Logan Bowlby

Overview

The Location Overview is where managers and operators see at-a-glance which Locations are ready for operation and which need attention. Each Location's row shows a readiness color — green, red, or gray — based on rules you define under Configuration > Location Overview. This article covers each setting, what it does, and how to combine them so the colors mean what you want them to mean.

Users must be Super Users or have the following Role to manage Location Overview settings:

  • Organization: Administrate

Why this matters: Readiness colors are how leadership and floor staff scan dozens of Locations in seconds. If the rules behind those colors don't match what your operation considers "ready," the colors lose meaning fast — green stops feeling reassuring, red stops feeling actionable. These settings let you tune the rules to your operation, organization-wide.


What the readiness colors mean

Color

Meaning

Green

The Location is ready. None of the configured "red" conditions are currently true.

Red

At least one configured red condition is true — missing Checklists, an unresolved high-priority Assignment, an active Blocking Downtime, etc. The Location needs attention before it's ready.

Gray

Readiness can't be determined — typically because no scheduled Checklists match the current filters or date range. Adjust filters or schedule the work to clear gray.

Note: These colors apply to the Location Overview in both the Mobaro Backend and the mobile app. They're related to — but separately configured from — the Ready for Operation indicator on the mobile app's Operations tile, which is covered in Managing Downtime and uptime from the mobile app.


Accessing the settings

1. Open Configuration

In the Mobaro Backend, navigate to Configuration.

2. Open the Location Overview tab

From the top navigation bar, select the Location Overview tab.

3. Find the Header Color section

All readiness rules are configured under the Header Color panel.


The settings

Each toggle adjusts the rules behind the readiness color. Mix and match to match your operation:

Setting

What it does

Color is only affected by approved Results

Only Results that have been approved by a Reviewer count toward the green status. Awaiting-validation and resumable Results don't influence the color. Use this when you want only validated work to clear the readiness check.

Red if one or more Checklists are missing

Turns the Location red whenever any required Checklist is outstanding — whether it's flagged Critical for Operation (CFO) or not. Use this when on-time Checklist completion is itself a compliance requirement, not just CFO Checklists.

Red if one or more active high-priority Assignments exist

Turns the Location red whenever it has an unresolved high-priority Assignment. Surfaces critical work that needs attention before the Location should be considered ready.

Red if a Blocking Downtime is active

Turns the Location red while a Blocking Downtime is in place — i.e., a Downtime with an auto-generated Assignment that must be resolved before the Location can run. Highlights operationally halted Locations clearly.

Allow all Users to look into a Location's readiness

Lets any User with access to the Location Overview drill into the underlying details — Results, Assignments, Downtimes — that drive the color. Without this, only Users with the relevant Roles see the breakdown.

Best practice: Turn on every red condition that genuinely blocks operation in your organization, and leave off the ones that don't. If "missing Checklist" turns the Location red but your operation tolerates a 30-minute grace period, the colors stop being trustworthy on busy mornings — staff start ignoring them. The point is signal, not noise.

Critical: Changes here apply organization-wide and take effect immediately. Every Location, every viewer of the Location Overview, sees the new logic the next time they load the page. Plan changes during off-peak hours and let your team know what's changing.


Example: a typical ride operations setup

Scenario

A theme park's operations leadership wants the Location Overview to clearly show, on opening morning, which rides are good to go and which are blocked. They use the Location Overview on a wall display in the operations center and on supervisors' phones during opening rounds.

Setup

  • Color is only affected by approved ResultsOFF. They want submitted Results to clear the color, even if a Reviewer hasn't validated yet — operations can't wait for review.

  • Red if one or more Checklists are missingOFF. Their CFO Checklists are what matter for opening; non-CFO Checklists (deep-cleaning audits, etc.) shouldn't make a ride look "not ready."

  • Red if one or more active high-priority Assignments existON. High-priority Assignments are how maintenance flags safety-critical issues; if one is open, the ride shouldn't show as ready.

  • Red if a Blocking Downtime is activeON. A ride with active Blocking Downtime is by definition not ready.

  • Allow all Users to look into a Location's readinessON. Any operator should be able to tap a red Location and see why.

Result

  • On the wall display, leadership scans the grid: green rides are ready, red rides are blocked.

  • When a ride shows red, supervisors tap in and see whether it's a high-priority Assignment, a Blocking Downtime, or both — and route the right team accordingly.

  • Non-CFO Checklists that haven't been completed yet don't pollute the color signal.


Frequently asked questions

Q: Do these settings apply to specific User Groups?
A: No — these are global settings that apply to every User who can access the Location Overview. The only per-User control is the Allow all Users to look into a Location's readiness toggle, which governs who can drill into the underlying details.

Q: Can I customize the thresholds for readiness colors?
A: The thresholds themselves are fixed — a Checklist is either missing or not, an Assignment is either active or not. What you can customize is which conditions trigger red in the first place. Toggle off any condition that doesn't reflect blocked operation in your context.

Q: How does the "approved Results" setting interact with the other rules?
A: It refines what counts as "Checklist complete." With it ON, a Result must be Reviewer-approved to clear the readiness check. With it OFF, a submitted Result clears the check even if it hasn't been validated yet. The other red conditions (Assignments, Blocking Downtimes) work the same way regardless.

Q: What if I disable every red condition?
A: Locations default to color logic based on per-Schedule Checklist completion and criticality only — i.e., the standard CFO behavior. The rest of the configurable rules just stop contributing.

Q: Why do some Locations show gray?
A: Gray means readiness can't be calculated — usually because no Checklists match the current date range or active filters. Either adjust the filters, or schedule the work that should be running.

Q: How does this relate to the Ready for Operation indicator on the mobile app?
A: The mobile app's Operations tile shows a Ready for Operation indicator on each Location row that gates whether the Location can be opened — see Managing Downtime and uptime from the mobile app. The Location Overview readiness colors here are a related but separate visualization, configured by the settings on this page.

Did this answer your question?