Team & People
Preventing Misdirected Emails for Beginners: Checks, External Email Rules, and Recovery Steps
Beginner | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)
Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.
Use this template to prevent misdirected external emails by setting pre-send checks and team rules for autocomplete, Cc versus Bcc, and attachments. First collect near-misses at work, sort causes into people, methods, machines, and materials, then pick high-impact, low-effort rules. It also covers traps: a password ZIP with the password in a second email does not count as a safeguard, since a wrong recipient tends to get both; Cc on group sends to outsiders shows all recipients every address; and senders who notice at once may stay silent, delaying contact. Start by reviewing To, Cc, and attachment names of external emails in your sent folder from the past week. If one goes out, follow five steps: contact the recipient, ask for deletion, tell your manager, record it, and prevent a repeat, with a promise not to blame early reporters. The 4 whiteboard pages run from cases to causes, rules, and response; the task board has 4 columns, 4 parent tasks, and 12 subtasks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Email Misdelivery Prevention for Beginners Board
How to use (4 pages): ① Write the goal and collect misdelivery cases (boards①–⑤) → ② Widen the causes into four bones and check traps (boards⑥–⑨) → ③ Rank rule ideas by effect and effort and table the rules (boards⑩–⑪) → ④ Set the 5 steps and owners for a slip (boards⑫–⑭)
1/4 Surface misdelivery moments
① Goal and scope (start writing here)
- Why make rules e.g. Last month a quote went to the wrong company. We must not repeat it
- Emails covered e.g. All external emails from the sales team. Internal-only emails are out of scope
- When to decide by e.g. Decide the rules by Friday of week 2 and start using them the next week
② Misdelivery cases (what happened, why it hurts)
| What happened | Why it hurts | Likelihood (1 to 5) | |
|---|---|---|---|
| Reply | e.g. "Reply all" sent an internal remark to an outside person too | e.g. The size of a discount discussed internally becomes known to the other party | e.g. 4 |
| Group send | e.g. An announcement sent with Cc showed every address | e.g. Other clients' names and addresses become known | e.g. 2 |
| Attachment | e.g. A quote for another company was attached and sent | e.g. Another company's prices and contact name go outside | e.g. 3 |
| Recipient autocomplete | e.g. A person from another company with the same surname showed up as a suggestion and the email went to them | e.g. A document that must stay inside reaches an unrelated person | e.g. 4 |
③ Close calls with recipients
- e.g. Just before pressing send, I noticed the recipient was a different person with the same surname
- What tipped you off, e.g. the company name in the signature looked different
- Write one of your own experiences
④ Close calls with attachments
- e.g. The quote file had the same name, and I almost attached last month's file for another company
- What tipped you off, e.g. opening the file before sending showed the wrong addressee
- Write one of your own experiences
⑤ Close calls with replies and group sends
- e.g. With "Reply all", an outside person I thought I removed was still in the recipients
- What tipped you off, e.g. there were more recipients than usual
- Write one of your own experiences
2/4 Widen the causes
⑥ Widen the causes of cases ② to ⑤ (fishbone diagram)
- Misdelivery to outside
- People e.g. In a hurry, I pressed send without reading the recipient
- Methods e.g. There is no rule on what to check before sending, even for external emails
- Machines e.g. Autocomplete puts a similarly named person first
- Materials e.g. The file name is just "Quote", so you cannot tell which company it is for
⑦ Trap: assuming a password ZIP plus a second email is safe
- What happens, e.g. if the recipient is wrong, the second email with the password tends to reach the same person
- How to check, e.g. read your company's rules on sending attachments and see whether this method counts as a safeguard
- A way to prevent it, e.g. share through the company's file-sharing service to named people only, with an expiry date
- Our workplace, e.g. we send to three clients this way. Discuss changing how we send
⑧ Trap: using Cc for several outside people
- What happens, e.g. every recipient sees the other people's names and email addresses
- How to check, e.g. open recent group sends in the sent folder and see whether outside people are lined up in Cc
- A way to prevent it, e.g. put several outside people in Bcc (a field hidden from other recipients), and have one more person look at the recipients before sending
- Our workplace, e.g. the monthly announcement email applies. General Affairs is in charge
⑨ Trap: not reporting even after noticing right away
- What happens, e.g. contacting the recipient and asking for deletion is delayed, and you find out only after it is forwarded
- How to check, e.g. see whether who to report to and how to reach them are written where everyone can see
- A way to prevent it, e.g. decide to tell your manager right away, and write a promise not to blame the person who reports (board⑭)
- Our workplace, e.g. no one is assigned to receive reports. Decide it in ⑬
3/4 Choose preventive rules
⑩ Line up rule ideas from ⑥ to ⑨ by effect and effort
Vertical axis: Effect (higher = bigger) / Horizontal axis: Effort (left = less, right = more)
- Decide now (big effect, little effort) e.g. For external emails, point at and read the recipient, Cc, and attachments before sending
- Plan and introduce (big effect, a lot of effort) e.g. Talk to IT about a setting that shows a confirmation screen for external sends
- Start with those who can (small effect, little effort) e.g. Tidy the address suggestions for people you email often and delete the ones you do not use
- Skip for now (small effect, a lot of effort) e.g. Wait for your manager to check every external email before sending
⑪ Rules chosen from the top left of ⑩ (rule, how, exception)
| Rule | How exactly | Exception | |
|---|---|---|---|
| Recipients | e.g. For external emails, pick the recipient again yourself | e.g. After using an autocomplete suggestion, compare what comes after @ with the other company's domain | e.g. With someone you write to daily, you may skip the comparison when just replying |
| Cc and Bcc | e.g. Use Bcc for several outside people | e.g. Put your own address in To and everyone else in Bcc | e.g. Cc is fine when everyone at the same meeting already knows each other's addresses |
| Attachments | e.g. Open the attachment and check its contents before attaching | e.g. Put the other company's name and the date in the file name | e.g. No exceptions |
| Check before sending | e.g. Read out the three items before sending | e.g. Point at and read the recipient, Cc, and attachments in that order | e.g. You may skip it for internal-only emails |
4/4 Act when it happens
⑫ Five steps for when an email goes out despite ⑪
- Contact the recipient Tell them it was sent by mistake e.g. Say by phone, "The email I just sent was a mistake"
- Ask for deletion Ask them to delete it unopened e.g. Ask them to delete the attachment without opening it and to reply once it is deleted
- Report to manager Tell what went where e.g. Give the recipient, the time sent, and what was attached. If personal information is involved, check with the internal contact and the latest official guidance on whether to notify
- Record Keep what happened e.g. Write the date and time, recipient, contents, and result of contacting them in the record table. Write what happened, not names
- Prevent a repeat Review the rules e.g. Review the causes with the four bones in ⑥ and add one rule or exception to the table in ⑪
⑬ Owners and contacts for the five steps of ⑫
| Owner | Contact | When to start | |
|---|---|---|---|
| Contact, deletion request | e.g. The person who sent it. On days off, a senior on the same team | e.g. The recipient's phone number (from their business card or signature) | e.g. Right after noticing |
| Report to manager | e.g. From the sender to the section manager | e.g. The manager's phone and the internal chat | e.g. A quick word right away. A detailed report the same day |
| Record, prevent repeat | e.g. The manager and the IT contact | e.g. The IT contact's desk (extension ____) | e.g. By the regular meeting next week |
⑭ Promise not to blame those who report
- Do not blame early reporters e.g. Answer someone who reports right away with "Thank you for telling us"
- Look for causes in the system, not the person e.g. Review the methods, machines, and materials bones in ⑥ first
- Record what happened, not names e.g. Write "in which scene and what", not "who", and share it at work
Task board contents
Not started 16 items
List risky moments
On page 1, write the goal and scope, then collect the misdelivery cases that happened or nearly happened at your workplace. The cases you gather here become the material for the causes and rules on the later pages. Press Ctrl+F (⌘F on Mac) and enter 3/4 to jump to page 3.
Review sent mail
Open your email app's sent folder, look through external emails from the past week, newest first, and check the To field, Cc field, and attachment names. Done when you write one email that caught your eye in a matching row of the table on board ② (about 15 minutes).
Set goal and scope
On board ①, write why you are making rules, whose emails they cover, and by when you will decide. Done when all three sticky notes are filled.
Add close calls
On boards ③ to ⑤, write close calls with recipients, attachments, and replies or group sends. After adding your own, ask coworkers for one each and add those too.
Widen the causes
On page 2, spread the causes of the page 1 cases across the four bones and check the traps that are easy to fall into. If the causes are not all just human slips, the rules you pick on page 3 become more concrete.
Fill in four bones
On board ⑥, looking at the cases on ② to ⑤, write at least one cause under each of people, methods, machines, and materials. Done when all four are filled.
Check ZIP and Cc
For the traps on boards ⑦ and ⑧, check how your workplace does it today and rewrite the notes on what happens, how to check, and a way to prevent it in your workplace's own words.
Check reporting gap
For the trap on board ⑨, check whether the place to report a misdelivery is written where everyone can see it. If not, write on a sticky note that you will decide it on page 4.
Choose the rules
On page 3, line up rule ideas by effect and effort, and tabulate the rules you can keep together with their exceptions. Once coworkers read the rules and agree, move the card to the Made a rule column.
Plot rule ideas
On board ⑩, create rule ideas from the causes in ⑥ and the preventive steps in ⑦ to ⑨ and place them. Pick three or more that land in the top left (big effect, little effort).
Table the rules
In the table on board ⑪, write the rule, the concrete way, and the exception for each scene. If an exception cell is empty, write No exceptions and you are done.
Show rules at work
Show the table on board ⑪ to everyone at work and ask what they cannot follow or what exceptions are missing. Done when you fix the table with their comments.
Act when it happens
On page 4, decide how to act and who does what when an email has gone out, and write the promise not to blame those who report. The aim is that, in a panic, anyone can open this page and see at once who does what.
Set the 5 steps
On board ⑫, write how your workplace does each of the five steps. Done when you have written down even what to say to the recipient.
Assign owners
In the table on board ⑬, write the owner, contact, and when to start for the five steps of ⑫ summarized in three rows. Also write a stand-in for days off.
Write no-blame rule
On board ⑭, write three promises not to blame people who report, and ask your manager to announce them in their own name. Done once everyone has heard.