Daily tasks cover routine checks, but a full shift often needs more structure — a sequence of subtasks, dependencies, and a clear handoff. MaintIQ's Ops tab is built for exactly that workflow.
What is the Ops tab?
The Ops tab shows a single, scrollable shift checklist for the current Facility. Each item can have:
- A short title and one-line description.
- Two to six subtasks (the granular things the tech actually does).
- A linked SOP for the full procedure.
- A target time, an assignee, and a priority pill.
When you tick a subtask, MaintIQ persists the state immediately and shows progress on the parent item. The parent flips to Complete when every required subtask is checked.
Running a shift
A clean shift loop looks like this:
- Sign in and switch to the correct Facility.
- Open Ops. The checklist is sorted with safety-critical items first.
- Work top to bottom. Tick each subtask as you finish it. If a subtask requires a reading or a photo, capture it inline.
- Skip with a reason when an item does not apply ("equipment locked out, see WO #1284").
- Hit End of Shift when the list is done. MaintIQ snapshots the checklist into History and starts a fresh one for the next shift.
Adding subtasks to an Ops item
Admins build the checklist from Admin → Ops Setup. For each item you can:
- Add subtasks in the order they should be performed.
- Mark a subtask as required so it blocks completion.
- Attach an SOP to surface the procedure inline.
- Set a duration estimate, which feeds the shift time-budget shown at the top of Ops.
Hand-off notes
The last step of every shift is the Hand-off note field. Use it for anything the next shift must know:
- "WO 1284 still open — vendor expected Thursday."
- "Tank 3 reading drifted up 0.4 PSI overnight."
- "Forklift battery 2 charged but not rotated in."
Hand-off notes are pinned at the top of the next shift's Ops page and surface in Insights as a "communication health" signal.
Tips for shift-checklist design
- Aim for 60–80 % of shift time on the checklist. Anything more leaves no slack for the unexpected; anything less means the checklist isn't capturing the real work.
- Order by safety, then by route. A tech should be able to walk one logical path through the building and tick items as they go.
- Re-evaluate quarterly. Equipment changes, lines move, vendors swap. A stale checklist becomes invisible.
FAQ
Can two techs work the same Ops checklist in parallel? Yes — subtask state syncs every few seconds. The last writer wins on conflict, with a small undo banner.
What if a subtask repeats across many items? Build it once as an SOP step and reference the SOP from every item. Edits propagate.
Does Ops respect cadences? Yes. Daily Ops items reset at local midnight; Weekly Ops items reset on Monday. You can mix cadences within the same shift checklist.