Overview
When a scheduled Checklist isn't completed within its window, Mobaro flags the Result as missed. Missed Results don't disappear — they require explicit action from a User with the right permission. There are two paths: approve the miss (acceptable, on the record, no further work) or reschedule it (the work still needs to happen, generate an Ad Hoc Slot to cover it). Both choices are tracked in the audit trail with comments and attachments.
The mental model: A missed Result is a question, not a verdict. The question is: "do we accept that this didn't happen, or do we still need it to happen?" Approving says yes, accept. Rescheduling says no, do it now. Either way, you owe the audit trail an explanation.
Required access: Approving or rescheduling missed Results requires a Reviewer Role with the Approve missing permission. See how to set up Roles for the permission model.
What "missed" means
A Result is missed when the Checklist's scheduled window passes without a completed run. This applies to Calendar slots and Ad Hoc Slots, both of which carry a scheduled time and a deviation window. Continuous Schedules don't produce missed Results in the same way — see Continuous schedules — setup and behavior.
Missed Results surface in:
The Missing results tab in Results.
Dashboards, where they count against compliance metrics.
Notification Rules, if configured to alert on missed slots.
Approving a missed Result
Approve when the miss is acceptable — for example, the Location was unexpectedly closed, the operator was reassigned to a higher-priority task, or the work simply wasn't required for that day. Approval clears the missed state but keeps it on the record.
1. Go to the Missing results tab
Open the Missing results tab in Results. Tick the missed Result(s) you want to approve.
2. Click Approve missing result(s)
Use the Approve missing button at the top of the list.
3. Add a comment and attachments
Document why the miss is acceptable. The audit trail will need this in six months — be specific ("Park closed early due to weather") rather than generic ("OK"). Attach photos or documents if relevant.
4. Confirm
A checkmark icon appears next to each approved Result. The Result remains in the audit trail with the approval, comment, and approver name attached.
Rescheduling a missed Result
Reschedule when the miss is not acceptable — the work still needs to happen, just later. Rescheduling creates a new Ad Hoc Slot configured with whatever timing and scope you set. The original missed Result stays on the record (it's not erased) — the reschedule is in addition.
1. Go to the Missing results tab
Open the Missing results tab and tick the missed Result(s) you want to reschedule.
2. Click Reschedule missing result(s)
Use the Reschedule missing button at the top of the list.
3. Configure the rescheduled Slot
Set the new scheduled time and any other Schedule options. You have all the original scheduling options available — this is creating a fresh Ad Hoc Slot. Add a comment and any attachments documenting why the original was missed and why the work is still needed.
4. Confirm
A reschedule icon appears next to each rescheduled Result. The original missed Result remains in reporting; a new Ad Hoc Slot now exists for the work to be completed.
Note: Rescheduled Slots inherit from the original Schedule's configuration but are created as Ad Hoc Slots — they have their own deviation window, recipients, and trigger source audit. The original Schedule continues to generate its normal slots; the rescheduled item is a one-off. See Ad Hoc Slots — setup and behavior.
Choosing approve vs reschedule
The decision is operational, not technical. A few patterns:
Park closed unexpectedly (weather, power outage, civic event) → approve. The work didn't need to happen.
Operator absent, work still required → reschedule. Cover the gap.
Schedule was overly aggressive and not realistic → approve and revise the underlying Schedule. Don't keep approving the same kind of miss week after week — fix the root cause.
Compliance-sensitive Checklist (safety, regulatory) → reschedule, with comment documenting urgency. Approving regulatory misses without rescheduling creates audit risk.
Intentional skip (planned maintenance, special event replaces the routine) → approve. Note the reason clearly so future reviewers understand the precedent.
Worked examples
Example 1: Power outage misses morning inspections
Scenario: A regional power outage closes the park before opening. Five rides have missed pre-opening inspection slots.
Setup: Operations Manager opens Missing results, ticks the five Slots, clicks Approve missing. Comment: "Park did not open due to regional power outage; pre-opening inspections not required."
Result: All five marked approved with a clean audit trail. No rescheduling needed — the rides won't operate that day.
Example 2: Operator out sick, safety check still required
Scenario: A 10am safety check on a critical ride is missed because the assigned operator went home sick. The ride is still operating; the check still needs to happen.
Setup: Supervisor opens Missing results, ticks the missed Slot, clicks Reschedule. Sets new time to 11:30am, scoped to a different qualified operator. Comment: "Original assignee out sick; rescheduled to next-available qualified operator."
Result: Original missed Result remains in the reporting trail. New Ad Hoc Slot generated and assigned. Compliance is preserved.
Anti-patterns to avoid
Watch out for these patterns, which quietly degrade the audit trail:
Bulk approving without comments — a "blank approval" tells future you and any auditor nothing about why the miss was OK. Always include a comment, even a brief one.
Approving the same kind of miss repeatedly — if a Schedule produces missed Results week after week and you keep approving them, the Schedule is wrong. Fix the underlying Schedule rather than rubber-stamping misses.
Rescheduling without checking who's qualified — rescheduled Slots inherit assignment requirements (Certifications, Roles). Setting an unrealistic new time or scope just creates a second missed Result.
Approving regulatory or safety-critical misses without clear justification — these are the records auditors look at first. Approving with a generic comment ("OK") is a risk indicator. Be specific or reschedule.
See also
Schedule criticality and Location operational status — for the related concept of how missed Results on critical Schedules affect a Location's operational state.
Ad Hoc Slots — setup and behavior — for the Slot type that rescheduling creates.
Setting up Roles — for the Approve missing permission and Reviewer Role configuration.
Calendar schedules — setup and behavior — for how missed slots are produced.
Frequently asked questions
Q: Can I undo an approval?
A: Approvals create audit-trail entries that can't be silently undone. Contact your Super User or support@mobaro.com if a correction is needed — the action will be logged.
Q: Does the original missed Result disappear after rescheduling?
A: No. The original missed Result stays in the audit trail and continues to count against compliance metrics for that period. The rescheduled Ad Hoc Slot is additive, not a replacement.
Q: Can a rescheduled Slot itself be missed?
A: Yes. Ad Hoc Slots have their own deviation window. If the rescheduled Slot is missed, it goes through the same approve/reschedule flow as any other missed Result.
Q: Who can see approval comments?
A: Anyone with access to the Result. Comments are part of the audit trail — they're meant to be read.
Q: Can I approve missed Results in bulk?
A: Yes — tick multiple in the Missing results list and approve them together. The comment applies to the batch. Useful for a single common cause (weather closure, planned closure) but be careful not to lose specificity when the misses have different reasons.