# Split a message when it asks for unrelated decisions

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

---

## Split a message when it asks for unrelated decisions

ID: MHC-D-RESEARCH-0609 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/split-a-message-when-it-asks-for-unrelated-decisions

Bundling saves sending effort but increases routing ambiguity.

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

### Use when

- One long message asks different people to decide unrelated things.

### Avoid when

- Do not fragment tightly coupled choices that need a shared trade-off; split only when independent closure improves coordination.

### Explanation

Keep one dominant coordination job per message or section. If two decisions have different owners, deadlines or evidence, split them into separate messages or clearly isolated sections so each can close independently.

### Example

A design approval and a production access request become separate asks because different people own them.

### Check

Each decision can be answered without resolving an unrelated issue.

### Limits

- Do not fragment tightly coupled choices that need a shared trade-off; split only when independent closure improves coordination.

### Evidence and sources

- supports: CDC guidance recommends lists, chunks and descriptive headings to make information easier to scan and organize. — RS-B843492FBF1442AD. Very short messages may not need headings; structure should match complexity. (Core items 8 through 10)
- supports: ONS guidance recommends writing around user needs, removing content that does not serve those needs, and using concise task-focused headings. — RS-96557E8AD37744B8. Regulated or audit-heavy work may require context that feels redundant to the immediate reader. (Put users' needs first; titles and headings; be concise)
- RS-B843492FBF1442AD: Description and Examples of Index Items — https://www.cdc.gov/ccindex/tool/description-examples-parta.html
- RS-96557E8AD37744B8: Writing and editing: Plain language — https://service-manual.ons.gov.uk/content/writing-for-users/plain-language

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/put-owner-output-and-deadline-on-the-same-line
