Writing Legal Content That Does Not Read Like a Brief

The reason most law firm content fails is not that the lawyer writing it lacks expertise. It is that the lawyer has spent a decade being trained, rewarded, and occasionally sanctioned into a single writing register, and that register was designed for a reader who is paid to finish the document. A judge reads your brief because the file is in front of them and the matter is on the calendar. A prospective client reads three sentences, decides whether you are talking to them or performing at them, and closes the tab. Those are not the same reader and they do not respond to the same prose.

Watch what happens when a partner sits down to write a page about, say, what a landlord can and cannot do when a tenant falls behind on rent. The instinct kicks in immediately. There is a heading with a statutory citation in it. There is an opening paragraph that establishes the scope of the discussion and notes that the analysis varies. There is a passive construction in the second sentence. Somewhere around paragraph four, after the framework has been properly laid out, the piece finally addresses the thing the person searching was frightened about, which was whether they were going to be locked out of their apartment on Friday. Everything in that page is correct. Almost nobody reaches paragraph four.

This is a translation problem, and it is solvable without lowering the substance. The firms that write well for prospective clients are not writing worse law. They are reordering it, stripping the terms of art that carry no information for a non-lawyer, and putting the qualifications where qualifications belong instead of where anxiety puts them. What follows is how that translation works in practice, sentence by sentence and section by section, including the question of where a disclaimer earns its place and where it just makes the page feel like a liability document.

The audience difference nobody names out loud

A brief has a captive reader, a known procedural posture, and an adversary who will exploit any imprecision. Every habit that follows from those three facts is correct in that context and wrong on a public web page. Front-loading the procedural history makes sense when the court needs orientation. Hedging every proposition makes sense when opposing counsel will quote your sentence back at you. Burying the conclusion at the end of the argument makes sense when the argument is what earns the conclusion. None of that survives contact with a person on a phone at eleven at night who typed a scared, specific question into a search box.

The client-facing reader has three things the judge does not have: an exit, an emotional state, and no obligation to grant you the benefit of the doubt. They are not evaluating the quality of your reasoning. They are running a much cruder test, which is whether this page seems to understand the situation they are in. If your first paragraph shows that you have understood the situation, you have earned the next paragraph. If it shows that you have understood the doctrine, you have earned nothing yet, because they cannot tell the difference between a lawyer who knows the doctrine and one who copied it, and every competitor page also has the doctrine on it.

Lead with the question they typed, not the doctrine that answers it

The single highest-leverage change most firms can make is mechanical. Take the question a person would have typed to land on this page, write it as the first heading or the first sentence in something close to their words, and answer it before you explain it. If the search was whether a stepparent can be made to pay child support, the page opens on that question and the first answer sentence says what usually happens, not what the governing framework is called. The framework goes in the next section, where it is a payoff rather than a toll booth.

Lawyers resist this because answering before qualifying feels reckless, and there is a real professional instinct underneath the resistance worth respecting. The resolution is not to skip the qualification, it is to sequence it. Say what is true in the ordinary case, then say immediately what changes it, then say what a reader in the unusual case should do next. That sequence is honest, it is complete, and it survives review. What does not survive is the version where the qualification arrives first and the answer never quite arrives at all, which is the version most firm pages currently publish.

Plain language is a subtraction, not a simplification

There is a fear that writing plainly means writing less accurately, and it is worth killing that fear directly because it stops good lawyers from publishing good work. Plain language does not mean removing the concept. It means removing the label when the label costs the reader more than it gives them. A term of art is a compression device built for people who already share the compression. Used with a lay reader, it is not precision, it is packet loss. Writing that a party has an obligation to preserve documents once litigation is reasonably anticipated conveys the actual thing. Writing that a litigation hold obligation attaches conveys the same thing to people who already knew it and nothing at all to everyone else.

