Relative pronouns in English don't follow one clean rulebook
I spent three years helping engineers and analysts at client companies fix their business writing. The most common mistake I saw wasn't verb tense or prepositions — it was relative clauses. People would write sentences that were 40 words long and then stop making sense halfway through. Here's what actually matters when you're trying to use relative pronouns inglês correctly, not some textbook version but the way it works in real professional writing.
Practical differences between relative pronouns inglês
The basic set is who, whom, which, that, and whose. But here's what nobody explains clearly: "that" and "which" are not interchangeable, and choosing wrong can change how a sentence is parsed entirely. In restrictive clauses — the ones essential to the meaning — "that" is standard American usage. "Which" belongs in non-restrictive clauses, the ones set off by commas that add extra but optional information. I once worked with a software architect who wrote this in a project document: "The API endpoint which returns user data is deprecated." He meant the specific endpoint that returns user data — the clause was restrictive, defining exactly which endpoint. But he used "which" instead of "that," which in strict American style signals a non-restrictive reading. A British reader wouldn't necessarily blink at it, but the American audience reading it would mentally pause and re-parse the sentence. That's the kind of delay you want to eliminate in technical writing where every second counts.
The fix was simple — swap "which" for "that" — but the problem ran deeper. He didn't understand why it mattered. Most people I've trained don't. They treat "that" and "which" as synonyms. They're not. The difference is structural, not stylistic. When you use "which" where "that" belongs, you're telling the reader that the information following is an aside. When the information is actually essential, the sentence becomes ambiguous. Who and whom have a similar confusion factor. Who is the subject form, whom is the object form. But in practice, "whom" sounds stiff in most professional contexts. I'd recommend using "who" even when "whom" would be grammatically correct in almost every workplace writing situation. The only time it's worth using "whom" is in very formal documents like legal briefs or academic papers where that register is expected. Using it elsewhere draws attention to the word itself and distracts from your point.
Whose is the one people avoid unnecessarily. You can use "whose" for things, not just people. "The company whose CEO resigned" is perfectly correct, even though a company isn't a person. Some style guides tell you to avoid this, but they're wrong. It's concise and unambiguous, which is exactly what you want. Alternatives like "the company and its CEO resigned" or "the company of which the CEO resigned" are clunkier and offer nothing in return. Here's a quick reference for when to use each:
👉 Clique no botão abaixo para saber mais sobre o assunto!
- That — restrictive clauses, defining the noun. Essential information. No commas around the clause. This is the default choice in American English for defining clauses about things and people.
- Which — non-restrictive clauses, adding extra information. Set off by commas. Use when the clause could be removed without changing the core meaning of the sentence.
- Who — people as subjects. Also acceptable as objects in most modern usage.
- Whom — people as objects. Formal. Consider dropping it in favor of "who" unless your audience expects formal register.
- Whose — possession, for people and things. Don't avoid it for inanimate nouns.
- Where — places or situations. Useful but often misused as a substitute for "in which" in overly formal writing. "The situation where we need to act" is fine. "The situation in which we need to act" is redundant wordiness.
- When — time references. Same principle as "where." Keep it simple.
The one counter-intuitive thing that trips up almost everyone: you can omit the relative pronoun entirely when it functions as the object of the clause. "The report that I sent you" becomes "The report I sent you" and is still grammatically complete. This is called a zero relative pronoun, and it's extremely common in professional writing. Omitting it makes sentences tighter without sacrificing clarity. But you cannot omit it when it's the subject. "The report that arrived yesterday is missing" — you can't say "The report arrived yesterday is missing." The clause breaks because there's no subject marker. Another edge case I ran into recently: relative clauses with prepositions. "The tool with which I fixed the bug" sounds stiff. "The tool I fixed the bug with" is more natural, but some strict editors will mark it down as a dangling preposition. There's no right answer here. Know your audience. If you're writing for a traditional legal or academic context, keep the preposition before "which." If you're writing internal documentation, team updates, or anything meant to be read quickly, put the preposition at the end. Readability wins in most business contexts.
How to check your relative clauses quickly
When I'm reviewing someone's document, I use a simple test. Read the sentence aloud. If you naturally pause before and after a clause, it's probably non-restrictive and should use "which" with commas. If you don't pause at all, the clause is restrictive and likely needs "that" instead. This works about 90% of the time. The other 10% is where you have to think about whether the information is essential to identifying the noun. Here's a concrete example from a real contract I reviewed. The original read: "The vendor, which provides hosting services, must comply with SOC 2 standards." The commas signal non-restrictive, meaning there's only one vendor and providing hosting services is just extra detail. But the next sentence referenced multiple vendors. The clause was actually restrictive — it needed to specify which vendor. The corrected version: "The vendor that provides hosting services must comply with SOC 2 standards." No commas, "that" instead of "which," and the sentence now correctly identifies the specific vendor among several.
This kind of error doesn't usually cause immediate misunderstanding, but in contracts and technical specifications it can create ambiguity that costs time and money later. I've seen disputes arise from exactly this kind of clause placement. Not dramatic, not exciting, just painfully preventable if you know the rule. One final practical note: British and American English diverge most noticeably on this topic. British writers routinely use "which" in restrictive clauses, and it's considered acceptable there. If you're writing for a UK audience, don't stress about the "that" versus "which" distinction as much. But if your audience is American or international, stick to the restrictive/non-restrictive rule. It's the safer default.
Also worth noting: in spoken English, relative clauses get collapsed constantly. "The guy that I was telling you about" becomes "The guy I was telling you about" or even just "The guy from earlier." Speech is a different register entirely, and trying to force written rules onto conversation sounds robotic. But when you're writing — emails, reports, documentation — the rules matter more because the reader has time to notice them.
