[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"article-body-the-9-percent-you-agreed-to-lose":3},"\nCompanies lose, on average, 9.2% of contract value after\nsignature. That is the long-standing benchmark from\n[WorldCC](https://www.worldcc.com/resource/Stopping-the-Leak-The-value-of-contracts.html),\nthe association that has studied commercial contracting for\ndecades, and more recent WorldCC-derived estimates run higher\nstill. On £1bn of annual contract spend, that is roughly £92\nmillion a year, agreed to in advance, clause by carefully\nnegotiated clause.\n\nThe mechanism is documented in the same research. Most companies\ndo not systematically track the obligations in their contracts\nafter signature, and many struggle even to locate the contracts.\nThe expertise flows into the words. The words go into a\nrepository. The commitments end up in people's heads, and people\nleave.\n\n## What a contract actually contains\n\nRead a substantial commercial agreement the way an operator would\nand it is a machine for generating future events, each with a\ndate, a condition and money attached:\n\n- Obligations with deadlines. Deliverables, notice periods and\n  reporting duties, on both sides.\n- Rights with windows. The price escalation, the benchmarking\n  right, the audit right. Each is worthless if its window passes\n  unnoticed.\n- Thresholds with consequences. Service levels that trigger\n  credits, volumes that trigger rebates, delays that trigger\n  penalties. Each needs an actual compared against a commitment.\n- Anniversaries with defaults. Renewals that auto-roll on old\n  terms, and price increases the contract allowed but nobody\n  applied.\n\nThe 9.2% is what these events cost when nobody operates them. The\nservice credit goes unclaimed because nobody joined the SLA data\nto the contract term. The escalation goes uninvoked because the\nwindow lived in a paragraph, not a calendar.\n\nEvery leaked pound had a clause protecting it. The clause worked;\nthe operation of the clause never existed.\n\n## From repository to instrument\n\nThe fix is unglamorous in the way profitable things usually are.\nConvert the contract estate from documents into structured\ncommitments, then wire the commitments to the data that tests\nthem:\n\n1. Extract the events. Every obligation, right, threshold and\n   anniversary, with dates, parties, amounts and the clause it\n   came from. The portfolio becomes a queryable calendar, not a\n   folder of PDFs.\n2. Join them to operational data. Service levels against the\n   monitoring systems, volumes against the order records, prices\n   against the invoices.\n3. Route each event to a named owner, with the money at stake and\n   the deadline attached. An opening escalation window becomes an\n   alert, not a line in a quarterly report.\n4. Score the recovery. Track claimed credits, invoked rights and\n   repriced renewals against the leakage baseline, so the\n   programme has a number and the number compounds.\n\n## Where to start\n\nBegin with the highest-value contracts and the event types that\nleak most, typically renewals and service credits, and let the\nrecovered value fund the long tail. Few compliance-adjacent\nprogrammes pay for themselves in the first quarter. This one does,\nbecause the money is not hypothetical risk avoidance. It is margin\nthe contract already earned.\n\nTurning contracts into monitored commitments joined to operational\ndata is what\n[the Prophesee Compliance Suite](/solutions/compliance/legal)\ndoes. Measure your own leakage first. [Start here](/contact).\n",1786984937260]