The working rule is that any term you would need to define for the reader either gets defined in the sentence where it first appears or gets replaced by what it means. There is a real cost either way, so choose deliberately: define the term when the reader will encounter it again in their matter and needs to recognise it, and replace it when they will never hear it again. Nobody needs to learn the phrase in personam jurisdiction to understand that a court in one state may not be able to make an out-of-state company appear. But someone facing a probate matter genuinely does need to learn what an executor is, because everyone around them will use the word for the next eight months.

Kill the string cite, keep the authority

Citation habits translate badly. A page that carries four citations in its second paragraph reads to a lay person as defensiveness, not credibility, because they cannot check any of them and were not asking for proof. Yet stripping authority entirely is the wrong correction, since it leaves you sounding like every content mill page on the same topic and gives an informed reader nothing to trust. The middle position is one named, linked source per claim that carries real weight, placed after the plain answer, written the way a person would say it out loud. Naming the specific statute or the agency that publishes the rule and linking to it does more for trust than four parentheticals.

This has a second benefit that matters more every year. Answer engines and AI summaries increasingly surface passages that make a clean, self-contained, attributable claim, and a sentence that names its source in plain words is far more portable than one whose meaning is locked inside a citation format. Write the sentence so it still means something if a machine lifts it out of the page and shows it to someone who never sees your site. That is not a trick, it is simply what a well-formed sentence with an honest attribution looks like.

Structure for the skimmer and the reader at the same time

Most people who arrive on a legal page do not read it in the sense you mean when you say reading. They scan headings, stop at whatever matches their situation, read one section closely, and leave. That behaviour is not laziness, it is triage, and the page has to be built for it. Headings should be questions or statements a reader would recognise as their own problem, not topic labels. A heading that says "Statutory framework" tells a scanner nothing. A heading that says "What happens if you miss the filing deadline" catches exactly the person who missed it.

Then make the first sentence under every heading complete on its own. If the reader lands mid-page from a search result, that sentence is the whole page as far as they are concerned. Write it so it survives being the only sentence they read, and let the rest of the section deepen it rather than build up to it. This is the same discipline as an executive summary, applied at the section level rather than once at the top, and it is the structural change that makes a long page feel short rather than a short page feel thin.

Write the process, not just the rule

Prospective clients are rarely trying to learn the law. They are trying to find out what is about to happen to them, in what order, and how long it will take. A page that explains the doctrine and stops has answered a question they did not ask. The pages that convert are the ones that walk the sequence: this is what happens first, this is what you will be asked for, this is where the delay usually comes from, this is what the other side typically does at this stage. That content is harder to fake, which is exactly why it works, because a writer who has never run the matter cannot produce it.

Firms that manage matters in a structured system already own this content without realising it. The stages your firm uses in a matter stage tracker, configured for how your practice area actually moves rather than a generic template, are the outline of the process piece. So is the deadline diary, which encodes the sequence of dates that a client cannot see and is anxious about. Reading your own stage configuration for a practice area and writing a paragraph about each step produces a more useful page than a week of research, because it describes what your firm does rather than what the treatise says.

Where the disclaimer belongs

Most firm pages get this backwards by putting a block of defensive text at the top, which achieves the one thing the firm did not want, namely telling the reader before they have read a word that nothing here can be relied on. A disclaimer at the top is not more protective than a disclaimer at the bottom, it is just more visible, and visibility is not the same as effectiveness. The right position is at the end of the substantive content, where the reader has already got the value and is deciding what to do, and where a clear statement that this is general information and not advice for their specific situation reads as candour rather than as a warning label.

Make it specific rather than boilerplate. A disclaimer that names the jurisdictions the page is written about, states that rules differ elsewhere, notes that the page reflects the position as of a given date, and tells the reader to confirm their own position with a lawyer licensed where they are, does actual work. Generic boilerplate does not, and it is worth checking your own regulator's rules here because advertising and disclaimer requirements vary considerably. Several US states impose specific requirements on how firm marketing must be labelled, the Solicitors Regulation Authority takes its own approach in England and Wales, and Canadian and Australian regulators differ again at the provincial and state level. Confirm what your bar or regulator requires before you rely on any template, including this description of one.

