# Brief the team before consequential work starts

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

---

## Brief the team before consequential work starts

ID: MHC-D-RESEARCH-0366 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/brief-the-team-before-consequential-work-starts

Five minutes of shared plan can be cheaper than five different plans.

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

### Use when

- Several people will act in parallel on a task where role confusion or resource gaps can create failure.

### Avoid when

- Do not add a formal brief to low-risk work that one person can perform safely without coordination.

### Explanation

Before execution, align on the goal, roles, sequence, known risks, available resources and the signal that would require replanning. Keep the brief short enough to preserve momentum. Its output is a shared plan, not meeting minutes.

### Steps

1. The goal and success condition are explicit.
2. Each critical role has an owner.
3. Dependencies and sequence are understood.
4. Important constraints and resources are visible.
5. A trigger for huddling or stopping is named.
6. Open disagreements are resolved or escalated before execution.

### Example

Before a production mass update, identify who runs it, who watches locks, who validates results and who can stop the batch.

### Check

Team members can independently state the same goal, their role and the main stop condition.

### Limits

- Do not add a formal brief to low-risk work that one person can perform safely without coordination.

### Evidence and sources

- supports: AHRQ TeamSTEPPS brief guidance asks teams to align on goals, roles, responsibilities, plan, workload and resources before work. — RS-A1C0CC62DAC0EEBE. The brief should be proportional to the task; low-risk individual work does not need a team ceremony. (Brief checklist)
- RS-A1C0CC62DAC0EEBE: Sharing the Care Plan: Brief — https://www.ahrq.gov/teamstepps-program/curriculum/team/tools/briefs.html

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/huddle-when-reality-invalidates-the-plan
