If you're buying or supplying the same kinds of goods or services over and over, signing a brand-new contract every time can get old fast.
That's where a framework agreement comes in. It's a practical way to set the ground rules once, so future orders (and future disputes) are much easier to manage.
In this guide, we'll break down what a framework agreement is, when it makes sense, what clauses matter most, and the common traps to avoid - in plain English, with a UK small business lens.
What Is A Framework Agreement (And What It's Not)?
A framework agreement is an "umbrella" contract that sets out the core terms that will apply to future purchases (often called "call-offs", "work orders", or "statements of work").
Instead of negotiating the full legal detail every time you place an order, you agree the big-ticket legal items upfront - like pricing structure, service standards, liability, and how disagreements are handled - and then you "switch on" the contract for each piece of work using a shorter document.
Framework Agreement vs "Normal" Contract
A traditional contract often covers:
- exact scope of work (what you're delivering)
- exact dates and milestones
- exact price
- full legal terms (IP, confidentiality, liability, termination, etc.)
A framework agreement usually covers:
- the legal framework that will apply to multiple future projects/orders
- the process for issuing call-off work (and what documents form part of the deal)
- the commercial structure (rate cards, pricing rules, payment terms, discounts)
- the risk allocation (liability caps, indemnities, insurance)
Then each future project is confirmed through a short order form or statement of work that plugs into the framework.
Framework Agreement vs Master Services Agreement (MSA)
You'll often hear "framework agreement" and "master services agreement" used interchangeably - especially in professional services and tech.
In practice, an MSA is commonly the "framework" for service-based engagements. The key difference is often industry convention and how the documents are structured, rather than any strict legal rule.
For service businesses, a master services agreement is a typical way to document the framework terms, with statements of work added as you go.
Framework Agreement vs Heads Of Terms
Framework agreements are usually intended to be legally binding (or at least largely binding), because they're designed to govern real purchases.
Heads of terms (or heads of agreement) are commonly used earlier - to summarise the commercial deal while the full contract is being drafted, and they can be partly binding, non-binding, or a mix.
If you're still negotiating the "shape" of a relationship, starting with Heads of Agreement can be helpful - but you generally don't want to rely on that document to run ongoing supply or service delivery.
When Should You Use A Framework Agreement?
Framework agreements aren't just for big corporates or government procurement. They can be a great fit for UK SMEs - as long as you're using them for the right reasons.
You should consider a framework agreement if:
- You're doing repeat work for the same customer (or using the same supplier) and don't want to renegotiate the legal terms each time.
- The scope changes from project to project, but the legal risk stays similar (e.g. marketing, IT support, consultancy, facilities, logistics).
- You need faster onboarding for new tasks - especially where your team needs to start work quickly.
- You want consistent risk allocation (liability caps, indemnities, IP ownership, confidentiality) across multiple orders.
- You're scaling and want a repeatable contracting process that doesn't break every time a new project starts.
Common Use Cases For UK Businesses
Framework agreements show up in a lot of everyday commercial relationships, for example:
- IT and SaaS services: ongoing support plus new feature work through separate statements of work
- Marketing agencies: a master agreement with monthly campaigns issued as work orders
- Construction and trades: repeat maintenance jobs with call-off tasks
- Product supply: a framework plus purchase orders as needed (often paired with a Supply Agreement)
- Recruitment / staffing: repeat placements under the same contractual rules
Done well, a framework agreement lets you move faster without cutting corners on your legal protection.
How Does A Framework Agreement Work In Practice?
The simplest way to think about it is: the framework sets the rules of the game, and each call-off is a "match" played under those rules.
Step 1: Agree The Core Terms Upfront
The framework agreement typically covers the terms that are painful (and risky) to renegotiate repeatedly, such as:
- definitions (what key terms mean)
- how you'll accept instructions and give approvals
- payment terms (including invoicing mechanics)
- intellectual property and licensing
- confidentiality
- data protection responsibilities
- liability caps and exclusions
- termination rights and what happens on exit
- dispute resolution and governing law
This is also where you should line up your "contract hierarchy" (more on that below), so you don't end up arguing later about whether the purchase order overrides the framework.
Step 2: Issue Call-Offs For Each Project Or Order
Call-offs are the documents that make a specific piece of work happen under the framework. They're usually shorter and more commercial than legal.
A call-off might be called:
- statement of work (SOW)
- work order
- purchase order (PO)
- service schedule
- call-off contract
Typically, the call-off includes the specifics:
- what you're delivering
- timelines and milestones
- fees for that work (or a reference to the rate card)
- project-specific assumptions and dependencies
- named contacts and governance
Step 3: Manage Changes Without Breaking The Contract
One of the biggest benefits of a framework agreement is that you can manage change in a controlled way.
Instead of rewriting the whole contract, you might:
- issue a change request under the call-off
- issue a new call-off (for additional work)
- vary the framework (less common, but sometimes needed for major commercial changes)
If you're dealing with changes regularly, it's worth understanding the difference between novation and assignment too - particularly if your customer wants to transfer the framework to another group entity during a restructure.
A Quick Note On Public Sector "Frameworks"
You may also hear "framework agreement" in the public procurement context (where contracting authorities set up frameworks that approved suppliers can be called off from).
The legal rules for those frameworks can be more specialised and change over time (including due to ongoing procurement reforms).
If you're supplying into a public sector framework, the commercial reality is often: the framework terms are largely fixed, and your job is to understand the risk profile before you sign - especially around KPIs, audit rights, and termination.
What Should A Framework Agreement Include?
A good framework agreement is more than "some general terms plus future orders". The details decide whether it's actually workable - and enforceable - when something goes wrong.
Here are key clauses you'll usually want to think about.
1) Scope And "No Commitment" Language
Many frameworks include wording that the customer is not guaranteed to place any minimum volume of orders.
This can be fair (customers don't want to promise spend they can't guarantee), but it can also create a commercial risk for suppliers who invest upfront.
If you're the supplier, you might push for:
- minimum spend or minimum volume commitments
- exclusivity (in limited scenarios)
- clear forecasting obligations (even if not binding)
- fees for onboarding, setup, or reserving capacity
If you're the customer, you'll usually want to keep flexibility - but still ensure the supplier must meet service levels when you do call work off.
2) Contract Hierarchy (What Wins If Documents Clash?)
This is one of the most important - and most overlooked - parts of a framework agreement.
In the real world, documents clash. For example:
- the framework says payment is 30 days, the PO says 60 days
- the framework says your liability cap is ?50,000, the SOW tries to increase it
- the framework says IP is assigned to the customer, but the SOW says the supplier retains IP
A clear hierarchy clause sets out the order of precedence, such as:
- call-off (but only for scope/timelines/pricing)
- framework agreement
- schedules
- purchase orders (often last, or excluded)
This saves you from "battle of the forms" arguments later.
3) Pricing Structure And Payment Terms
Framework agreements often work best with a predictable pricing structure, like:
- rate cards (daily rates / hourly rates)
- fixed prices per deliverable category
- discount tiers based on volume
- price review mechanisms (e.g. annual uplift, CPI-linked increases)
If you build in price increases or uplifts, you should set out the notice and calculation method clearly. Price change disputes are avoidable when you've set expectations upfront.
4) Service Levels, Acceptance, And Governance
If the framework is for services, you'll usually want to document how performance is measured and managed, such as:
- service levels (SLAs) and KPIs
- support response times
- how deliverables are accepted or rejected
- rectification periods (a chance to fix issues)
- project governance (meetings, reporting, escalation paths)
In many disputes, the problem isn't that someone "didn't perform" - it's that no-one agreed what "done" looked like.
5) Intellectual Property (IP) And Licensing
Framework agreements are a common place for IP confusion, especially in creative, tech, and consultancy work.
Key questions to clarify include:
- Who owns pre-existing IP (background IP)?
- Who owns new deliverables created under each call-off (foreground IP)?
- Does the customer get an assignment of IP, or a licence to use it?
- What happens with reused tools, templates, code libraries, and know-how?
Even if you've got a great commercial relationship, you don't want IP ownership to be "implied". It's much easier to agree it now than argue about it after you've delivered value.
6) Liability Caps, Indemnities, And Risk Allocation
Liability is where framework agreements often carry the most value. You set the risk position once, then rely on it repeatedly.
Most frameworks include some combination of:
- overall liability caps (e.g. a fixed amount or a multiple of fees)
- excluded losses (like indirect or consequential loss)
- indemnities for third-party claims (e.g. IP infringement)
- insurance requirements
If you're working through what's market-standard (and what's enforceable), it helps to understand how limitation of liability clauses work in UK contracts.
7) Confidentiality And Data Protection
Many frameworks include confidentiality terms, but if personal data is being processed (customer lists, employee details, end-user data, analytics, etc.), you'll usually need to address data protection properly too.
Depending on the relationship, that could include:
- controller/processor roles
- security obligations
- sub-processor rules
- international transfers
- data breach notification
Where you're collecting personal data directly (particularly online), your public-facing documents matter too - for example, having a Privacy Policy that matches what you actually do in practice.
8) Term, Termination, And Exit Management
Framework agreements often run for a fixed term (e.g. 1?4 years) with options to extend.
Think about what you need if the relationship ends, such as:
- what happens to ongoing call-offs when the framework ends
- termination for convenience (and whether fees are payable)
- termination for breach and cure periods
- handover obligations (returning data, transferring work-in-progress)
- post-termination access and licences
This is one of those areas where it's easy to be optimistic and say "we'll work it out later" - but having an exit plan in the contract is what protects your business if the relationship sours.
Common Framework Agreement Risks (And How To Avoid Them)
A framework agreement can save you time and reduce disputes - but only if it's drafted and used properly.
Here are the big issues we see in practice.
Risk 1: The Framework Doesn't Create Any Binding Obligations
Some frameworks are drafted so loosely that they don't clearly create enforceable obligations (or they rely too heavily on "we'll agree later" language).
If your framework is intended to be binding, you need clarity on:
- what is agreed now vs what is agreed in a call-off
- how call-offs are formed (signatures, email acceptance, portal acceptance)
- which terms automatically apply to every call-off
Unclear acceptance mechanics can lead to arguments about whether a call-off was ever validly created.
Risk 2: Call-Offs Accidentally Override The Core Protections
It's common for operational teams to issue work orders quickly and include additional terms (sometimes copied from another deal).
Without a clear hierarchy clause - and internal discipline - you can end up with key protections being undermined. That can include liability caps, payment terms, IP ownership, and termination rights.
Risk 3: Scope Creep And "Free Extras"
Frameworks can make repeat work feel informal, which can be great for speed - but dangerous for scope creep.
As the supplier, you want a clear process for:
- change requests
- additional fees for out-of-scope work
- assumptions and dependencies (what you need from the customer)
As the customer, you want transparency on what's included, and what triggers extra charges, so budgeting doesn't get messy.
Risk 4: Pricing Reviews Turn Into Pricing Disputes
"We'll review pricing annually" sounds simple - until you're in year two and you can't agree on the increase, the benchmark, or whether it applies to existing call-offs.
If you include a price review mechanism, make it specific:
- what can change (rates? minimum fees? expenses?)
- when it changes
- how it's calculated
- what notice is required
- what happens if you can't agree (termination right, escalation, etc.)
Risk 5: The "Framework" Conflicts With Your Standard Terms
Many businesses have their own terms in the background - website terms, order confirmations, platform terms, or standard T&Cs.
If you're using a framework agreement, you generally want it to be the primary contract governing the relationship, and for other terms to be excluded (or clearly subordinated), otherwise you can end up with a messy "which terms apply?" situation.
If your business relies heavily on standard terms, it can help to have them properly set up and consistent - like standard terms and conditions that match how you actually sell and deliver.
Risk 6: The Framework Isn't Signed Or Executed Correctly
This sounds basic, but it matters. If the framework is meant to be legally binding, you want clear evidence of agreement, especially where:
- the other party is a company (and you're relying on company signing rules)
- the contract is executed as a deed (less common for frameworks, but possible in some settings)
- you're accepting via email or an e-sign platform
If you're unsure what "properly executed" looks like in the UK, the practical rules around executing contracts and deeds are worth getting right from day one.
Key Takeaways
- A framework agreement is an umbrella contract that sets the core legal and commercial terms for future call-off work, so you don't have to renegotiate everything each time.
- Frameworks work best for repeat supply or repeat services where scope varies between orders but the risk profile stays broadly consistent.
- The call-off documents (SOWs, work orders, POs) should cover project specifics, while the framework governs the key protections like liability, IP, confidentiality, and termination.
- A clear contract hierarchy is essential, so you don't end up in disputes about whether a purchase order overrides the framework.
- Common pitfalls include scope creep, unclear price review mechanisms, accidental conflicts with standard terms, and poor execution/signing practices.
- Because the framework sets the rules for an ongoing relationship, it's worth getting it drafted (or reviewed) properly rather than relying on generic templates.
If you'd like help putting a framework agreement in place (or reviewing one you've been sent), you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.
