Contract Management for General Counsel (2026)

A general counsel does not manage contracts one at a time. By the time a GC is involved, the question is rarely about a single clause. It is about the whole book: how much risk the company is carrying across thousands of agreements, why the legal team is the bottleneck on every deal, whether the business is signing consistent terms, and what to tell the board when they ask about contractual exposure. The GC's job is to make the portfolio safe and the process fast at the same time, usually with a team that is too small for the volume. This guide covers how to run contracts at that level. ## The GC's real problem The GC sits above the day-to-day, so the pain is different from any single team's: - No view of the whole book. Nobody can answer, quickly, what terms the company has agreed across all its contracts, or where the concentrated risk sits.

• Legal is the bottleneck. Every contract routes through a small team, so deals wait and the business resents the delay.
• Inconsistent terms. Different people agree different positions on the same issue, so the company's risk posture is accidental, not chosen.
• No leverage from the back-book. Thousands of signed contracts hold obligations, renewal dates and risk that nobody has extracted.
• Reporting up is hard. When the board asks about contractual risk, the answer is anecdote, not data. ## What good looks like for a GC A governed portfolio, not a pile of files. Every active contract is in one place with its key terms, obligations, renewal dates and risk extracted, so the book can be queried. Scaled judgement through playbooks. The GC's positions on common clauses are written into a playbook, so the business and junior lawyers can apply them without escalating every time. Self-serve for standard work, escalation for the rest. Standard, low-risk contracts flow without legal touching them; legal spends its time on genuine judgement calls. A risk view across the book. The GC can see where liability is uncapped, where indemnities are broad, where non-standard terms were agreed, and where the renewals and obligations cluster. Board-ready reporting. Contractual exposure can be summarised with numbers: how many contracts, what value, what risk, what is renewing. ## A workflow a GC can run the company on 1. Consolidate the portfolio. One repository for active contracts, with key terms extracted. This is the foundation of governance.

2. Write the playbook. Document the company's standard positions, fallback positions, and hard limits on the clauses that matter.
3. Delegate by risk. Define which contracts are standard enough to self-serve, which need review, and which must reach the GC.
4. Extract risk from the back-book. Pull obligations, renewal dates, liability caps and non-standard terms out of signed contracts so the risk is visible.
5. Report on a cadence. Turn the portfolio into regular numbers for the board: exposure, concentration, renewals, and where the team's time goes.
6. Measure and tune. Track cycle time, escalation rate and the share of self-serve work, and adjust the playbook to move them. ## Scaling judgement, not headcount The central GC move is to turn judgement into reusable rules. A GC cannot read every contract, but a GC can decide, once, where the company stands on liability caps, indemnities, auto-renewal, governing law, data terms and the rest, and write that down. The playbook is how one lawyer's judgement reaches a hundred deals. The repository is how the GC keeps sight of the exceptions that still need a human. Good contract management at the GC level is mostly these two things working together. ## Picking tools Enterprise CLM tools are built for exactly this scale. Icertis and Ironclad are strong on workflow, approvals and governance across large organisations; LinkSquares and Evisort focus on extracting terms, obligations and risk from a large back-book for reporting; DocuSign CLM covers the full lifecycle to signature; Juro and SpotDraft suit leaner teams that want fast creation with light governance. For a GC the test is whether the tool gives a true portfolio view and a reliable way to enforce the playbook, not just faster drafting. Weigh each against the size of your book and the maturity of your process. ## Measuring it A GC can run the function on a short dashboard: average contract cycle time, the share of contracts handled without legal touching them, the escalation rate, total and concentrated liability exposure, obligations tracked versus total, and renewals caught early. Moving those numbers is the function getting both safer and faster. ## One AI workspace for the whole book Much of what a GC needs is extraction and consistency at scale: reading every contract for its obligations, dates and risk, drafting from the firm's own positions, and keeping one record. That work fits an AI contract workspace tuned to the company. Adira, built on Anthropic's Claude, builds a persona of how your company contracts and its risk posture, drafts from your playbook, shows a per-clause risk view and a single risk-posture meter per document, tracks obligations and key dates as dated alerts, and keeps every version on a live timeline. More at Adira. The governance workflow above stands on its own. ## Bottom line A general counsel manages the portfolio, not the paragraph. The failures that matter are no view of the whole book, a legal team that bottlenecks every deal, and risk that cannot be reported to the board. Consolidate the portfolio, write the playbook, delegate by risk, extract risk from the back-book, and report on a cadence. Scale judgement through rules and keep sight of the exceptions, and the legal function becomes something the company can run on rather than wait on.