The bytes // they want you

“Essential statement → main points → detailed information” structure. Sections clearly separated, included only if justifiable.
Action items, questions and answers clearly organized: separate lines, identifiable, responsible person mentioned.
Subject is concise, relevant and specific-enough to be distinguishable and searchable.
Subject contains a label for expectation management, urgency, or context.
Message reviewed and the best practices applied, even if rewriting needed.

The message starts with a short, essential statement, continues with the main points behind the statement, then supported by detailed information. These sections are clearly separated. Latter sections are included only if justifiable.
The action items, questions and answers are clearly organized: located on separate lines, identifiable (by numbers, identifiers, or embedded references), with the responsible person mentioned.
The subject is concise and relevant to the message’s content. It contains enough specific information to distinguish it from other emails and to aid in searchability.
The subject contains a notable, conventional label that clearly communicates the message’s purpose. The label indicates expectation management (action required, information, …), urgency (urgent or not, specific date), or context (project name).
I reviewed the message and applied all the best practices which I am committed to following, even if it meant rewriting parts of the message.

Checklist: Sending email