Template
Make the subject line carry state and ask
The subject line is the first routing layer.
When it fits
- Inbox subjects such as 'Question', 'Update' or a ticket number provide no triage value.
When to avoid it
- Avoid putting sensitive data in subject lines when mail systems, notifications or policy make that unsafe.
A template to use
[Object] — [state / action needed] [by date if critical]
Why it matters
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.
An example
'49-208 — status correction needed before today's import' is more useful than 'Urgent question.'
Check your result
Someone scanning only subject lines can route the message correctly.
Keep this limit in mind
- Avoid putting sensitive data in subject lines when mail systems, notifications or policy make that unsafe.
Connected ideas
Useful withState what the reader must do before giving the history
Evidence and sources
ONS content guidance recommends frontloading important information because readers often scan for task-relevant material rather than reading linearly.
The guidance is for web content and is applied here by analogy to async work communication.
Writing and editing: Structuring content · Frontload your content and descriptive headings
ONS guidance recommends writing around user needs, removing content that does not serve those needs, and using concise task-focused headings.
Regulated or audit-heavy work may require context that feels redundant to the immediate reader.
Writing and editing: Plain language · Put users' needs first; titles and headings; be concise