Passive voice is one of those writing rules everyone has heard and almost no one fully understands. The instruction "avoid passive voice" appears in style guides, grammar checkers, and manager feedback. Yet passive constructions appear every day in well-written reports, legal documents, and professional emails, without anyone noticing. The real skill isn't avoiding passive voice. It's knowing when each form does the better job.
What passive voice actually means
In an active sentence, the subject performs the action: "The manager approved the budget." In a passive sentence, the subject receives the action: "The budget was approved by the manager." The subject and object swap roles, and a form of "to be" joins a past participle to carry the verb.
That structure does three things at once. It moves the focus from who did something to what was done. It lets the writer omit the actor entirely ("the budget was approved"). It slows the sentence down, adding words and sometimes muddying causation. That's why most writing guides tell you to cut it. They're right, most of the time.
Spell-check tools flag passive constructions automatically, but spell-check misses your worst mistakes because it doesn't understand context. A passive sentence that a grammar tool flags as a problem may be exactly the right construction for what you're trying to say.
When passive voice hurts your writing
Most of the damage passive voice does in business writing comes from one habit: hiding the actor when the reader needs to know who is responsible.
Consider a project update that says "Errors were introduced in the final report." That sentence protects someone. It tells the reader something went wrong, but doesn't say who introduced the errors or why. If accountability matters, and in most professional contexts it does, the passive construction is doing harm. "The data team introduced errors while importing the final spreadsheet" is harder to write, but it gives the reader information they can actually act on.
Passive voice also fragments the body of a business email in ways that readers notice even if they can't name them. When every sentence buries the actor, the email feels vague and evasive. Readers pick up on that register and trust the writer less.
The third problem is length. Passive constructions almost always add words. "The decision was made by the committee to delay the launch" takes eleven words. "The committee decided to delay the launch" takes seven. In high-volume professional communication, that extra bulk compounds quickly.
When passive voice is actually the right choice
There are four situations where passive voice earns its place.
The actor is unknown or irrelevant. "The server was upgraded overnight" is perfectly appropriate if the reader doesn't need to know which engineer did the work. Forcing an active construction here ("the infrastructure team upgraded the server overnight") adds information weight for no benefit.
The subject is the important thing, not who acted on it. "The proposal was rejected at the board level" keeps attention on the proposal and its fate, which is what matters to most readers of that sentence. In a progress report, where readers want to track the state of deliverables rather than follow every actor, this kind of passive construction is standard and appropriate.
You're deliberately softening bad news. This is a legitimate use, not a cowardly one. "Your application was unsuccessful" is less blunt than "We rejected your application." Both sentences carry the same fact. The passive version removes the pointed "we rejected you" dynamic, which can be the right call when you're communicating with someone outside your organisation. Use it deliberately, not reflexively.
You're writing in a field that uses it conventionally. Legal, scientific, and regulatory writing uses passive voice as a default. "The claim must be filed within 30 days" is standard contract language. Rewriting it as "you must file the claim within 30 days" might actually introduce ambiguity about who the "you" refers to. Know your genre.
A quick test for every passive sentence
Before you rewrite a passive construction, ask two questions. First: does the reader need to know who did this? If yes, rewrite actively. If no, the passive may stay. Second: does removing the actor change the meaning in a way that could mislead someone? If removing the actor makes the sentence evasive rather than simply concise, rewrite it.
Here's the test applied to a real example. "Mistakes were made during the onboarding process." Who made them? Does the reader need to know? If this sentence appears in an internal post-mortem, yes, the reader needs to know. Rewrite. If it appears in a public-facing summary where naming individuals would be inappropriate, the passive serves a real purpose.
One more thing: passive voice is only a problem when it's a reflex. Writers who reach for it consciously, for a specific reason, almost always use it well. Writers who reach for it out of habit, because it feels more formal or more careful, almost always use it badly. The difference is whether you can state why a sentence is passive before someone asks.
Recognising passive in your own drafts
The fastest way to catch passive constructions in your own writing is to read the draft aloud and listen for "was," "were," "is," "are," "been," and "being" paired with a past participle. That cluster is the passive voice signal. Not every instance is a problem. But each one deserves a second look.
A second technique: search for the word "by" in any document longer than a page. "The report was reviewed by the team." "The policy was drafted by legal." These are the passive constructions that include an actor, and they're almost always better rewritten in active form. "By" doing heavy structural work is a clear sign the sentence was built backwards.
A structured proofreading checklist catches passive constructions more reliably than a single read-through, precisely because you're looking for one category of problem at a time rather than everything at once. Give passive voice its own pass. You'll find more of it than you expected, and you'll fix the ones that matter.
Passive voice isn't a writing sin. It's a tool with a specific job. Use it for that job, cut it everywhere else, and your business writing will be sharper for it.