Overview
Schedule criticality is how Mobaro decides whether outstanding Checklist work should stop a Location from showing as ready. When a Calendar Schedule or Ad Hoc Slot is marked Critical for operation, an incomplete Checklist from it turns the Location's header red (Not ready for operation) on the Location Overview dashboard widget at the moment its mode says, so anyone watching sees whether the park is ready to open — instead of a Dashboard that cries wolf.
At a glance |
|
Who can do this | Criticality: Super Users, a Schedule's Owners, or a Role with Schedules › Create or Modify. Header Color options: Super Users or a Role with Organization › Administrate. |
Where | Schedules › a Calendar Schedule or Ad Hoc Slot › Compliance › Is critical for operation; Configuration › Location Overview › Header Color |
Works on | Backend (web) — the Location Overview dashboard widget; RideOps readiness |
Availability | All organizations |
💡 Why this matters: Criticality answers "if this Checklist isn't done yet, can the Location operate?" A pre-opening safety check on a coaster: yes, critical — not done means don't open. A weekly trash-bin audit: no, not critical — a miss is a tracking issue, not an operational blocker.
What criticality controls
Tick Is critical for operation in a Calendar Schedule's or Ad Hoc Slot's Compliance section, then choose a mode. The mode decides when, relative to each slot's start, deadline and grace period, an incomplete Checklist starts to count against the Location:
Mode | Location turns red… | Until… |
Always | as soon as the slot starts | the Checklist is completed, or its Missing Result is approved or rescheduled |
When overdue | when the deadline passes (start of the grace period); with no grace period, when the slot ends | the Checklist is completed, or its Missing Result is approved or rescheduled |
When missing | when the slot ends (end of any grace period) | the Missing Result is approved or rescheduled |
There is no separate "critical phase" or lead time — a critical Checklist counts from the times above until it's dealt with. To make a check affect the Location earlier, start its slot earlier. A Calendar Schedule's criticality applies to all of its slots, including those inherited from master Calendars; each Ad Hoc Slot has its own; Continuous Schedules can't be critical. For each mode in detail, see Understanding criticality settings with schedules.
How criticality shows on the Dashboard
The Location Overview widget gives each Location a red or green header — no amber (a Location that isn't red but has no Checklists counted shows gray instead of green). It turns red when a critical Checklist is outstanding, or when a Header Color option applies:
Header Color option | Default | Turns the Location red when… |
Red if one or more checklists are missing | On | a Checklist on the Location has an unhandled Missing Result, 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 exists on the Location. |
Red if one or more active overdue assignments exist | Off | an open Assignment on the Location is past its deadline. |
Red if a blocking downtime is active on the location | On | the Location has a blocking Downtime. |
Color is only affected by approved results | Off | a critical Checklist's completed Result still requires validation — red until it's approved. |
Set these per organization in Configuration › Location Overview › Header Color (Super Users, or Roles with Organization › Administrate). See Configuring readiness colors on the Location Overview.
⚠️ Heads-up: Because Red if one or more checklists are missing is on by default, any Missing Result turns its Location red once the slot ends — even from a Schedule that isn't critical. So a non-critical Schedule and a When missing Schedule affect the header the same way. Turn the option off if only critical Schedules should drive it.
The header color is separate from the Location's operational status (open, closed, or in Downtime), which the widget shows on its own — see Downtime on Dashboards — color states and metric widgets. In RideOps, the same critical Checklists — together with Assignments, blocking Downtime and other checks — decide whether a Location is Ready for operation.
Reschedule a critical Missing Result
When you reschedule a Missing Result from a critical slot, Mobaro keeps it critical by default: the rescheduled Checklist is set to Always and starts immediately, so the Location stays red until it's done. In the web app, the reschedule dialog shows "This checklist is currently critical for operation. The rescheduled checklist will inherit this by default." — you can change the criticality before confirming. See Approving or rescheduling missed Results.
Worked criticality examples
Example 1: Pre-opening ride inspection. A coaster can't open at 9:00am without an inspection from 8:00am. Setup: a Calendar Schedule Pattern from 8:00 to 8:45, grace period until 9:30, Is critical for operation set to Always. Result: from 8:00am the header is red, so the Park Director sees the ride isn't ready; once the inspection is done at, say, 8:15am, it clears. (With When overdue, the header would stay green until 8:45am and turn red only if the inspection still wasn't done.)
Example 2: Daily F&B health check (non-critical). Missing a daily food-temperature log is a tracking concern, not a reason to stop serving guests. Setup: a Calendar Schedule, not critical; it still produces Missing Results to handle. Result: the Schedule doesn't affect the header while the slot runs. If the log is missed, the Location turns red when the slot ends if Red if one or more checklists are missing is on (the default), until the Missing Result is handled. Turning that option off keeps such misses off the header, for every non-critical Schedule.
Example 3: Annual structural inspection. Without it, the coaster can't open for the season. Setup: a Specific — or an Ad Hoc Slot — that starts well before opening day and ends before it, critical with Always; on an Ad Hoc Slot, tick Notify assignees when scheduled checklist(s) becomes available to alert the team when it opens. Result: the header is red from the slot's start until the inspection is completed, visible well before opening morning. If the slot ends without it, the Missing Result keeps the Location red until handled.
Criticality anti-patterns to avoid
These patterns break the signal-to-noise ratio of the Dashboard:
Marking everything critical — red just means "something is outstanding" with no prioritization, and the Dashboard becomes background noise. Reserve critical for Schedules that genuinely affect operational readiness.
Marking nothing critical — the header only reacts to Missing Results, Assignments and Downtime, and the Dashboard isn't pulling its weight as a real-time operational tool. At least pre-opening safety inspections should typically be critical.
Long slots on Always — an Always Checklist keeps the Location red from the slot's start until it's done. If the slot opens hours before the work can realistically happen, the Location stays red for no reason. Start the slot when the check becomes relevant, or use When overdue.
🛑 Critical: Don't combine Is critical for operation with Ignore missing results. No Missing Result is created, so there's no record to approve or reschedule, and a When missing Schedule never turns the Location red. Mobaro warns you when you combine the two.
Related articles
Schedule compliance settings — every compliance option by Schedule type.
Calendar schedules — setup and behavior — the Schedule type criticality is most commonly configured on.
Frequently asked questions
Why is my location still red when all the checklists are done?
Something else counts: a Missing Result not yet approved or rescheduled, from any Schedule (Red if one or more checklists are missing is on by default), a Result awaiting approval when Color is only affected by approved results is on, an open high-priority Assignment, or a blocking Downtime.
How do I clear a missing result that's keeping the location red?
Approve it or reschedule it from Missing Results. A Missing Result can't be disapproved. A rescheduled critical Checklist is set to Always by default, so the Location stays red until it's completed. If it's still red afterwards, open the Location's color explanation to see what's left.
Who can reschedule a missed checklist?
Super Users, or users with the Results › Validate Missing permission who are a Reviewer of the Schedule and a member of the Location. Rescheduling creates an Ad Hoc Slot, so it also needs Schedules › Create. See Approving or rescheduling missed Results.
How do I approve lots of missing results at once?
In Missing Results, select them and choose Approve missing result(s) or Reschedule missing result(s). You can select up to 100 at a time.
Can I see what time a location turned green?
No. The header color is calculated live, and its history isn't stored. Use the completion or approval time of the last critical Result, or the approval time of the last Missing Result, instead.