Contract process design: mapping and redesign before CLM

HOVR Legal maps the contract process together with you, from request to archive: templates, approval rules, who signs, where the contract is kept and how renewals are tracked. The process can be mapped before a system is chosen, and it then becomes the requirements specification for the system.

Step by step

# StepWhat is decidedWhat you have afterwards
1Current stateHow contracts are requested, reviewed, approved, signed and archived today, and where they get stuckA map of the current process
2Request and triageHow contracts come in and which route each contract type takesA triage rule per contract type
3Templates and playbookWhich templates should exist, who owns them, and the positions per clauseA template library with owners and versions, and a playbook
4Approval rulesWho approves which contracts, by amount and type, and how the approval is recordedApproval rules
5SignatureWho signs under the company's registered signatory rules and powers of attorney, and which level of electronic signature each contract type requiresRules for signing
6Archive and renewalsWhere the contract is kept, with which metadata, and who tracks renewal, notice period and price adjustmentAn archive rule and a tracking list
7MeasurementLead time per contract type and the share of contracts on the standard routeA baseline

Who it is for

Legal departments that want to bring order to the flow of contracts, either ahead of choosing a contract system or to manage without one. Also departments that already have a system but where contracts still go around it.

What you contribute

  • A person with a mandate to decide on the approval rules and the positions in the playbook. Whoever sets the rules has to stand by them when they lead to a bad outcome, so the decision should sit with someone who can make it.
  • A sample of representative contracts per contract type.
  • The current approval rules, signatory rules and powers of attorney.
  • Time for conversations with the people in the business who request contracts and with finance.

What is not included

Choosing a contract system, which is legal technology selection. Implementing a chosen system, which is implementation. AI review against the playbook in a tool, which for Claude is done in the Claude for Legal setup. Review and negotiation of individual contracts.

What it is

Contract process design gives the department a written contract process and the documents that hold it together: a triage rule, a template library with owners, a playbook, approval rules, rules on who signs, and an archive with tracking. Every contract already goes through the steps. The engagement writes them down so that they look the same every time and can be measured. The steps are explained in the guide to the contract process in eight steps, from request to archive.

Before or without a contract system

The process can be mapped before a system is chosen. It then becomes the requirements specification for the system: every step, rule and field in the process is a requirement the vendors have to answer, see the CLM requirements checklist. The process can also run without a contract system, with templates in the document management you already have, e-signature and an archive with metadata.

From the founder

When I built a contract management platform, I met general counsel who wanted a system to fix a department that had no structure.

Nils-Erik Jansson, founder of HOVR Legal

A system brought in before the process exists on paper automates the disorder.

What is included

  1. Current state. A review of a sample of contracts per contract type, and conversations with the people in the business who request contracts and with finance.
  2. Triage. A rule per contract type: a standard contract on your own template without a lawyer, your own template adjusted by a lawyer, the counterparty's paper with a full review, or outside counsel. Requests are linked to the department's way in, see legal intake and triage.
  3. Templates and playbook. A template library with owners and one current version per template, see template library and playbook as a process. A playbook with the standard position, fallback and limit per clause for the contract types you use most, see the contract review playbook.
  4. Approval rules and signature. Who approves, who signs, and where the decision is recorded so that it can be found later. For electronic signatures, see e-signatures under eIDAS, with Sweden as an example.
  5. Archive and tracking. Metadata fields for each contract: party, type, amount, start, end, notice period and person responsible. The reminder goes to the owner in the business.
  6. The process in one place. The process map with the tool for each step, how long each step may take, what counts as done for each step, and a date for the next review.
  7. A requirements specification, if you are going to choose a system. The process translated into requirements in the form of the checklist, with threshold requirements marked.

What you get

  • The process map from request to archive.
  • A triage rule, approval rules and rules for signing.
  • A template library with owners and versions, and a playbook for the contract types chosen.
  • An archive rule with metadata fields and a tracking list.
  • A requirements specification for a contract system, if you are going to choose one.
  • A written handover with an owner for each document.

The documents are in your template and go with you to the system you choose, or work without a system.

Time

Scope and time are agreed in the first conversation. If you need help with only one of the steps, such as just the approval rules or just the requirements specification, the step can be done on its own.

Next step

One hour on how contracts flow today and whether you are about to choose a system. Write to hello@hovrlegal.com.

Read also the contract process in eight steps, from request to archive and CLM requirements for a Swedish legal team.

Ask a question or choose a time for a conversation.

Get in touch

Back to Legal operations

More under Legal operations