Overview
Use a rotation when different equipment must be inspected on different weeks. For example, an eight-seat ride might inspect seats 1–2 in week one, 3–4 in week two, 5–6 in week three and 7–8 in week four.
This is a planning example. Use the inspection intervals and scope required by your own procedure.
At a glance |
|
Who can do this | Super Users, or Schedules › Create; Owners, creators or Schedules › Modify can maintain existing Schedules. |
Where | Schedules › Calendar Schedule › Specifics |
Works on | Backend (web), Mobile app |
Availability | All organizations |
💡 Why this matters: Separate work for each group makes the equipment due this week clear and gives each group its own completion record.
Choose the Schedule structure
A Calendar Schedule’s What? Checklists and Where? targets apply to all its slots. Adding four Patterns to one Schedule does not rotate which Checklist or Asset is due.
Create one Schedule for each equipment group. Use a clearly named Checklist for each pair, or one common Checklist with selected Assets on each Schedule if Asset scheduling is enabled. Follow Asset-driven Schedules for that add-on’s requirements.
⚠️ Heads-up: Patterns repeat on selected weekdays every week. There is no every-other-week or every-four-weeks Pattern. Use dated Specific slots for this rotation; they do not repeat automatically.
Build the rotation
Plan the dates first.
Create a simple date plan before editing Mobaro. For example, start the four groups on 5, 12, 19 and 26 October 2026. Group one’s next date is 2 November, four weeks after its first. Extend the plan far enough to cover your operating period.
1. Create one Schedule per group
Set each Calendar Schedule’s What?, Where?, assignees, reviewers, compliance and time zone. Name it for its scope, such as “Seat inspection: 1–2”. Do not include all equipment groups on every Schedule.
2. Set the dated start and deadline
In Specifics, add each date for that group and set the start and deadline.
3. Choose reminders and save the Specific
Add a grace period and reminders only where your procedure calls for them. Save each Specific. See Specific slot settings.
Check a complete cycle
4. Verify the Schedule and its calendar
Review at least the first five weeks, including the first repeat of group one. Confirm exactly the intended equipment appears each week, with no accidental weekly Pattern or inherited Calendar adding extra slots.
Use Schedule Metrics to check targets and assignees, then inspect the Calendar and the work available to a representative User. Asset-targeted work requires access to the Asset’s Location.
Maintain future dates
Assign someone to extend the dated slots before the last planned cycle. A missed or rescheduled inspection does not move the rest of the rotation automatically. Review whether your procedure requires a catch-up inspection, a revised rotation, or both.
For work every second week, use the same approach with dates fourteen days apart. Keep work with different deadlines on separate Schedules; Checklist pages cannot have independent due dates.
Best practices
Keep an equipment-to-Schedule list beside the date plan.
Check inherited Calendars before adding new slots.
Verify the next cycle when the operating season or inspection procedure changes.
Frequently asked questions
Can I inspect two of eight seats each week?
Yes. Separate the seats into the required groups and give each group its own Schedule and dated Specific slots. If using Assets, select only that group’s Assets on its Schedule.
Can one question become due every two weeks?
Questions do not have independent Schedule deadlines. Put the separately due work in its own Checklist and Schedule, with dated Specific slots fourteen days apart.
Can different pages of one Checklist have different deadlines?
No. A Schedule slot applies to the Checklist as a whole. Use separate Checklists and Schedules when the work needs different completion windows.