An email can be polished and still send someone to the wrong place, on the wrong day, or with the wrong amount in mind. The risky mistakes are often small: one digit, a missing unit, a date that means different things in different regions, or a familiar name attached to the wrong address. A deliberate final pass helps catch these before sending. Instead of rereading the message as a whole, check each detail against its source and ask what action the recipient will take if that detail is wrong.
The useful bits
- Check the recipient address and displayed name separately, especially when using autocomplete.
- Spell out dates and include units or currency wherever they could be misunderstood.
- Compare important figures with the original source, then reread the message for the action it requests.
Start with the person who will receive it
Check the To, Cc, and Bcc fields before reviewing the message body. Confirm that each address belongs to the intended person or group; a familiar display name is not enough. Autocomplete can select a different contact with a similar name, and a reply or forwarded thread can include people who no longer need the information.
If the message contains private details or asks someone to act, pause on every recipient. Ask whether each person should see the full message and whether the requested action is actually theirs. Remove unintended recipients before you send, rather than relying on a later correction.
To: [intended recipient] <[person]@example.com> Cc: [colleague who needs a copy] <[colleague]@example.com>
Match names to the right identity
Compare names in the greeting, message body, and attached-file references with the source you are using, such as the original request or an approved contact record. Look for similar names, swapped first and last names, and copied text left over from another message. If you are unsure how someone spells a name, check rather than guessing.
Identity matters beyond the greeting. A wrong person named in a subject line, schedule, handoff, or approval request can make the message appear to concern somebody else. Search the draft for names and check each occurrence in context.
Make the date hard to misread
Numeric dates can be ambiguous: a format such as 04/05 may be read as April 5 or 4 May, depending on convention. When the timing matters, spell out the month. Include the year when the message could be saved, forwarded, or acted on later. Add a time and time zone when a deadline or meeting depends on them.
Then compare the date with the source, not just with another place in your draft. If an email says a task is due on a named weekday, verify that the weekday and calendar date agree. If they conflict, clarify before sending instead of choosing one silently.
Less clear: Please send the file by 04/05. Clearer: Please send the file by 5 April [year].
Verify figures, currency, and units at the source
For an amount, quantity, measurement, or account reference, open the original source and compare the value digit by digit. Check decimal points, commas, negative signs, leading or trailing zeros, and whether the value is a total, a rate, or a per-item figure. Do not rely on memory or on a number copied earlier in the thread.
Give the figure its context. Add a currency label, measurement unit, or time period where needed; “250” alone may not tell the reader whether you mean dollars, items, or a monthly limit. If the source itself is unclear or inconsistent, resolve that uncertainty before asking someone to act on the number.
Read the message as an instruction
After checking individual details, read the email once from the recipient’s point of view. Identify the action requested and the relevant person, date, and figure. Ask: Could someone reasonably take a different action because a phrase is vague? If so, revise the wording rather than expecting the recipient to infer what you meant.
Pay particular attention to changes that are easy to overlook, such as “before” versus “after,” a revised deadline, or an amount that replaces an earlier one. Make the current instruction explicit. If a previous figure or date remains in the thread, distinguish the confirmed value from the superseded one.
Use a final pass that is easy to repeat
For consequential messages, use the same order each time: recipients, identity, dates, figures and units, then requested action. Checking one category at a time is more reliable than scanning the whole draft while thinking about several details at once. For critical values, put the source beside the draft and point to each character as you compare; this can help expose a transposed digit or misplaced decimal.
Finish by confirming that the corrected detail appears in every relevant place, including the subject, body, and any attachment you are describing. Then check the address fields once more immediately before sending. If the source cannot confirm a detail, hold the message and ask the appropriate person rather than presenting a guess as settled.
- Recipient: right address, right people, no unnecessary copy.
- Identity: names match the source and the context.
- Date: month written out; year, time, or time zone added when needed.
- Figure: compared with the source; currency or unit stated.
- Action: recipient can tell exactly what to do and by when.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction
