Contracts Manager

I think of the lifecycle in four stages: intake, drafting and negotiation, execution, and post-signature management. When a request comes in, I clarify the commercial intent before touching a template, because the wrong starting clause set costs more time later than a five-minute conversation up front. I draft from an approved playbook where possible, redline against our fallback positions, and route anything outside standard risk tolerance to legal counsel. Once signed, the contract goes into our repository with key dates, obligations, and renewal triggers tagged, usually 90 days before expiry for anything with an auto-renewal clause. I review my active portfolio monthly so nothing rolls over on outdated terms. The stage most teams underinvest in is post-signature tracking, and it is where I have caught the most avoidable cost.

I work from a risk threshold that I agree with legal at the start of any engagement, usually tied to contract value, data sensitivity, and deviation from our standard templates. A vendor NDA or a low-value renewal on unchanged terms I sign off myself. Anything involving unlimited liability, IP assignment, unusual indemnification, or a contract over a set value goes to counsel, even if the commercial team is pushing for speed. I also escalate anything I am not fully confident reading correctly, which happens less often now but did more in my first year. Being clear about that threshold means legal only spends time on the contracts that actually need their attention, and it protects the business from a manager who approves something outside their competence just to keep a deal moving.

I start by figuring out whether the pushback is about the substance of the clause or just the wording, because those need different responses. If it is wording, I usually have flexibility to redraft in language that still protects the same position. If it is substance, like a liability cap they refuse to accept, I go back to what we are actually trying to protect against and ask whether there is a narrower way to get there, maybe scoping the cap to certain types of loss rather than removing it entirely. I keep the conversation focused on the underlying risk rather than the clause itself, which usually finds a compromise faster than restating our position. If we cannot move and the risk is material, I loop in legal and the business owner together so the trade-off gets made with full visibility, not by me alone.

I have worked mainly in Ironclad and DocuSign CLM, and I lean on them for three things: template governance, workflow routing, and obligation tracking. Template governance means the version everyone pulls from is the current approved one, not an old copy sitting in an inbox somewhere. Workflow routing lets me set approval steps by contract type and value so a low-risk renewal does not sit in the same queue as a six-figure vendor deal. Obligation and renewal tracking is where I get the most day-to-day value: automated alerts at 90, 60, and 30 days before a key date mean nothing depends on my memory. I also use the reporting layer monthly to check cycle time and where contracts are getting stuck, which has helped me spot a recurring bottleneck at the procurement approval step twice in the past year.

We were finalising a services agreement with a new vendor, and the version that came back after their legal review had quietly widened an indemnification clause to cover consequential damages, not just direct losses. It was a single word change buried in a clause that had already been through three rounds, which is exactly how these things get missed. I flag every redline against the previous version rather than reading the document fresh each time, and the comparison caught it immediately. I raised it with our legal counsel and pushed back to the vendor, explaining that the change was outside what either side had agreed to in the negotiation calls. They accepted reverting it without much friction once I framed it as restoring the agreed position rather than reopening the negotiation. It reinforced why I never skip the redline comparison, even on a document I think I already know well.

We were renewing a software contract with a vendor who had raised their price by 40 percent year on year with no change in service level. My first move was not to counter on price directly, but to build a clear picture of our actual usage against what we were licensed for, which showed we were paying for about 25 percent more seats than we used. I brought that data into the conversation, which shifted the discussion from "can you reduce the increase" to "let us right-size the contract to what we actually need". We ended up at a renewal that was 12 percent below the original price despite where the vendor started, with a usage review built into the renewal terms so it would not happen again. The lesson I keep applying is that data changes a negotiation more than pressure does.

I inherited a portfolio where roughly 60 contracts were approaching renewal within the same eight-week window, a result of a prior team not tracking dates consistently. I triaged everything by value and risk first, since not every contract needed the same depth of review. Anything low-value and unchanged went through an expedited approval path I built with legal sign-off in advance, which cleared about half the backlog quickly. The higher-value or higher-risk contracts got full review, and I set a daily target so nothing sat untouched. I also flagged three contracts we should not renew at all based on low usage, which saved the business real money beyond just clearing the backlog. We closed the window with everything actioned and no lapses, and I built a rolling 90-day dashboard afterward so a backlog like that could not build up unnoticed again.

I maintain a risk register that sits alongside the contract repository, tagging each agreement against a small set of flags: data protection exposure, regulatory dependency, non-standard liability terms, and jurisdiction risk. Every new contract gets scored against those flags at signature, not retrospectively, because retrofitting a portfolio review is far slower. I run a quarterly audit sampling a portion of the active portfolio to check the tags still match reality, since obligations and regulations shift over the life of a contract. When something like a change in data protection law affects a category of agreements, I can pull every flagged contract in minutes rather than searching manually. I also keep an open line with our compliance team so flags are defined jointly, not something I invent alone, which means the register actually gets used by people outside my team.

I would start with the templates, not the software, because a clean repository full of inconsistent templates just organises the mess instead of fixing it. I would work with legal to lock down approved templates and fallback clause positions for the contract types we use most often, then build a simple playbook so anyone drafting a first-pass contract knows what is standard and what needs escalation. Once that foundation exists, I would migrate historical contracts into the repository in priority order, starting with anything with an upcoming renewal or an active obligation, rather than trying to backfill everything at once. I would tag each contract with owner, key dates, and risk level on the way in. Reporting and dashboards come last: they are only useful once the underlying data is clean, and building them too early just produces reports nobody trusts.

I start from what we are actually exposed to in the relationship, not a generic position, because the right cap for a low-value software subscription is very different from the right cap for a vendor handling sensitive customer data. I typically anchor to a multiple of contract value as a starting point, then adjust based on the specific risk: data breach exposure or IP infringement often warrants carving those categories out of a general cap entirely. When a vendor resists any cap, I focus the conversation on what happens in a worst-case scenario for both sides, which usually makes the case for a reasonable limit better than restating our policy. I loop legal in early on anything involving uncapped liability or unusual indemnities, but I come to that conversation with a recommended position already, not just a question, so we can move faster.