The Clause and the Customer: Editing Legal Copy for Clarity, Caution and a Recognisable Brand Register

Terms and conditions, privacy notices and policy pages are often treated as the furniture of a website: necessary, rarely admired, and usually written by committee. When an editor is asked to make them 'more human', the risk is a swing from impenetrable legalese to breezy reassurance that promises more than the business can stand behind. Neither serves the reader. The useful middle ground is not a joke in the liability clause. It is a clear, consistent register that removes needless distance while leaving legal precision intact.

For UK businesses, the stakes are practical as well as reputational. A customer who understands when a refund is due, how to cancel, or what happens to their data is less likely to arrive at a complaint with a sense of having been misled. A reader who meets a wall of archaism may simply stop reading — and then claim they were never told. Editing legal copy is therefore an exercise in trust: not softening the obligation, but making the route to it visible.

Begin with the clauses you cannot move

The first pass is not a rewriting pass. It is a sorting pass. Isolate the provisions that carry legal weight: definitions, liability limits, termination rights, payment terms, data subject rights, statutory references and anything that has been drafted to withstand scrutiny. Mark them in the document and treat them as fixed unless a solicitor or compliance lead invites a change. An editor can improve the explanation around a clause without altering the clause itself.

This distinction matters because 'plain English' is sometimes used as a licence to flatten everything. It should not be. A liability cap is not clutter. A data retention period is not a tone problem. The editorial task is to ask, line by line: is this wording here because the law or the contract requires it, or because no one has troubled to say it more directly? The first category stays. The second is yours to revise.

Separate caution from habit

Legal drafting accumulates hedges for understandable reasons, but not every hedge is doing legal work. Phrases such as 'in relation to', 'for the purposes of' and 'shall be entitled to' often survive because they feel suitably formal, not because removing them would change the meaning. The test is whether the words carry an obligation, a condition, a time limit or a defined term. If they do, keep them. If they merely add distance, rewrite the surrounding sentence.

A cautious before-and-after, subject to legal review, might run as follows.

Before: 'The Company reserves the right, in its sole discretion, to suspend or terminate the User's access to the Services without notice where the Company reasonably considers that the User has breached any of these Terms.'

After: 'We may suspend or end your access to the service if we reasonably believe you have broken these terms. Where the law allows, we may do so without notice.'

The second version is not simply chattier. It identifies the actor, separates the trigger from the consequence, and keeps the discretion and the notice position visible. It also uses 'we' and 'you' consistently. That consistency is the beginning of voice.

Hold one register, not one tone

Voice in legal copy is often misunderstood as personality. In practice, it is closer to steadiness. A business that uses 'we' on its homepage and 'the Company' in its terms is asking the reader to change relationship mid-journey. A privacy notice that alternates between 'we', 'the organisation' and 'the data controller' makes the reader do unnecessary work. Decide on the grammatical person, the level of formality and the vocabulary, then apply them across the policy set.

For many UK businesses, a formal but direct register works best. It can use 'we' and 'you', short sentences and ordinary verbs, while avoiding contractions if that suits the brand. It should avoid both mock cheerfulness and institutional coldness. The aim is not to sound like a friend. It is to sound like the same organisation the customer has already chosen to deal with.

Headings carry much of this work. 'What we do with your information' is clearer than 'Data processing activities'. 'When you can cancel' is clearer than 'Termination rights'. A heading should answer the question the reader has arrived with, not describe the clause from the drafter's point of view.

Rewrite the explanation, leave the obligation

A useful method is to build each section in layers. The heading names the topic. A plain summary tells the reader what the clause means for them. The clause itself follows, with its defined terms and legal qualifications intact. Not every page needs all three layers, but the principle is sound: explanation can be edited for voice; obligation should be edited only for accuracy.

Consider a privacy notice sentence:

Before: 'We may process your personal data for the purposes of legitimate interests pursued by us as a controller, namely direct marketing, where you have not exercised your right to object.'

After: 'We use your details to send you marketing we think may interest you, because we have a legitimate interest in doing so. You can object at any time.'

The second version keeps the lawful basis and the right to object. It removes nominalisations and the unnecessary 'purposes of' construction. It does not pretend the processing is something other than marketing. That is the balance: the reader sees the substance, and the legal foundation remains visible.

Keep precision where it earns trust

There are places where a plain-English impulse must give way. Time limits should be exact: 'within 30 days', not 'about a month'. Liability exclusions should remain as drafted. Definitions should be used consistently, even when repetition feels clumsy. Data retention periods should be specific enough to be meaningful. Statutory rights, including those under the Consumer Rights Act 2015, should not be paraphrased into something more generous or more restrictive than the law allows.

The same applies to cross-references. If a clause says 'subject to clause 8.2', the reader needs to be able to find clause 8.2 and recognise it. Editing headings and summaries is helpful; breaking the mapping between them is not. A final check should confirm that every internal link, defined term and cross-reference still points where it should.

A line-level pass for policy pages

Read the page as a customer would, in the order they would meet it. Then edit in this order: mark the non-negotiable clauses; identify the reader's likely question at each heading; replace nominalisations with verbs; split sentences that carry more than one obligation; make the actor clear; remove hedges that do no legal work; keep terms that do; and check the register against the rest of the site.

Finally, have the revised text reviewed by whoever carries legal responsibility. An editor's role is to make the copy clearer and more consistent, not to certify compliance. The distinction is important, and it should be stated plainly in the handover. Good legal copy does not sound like a warning label. It sounds like a business that knows what it is promising, and can say so without hiding behind the small print.