What does a rotten template look like?
It rarely looks broken. It opens, it has the logo, the headings are all there. The problems are in the detail. The engagement letter still refers to a previous name for a regulator. The proposal still lists a service line the firm dropped. The limitation clause is the version the insurers asked the firm to change. The fee section describes a billing arrangement nobody has used in years. The contact block names someone who has left.
None of this happens at once. A template is accurate on the day it is approved and starts ageing the next morning. The firm changes its terms, its services, its people and its house style, and each change has to reach every master document that touches it. Mostly, it does not.
Why does nobody notice?
Because nobody uses the template. That is the uncomfortable truth in most firms. When a fee earner needs a new report, letter or proposal, they do not go to the template library. They open the last similar document they sent, or the one a colleague sent that went down well, save a copy and start editing. It is quicker, it already contains the right tone for this kind of client, and it has the recent changes that the master lacks.
So the real standard in the firm is not the template. It is a scattering of recent live documents, each slightly different, each carrying the fixes that one person made on one job. The official template sits in a folder, correct as of whenever someone last had time to look at it, used mainly by new starters who do not yet know better.
That is why templates rot. Not through carelessness, but because the way work actually flows through the firm bypasses them. Every correction is made downstream, in a document that goes to a client and then gets filed. Nothing carries it back upstream.
Why doesn't a template review fix it?
Most firms have tried the clean-up. Someone is given a week, or a project, to review every template, bring them into line and republish the library. It feels productive and the result looks good. Six months later the drift is back, because nothing about the underlying habit has changed.
The review treats the template as the problem. The real problem is that the template is outside the path of the work. As long as starting from the last document is faster and feels safer than starting from the master, people will do it, and every improvement will once again be made in a copy. A tidy library that nobody opens is still a library nobody opens.
There is a quieter cost as well. When the master and the working documents disagree, fee earners learn that the master cannot be trusted. That makes them even less likely to use it, which accelerates the drift. The library loses authority, and once lost, it is hard to win back with a memo.
Whose job is it to keep templates current?
In most firms, nobody's. Templates tend to belong to a shared drive rather than to a person. Marketing owns the look, compliance owns some of the clauses, a partner owns the technical content, and an office manager owns the folder. Each assumes someone else is watching the whole.
A template that matters needs one named owner who is close to the work, and a simple rule: when you change a standard section in a live document because the standard was wrong, you tell the owner, and the master is updated that week. That sounds like administration. In practice it is the only mechanism that closes the loop, and without it no amount of tidying lasts.
What stops templates rotting?
Put the template back in the path of the work. If producing a document starts from the approved master, automatically, with the client's details and the job's specifics dropped in, then the master is used every time, and any error in it is seen quickly by the people who rely on it. Drift becomes visible instead of silent.
Three things have to be true for that to hold:
- Starting from the template must be faster than starting from a copy. If it is not, people will copy, whatever the policy says.
- Standard content must live in one place. A limitation clause, a regulatory reference or a description of a service should exist once and be pulled into every document that uses it, so one change updates them all.
- Corrections must flow back. When a reviewer changes standard wording, that change should reach the owner and the master, not stay in one client's file.
This is one of the places where AI is genuinely useful in a firm, not because it writes better prose but because it can assemble a document from a firm's approved parts every time, reliably, and flag where a draft departs from the standard. We describe what that looks like in practice on the template management page, and the practical groundwork is covered in preparing templates for automation.
Why does this matter more than it seems?
Templates are where a firm writes down what it has agreed to. Scope assumptions, exclusions, payment terms, liability limits, data protection wording: all of it tends to sit in standard sections that nobody reads closely because they are standard. When those sections drift, the firm may be offering terms it no longer intends, or omitting ones it now relies on, across every document that uses them.
The engagement and scope documents at the start of an instruction are usually the most exposed, which is why they are often the best place to begin. Scope documents covers that job specifically. The copy-and-edit habit that causes the drift carries risks of its own, which we look at in the risk in copy and edit.