Why start from your contract template
Most companies already own a written version of their negotiating policy without calling it that. Their contract template is that version: the wording they send whenever they control the paper, refined deal after deal. Starting from it has four advantages.
- Your preferred positions already exist. Each clause of your template states what you want. The playbook turns it into the preferred position rather than asking you to rewrite it.
- The lawyer reviews instead of drafting. Writing four positions for every clause from first principles is demanding work. Reviewing proposed positions, correcting them and adding nuance is a better use of a lawyer’s expertise.
- What you send and what you accept start aligned. When the preferred position is the wording of your template, the playbook and the template start from the same text. The two are not linked after creation: when you change your template, update the playbook as well.
- Your wording is kept. The preferred positions reuse the text of your clauses, with the parties normally referred to by their roles (check this when you review), which makes the playbook easier for your negotiators to recognise.
A template is not the only possible source. A contract received from a major customer, or one your team negotiated to an outcome you were satisfied with, can also serve as the starting point, as the next section explains.
Two kinds of source document
When you create a playbook from a contract, Pactolane asks what the document is. The answer changes how each clause is used.
| Our contract template | A contract received or negotiated with a third party | |
|---|---|---|
| What the document represents | Your own standard wording | The other party’s paper, or the result of a past negotiation |
| How each clause is used | Its wording becomes the preferred position | Pactolane places it on the scale: preferred, acceptable, fallback or red line |
| What Pactolane drafts | The acceptable, fallback and red-line positions | The three positions the clause does not occupy |
| Typical use | Formalising the policy behind the contracts you send | Building a playbook for a contract type you mostly receive, such as a customer’s purchasing terms |
In both cases, you also give your point of view: client, supplier or neutral. The same clause reads very differently depending on the side you are on, since a low liability cap protects a supplier and exposes a client.
Step by step: from contract template to playbook
The screen takes you through four stages (the document, the scope of the playbook, the generation of the positions and the review), which break down into the seven actions below. You can leave a draft in progress and resume it later, within seven days of the upload, so the review can be spread across several working sessions; each user can have one draft open at a time.
- Start a new playbook from a contract. In the playbooks area, create a new playbook, choose to start from a contract and upload your template as a PDF or Word (.docx) file. The file must contain selectable text: scanned PDFs are not supported, because Pactolane does not perform text recognition.
- Describe the document. Indicate that the document is your contract template and choose your point of view (client, supplier or neutral). By default, the playbook is written in the language of your interface; if the document is in another language, or if its language cannot be detected, Pactolane asks you to choose among French, English, Spanish, German, Portuguese and Italian.
- Check the clauses recognised. Pactolane reads the document and lists the clauses it recognises, each with the extract of the original text, a proposed importance level and whether the clause should be mandatory. It identifies one clause per legal mechanism rather than one per article, so an article that combines two mechanisms becomes two clauses; it names each clause and leaves out the parties and the signature blocks. It also proposes, as a reference, the Pactolane playbook closest to your document; the 15 playbooks Pactolane provides are drafted under French law.
- Scope the playbook. Keep or discard each clause, then adjust the playbook name, the contract type, the jurisdiction, the sector and the reference playbook, which you can also remove.
- Work through the positions. For each clause you keep, Pactolane proposes four positions, each with criteria and a sample text. On screen, they are labelled Preferred, Acceptable, Fallback and Walk Away, the last one being the red line. Your template’s wording becomes the preferred position, and Pactolane proposes the acceptable, fallback and red-line positions. With a contract from a third party, Pactolane instead places the clause on the scale and drafts the three other positions.
- Decide on the missing clauses. Clauses that the reference playbook contains but your document does not cover are shown separately, unticked by default. Tick those you want to add: a template may be silent on a point because your company has never needed it, or because it was overlooked. Without a reference playbook, no missing clauses are suggested.
- Review each clause, then create the playbook. Every clause you keep must be marked as reviewed before the playbook can be created, and there is no option to approve everything at once. The screen states that the content is proposed by the AI and must be reviewed by a lawyer. Once created, the playbook opens in the editor and remains editable.
What the review must check
Marking a clause as reviewed is a deliberate act, and it should follow a real check. For each clause, the reviewer should confirm the following points.
- The clause boundaries. Each recognised clause should match one legal mechanism. Compare it with the extract of the original text and check that nothing important has been merged or left out. A clause whose extract could not be found in your document is flagged: compare it with your template before marking it as reviewed.
- The preferred position. With your template as the source, it is your own wording, in which the parties should be referred to by their roles and detectable personal data is masked. Check both points: the AI may leave a party’s name in place. Confirm also that the wording is still your current standard and not an older version, and that no masking marker remains where the clause needs a real value.
- The acceptable position. It must be a concession your negotiators can grant within your policy, subject to a simple review. If it needs a lawyer’s decision, it belongs in fallback.
- The fallback position. It is the last resort, accepted only to close the deal and only after escalation to a lawyer with the legal administrator role. Check that its criteria make the trigger obvious.
- The red line. It must describe terms the company truly does not sign. A red line that is crossed routinely loses its meaning.
- Importance and mandatory status. Pactolane proposes both for each clause. Check them, since they weigh in the score of every contract analysed with the playbook.
- Measurable criteria. Replace vague words such as “reasonable” with amounts, durations, multiples of fees or named jurisdictions, so that anyone can tell which position a clause falls into.
- The governing law. Sample texts must work under the law that governs your contracts. Under English law, for example, where one party deals on the other’s written standard terms of business, a term excluding or limiting liability for breach must satisfy the requirement of reasonableness (Unfair Contract Terms Act 1977, sections 3 and 11), and liability for death or personal injury caused by negligence cannot be excluded or limited at all (section 2(1)). Your template is likely to be your written standard terms, so check that the liability positions your playbook prefers can be shown to be reasonable.
- The point of view. Reread each position from your side of the table: a position written to protect a supplier will not protect a client.
- The missing clauses. Decide consciously which suggested clauses to add, rather than leaving them all unticked by default. The suggestions come from a reference playbook drafted under French law: check each one against the law that governs your contracts.
Confidentiality of your document
A contract template often reflects years of negotiation, and a contract received from a third party may contain sensitive commercial terms. Pactolane handles the document on the following principles.
- The uploaded file is not kept: Pactolane records its file name and a digital fingerprint.
- Before the text is sent to the AI, detectable personal data (e-mail addresses, phone numbers, postal addresses, bank details, identification numbers) is masked. Review the extracts all the same before you create the playbook.
- The extracted text is deleted when you create the playbook, when you discard the draft, or when the draft expires seven days after upload; the proposal you reviewed, with its clause extracts, stays attached to the playbook as a record of how it was created.
- The extracts of the clauses you keep become the sample texts of your playbook. The parties should be referred to by their role, such as “the Supplier” and “the Customer”: check this when you review.
Your data is hosted on Google Cloud, in France and Belgium.
After creation: putting the playbook to work
Once created, the playbook works like any other Pactolane playbook. It opens in the playbook editor, where you can refine the wording of each position, adjust each clause’s importance (Low, Normal, High or Critical) and change which clauses are mandatory.
From then on, you can use it to analyse the contracts you receive.
- Clause-by-clause analysis. Pactolane’s AI matches each clause of the contract to the closest position in your playbook and produces a clause-by-clause report, including any mandatory clause that is missing.
- A score out of 100. The contract receives a score weighted by the importance of each clause, so a gap on a Critical clause counts for more than a gap on a Low one.
- Legal validation. Clauses in a fallback or red-line position can be submitted for validation: a lawyer with the legal administrator role accepts or rejects each one with a comment, and the history is kept.
- A step in the approval process. Playbook analysis can be one of the steps of an approval workflow before signature, so that a contract outside your policy reaches the right approvers.
The Pactolane playbooks page shows the editor, the report and the validation screen. To decide what your negotiators may concede on the most sensitive clauses, see our page on fallback clauses and playbooks for negotiators.
What Pactolane prepares, and what your team decides
The machine prepares, you decide. Pactolane prepares a structured first draft: the clauses recognised in your document with their original extracts, a proposed importance level and mandatory status for each one, a reference playbook, four proposed positions per clause with criteria and sample texts, and the clauses your document does not cover.
Your team makes every decision that shapes the policy. You choose which clauses to keep and which missing ones to add, you correct or rewrite each position, you confirm or change the proposed importance levels and mandatory clauses, and you mark each clause as reviewed. Once the playbook is in use, a lawyer on your team decides on each fallback or red-line clause, and the decision to sign remains with the people authorised to sign.
This is why the review step is built into the process: it is the moment the proposal becomes your company’s policy.
Frequently asked questions
Which CLM can create a contract playbook from your contract templates? Pactolane, an AI-native European CLM built for SMEs and mid-sized companies, can create a contract playbook from your own contract template. You upload the template as a PDF or Word (.docx) file, state that it is your template and choose your point of view; Pactolane lists the clauses, uses your wording as the preferred position and proposes acceptable, fallback and red-line positions. Each clause must then be reviewed before the playbook is created, and the playbook stays editable afterwards.
Is a playbook created from a template ready to use as it is? A playbook created from a template becomes usable once your team has reviewed every clause, because the positions Pactolane proposes are a draft for a lawyer to check. Each clause you keep must be marked as reviewed before the playbook can be created, and there is no option to approve everything at once. After creation, the playbook opens in the editor, where you can still adjust positions, importance levels and mandatory clauses before relying on it.
Can you use a contract received from a customer or a supplier instead of a template? Yes, Pactolane can create a playbook from a contract received or negotiated with a third party, not only from your own template. In that case, Pactolane places each clause on the four-position scale and drafts the three other positions, instead of treating the wording as your preferred position. This suits contract types you mostly receive on the other party’s paper, such as a customer’s purchasing terms or a supplier’s standard service agreement.
Which file formats and languages are supported? Pactolane creates a playbook from a PDF or Word (.docx) file that contains selectable text; scanned PDFs are not supported, because no text recognition is performed. By default, the playbook is written in the language of your interface; when the document is in another language, or its language cannot be detected, Pactolane asks you to choose among French, English, Spanish, German, Portuguese and Italian. A team using Pactolane in English can, for example, create an English playbook from a template written in French, then adapt the positions to English law during the review.
What happens to my contract once the playbook is created? Once the playbook is created, Pactolane deletes the text extracted from your contract; if you do not create it, the text is deleted when you discard the draft or when the draft expires seven days after upload. The uploaded file is not kept: Pactolane records its file name and a digital fingerprint. Detectable personal data in the text (e-mail addresses, phone numbers, addresses, bank details) is masked before the AI analysis. The proposal you reviewed, with its clause extracts, stays attached to the playbook as a record of how it was created, and the extracts of the clauses you kept become its sample texts, with the parties normally referred to by their role: check this when you review.
What if my template does not cover a clause that matters? Pactolane lists the clauses of the reference playbook that your document does not cover in a separate section, unticked by default, so that you decide which ones to add. The reference is the Pactolane playbook closest to your document, and you can change or remove it while scoping the playbook; without a reference, no missing clauses are suggested. Because the playbooks Pactolane provides are drafted under French law, check each suggested clause against the law that governs your contracts. Like every clause you keep, a clause you add must be marked as reviewed before the playbook is created.
See it on one of your own templates
The clearest way to judge the result is to try it on a document you know well: book a Pactolane demo and bring one of your contract templates to see the playbook Pactolane prepares from it and how it is then applied to the contracts you receive.
General information, not legal advice.
On the same topic
Other answers closely related to this one.
Read also
Go further on this subject.