Overview
A Continuous Schedule makes Checklists continuously available to its Assignees at the Locations or Assets it applies to. There are no slots, no start or end times and no recurrence — users start the Checklist whenever they need to, as often as they need to. In the mobile app, these appear under Continuous Checklists.
At a glance |
|
Who can do this | Super Users or a Role with Schedules › Create. To edit it later: also the Schedule's Owners, its creator, or Schedules › Modify. |
Where | Schedules › Create › Continuous Schedule |
Works on | Backend (web) to set up; Mobile app to run the Checklists |
Availability | All organizations. Asset targets need Scheduling functionality for assets; Require validation on rule deviation needs Water Quality functionality. |
💡 Why this matters: 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 without a fixed time slot. Users can start the Checklist at any point, and it stays available after they complete it. Because nothing is due at a particular time, there is no "missed" state — a Continuous schedule never produces Missing Results, and it can't be marked Critical for operation.
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.
The same Checklist is run over and over at a fixed point, such as a shared device at a station — the Behavior settings below are built for this.
You are replacing a paper process where users just knew to do the check "sometime today."
When to avoid a Continuous schedule
⚠️ Heads-up: 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 a Calendar Schedule or an Ad Hoc Slot when:
You need to know the task happened within a specific window.
A task that isn't done should show up as a Missing Result.
You want late completion flagged (Require timely answer) or the task to affect a Location's readiness (Critical for operation).
The task is triggered by a specific event rather than a general operating day.
Set up a Continuous schedule
To create a Continuous schedule in the Mobaro Backend:
1. Go to Schedules
Open Schedules in the Mobaro Backend.
2. Click Create
Click Create and choose Continuous Schedule.
3. Fill in General
Enter a Title (required) and, optionally, a Description.
4. Choose Checklists in What?
Choose the Checklists this Schedule makes available. At least one is required.
5. Choose targets in Where?
Choose the Locations or Location Groups in Applies to (Locations/Location Groups), and any Exclusions (Locations/Location Groups). If your organization has Scheduling functionality for assets, you can set Target type to Assets and pick Assets instead.
6. Add people in Who?
Add people in Assigned to (Users/User Groups), Reviewers (Users/User Groups) and Owners (Users/User Groups), and choose who else can see the Results in Results visible to. See Schedule stakeholders: assignees, reviewers, and owners.
⚠️ Heads-up: If you don't add any Reviewers, only Super Users will be able to validate Results from this Schedule.
7. Set Behavior
Set how the Checklist behaves on the device — see Behavior settings below.
8. Set Compliance
Choose the validation and competency settings that apply — see Compliance options below.
9. Save the Schedule
The Checklists are now available to the Assignees at the Locations or Assets you chose.
Continuous schedule Behavior settings
Continuous schedules are the only Schedule type with a Behavior section. These settings control how the Checklist runs on the device:
Setting | What it does |
Automatically advance pages | The Checklist automatically moves to the next page when every question on the page is answered. |
Restart on completion | The Checklist automatically restarts when all questions have been answered. |
Enable timeout | The Checklist starts over if the user doesn't interact with it for a given time. Set the time in Timeout in seconds. |
Require password to exit | The user can't exit the Checklist without entering the correct Password. |
Continuous schedule compliance options
Because there is no slot time, there is nothing to "be late to", so Continuous schedules have a shorter Compliance section than Calendar Schedules and Ad Hoc Slots:
Mark all results as requiring validation
Require correct GPS location
Require maximum score
Require minimum answer duration
Require validation on rule deviation — only shown when your organization has Water Quality functionality
Enable Time Registration — Optional or Required
Required Competencies, optionally with Restrict access based on required competencies
Allow early start, Ignore missing results, Require timely answer and Is critical for operation aren't available on Continuous schedules. For what each option does, see Schedule compliance settings.
Common Continuous schedule patterns
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.
Rolling safety sweeps — a midway team runs a Continuous "Area safety sweep" Schedule that any user can pick up during their shift.
Guest-service variable-frequency tasks — Guest Services has a Continuous "Restock guest amenities" Schedule. Frequency varies by park traffic, so a Continuous schedule is a better fit than a rigid Calendar.
Shared-device station check — a ride station has a tablet that runs a Continuous "Dispatch check" Schedule with Restart on completion, Enable timeout and Require password to exit turned on, so each operator starts a fresh Checklist and can't leave it without the password.
Related articles
Choosing a Schedule type — comparison of Calendar, Continuous, and Ad Hoc.
Schedule compliance settings — full list of compliance options by Schedule type.
Best practices
For a shared device that runs the same Checklist all day, combine Restart on completion and Enable timeout so every user starts from a fresh Checklist, and add Require password to exit so users can't leave it.
Frequently asked questions
How do I make a checklist available whenever it's needed?
Create a Continuous Schedule: Schedules › Create › Continuous Schedule, then add the Checklists, targets and Assignees. It has no time slots, and Assignees find the Checklist under Continuous Checklists in the mobile app.
A user can't see the continuous checklist in the app. Why?
They must be in Assigned to (Users/User Groups), directly or through a User Group, and be a member of a Location the Schedule applies to (directly or through a Location Group target). Check both, then have them tap the refresh icon in the app's dashboard header.
Can users complete a continuous checklist more than once, even on the same day?
Yes. The Checklist stays available after it's completed, and each completion is saved as a separate Result. With the Checklist's Restart on completion turned on, it restarts automatically as soon as it's finished.
What's the difference between a calendar schedule and a continuous schedule?
A Calendar Schedule makes a Checklist available in time slots and logs a Missing Result when a slot is missed. A Continuous Schedule is always available, so nothing can be missed. See Choosing a Schedule type: Calendar, Continuous, or Ad Hoc.
Why doesn't my continuous checklist affect the Location Overview?
A Continuous Schedule has no slots, so it never produces Missing Results and can't be critical for operation. It doesn't count towards a Location's red or green state. Use a Calendar Schedule or an Ad Hoc Slot if the check should count.