Maintenance backlog board template for the 15‑minute KPI huddle

Maintenance backlog board (kanban) — template and daily use guide

Purpose: Make maintenance work and risk visible each shift so the team can prioritize repairs that prevent chronic losses, keep critical assets running, and move short-blocking items to resolution or documented escalation.

Board columns (left → right)

• New — recently reported failures or requests awaiting triage.
• Triage — brief assessment started: safety, priority, parts check, owner assigned.
• Planned — scheduled work with materials, permit, and shift assignment.
• In progress — actively being worked by assigned technicians.
• Awaiting parts — work stopped for parts; include ETA and supplier contact.
• Blocked — blocked by outside teams, permits, engineering decisions, or safety holds.
• Complete — finished and closed after required checks (safety, QA, update CMMS).

Standard card fields (what every card shows)

• Asset: ID and short name
• Failure mode / symptom: concise description
• Priority: P1 (safety/production down), P2 (major impact), P3 (routine), P4 (improvement)
• Owner: primary assigned person or team
• ETA for parts: date/time or 'vendor contact + ETA'
• Expected MTTR: best estimate for restore
• Safety concerns: yes/no + short note if yes
• Age: hours/days since created (helps highlight stale items)
• Repeat flag: mark if this is a repeat failure (repeat count)
• Critical spares flag: indicate if this item needs a critical spare reorder

Example card

Daily 15‑minute huddle script (timeboxed)

1. 0:00–0:90 — Quick safety check and KPIs: PM compliance %, open P1 count, number awaiting parts, number blocked. Call out any immediate safety holds.
2. 1:30–6:30 — Review New → Triage → Planned columns: confirm owners, parts ETA, and whether work is correctly prioritized. Move any card lacking owner into 'Triage' and assign someone.
3. 6:30–10:30 — Inspect In progress, Awaiting parts, and Blocked: focus on items that put production or safety at risk within the shift or next shift. For each critical card state the current blocker and next action (who, what, by when).
4. 10:30–12:30 — Escalations: trigger escalation rules for items exceeding thresholds (see below). Confirm who will escalate and the expected follow‑up time.
5. 12:30–15:00 — Confirm actions, owners, short follow‑ups, and any handover notes. Call out one improvement idea to capture (Kaizen candidate) and who will log it after the huddle. Close the meeting on time.

Escalation rules (examples)

• Any P1 (production down or safety) not moved to In progress within 15 minutes → escalate to Maintenance Lead immediately.
• Any item in Awaiting parts with unknown ETA or ETA beyond next shift → maintenance planner contacts purchasing and vendor; if no update within 2 hours escalate to Maintenance Manager.
• Any asset with 2+ repeats in 30 days → create a failure-investigation ticket and escalate to Reliability Engineer within 24 hours.
• Items in Blocked for more than one shift without a clear next action → escalate to Operations Manager for coordination.

Rules of engagement (keep the huddle effective)

• Keep it short — no troubleshooting or work planning in the huddle. The goal is alignment, ownership, and clear next steps.
• Assign a timekeeper and a board owner (rotating role) to ensure actions are recorded and CMMS updated after the huddle.
• Use WIP limits for In progress (e.g., max 2–3 cards per technician) to avoid multitasking waste.
• Avoid blame: focus on removing blockers and reducing repeat failures. Capture root-cause work as separate investigations.

How to use the board beyond the huddle

• Groom backlog daily or every shift: validate priorities, check spare parts stock, and confirm planned dates.
• Track KPIs weekly from the board: backlog age, percent awaiting parts, mean time to repair (MTTR), PM compliance, and repeat-failure rate.
• Convert repeat or high-impact items into improvement projects and log them into the continuous improvement backlog with owners and due dates.

Avoiding common failures

• Hidden backlogs: require any unassigned card older than X hours to be escalated for triage.
• Parts bottlenecks: tag cards that require critical spares and trigger reorder rules when flagged twice in a month.
• Meeting drift: stop troubleshooting; assign owners to follow up and report status in the next huddle.

Integration and CMMS discipline

Ensure every board card links to or mirrors the CMMS work order. Board updates should be mirrored to CMMS at shift end so historical data (MTTR, backlog age, repeat failures) remains reliable for trending and improvement work.

How to start: Print a visible board, or implement the same columns in your CMMS/Kanban tool. Run the 15‑minute huddle for two weeks, tune timeboxes, and capture two process improvements that reduce recurring rush work.