Passive voice (was: Eschew, Evade, and/or Eradicate Legalese)

Subject: Passive voice (was: Eschew, Evade, and/or Eradicate Legalese)
From: Dave C <davec2468 -at- yahoo -dot- com>
To: Tech Writing <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Sun, 23 Nov 2014 07:46:05 -0800

What arguments do we make to management and/or document originators that passive voice is… well, bad? I’ve always found a tepid audience when trying to describe why.



> Of course, there'd still be plenty of work for us converting passive voice to active voice, structuring documents rationally, and all those other things we do that add value.
> [Mike Starr]

Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


Eschew, Evade, and/or Eradicate Legalese: From: Mike Starr

Previous by Author: How to mention distant-past experience on a resume?
Next by Author: Re: Passive voice
Previous by Thread: Eschew, Evade, and/or Eradicate Legalese
Next by Thread: Re: Passive voice

What this post helpful? Share it with friends and colleagues:

Sponsored Ads