In-house legal

Running an overflow desk under your General Counsel: playbook, escalation, metrics

An external desk works when it behaves like part of your legal function: your positions, your escalation rules, your numbers. How to set that up without a six-month project.

Services agreement — Vendor template § 9 Liability

9.2 Neither party excludes liability for death or personal injurydeath or personal injury, fraud, wilful misconduct or breach of Clause 14 (Confidentiality).

Redline · round 1 1 escalation
In short
  • The playbook comes first. Two hours with the people who decide is enough for a first version.
  • The desk closes what is inside the playbook; it escalates red lines, silence and commercial trade-offs — as decisions, with a recommendation.
  • Three numbers tell you whether it works: turnaround, deviation rate and escalation rate.

Why the playbook comes first

Without written positions, an external desk can do one of two things: ask your lawyers about every clause, which saves them nothing, or apply its own view of the market, which is not your view. A playbook is what turns outside capacity into your capacity. It also outlives any provider: it is your document, and it keeps working if the desk does not.

Writing it in two hours

The first version does not need to be complete. It needs to cover the contracts that fill your queue.

  1. Pick the contract types. Usually three or four — for example supplier agreements on the supplier’s paper, NDAs, services agreements and DPAs. Leave the rest for later versions.
  2. Pull the last ten signed documents of each type. The desk reads them before the session and drafts the clause list and the positions you actually hold, which are not always the ones in your template.
  3. Hold one session with the people who decide. The GC or the head of commercial legal, and whoever owns procurement risk. For each clause: your position, the fallback you accept without discussion, the red line, and who decides beyond it.
  4. Approve and version it. Version 1.0, a date, and the name of the person who approved it. Every later change is a new version, so a redline can always be traced to the rule that applied on the day.

The format is a table, not a memo. See what a contract playbook looks like for a template.

What the desk closes on its own

Anything inside the playbook: a change that moves the counterparty’s draft to your position, or accepts one of your listed fallbacks. These close without reaching your team. They are still visible: every change carries a comment, and the summary lists every point where the final text differs from your position, even where the fallback was pre-approved.

What comes back to you

  • Red lines. The counterparty insists on a term the playbook rules out.
  • Silence. A clause the playbook does not cover — a new type of indemnity, an unusual exclusivity, a regulatory term.
  • Commercial trade-offs. Accepting a weaker warranty in exchange for a better price is a business decision, not a legal one.
  • Thresholds you set. Contract value, term, certain counterparties or certain countries.

An escalation is not a question. It arrives as a decision to take: the issue in two sentences, the desk’s recommendation, the alternatives and what each one costs. Your lawyer answers in a line. Each answer is a candidate for the next playbook version, so the same question is not asked twice.

Three metrics

Measure the desk the way you would measure your own team, with numbers you can read in a minute a month.

Turnaround

Time from receipt of the document and instructions to the redline, and for each negotiation round. Measure every round, not only the first: the first redline is rarely where a deal stalls. Look at the slowest documents, not the average.

Deviation rate

The share of documents signed with at least one term outside your position, whether a pre-approved fallback or an escalated exception. A deviation rate close to zero usually means the positions are softer than they look. A very high rate means the playbook describes the contracts you would like to sign, not the ones the market gives you. Either way, it is a reason to revise the playbook rather than to blame the desk.

Escalation rate

The share of documents that needed a decision from your lawyers. It is high in the first weeks, while the playbook is thin, and should fall as answers are written back into it. If it does not fall, either the playbook is not being updated, or the desk is escalating what it should close.

Several teams, several entities

In a group, procurement in one country and sales in another do not hold the same positions, and should not have to. The structure that works:

  • A common core for the terms the group decides centrally — liability, data protection, sanctions, governing law.
  • A playbook per team or entity on top of it, approved by that team.
  • Portal users per team, separating those who order work from those who only follow status, and invoicing per entity where the entities pay separately.
  • One senior lawyer across the account, who sees when two teams have drifted apart on the same clause and raises it with the GC.

Start with the team that has the longest queue. Add the next one when its playbook is approved, not before.

A monthly review in twenty minutes

Once a month: the three numbers, the escalations and how they were decided, and the proposed playbook changes. The GC approves or rejects the changes, and the desk issues the next version. That is the whole governance.

General information, not legal advice. This page describes how EU and cross-border commercial contracts commonly work; it is not advice on your situation, and no engagement arises until a service agreement with Icon.Partners is signed. For advice on a specific contract, speak to a lawyer qualified in the relevant jurisdiction.

Next step

Start with the queue, not a call.

Send one real contract on per-document terms. If it is what you need, we build the playbook with your team and move to a desk.

Book a contract call