Skip to content

Tips for Proofreading Emails Like a Pro

This month’s Better Writing at Work e-newsletter features the article “10 Tips for Proofreading Your Emails.”

Here are three of my favorite tips, followed by two that readers sent me:

1. Double-check the spelling of names. Check the signature block of any message you are replying to, to be sure you are writing to Kathryn rather than Katherine, Catharine, or Kathy. Also, be careful of organization names and abbreviations. The U.S. Coast Guard is not USGC. The Canadian Broadcasting Company is not CCB.

2. Check dates, times, and day-date combinations. Open your calendar to be sure May 1 is a Friday (it’s not). Also, check dates and times carefully before sending a meeting request, and remember that Outlook adjusts meeting times for the time zones of your recipients.

3. Test every hyperlink. Be sure it is live and accurate. Remember that your grammar and spelling checker will not flag a typo in a URL. Also, be sure the email describes the link accurately. For example, www.redcross.org does not link to a specific Red Cross endeavor, so an email should not suggest that it does.

4. Read your paragraphs backwards, that is, read the sentence at the end of the paragraph first, then the one above, and so on. This approach allows you to disassociate what you intended to write from what is actually there and to catch incomplete or incoherent sentences that have sneaked into revisions. (This tip came from Rachel Petrich of Port of Seattle.)

5. Be sure you have indicated the time zone of a meeting or a phone call when your reader is in another time zone. That way, when you write, “I will call you at 11 a.m.,” there is no confusion about whether you mean 11 a.m. Pacific Time or 11 a.m. Eastern Time. (This tip came from Tim Jones of NetSpeed Learning Solutions as an add-on to Tip 2 above.)

Lynn

Posted by Lynn Gaertner Johnson
By Lynn Gaertner-Johnston

Lynn Gaertner-Johnston has helped thousands of employees and managers improve their business writing skills and confidence through her company, Syntax Training. In her corporate training career of more than 20 years, she has worked with executives, engineers, scientists, sales staff, and many other professionals, helping them get their messages across with clarity and tact.

A gifted teacher, Lynn has led writing classes at more than 100 companies and organizations such as MasterCard, Microsoft, Boeing, Nintendo, REI, AARP, Ledcor, and Kaiser Permanente. Near her home in Seattle, Washington, she has taught managerial communications in the MBA programs of the University of Washington and UW Bothell. She has created a communications course, Business Writing That Builds Relationships, and provides the curriculum at no cost to college instructors.

A recognized expert in business writing etiquette, Lynn has been quoted in "The Wall Street Journal," "The Atlantic," "Vanity Fair," and other media.

Lynn sharpened her business writing skills at the University of Notre Dame, where she earned a master's degree in communication, and at Bradley University, with a bachelor's degree in English. She grew up in suburban Chicago, Illinois.

12 comments on “Tips for Proofreading Emails Like a Pro”

  • Thanks Lynn….very nice tips and very important. Allow me to add a few please –
    1) I insert the sender’s email id only after completing the email and double checking it. This helps in avoiding the risk of sending it in a hurry and then realizing that certain words or points could have been been drafted in a different way or may be deleted.
    2) Even while replying, I delete the ids and then reply (of course not applicable for routine replies…)

    Thanks and regards,
    Sanjay I – Pune,India

  • Thanks a lot. Very good points. For the sake of completion, here is two more:
    1) Double check the attachments to make sure you have attached them correctly and nothing is left out.
    2) Use the delay feature for sending emails, so you could come back if anything was forgotten. This feature is available in GMail and email applications like Outlook.

  • Lynn, that is a great list for editing. I may have to print it out and tape it to my monitor.

    My tip may sound weird but it works for me. I try to read each email (or at least business emails) three times before sending. This helps me catch typos and correct the tone of the email.

    I also try to imagine myself as the person receiving the email. This helps me remove vague statements and inappropriate jargon.

    Lisa

  • Hi, everyone. I am glad you like these tips. I hope you are also subscribers to “Better Writing at Work” so you can read the full list. If not, subscribe at http://www.syntaxtraining.com/signup.html

    Sanjay, your suggestions are excellent. Thank you!

    Ehsan, thank you for mentioning attachments. That tip is very important. I also like the idea of the delay, although I have not used it myself.

    Lisa, I agree: three times is the charm. It’s so important to proofread again, especially after making edits. The tiny edits, such as inserting a word that needs “an” before it instead of “a,” are the errors a third reading can catch.

    Phil, I am glad you like Rachel’s idea. I am going to try it too.

    Ruth, you are welcome!

    Lynn

  • Thanks for the great tips, Lynn. I teach a Business Communications course for community college students and always share your site in class. I suggest they read your posts regularly to pick up tips like the ones you’ve shared here.

  • For important emails, I also use Sanjay’s trick: I add the recipient’s email address at the last minute, when I am sure the rest is okay. If I am replying, I cut the recipient’s address out of the “To:” line and temporarily paste it at the top of the email text until the email and attachments are ready to go.

    George

  • Another way to catch errors is to change how the text looks. Use a different font (and/or colour) or cut and paste what you’ve written into a Word document and read it again. Of course, the surefire way of spotting an error is to hit ‘Send’. 😉

Leave a Reply

Your email address will not be published. Required fields are marked *