The contract process in eight steps, request to archive
The contract process has eight steps: request, triage, template or draft, review, negotiation, approval, signing, and archive with monitoring. For a department of one to ten lawyers it fits on one page. Writing it down pays: WorldCC has measured this for more than ten years, and companies lose on average close to ten per cent of contract value through weaknesses in how contracts are handled, while the best lose a few per cent. Here are the steps, where templates, the playbook, AI and e-signature come in, and where the process stalls.
Updated by Nils-Erik Jansson
- AI belongs here, with the lawyer in control
- Where the process stalls
Step 4 of 8
Review
Review against the playbook: standard, fallback and limit per clause. The result is a list of points to negotiate, with your position on each.
Who: The lawyer reads and decides.
Where AI comes in
A tool with the playbook loaded flags deviations and proposes text from the fallbacks.
Nothing is sent anywhere. Your choice stays in your browser.
Make it yours
Add which tool is used, how long each step may take and what counts as done, and set a date for the next review. Put it where the business can see it.
When you need a system
When the business is to generate contracts from templates in volume, or when approvals are to follow rules instead of people. At that point the one-page process is the requirements list for the system.
Background
Why the process is money
WorldCC measures value erosion, the share of a contract's value lost through weaknesses in how it is handled. It stood at 9.2 per cent in 2014 and 8.6 per cent in 2023, with the best organisations just over 3 per cent and the worst over 20 [1]. The November 2026 report says close to 10 per cent [2]. WorldCC also notes that the most negotiated terms have stayed largely the same for fifteen years [3]: limitation of liability, price and indemnities are negotiated again and again, with the same arguments, by the same people.
The value leaks in the handling. Contracts are requested too late, reviewed differently depending on who gets them, approved in email threads, signed on paper and filed in folders nobody monitors. A small department without a system can fix this with a process on one page.
The eight steps
| Step | What happens | Who |
|---|---|---|
| 1. Request | The need is logged in one place with six fields: who, business unit, contract type, counterparty, when it is needed, and whether the counterparty has a draft. This is the legal front door applied to contracts. Without this step, contracts arrive as email attachments headed "quick question". | The business |
| 2. Triage | Sorted within a day: a standard contract on your own template with no lawyer, your own template adjusted by a lawyer, the counterparty's paper with full review, or outside counsel. The rule is written on one page per contract type. An AI tool set up with the rules can propose the route. | Whoever holds the triage role that week. The lawyer decides |
| 3. Template or draft | Your own template from the library, with an owner and a version, see template library as a process. The counterparty's paper is received in an editable format. This is where it is settled whether the negotiation starts from your positions or theirs. | A lawyer or the business, depending on the triage route |
| 4. Review | Review against the playbook: standard, fallback and limit per clause, see the contract review playbook. A tool with the playbook loaded flags deviations and proposes text from the fallbacks. The result is a list of points to negotiate, with your position on each. More in the guide on reviewing AI output. | The lawyer reads and decides |
| 5. Negotiation | The playbook is the mandate. The negotiator decides anything within the limit, and anything at the limit goes to whoever the playbook names. Changes are tracked in the document, not in email. When the same clause has been given away three times, the playbook is updated. | The negotiator |
| 6. Approval | The approval matrix in one step: who approves which contracts, by value and type, and how it is recorded. Approval is a decision and must be traceable afterwards. See below on why the process stalls here. | Whoever the approval matrix names |
| 7. Signing | Electronic, at the level the contract type requires, with an evidence package that can be exported, see e-signatures in Sweden. The service handles signing order and reminders. Paper only where a formal requirement calls for it. | The parties, through the e-signature service |
| 8. Archive and monitoring | The signed contract and the evidence package are archived with metadata: party, type, value, start, end, notice period, owner. Renewal, notice period and price adjustment are monitored, see contract renewals with AI. | The legal department. The reminder goes to the owner in the business |
Where it stalls
Before step one. The business negotiates on its own for weeks and comes to legal with a finished document and a deadline of tomorrow. The fix is a front door that is faster than doing it yourself.
At step six. The approval circulates in an email thread with five people and nobody knows whether it is done. The fix is an approval matrix on one page and one place where the approval is recorded.
When I was building a contract management platform, some general counsel did not want a structured workflow. Whoever sets the rules (liability caps, approval thresholds, escalation) also answers for them when they produce a bad outcome. "Send everything to me" feels like control. It is a slow way of not deciding.
At step seven. The contract is printed, signed, scanned and emailed, and the signed version differs from the approved one. The fix is e-signature with document locking.
After step eight. The contract is archived without metadata or monitoring, and renews automatically a year later. The fix is the metadata in step eight and a monthly review.
The process on one page
The table above is the basis. Add which tool is used, how long each step may take and what counts as done, and set a date for the next review. CLOC counts practice operations as one of its twelve competencies [4]; in a small department that competency is the table. Put it where the business can see it, and measure it by lead time per contract type and the share of contracts on the standard route, see five metrics.
When you need a system
When the business is to generate contracts from templates in volume, when approvals are to follow rules instead of people, when contract data needs to feed other systems, or when the archive has grown so large, with so many owners, that nobody can keep track of it. At that point the one-page process is the requirements list for the system, see the CLM requirements checklist. A system brought in before the process exists on paper automates the disorder.
How HOVR Legal works with this
The contract process is one of the areas under legal operations, and the engagement is described under contract process design. As a fixed-scope project HOVR Legal maps the process with you, writes the triage rule and the approval matrix, sets up the template library and the playbook for the contract types you use most, and does the first measurement. If AI review is to be built into a tool, that is done in the Claude for Legal setup.
Read also legal front door and template library and playbook as a process.
Frequently asked questions
- Does a department of three lawyers need a formal contract process?
- It already has one. It just is not written down. Every contract goes through the eight steps whether anyone decided it or not. A written process means the steps look the same every time, the business knows where its contract is, and you can measure where the time goes. It fits on one page.
- What exactly is the value that leaks?
- WorldCC's research from 2014 found average value erosion of 9.2 per cent of contract value, and the 2023 follow-up put it at 8.6 per cent, with the best just over 3 per cent and the worst over 20 [1]. WorldCC's report from November 2026 says organisations lose close to 10 per cent of contract value through weaknesses in contract management [2]. In practice it is renewals nobody cancelled, price increases nobody challenged, obligations nobody followed up, and the same terms negotiated again and again.
- Where does AI belong in the process?
- In three steps, with the lawyer in control: triage (sorting the request and proposing a route), review (comparing the counterparty's paper with the playbook and proposing text from the fallbacks) and archive (extracting metadata and building the renewal list). It does not belong in negotiation, which is for people, or in approval, which is a matter of accountability. See the guide on the contract review playbook.
Statements about Anthropic's terms and products were read on Anthropic's pages on 10 November 2026 and are checked at the start of every engagement.
Sources
- [1]Are organizations unlocking their full financial potential?, World Commerce & Contracting, 18 August 2023
- [2]The ROI of contracting excellence 2026, World Commerce & Contracting, 9 November 2026
- [3]Most Negotiated Terms, World Commerce & Contracting, the overview page
- [4]CLOC Core 12, Corporate Legal Operations Consortium, the Practice Operations competency
Back to Legal operations
More under Legal operations
- Legal intake and triage for business requests
HOVR Legal builds a way in for the business's legal questions: channel, categories, four routes, triage rule, response times and measurement. No new system.
- Contract process design: mapping and redesign before CLM
HOVR Legal maps the contract process with you: templates, approval rules, who signs, where the contract is kept and renewals. Before or without buying a CLM.
- Outside counsel management and external legal costs
HOVR Legal sets up how you manage outside counsel: which matters go out, a panel, engagement terms, billing guidelines and follow-up of the cost.
- Part-time interim legal operations lead
HOVR Legal takes on the legal operations lead role one or two days a week: plan, implementation, measurement and handover, reporting to the general counsel.
- A legal front door for a legal team of three
One way in for the business's legal questions: a form, four routes, response times and measurement. Built for a small department with no new system.
- Measuring the legal department: five metrics, no system
Five metrics from the inbox and invoices: requests per category, time to first response, standard route share, outside counsel spend, contract lead time.
- Managing outside counsel: panel, fixed fees and invoices
A panel of three to five firms, an instruction per matter, fixed fees where possible, three-point invoice review and an annual review.
- Template library and playbook as a process
Why template libraries die and how a small legal department keeps its templates and playbooks alive.
- How to write a contract review playbook
A playbook sets the position per clause: standard, fallback and limit. How to write one for contracts under Swedish law, with an NDA as the example.
- Interim head of legal operations: when and how
When a legal department needs a part-time interim head of legal operations, and what the role does in the first ninety days.
- Legal operations maturity model for small teams
CLOC's twelve competencies and ACC's maturity model adapted to a legal department of one to ten lawyers.
- The legal department budget and annual cycle
How a legal department of one to ten lawyers builds a budget management understands: five lines, invoices as the basis, and a case the CFO can assess.