# Escalate concern with a shared signal phrase

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

---

## Escalate concern with a shared signal phrase

ID: MHC-D-RESEARCH-0369 · Version: 0.1.0 · Kind: pattern
Source: https://vedokrok.com/knowledge/escalate-concern-with-a-shared-signal-phrase

Sometimes the useful upgrade is not louder speech but less ambiguous speech.

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

### Use when

- A team needs unmistakable language that says a disagreement has crossed into material risk.

### Avoid when

- Do not label routine disagreement a safety issue; overuse destroys the shared meaning of the escalation signal.

### Explanation

Use graduated shared language: state that you are concerned, then why the situation makes you uncomfortable, then explicitly name the safety or material-risk issue if it remains unresolved. The value comes from the team agreeing that these phrases change the response mode.

### Recognition

I am concerned because [evidence]. I am uncomfortable proceeding while [unresolved risk]. This is a material safety/risk issue because [possible harm].

### Example

'I am concerned that the file contains production IDs. I am uncomfortable running it without reconciliation. This is a data-integrity risk because the update is irreversible.'

### Check

The listener recognizes that the message requires resolution or escalation rather than ordinary debate.

### Limits

- Do not label routine disagreement a safety issue; overuse destroys the shared meaning of the escalation signal.

### Evidence and sources

- supports: AHRQ's CUS tool provides graduated signal phrases—concerned, uncomfortable, safety issue—to make escalating risk explicit to the team. — RS-E5A18A777943BA7F. Use safety language only for material risk; overuse weakens the shared signal. (CUS steps)
- RS-E5A18A777943BA7F: Tool: CUS — https://www.ahrq.gov/teamstepps-program/curriculum/mutual/tools/cus.html

No review details supplied.
