Maintenance KPI Huddle — 15-minute Agenda & Template

Purpose

A concise 15‑minute huddle to keep maintenance teams aligned on backlog health, preventive-maintenance (PM) compliance, and early warning signs on critical assets so issues get prioritized, owned, and either resolved or escalated before they become chronic losses.

When & Who

Cadence: daily or shift‑change, 15 minutes sharp.
Participants: maintenance lead (facilitator), shift supervisor, on‑duty technicians, reliability engineer (as needed). Limit attendees to those who contribute decisions or actions.

Roles

• Facilitator: keeps time, runs the script, ensures owners are assigned.
• Metric Owners: update their metrics before the huddle and speak to deviations.
• Action Owners: accept assignments, confirm target and verification method.
• Escalation Owner: person or role who will escalate per rules (e.g., Maintenance Manager).

Timeboxed Agenda (15 minutes)

1. Quick metric roll-up — 5 minutes

   Facilitator reads the snapshot. Metric owners call out only exceptions (out of tolerance) and one-sentence context.

2. Top 3 risks & short containment — 5 minutes

   Cover the three highest-risk open items (asset, symptom, immediate containment). State current impact (production lost hours or safety risk) and containment taken.

3. Assignments & verification plan — 3 minutes

   Assign clear owners, next action, due time, and verification method (photo, sign‑off, test result, updated work order).

4. Escalations & blockers — 2 minutes

   Apply escalation rules for items that meet thresholds (see below). Note blockers that need support outside the team.

Facilitator Script (keep it tight)

Start on time. "Today’s snapshot — exceptions only. Metric owner X, short note." Move quickly: if troubleshooting is needed, schedule a follow-up; do not convert this into a troubleshooting session.

Metrics Snapshot Template

Keep this visible for the huddle (whiteboard, shared screen, or printed sheet). Metric owners update values before the meeting.

Top 3 Risks Template (use one row per risk)

• Asset: pump A3 — Symptom: overheating; Impact: 2 hr/day lost; Containment: reduced load; Owner: Miguel; Next action: vibration capture by 10:00; Due: today 16:00.

Assignment & Verification Rules

• Each assignment must have one owner, one measurable next step, and a due time.
• Verification must be explicit: photo, work-order status, test result, or supervisor sign‑off.
• Unfinished actions roll into the next huddle with an updated plan or are escalated per rules.

Escalation Rules (examples)

• Any critical asset risk with expected downtime > 4 hours → escalate to Maintenance Manager within 30 minutes.
• Backlog > threshold (e.g., > 10 open high‑priority orders) → escalate to Planning to reassign resources.
• PM compliance < target for two consecutive weeks → escalate to Reliability for root-cause review.

Pre-huddle Preparation

• Metric owners update the snapshot 15 minutes before the huddle.
• Bring evidence for any exception (photos, work‑order IDs, short data printouts).

Post-huddle Follow-up

• Record action items in the CMMS/work‑order system within 1 hour.
• Owner updates the item status before the next huddle or confirms escalation.

Common Pitfalls (Mal Hungers) — Avoid These

• Turning the huddle into a troubleshooting workshop — schedule a separate problem‑solve if needed.
• Using the meeting for blame — focus on facts, containment, and owner commitments.
• Allowing vague owners or missing verification — both kill follow-through.

Quick Checklist for Every Huddle

1. Start on time, confirm timekeeper.
2. Read exceptions from the snapshot (60–90 seconds each max).
3. Agree on top 3 risks and containment (1 minute each).
4. Assign owners, due times, and verification methods.
5. Apply escalation rules where thresholds are met.
6. End with one sentence: who does what by when.

Use this agenda as the standard for teams, and consider packaging the snapshot template and action log as a reusable checklist or interactive form so every huddle reliably produces recorded, auditable outcomes.