Build a Personal Email Checklist for High-Stakes Messages

Start with the consequence

First decide what could go wrong if the email is inaccurate, incomplete, or sent to the wrong person. A scheduling note may mainly need a date and time check. A message that shares a proposal may also need a recipient, attachment, version, and confidentiality check. A request for approval should make the decision and response deadline clear.

Use that risk to decide what belongs on your checklist. Avoid making one long list for every email: irrelevant checks become easy to skip. Keep a short core list for all high-stakes messages, then add a few task-specific items. If the message changes purpose or audience, review the list again rather than assuming the old checks still fit.

Build a compact core list

A useful core checklist covers who will receive the message, whether the content matches the intended purpose, whether important details match their sources, and whether the message asks for a clear next step. Make each item a direct question you can answer, not a vague instruction such as “check everything.”

For recipients, consider To, Cc, and Bcc separately. Confirm each address and whether each person should receive the information. When replying or forwarding, inspect the full recipient list instead of relying on the thread’s previous audience. If a name or address appears similar to another, pause and verify it before sending.

• Are the recipients and recipient fields appropriate?
• Do names, dates, figures, and claims match the source?
• Are the intended files attached and correctly identified?
• Is the requested action and any relevant timing explicit?

Verify details from the source

Memory is useful for composing, but it is a weak final checker. Open the calendar invitation, approved document, order details, or other authoritative material and compare the email against it. Check names, spelling, dates, time zones when relevant, amounts, reference numbers, and any wording that could change a commitment.

For figures, compare the value and what it represents. A total, a per-person amount, and a date range are not interchangeable. If a detail is uncertain or the source conflicts with the draft, do not guess. Resolve the discrepancy or clearly ask for confirmation before presenting it as settled.

Treat attachments as part of the message

An attachment check is more than noticing that a file is present. Confirm that it is the intended document, that its name or version makes sense, and that it is appropriate for the recipients. If the message refers to a specific page, proposal, or revised file, verify that the attached item is the one described.

Then compare the draft with the attachment: do the dates, figures, and names agree? If you mention an attachment in the body, check that the file is actually included before sending. If there are several files, make the body clear about which one supports which request. Do not assume that a familiar filename proves the contents are correct.

Make the next step unmistakable

Readers should be able to tell what you need from them and what happens next. State the requested action plainly: review, approve, choose, provide information, or attend. Include a deadline only when it is real and supported by the task. If the recipient needs to respond to a particular question, put that question where it is easy to find.

Check that the tone and level of certainty match the facts. A tentative option should not read like a confirmed decision; a promise should not appear unless it is authorized and accurate. If the message contains a consequential commitment, compare that sentence with the relevant source or approval rather than relying on a quick reread.

Use a final pass that fits the task

Before sending, take one pass through the checklist in a consistent order: recipients, purpose, source-backed details, attachments, and requested action. Read the subject and opening alongside the recipient list; together they should make sense for the audience. Then scan the full message for leftover placeholders, contradictory dates, and text that belongs to an earlier draft.

A practical example for sending a proposal for review is: confirm the reviewer’s address and Cc list; compare the recipient’s name and review deadline with the project source; verify the proposal version and attached file; check that cited figures match the document; and state what feedback is needed. After each check, look at the relevant source or file. A completed tick is useful only if it reflects an actual comparison.

• Confirm the final draft and attachment are the versions you intend to send.
• If a detail cannot be verified, pause and resolve it instead of relying on recollection.
• After sending, confirm the message appears in the sent-message view and, if needed, that the expected attachment is shown there.

To: [reviewer]@example.com
Cc: [project contact]@example.com
Subject: [Project name] proposal for review by [verified date]

Please review the attached [verified proposal version] and send feedback on [specific section or question] by [verified deadline].

Final check: recipient fields match the intended audience; names, figures, and deadline match the project source; attached file is the intended version; requested action is clear.