Managing a framework agreement does not begin at the signature, but in the years that follow. Six months after the award, you often no longer know exactly what has been called off under your framework agreement. The project team has disbanded, attention has shifted to the next tender, and the call-offs continue without anyone keeping a central eye on them. That is the moment when managing a framework agreement really counts.<\/p>\n\n\n\n
The value of a framework agreement is not created during the tender. It is created through the management of the call-offs, consumption and performance that flow from it for years. And that is precisely where attention tends to fade at most organisations.<\/p>\n\n\n\n
A tender takes months. Market analysis, award criteria, objection periods, conversations with suppliers. On the day of signing, it feels like a conclusion. In reality, management begins at that moment.<\/p>\n\n\n\n
The people who know the contract are the quickest to move on after the award. The procurement manager picks up the next tender. The project team disbands. The contract manager who inherits the file does not know the negotiations and has to work with what is on paper. There is a reason contract management is described as a continuous cycle: from recording and managing to monitoring, evaluating and improving. With a framework agreement, that cycle is not a formality, but the place where the money sits.<\/p>\n\n\n\n
A framework agreement is a framework. It sets out the conditions for future contracts, but it is not a purchasing obligation. The concrete assignments, the call-offs, are placed separately under that framework.<\/p>\n\n\n\n
That distinction is the heart of the management problem. The framework contract stands still: the rates, the scope, the ceiling and the indexation arrangements are fixed. The call-offs move. They are called off in a decentralised way, across different departments and locations, spread over years. Anyone who only sees the framework contract does not see what happens in practice. And anyone who only looks at individual call-offs loses sight of the framework.<\/p>\n\n\n\n
Take a local authority with a framework agreement for technical maintenance, where four departments may call off assignments independently. The framework contract is clear. But the sum of the call-offs lives nowhere. At the end of the year, the contract ceiling turns out to be almost reached, while no one steered on it during the year.<\/p>\n\n\n\n
Framework agreements in principle have a maximum term of four years, with exceptions that allow a longer term. That trend towards longer framework contracts is relevant, because every additional year increases the management burden. A longer term means more indexation rounds, more call-off moments and more performance to record.<\/p>\n\n\n\n
With a long-running framework contract, this stacks up. One indexation that is applied incorrectly works through every subsequent call-off for years. A scope that quietly stretches through partial assignments only becomes visible when it is too late. And it is precisely with these longer contracts that an average saving of 8 per cent per year adds up considerably over several years, provided you take management seriously.<\/p>\n\n\n\n
Without active management of a framework agreement, the risks build up. Not spectacularly, but creepingly. The problems that recur most often:<\/p>\n\n\n\n
These problems rarely arise from unwillingness. They arise because the information is fragmented: the framework contract in one system, the call-offs in invoices and emails, the performance in the heads of people who happened to be there. According to WorldCC, PwC and McKinsey, an average of 2.6 per cent of contract value leaks away each year through poor contract management. With a framework agreement of dozens of call-offs over four years, that is not a theoretical figure.<\/p>\n\n\n\n
To manage a framework agreement, you need several things continuously in view per framework contract. Not as a separate report after the fact, but as a living overview you steer on:<\/p>\n\n\n\n
In the Contract Dashboard from GRIP<\/a>, you link those call-offs and performance to the framework contract they fall under. That way you see in one overview how much has been called off, how much ceiling remains, and whether the supplier delivers what you pay for per partial assignment. Recording stays in your ERP or spend system. The managing happens in GRIP, which adds the layer those systems lack.<\/p>\n\n\n\n The mistake in thinking that costs the most money is treating the framework agreement as a closed file. The CATS CM methodology, which GRIP follows seriously as one of the few Dutch parties, is about precisely the opposite. A contract is a living document with obligations, actions and performance that you follow up throughout the entire term.<\/p>\n\n\n\n For a framework agreement, that means: you link every call-off back to the framework, you record every performance, and every open action gets an owner and a date. Not because you have to, but because at the next indexation round, renewal or re-tender you want a substantiated story instead of a reconstruction from old emails. You can read more about the difference between keeping a file and genuinely steering in contract administration versus contract management<\/a>.<\/p>\n\n\n\n Do not start with a stricter contract, but with consumption against the ceiling. That is the figure that goes off the rails first and is the hardest to reconstruct. Put a weekly updated total on it, linked to the individual call-offs, and you catch both ceiling overruns and scope creep before they become visible in the annual figures.<\/p>\n\n\n\n Only after that comes the performance side: KPIs and SLAs per partial assignment, with an owner for each open action. For local authorities and public organisations with many decentralised call-offs, that order is the difference between steering and accounting after the fact. On the page for the public sector<\/a>, you can see how organisations bring that combination of call-offs, consumption and performance into a single environment.<\/p>\n\n\n\nFrom a signed file to a living contract<\/h2>\n\n\n\n
Where do you start with managing a framework agreement?<\/h2>\n\n\n\n