Jurisdiction honesty reads as competence

There is a real fear that saying "this depends on where you are" makes a firm sound evasive, and it is misplaced. Vagueness sounds evasive. Specificity about where a rule changes sounds like someone who has practised. If a page about security deposits says that in most of the jurisdictions the firm practises in the landlord has a defined window to return the deposit, then names the states where that window differs materially, the reader learns two things at once: the answer, and that you are the kind of firm that knows the difference. Content mill pages cannot do this, because the writer does not know where the boundaries are.

This matters commercially, not just ethically. A page that is honest about jurisdiction attracts the readers you can serve and gently disqualifies the ones you cannot, which is the whole point of content that feeds an intake pipeline rather than a traffic dashboard. A firm licensed in three states does not want the volume from the other forty-seven, it wants the qualified enquiries from its own. Saying so in the page is cheaper than filtering it out later on a call that someone billed thirty minutes to.

The handoff between the page and the intake

The last paragraph of a content page is doing a different job from the rest of it, and most firms waste it. A reader who reaches the end has self-selected as someone with the problem you just described, which makes this the highest-intent moment on the entire page, and "contact us to learn more" squanders it. Tell them precisely what happens next: what the first conversation covers, how long it takes, whether it costs anything, and what they should have in front of them. Specificity about the next step converts far better than enthusiasm about the firm.

Then make sure the machinery behind that step is not the weak link. Intake that lands in a shared mailbox loses enquiries. Intake that lands in a structured system, where the enquiry becomes a contact with labels recording the role and the referral source that brought them in, and where a conflict check searches the full contact and matter history including closed matters and every role a party played, turns a page visit into something the firm can act on the same day. When that person becomes a client, the client portal they log into is real-time and privilege-filtered per document, with e-signature inside the same login and no separate account to create, so the experience the content promised does not collapse at the first handoff.

Keeping the page true after it publishes

Legal content decays in a way that most marketing content does not, because the underlying rules change and a wrong page is worse than no page. Every piece needs an owner, a review date, and a visible note of when it was last checked, and the review needs to be a calendar item rather than an intention. The lightweight version of this is a spreadsheet with a page, an owner, a date and a source to re-check. The version that survives a busy quarter is one where the review sits in the same system that holds the firm's other dates, so it competes for attention on equal footing with everything else the firm has committed to.

Version discipline matters here too, particularly when several people touch a page. Documents in a firm's system carry a comment field recording what changed and why, and applying the same habit to published content pays off the first time someone asks why a paragraph about a filing deadline was rewritten in March. Storing the source material and the approved draft where the firm already stores everything else, encrypted at rest with AES-256 under a per-firm key, keeps the marketing files under the same standard as the matter files rather than scattered across personal drives and email threads.

What this actually changes

None of this asks a lawyer to write worse. It asks for a specific set of reversals: the answer before the framework, the reader's words before the term of art, the process before the doctrine, the named source instead of the string cite, and the disclaimer at the end where it is candour rather than at the top where it is a shrug. Every one of those is a structural decision made before the first sentence gets written, which is why editing a brief-shaped page into a client-shaped one usually fails and rewriting it from the question usually works.

The firms that do this consistently end up with an asset that behaves differently from a marketing spend. A page written this way keeps working, keeps getting cited by the answer engines that increasingly sit between a person and a firm, and keeps producing enquiries from people who arrive already understanding what the firm does and roughly what the process will look like. Those are cheaper clients to sign and easier ones to serve, because the expectation-setting happened before anyone picked up the phone.

The last thing worth saying is that content is only half the system. A page that brings in the right enquiry and then drops it into an unstructured inbox has converted nothing, which is why the writing and the intake process have to be built as one thing rather than handed between a marketing effort and an operations effort. Casely is cloud-native with no local install and a Free plan at $0 to start, so the firm can wire the handoff properly before the content starts producing volume rather than after the first enquiry goes missing.