The Grammar of Identity and Reference
I spent a good chunk of time in my early twenties working as a technical writer for a legal tech platform, and one of the more frequent tickets we got was from users confused about relative clauses. They would type "the person who is coming" versus "the person whom is coming" and genuinely not understand why one felt wrong even though the sentence structure looked identical at first glance. That confusion reveals something most grammar guides gloss over: the word "who" carries weight beyond its basic function as an interrogative pronoun. At its foundation, who serves two distinct grammatical roles. It functions as an interrogative pronoun when asking questions about people. It also operates as a relative pronoun when introducing dependent clauses that modify nouns. That basic distinction matters because the relative pronoun usage is where things get genuinely complicated, and it is where most style guides fail to provide useful guidance. The interrogative use is straightforward enough. You are asking about the identity of a person or people. But the relative clause application has real implications for how sentences parse and how readers interpret your meaning. When you write "the author who wrote this book died last year," you are creating a restrictive clause. The clause specifies which author. When you write "my uncle, who lives in Ohio, is visiting," the clause is non-restrictive. It adds information without narrowing down which uncle.
I learned to spot this distinction quickly, but I had a much harder time explaining it to developers building search indexing tools. One particular problem came up when we were designing a natural language query parser for a document retrieval system. The parser kept failing on sentences like "find the researcher who published papers on machine learning in 2019 versus those who published in 2020." The relative clause structure created ambiguity about whether "who" referred to the same researcher across both time periods or different groups entirely. We ended up writing a custom regex layer that identified the antecedent of "who" by tracking noun phrases across clause boundaries, then cross-referencing temporal markers to resolve the scope. That workaround added about three weeks of development time but reduced false positives from 40 percent down to roughly 8 percent. Not perfect, but workable.
Common Pitfalls That Trip Up Experienced Writers
Most grammar advice stops at the who versus whom distinction, which is useful but incomplete. The more subtle errors come from misplaced modifiers and antecedent ambiguity. Consider the sentence "she told the teacher who was absent." Is she reporting that the teacher was absent, or is she describing the person she told? The reader has to backtrack to figure out who the relative clause actually modifies. I see this kind of structural ambiguity in code comments all the time. Developers assume the variable name makes the reference clear, but the pronoun chain creates a genuine parsing problem. Another frequent mistake involves singular versus plural antecedents. "Each of the students who have completed the assignment may submit." Some editors will insist on "has completed" because they see "each" as the governing noun. Others will argue for "have" because "students" feels closer to "who." Both readings exist in published work. The truth is that usage varies by style guide, and there is no universal rule that resolves every case cleanly. My own practice has been to consult the specific style manual required by the publication or organization, then apply it consistently. Inconsistency matters more than the choice itself.
Get the Full Details
Advanced Usage in Legal and Technical Writing
Legal documents push the relative pronoun to its limits. You will encounter constructions like "any party who shall fail to comply with the terms of this agreement" that feel stilted but persist because legal drafting conventions prioritize precision over readability. The word "who" anchors the obligation to a specific category of person. Switching to "which" would collapse the entire grammatical structure and change the legal meaning. I once spent an afternoon tracking down why a contract clause was being interpreted differently by two counsel. The issue traced back to a missing comma after "party" that turned a restrictive clause into something ambiguous. A single character change shifted the obligation from a defined group to an undefined set of actors. That experience reinforced how little room there is for carelessness in this space. Technical documentation faces a similar challenge, though the stakes are different. Consider API reference material where you describe behavior tied to specific user roles. "An administrator who has enabled multi-factor authentication must verify their identity each session." If you accidentally remove the relative clause, you change the rule from applying only to a subset of administrators to applying to all administrators. The grammatical structure encodes policy. Writers who treat this as optional or decorative are not doing their readers any favors.
Limits of the Word and When to Choose Alternatives
The word "who" does not work for everything. It applies to people and personified entities. When referring to organizations, animals, or inanimate objects, "which" or "that" is the standard choice, though some style guides permit "who" for animals with individual names in narrative writing. Using "who" for a corporation is generally marked as informal or stylistically marked, and in technical contexts it will read as imprecise. Even within its proper domain, "who" has constraints. Compound antecedents joined by "or" or "nor" create agreement problems that "who" does not resolve neatly. "Neither the manager nor the employees who submitted the report" leaves you uncertain about whether the relative clause attaches to the nearest noun or the entire compound. Rewriting the sentence eliminates the ambiguity faster than trying to force "who" to carry the weight. I tend to recommend rephrasing over consulting a grammar table for these cases. A clearer sentence beats a grammatically defensible one in practical writing. There are also dialectal and register variations worth noting. In many varieties of English, especially in spoken usage and informal writing, "who" frequently replaces "whom" without marking the distinction. This is a real feature of the language, not an error per se, but it can signal carelessness in formal technical writing if applied indiscriminately. Knowing when to preserve the distinction and when to let it go is part of the skill, and it comes from reading widely and editing your own work multiple times rather than following a single rigid rule.
Practical Guidance for Better Usage
The most useful approach I have found is to read sentences aloud before finalizing them. Your ear catches structural problems that your eyes skip over. A sentence where "who" is attached to the wrong noun will often feel awkward when spoken. This is not foolproof, but it catches a meaningful percentage of errors without requiring you to diagram every clause. When working with relative clauses, identify the antecedent first, then check whether the clause is restrictive or non-restrictive, then verify that the verb agreement matches the antecedent. That sequence works for the vast majority of cases. For edge cases that resist this process, step back and rewrite. There is no penalty for restructuring a sentence to avoid a tangled relative clause. I also keep a running list of sentences that gave me trouble during editing. Over several years this accumulated into a small personal reference that covers the exceptions and ambiguities I encountered most often. It is not comprehensive, but it covers the patterns that actually show up in the work I do. You can build something similar if you track your own recurring mistakes rather than memorizing rules that rarely apply to your specific writing context.
The word "who" is simple in definition and deceptively complex in practice. It carries grammatical relationships, legal obligations, technical specifications, and stylistic signals all at once. Treating it with the attention it deserves improves clarity across every genre of writing, even if the improvements are incremental rather than dramatic.
