# Make the subject line carry state and ask

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

---

## Make the subject line carry state and ask

ID: MHC-D-RESEARCH-0606 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/make-the-subject-line-carry-state-and-ask

The subject line is the first routing layer.

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

### Use when

- Inbox subjects such as 'Question', 'Update' or a ticket number provide no triage value.

### Avoid when

- Avoid putting sensitive data in subject lines when mail systems, notifications or policy make that unsafe.

### Explanation

Use the subject to encode the object plus current state or required action. Keep details in the body. For recurring threads, update the subject when the state materially changes instead of preserving a misleading old label forever.

### Template

[Object] — [state / action needed] [by date if critical]

### Example

'49-208 — status correction needed before today's import' is more useful than 'Urgent question.'

### Check

Someone scanning only subject lines can route the message correctly.

### Limits

- Avoid putting sensitive data in subject lines when mail systems, notifications or policy make that unsafe.

### Evidence and sources

- supports: ONS content guidance recommends frontloading important information because readers often scan for task-relevant material rather than reading linearly. — RS-97DF2212DB5C5E61. The guidance is for web content and is applied here by analogy to async work communication. (Frontload your content and descriptive headings)
- 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-97DF2212DB5C5E61: Writing and editing: Structuring content — https://service-manual.ons.gov.uk/content/writing-for-users/structuring-content
- 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/state-what-the-reader-must-do-before-giving-the-history
