Passive Voice Isn't Always Wrong: When to Use It
"Mistakes were made" gets mocked for a reason — it's passive voice doing exactly what critics accuse it of, hiding who did what. But that example gets stretched into a blanket rule that passive voice is always weaker writing, and that rule is wrong often enough to be worth pushing back on.
What passive voice actually is
Active voice: the subject performs the action. "The team shipped the update." Passive voice: the subject receives the action. "The update was shipped." Nothing in that second sentence is broken. It's a different lens on the same event, and it exists in every style guide because it's occasionally exactly what a sentence needs.
The reason passive voice earns a bad reputation is that it's frequently used to obscure responsibility, and it tends to add words without adding meaning. Both of those are real tendencies. Neither is a universal law.
When active voice really is better
Most of the time, yes, active voice is the stronger default. It's more direct, usually shorter, and it tells the reader who did what without extra inference. If you're describing an action and the actor matters to the reader — who fixed the bug, who approved the budget, who made the decision — active voice serves that better almost every time. This is why style checkers default to flagging passive voice: as a general-purpose heuristic, it's a decent one.
When passive voice is the right call
When the actor is unknown, irrelevant, or obvious from context. "The bridge was built in 1932" doesn't need "workers built the bridge in 1932" — nobody's asking who specifically swung the hammers. Forcing an actor into the sentence just to satisfy an active-voice rule adds clutter, not clarity.
When the action matters more than the actor. In scientific and technical writing, this is standard practice for a reason: "the sample was heated to 80 degrees" keeps the focus on the process, not on which lab tech turned the dial. Rewriting every methods section into active voice doesn't improve it — it shifts emphasis away from what the reader actually needs.
When you want to soften a statement diplomatically. "The deadline was missed" is a gentler opening than "you missed the deadline," and there are real contexts — feedback, incident reports, customer communication — where that softening is the right call rather than evasive.
When the receiver of the action is the topic of the paragraph. If your paragraph has been about a product, keeping the product as the grammatical subject ("the product was redesigned around user feedback") maintains a smoother thread than suddenly switching to "the design team redesigned the product," which shifts focus mid-thought.
When you genuinely don't know or can't disclose the actor. Passive voice isn't always evasive — sometimes it's accurate. "The data was leaked" might be a completely honest sentence if you don't yet know who leaked it.
When to actually fix it
Passive voice is worth rewriting when it's hiding an actor that the reader needs to know, when it's making a sentence noticeably longer for no gain, or when it's stacked with several other passive sentences in a row, creating a flat, distancing tone across a whole paragraph. That last one is a real pattern worth watching for — one passive sentence is a style choice, but five in a row usually signals the whole passage needs a rewrite for energy, not just grammar.
| Context | Passive or active — typical recommendation |
|---|---|
| Describing who made a decision or took an action | Active — reader needs to know who |
| Scientific/technical methods writing | Passive often appropriate — process matters more than actor |
| Actor is unknown or irrelevant | Passive is fine — forcing an actor in adds clutter |
| Delivering critical feedback or bad news | Passive can soften tone appropriately, used sparingly |
| Marketing copy and calls to action | Active — passive drains urgency and energy |
| Maintaining a paragraph's established subject/topic | Passive can preserve flow better than switching subjects |
| Multiple passive sentences in a row | Usually needs revision — signals a flatter tone throughout |
How to spot passive voice without overthinking it
A quick mechanical test works better than trying to memorize grammar terminology: if you can insert "by [someone]" after the verb and the sentence still makes sense, you're likely looking at passive voice. "The report was written [by the team]" works. "The team wrote the report" doesn't take the same insertion naturally, because the actor is already stated. This test isn't perfect for every sentence, but it catches the large majority of cases without requiring you to identify past participles or auxiliary verbs by name.
Another practical signal is length. Passive constructions frequently add a word or two compared to their active equivalent, because they need an extra form of "to be" to carry the sentence. If you notice a sentence feels slightly padded compared to how you'd say the same thing out loud, checking whether it's passive is a reasonable first diagnostic step.
A common overcorrection worth avoiding
Writers who've internalized "avoid passive voice" sometimes overcorrect into inserting an actor where none is needed, purely to satisfy the rule. "Three people were injured in the accident" becomes an awkward "The accident injured three people," which reads stranger than the original because it makes the accident itself into an active agent, which isn't how most readers naturally think about causation in that context. This is worth watching for specifically because it's a case where blindly applying the active-voice rule produces a worse sentence than the one it replaced — a sign that the rule was being followed mechanically rather than in service of actual clarity.
Passive voice in headlines and titles
One place passive voice reliably underperforms is headlines, where active voice's directness and brevity are almost always an advantage. "Company Fined for Data Breach" reads faster and hits harder than "Fine Issued Against Company for Data Breach." Headlines are read in a fraction of a second, and every extra word or indirect construction costs attention you don't get back. If you're auditing a piece for passive voice and short on time, headlines and subheadings are the highest-value place to check first.
The actual rule of thumb
Default to active voice, because it's shorter and clearer more often than not. But when you catch yourself rewriting a sentence into active voice purely to satisfy a rule, and the result reads more awkwardly than the passive version did, that's a sign the rule shouldn't apply here. Passive voice is a tool. Like most tools, it's bad only when it's used for the wrong job.
If you want a quick, second-opinion check on a piece before you publish it, Grammachine's readability checker flags passive voice among other patterns worth a second look — it's a prompt to reconsider, not a verdict to obey automatically.
For more writing-craft breakdowns like this one, sign up at /#lead.
Frequently asked questions
Is passive voice grammatically incorrect?
No. Passive voice is a normal, grammatically correct construction. The advice to avoid it is a style preference, not a grammar rule, and it's situational rather than absolute.
How do I know if a sentence is passive?
Look for a form of 'to be' plus a past participle, where the subject receives the action rather than performing it — 'the report was written' rather than 'she wrote the report.' If you can add 'by someone' after the verb, it's likely passive.
Why do style checkers flag passive voice so aggressively?
Because it's a fast, mechanical thing to detect, and it correlates with wordier, vaguer writing often enough to be a useful default warning. It doesn't mean every flagged sentence is actually wrong.
Does passive voice make writing weaker in general?
It often makes writing wordier and less direct, which is why active voice is the safer default. But 'often' isn't 'always,' and treating it as an absolute rule leads to worse writing in specific contexts, not better.
Should I turn off passive voice warnings in my style checker?
Not necessarily — keep the warning as a prompt to double-check the sentence, but don't treat every flag as something that must be fixed. Judgment beats a blanket rule here.