Huddle Facilitator Scripts & Escalation Matrix

Welcome — Purpose & Promise

Huddles are short, disciplined conversations that turn data into action. These scripts help facilitators run consistent, outcome-oriented daily and weekly huddles that surface risks and opportunities, assign clear owners, and escalate issues with predictable response times. Use the scripts as spoken prompts, not walls of text. Keep the rhythm tight: identify, assign, act, and follow up.

Core Roles

• Facilitator: Keeps time and enforces agenda; ensures decisions and owners are captured.
• Timekeeper: Optional for larger groups; calls out remaining time and enforces cadence.
• Data Owner / Reporter: Briefly presents the facts (metrics, exceptions, tickets).
• Action Owner: Person accountable for an item and follow-through.
• Escalation Contact(s): Named individuals or roles for cross-functional or elevated issues.

Daily Huddle — 10-minute flow (Script)

Goal: Rapid surface of red/amber/green items, confirm owners, and create any required escalations.

1. Start (30–60s) — Facilitator: “Good morning. Let’s run a tight 10-minute huddle. Our aim is to confirm today’s priorities, surface anything blocking delivery or safety, and assign owners for actions.”
2. Quick Metrics Snapshot (60s) — Data Owner: “Key numbers: [safety], [quality], [delivery], [OEE]. Current status: red, amber, or green.” Keep to one sentence per metric.
3. RAG Calls (3–4 min) — Facilitator: “If you’re green, say ‘Green’ and call one improvement. If amber, say ‘Amber’ and name the risk. If red, say ‘Red’ and briefly state the blocking issue and who owns next steps.”
   • Each person: 20–30 seconds.
   • If an amber/red needs >2 minutes, capture as an action and move on; consider escalation per matrix.
4. Owner Check-ins (2–3 min) — Facilitator: “Owners from yesterday, quick update: done, in progress, or blocked.” Owners answer in one sentence. If blocked, record escalation trigger.
5. Escalation Triage & Assign (60–90s) — Facilitator: “We have X escalations. Who owns next action and when will it be resolved/updated?” Capture owner and due time. If cross-functional or high-impact, follow escalation matrix (see below).
6. Close (15–30s) — Facilitator: “Summary: owners and due times. We’ll follow up in tomorrow’s huddle. If this item requires coordination before then, owner will escalate to [role] now.”

Daily Facilitator Quick Script (Copy-and-Read)

“Good morning. Ten-minute huddle: metrics, RAG calls, owner check-ins, and any escalations. Metrics: [read numbers]. RAG calls — green, amber, red? (go around). Owners: quick updates. Any items requiring escalation? If yes, I’ll record owner and trigger the escalation matrix. Summary: [state owners and due times]. Thanks, see you tomorrow.”

Weekly Huddle — 30–45 minute flow (Script)

Goal: Trend review, cross-functional coordination, remove systemic blockers, and update escalation status.

1. Opening (1–2 min) — Facilitator: “Weekly huddle: review trends, progress on escalations, and pick 1–3 improvement experiments.”
2. Trend Review (8–12 min) — Data Owner: Show short trend lines for last period (safety incidents, defects, on-time delivery, process yield). Facilitator asks: “What changed? Any root-cause leads?”
3. Escalation Status (8–10 min) — Review all open escalations, owners, actions taken, and ETA. If an item remains unresolved beyond expected SLA, bump per escalation matrix.
4. Cross-functional Blocking (6–8 min) — Surface items that need another team’s input. Assign liaison and timeline.
5. Improvement Experiments (6–8 min) — Pick 1–3 small experiments (PDCA/plan-do-check-act). Assign owner, measure, and expected check-in date.
6. Wrap (1–2 min) — Confirm owners and next check-in. Document any high-priority escalations that require leadership attention.

Escalation Matrix (Use to decide when and how to escalate)

Escalate when an issue meets one or more triggers: safety risk, customer-impacting defect, >X hours stoppage, cross-functional blocker >24 hours, repeated failure, or resource/skill gap preventing resolution.

Escalation Capture Template (copy into your issue tracker or form)

Use this set of fields when capturing items in the huddle. These fields are intentionally short so the facilitator can capture them in real time. Consider converting to an interactive form for faster recording.

• Issue Title: One-line summary
• Issue ID: (auto-generated by tracker or create quick ID)
• Date/Time:
• Raised By:
• Impact: safety / quality / delivery / cost (choose one or more)
• Severity / RAG: Red / Amber / Green
• Short Description: 1–2 sentences
• Immediate Owner: name and role
• Escalation Level: 1–4 (per matrix)
• Due/ETA: date/time
• Next Update: date/time and expected channel (huddle, email, ticket)
• Notes / Actions Taken: brief log entries

Facilitator Checklist (one-page)

1. Start on time; state goal and timebox.
2. Read metrics succinctly.
3. Run RAG round; enforce 20–30s per person.
4. Record owners and due times for every amber/red.
5. Decide escalation level at the moment an item is surfaced.
6. Confirm owner acknowledges and accepts the due time.
7. Summarize owners and next update before closing.
8. Log captured items into the issue tracker or escalation form (see template).
9. Close on time; assign who will communicate externally if required.

Owner Check-in Mini Script

When the facilitator asks an owner for an update, encourage this concise response format:

“Status: [done / in progress / blocked]. Current action: [what I’m doing now]. ETA or next update: [time or huddle]. If blocked, escalation needed: [yes/no] — desired help: [one sentence].”

Training Tips & Common Pitfalls

• Keep the huddle short — long troubleshooting belongs in a separate troubleshooting session.
• Don’t let experts dominate; capture their input as an action if deeper discussion is needed.
• Enforce the owner acceptance rule: an owner must explicitly accept a task and a due time.
• Use visual cues (kanban, dashboard, RAG board) to speed the RAG calls and keep attention focused on exceptions.
• Review closed escalations weekly to capture lessons and prevent recurrence.

Where to Put This Into Practice

Train facilitators with role-play: simulate a 10-minute huddle and practice capturing two escalations. Use decks 1130 and 165 as referenced for site templates and dashboard links. Consider a short facilitator competency checklist: punctuality, RAG enforcement, capture quality, and escalation accuracy.

Next Steps — Make it Operable

Recommended immediate actions:

1. Adopt the daily and weekly scripts as standard operating practice for your site.
2. Configure an escalation form (fields listed above) in your tracker or on the platform so facilitators can log issues during the huddle.
3. Assign clear escalation contacts for each level and publish them in the huddle area and team handbook.
4. Run a facilitator calibration session once a month to keep behaviors aligned.

Use this pack to reduce facilitator variability and to ensure huddles move issues from talk to owned action.