# Huddle when reality invalidates the plan

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Huddle when reality invalidates the plan

ID: MHC-D-RESEARCH-0367 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/huddle-when-reality-invalidates-the-plan

Do not keep executing the old plan while privately admitting it is obsolete.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Conditions, workload, team availability or evidence change enough that the existing plan is no longer reliable.

### Avoid when

- A huddle is a replanning tool, not a recurring status meeting with no changed decision or action.

### Explanation

Pause briefly, state what changed, identify which part of the plan is now invalid, redistribute work or alter the sequence, and restate the updated plan. Any team member should be able to call the huddle when they see a material change. End when the new shared plan is clear.

### Steps

1. The team leaves with an updated plan that explicitly responds to the changed condition.

### Example

A key expert becomes unavailable during a cutover; the team huddles to reduce scope and reassign the validation role.

### Check

The team leaves with an updated plan that explicitly responds to the changed condition.

### Limits

- A huddle is a replanning tool, not a recurring status meeting with no changed decision or action.

### Evidence and sources

- supports: AHRQ TeamSTEPPS recommends a huddle when conditions, membership or plan effectiveness change enough to require replanning. — RS-E4B2297A7C4B514A. A huddle should change the plan or shared state; recurring updates without a decision need are a different meeting. (Monitoring and Modifying the Plan)
- RS-E4B2297A7C4B514A: Monitoring and Modifying the Plan: Huddle — https://www.ahrq.gov/teamstepps-program/curriculum/team/tools/huddle.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-one-person-the-incident-command
