Cadence configuration: building the recurring schedule

A cadence is a template: "every Monday at 8 AM, generate the 'walk-in cooler temp check' task and assign it to the on-duty kitchen tech." Get these right and the rest of MaintIQ runs on rails.

Opening cadence configuration

Admin → Cadences. You will see a list of every cadence at the selected facility, grouped by frequency.

Anatomy of a cadence

• Name — what the task will be called.
• Frequency — Daily, Weekly (pick days), Monthly (pick day-of-month or pattern like "first Monday"), or custom cron.
• Window — the start and end time when the task is due (e.g. 6 AM–10 AM).
• Assignee rule — a specific user, a role, or "on-duty in area X".
• Linked SOP — the procedure to follow.
• Photo required — yes / no.
• Skip allowed — yes / no (off for safety-critical tasks).
• Area — which area chip the task carries.
• Asset — which equipment, if any, the task is about.

Frequency examples

Bulk operations

The cadence list supports multi-select:

• Duplicate — clone a cadence to another facility.
• Pause — stop generating new tasks while keeping the cadence definition.
• Reassign — change the assignee on many cadences at once.

Effective dates

Each cadence has a start date and optional end date. Use these for seasonal tasks (e.g. snow-clearance daily from Nov 15 to Mar 15).

Test runs

Click Preview next 30 days on any cadence to see exactly when tasks will be generated. Useful before activating a complex pattern.

Common mistakes

• Overlapping windows — two cadences both due 6–8 AM with the same assignee creates redundant work. Stagger them.
• No SOP link — technicians end up doing it from memory. Always link an SOP unless the task is truly self-evident.
• Wrong time zone — facility time zone determines "today" boundaries. See Facility settings.

Related guides

• Facility settings
• Understanding task cadences
• Linking SOPs to tasks