Template library and playbook as a process

A template library stays alive through three habits: one owner per template, one current version in one place, and review when something changes. The playbook is part of the same system. This applies to a department of one to ten lawyers. A library built as a project falls out of use once the templates age and nobody knows which version applies.

Updated by Nils-Erik Jansson

Why libraries die

Three causes are close at hand. Nobody owns the individual template, so nobody changes it when the law, practice or the business changes. Versions live side by side, in email, on drives and at the law firm, and nobody knows which one applies. And the library is never measured, so nobody sees that it has fallen out of use until someone asks why the contracts all look different.

CLOC counts knowledge management as one of the twelve legal operations competencies [1]. In a small department it comes down to three habits.

Habit one: one owner per template

Every template has a named owner in the department. The owner makes sure the template is current, decides on changes and answers questions about it. The owner's name goes on the template's cover page, with the date of the last change and one sentence on what changed. If the owner changes role, the template changes owner the same week.

It sounds trivial. Without an owner, nobody changes the template.

Habit two: one current version, in one place

The template lives in one place, in the system the business already uses. All other copies are working copies. The version number is in the footer, and old versions are archived and removed from the place people fetch templates from. When a law firm delivers an updated template, it goes through the owner and then into the library.

When I was building a contract management platform, customers often asked for their users to be able to edit the contract in free text. When I asked what they actually changed, the answer was the same every time: a date, a number, maybe a clause selection. Five fields, tops. That is a workflow.

The playbook belongs with the template. For each template there is a playbook with the standard position, fallback and limit for each clause, see the guide on the contract review playbook. When the template changes, the playbook changes the same day, by the same owner. They are a pair of documents.

Habit three: review on signal, not on the calendar

Review should happen on a signal: when a law or a piece of guidance changes, when the business has negotiated away the same clause three times, when a dispute has shown that a clause did not hold, when a new type of request turns up at the front door. The owner receives the signal and decides on a change within a week. Once a year the department goes through the list of templates and removes those that have not been used.

Measurement

Two figures are enough. How many times each template was fetched during the quarter, from the system's statistics or a simple counter. And the share of signed contracts that are based on a template with no changes, with changes within the playbook, or outside the playbook. The second figure can be taken from the review if the tool is set up with the playbook, and it is the one that shows whether the library actually governs anything.

What AI tools change

Two things. The playbook becomes the governing document, because a tool that reviews against it can handle the counterparty's paper as well as your template. And templates can be generated from the playbook instead of the other way round: the standard positions are assembled into a template for the situation at hand, with fallbacks ready. That requires the playbook to be written as text, not as policy, and someone to own it.

What does not change is the habits. A tool that reviews against a playbook nobody owns gives wrong answers with more confidence.

Template libraries and playbooks are part of the contract process design engagement under legal operations. As a fixed-scope project HOVR Legal goes through which templates are needed, sets owners and versions, writes the playbook for the contract types you use most and sets up the measurement. If the playbook is to be loaded into an AI tool, that is done in the Claude for Legal setup.

Read also the contract process from request to archive in eight steps and measuring the legal department.

Frequently asked questions

How many templates does a department of five lawyers need?
Start with the templates that cover most of the volume: NDAs, the two or three most common customer contracts, purchasing agreements, consultancy agreements, data processing agreements, employment contracts and a few letters. The rest are variants that belong in the playbook as alternative clauses, not as templates of their own.
Where should the templates live?
Where the business already looks: in the document system or intranet the company uses, with one page per template saying what it is for, who owns it and when it last changed. Not in a folder on the legal department's drive. A CLM system is the right place when the business is to generate contracts from the templates in volume, see the CLM requirements checklist.
What do AI tools do to the template library?
They make the playbook more important than the template. A tool set up with the department's playbook can review the counterparty's paper and propose text from the fallbacks, which reduces the need for the counterparty to use your template. You still need the template when you hold the pen, but the playbook is what scales. See the guide on the contract review playbook.

Sources

  1. [1]CLOC Core 12, Corporate Legal Operations Consortium, the Knowledge Management competency

Back to Legal operations

More under Legal operations