Overview
A Continuous schedule is a Mobaro Schedule type that users run on demand. There is no fixed slot time and no recurrence — the Schedule is available across the entire day, and users decide when to run the Checklist.
The one thing to know: Continuous schedules trade compliance timing for user flexibility. Use them for tasks where the timing matters less than the fact that the task was done at all.
What a Continuous schedule is
A Continuous schedule makes a Checklist available to users throughout the day without a fixed time slot. Users can start the Checklist at any point; there is no "missed" state the way a Calendar or Ad Hoc slot produces when its window passes unrun.
The Checklist appears in the user's task list whenever the Schedule is active and remains there until they run it. If they do not run it, no specific slot is missed.
When to use a Continuous schedule
Continuous schedules work well when:
The task needs to happen during the operating day but the exact timing doesn't matter — for example, a mid-shift safety sweep that can happen any time between 10am and 4pm.
The task is opportunistic — for example, a cleanliness check a user runs whenever the queue is short.
Multiple users may pick up the same task at different times and you want any of them to run it.
You are replacing a paper process where users just knew to do the check "sometime today."
When NOT to use one
Important: Do not use a Continuous schedule when compliance timing matters. If a regulation or SOP requires the task to happen at a specific point in the day (pre-opening inspections, end-of-day reconciliations), use a Calendar schedule instead.
Specifically, switch to Calendar or Ad Hoc when:
You need to know the task happened within a specific window.
Missing the task has regulatory consequences.
You want to track deviation — for example, how late an inspection was.
The task is triggered by a specific event rather than a general operating day.
Setting up a Continuous schedule
To create a Continuous schedule in the Mobaro Backend:
1. Go to Schedules
Open the Schedules module in the Mobaro Backend.
2. Click Create schedule
Use the Create schedule button to begin a new Schedule.
3. Select Continuous as the Schedule type
Pick Continuous from the Schedule type options.
4. Pick the Checklist
Choose the Checklist this Schedule will run.
5. Scope the Schedule
Apply the Schedule to the appropriate Locations, Assets, and Users or User Groups.
6. Configure compliance options
Set completion tracking, minimum runs per day, and any Assignment requirements (see the next section).
7. Save the Schedule
The Schedule is now live and will surface to scoped Users.
Compliance and deviation options
Continuous schedules have the narrowest set of compliance and deviation options of the three Schedule types. This is by design — because there is no fixed slot time, there is nothing to "be late to."
Typical options available:
Completion tracking — whether the Schedule counts as "done for the day" once it has been run at least once.
Minimum runs per operating day — if you require the Checklist be run more than once.
Assignment requirements — whether a User must have a specific Certification or Role to run the Checklist.
For the complete list of compliance options available on each Schedule type, see the Schedule compliance reference.
Common patterns
Pattern: opportunistic quality checks
A food and beverage stand has a Continuous "Mid-shift cleanliness check" Schedule that users run whenever the queue is short. There is no fixed time; the point is that it happens a few times per shift.
Pattern: rolling safety sweeps
A midway team runs a Continuous "Area safety sweep" Schedule that any user can pick up during their shift.
Pattern: guest-service variable-frequency tasks
Guest Services has a Continuous "Restock guest amenities" Schedule active during the operating window. Frequency varies by park traffic, so a Continuous schedule is a better fit than a rigid Calendar.
Related
Schedules overview — comparison of Continuous, Calendar, and Ad Hoc.
Calendar schedules — setup and behavior.
Ad Hoc Slots — setup and behavior.
Schedule compliance reference — full list of compliance options by Schedule type.
Frequently asked questions
Q: Can a Continuous schedule be "missed"?
A: No. Because there is no fixed slot time, there is nothing for the Schedule to count as missed. If you need missed-state tracking, use a Calendar or Ad Hoc Schedule.
Q: Can I switch a Continuous schedule to Calendar later?
A: You generally cannot change the type of an existing Schedule. To change types, archive the existing Schedule and create a new one of the desired type.