When should an organisation use a framework agreement?

A framework agreement establishes the terms, and usually the pricing basis, on which purchases may be made from an appointed supplier or group of suppliers over a period. It is not a contract for anything until a call-off is made against it. The call-off is the actual contract: the volume, the service levels and the commitment all arrive with it, which is why it deserves more attention than it usually gets.

Being on a framework obliges a supplier to nothing except to remain available on the agreed terms, and in most cases it obliges the buyer to nothing at all. Most cases is not all: single supplier and some construction and consultancy models carry exclusivity or minimum volume provisions on the calling-off body, and that is precisely the kind of thing worth reading before assuming it is not there.

Speed

The largest legitimate reason. A call-off skips supplier selection entirely, which is where most of the elapsed time in a full procedure goes. A competition among framework suppliers is still weeks rather than days once you allow for clarifications and evaluation, so the honest comparison is weeks against months, not days against months.

A compliant route

The competition that appointed the suppliers has been run by someone else and the audit trail for that sits with the framework owner. Useful, and not a substitute for a defensible record of your own call-off decision.

Pre-negotiated terms

Sometimes genuinely better than an individual organisation would achieve, particularly on liability and standard clauses. Sometimes materially worse. Read them.

Lost competitive tension

The cost. Framework rates are commonly ceiling rates set against an aggregated opportunity rather than a price for your requirement. Awarding at those rates on a material requirement leaves money on the table.

Specification constraint

The requirement has to fit what the framework covers. Stretching one to fit a lot is a commercial mistake anywhere and, in a regulated procurement, a challenge risk that sits with the calling-off body rather than with the framework owner.

Supplier fees

Frameworks are commonly funded by a fee paid by suppliers and recovered in the price. Under the current regime a fee can only be charged to a supplier awarded a call-off, must be a fixed percentage of that contract's estimated value, and has to be set out in the framework documents and the tender notice. There is no separate access or management fee to be negotiated away, so treat it as part of the price rather than as a line to attack.

Whether to run a competition among the framework's suppliers or award without one is the decision that determines whether a call-off is good commercial practice or an administrative shortcut. It is worth being precise about the terms, because two of them are commonly used loosely.

Awarding a call-off without competition is only available where the framework itself sets out the core terms of the call-off contracts and an objective mechanism for selecting the supplier, and it is not what the legislation means by direct award. Direct award is a separate route with its own narrow grounds, used to place a contract without a competitive tendering procedure at all. Confusing the two in a decision record is the kind of thing that gets quoted back at you.

• Awarding without competition is defensible for low value, urgent or genuinely standardised requirements where the framework's own selection mechanism produces the answer.
• Competing is worth the additional weeks wherever the value is material, the requirement has any specificity to it, or the rates are ceilings rather than firm prices.
• Refining the requirement before competing is what produces the difference. A call-off document that restates the framework specification will produce the framework price.
• There is a boundary to that refinement. You cannot make substantial changes to the framework's terms at call-off, and you cannot introduce award criteria the framework did not envisage. Where the framework sets a permitted range for the price and quality weightings, that range is the room you have.
• Expect a smaller field than the lot suggests. On large multi-supplier lots a response of two or three is normal and a single response is not unusual, which is the main reason competitions inside frameworks disappoint.

One practical difference is worth knowing before planning the timetable: the competitive selection process used to award a call-off is not a competitive tendering procedure, so assessment summaries and the mandatory standstill period do not apply. Some authorities run a voluntary standstill anyway. That is a judgement about challenge risk rather than a requirement.

The framework decides who can bid. The call-off decides what you pay.

• Whether your organisation is actually named or covered as a permitted user.
• The lot structure, and which lot the requirement genuinely falls in rather than which one is closest.
• The framework's expiry, and whether a call-off term is permitted to run beyond it. Under the current regime the general maximum framework term is four years, with eight for defence and security and for utilities, and longer only where the nature of what is being supplied requires it and the reasons are published. Open frameworks work differently again, running as a scheme of successive frameworks up to eight years with mandatory reopening, which is how new suppliers get in.
• Whether the rates are firm, indexed or ceiling rates, and what the indexation clause actually says.
• The call-off terms, particularly liability, termination, intellectual property and exit, and how much of them you are permitted to amend.
• The change control mechanism, because requirements move and an inflexible call-off becomes a problem in year two.
• Whether the framework owner manages supplier performance in any meaningful way. Usually the answer is that they do not, and above a value threshold you now carry published performance duties of your own regardless.

That last one catches people out. A framework call-off is a contract like any other for the purposes of the published performance regime, so the KPIs have to be written into it and someone has to own the assessment afterwards.

A framework call-off is one option among several, and it is frequently chosen by default because the others were never considered.

1. 01Modify or extend the existing contractThe first thing an experienced practitioner looks at when a contract is running out, and the option most often skipped. Public contracts can be modified in defined circumstances, including below certain value thresholds, and a contract change notice may be required. It is a narrow route with real limits and it is not the same as an extension nobody has grounds for.
2. 02A dynamic marketA list of qualified suppliers that must stay open to new applicants throughout its life, which suits markets that change quickly or where new entrants matter. The important practical difference from a framework is that a contract awarded under one has to be competed, so it does not offer the speed a framework does. The old dynamic purchasing system and qualification system terminology no longer applies.
3. 03Aggregate with another organisationSlower and often better priced, and it needs the other organisation's timetable to match yours, which is why it works when planned and not when it is a rescue.
4. 04Run your own procedureWhere the requirement is large, well understood and attractive to the market, a direct approach frequently produces a better answer, and the time cost may be affordable if the expiry was seen coming.

That last condition is the recurring one. Where frameworks are being used mainly because contracts expired without warning, the framework question is a symptom. Contract expiry and notice data is the cheaper fix, and it turns the framework back into a choice.

1. 01Awarding at ceiling rates on a material requirementFast, compliant, and more expensive than the same requirement competed among the same suppliers. The saving in elapsed time is real and it is usually smaller than the price difference.
2. 02Treating the call-off terms as settledMany frameworks allow the call-off terms to be refined within limits. Accepting the default position without reading it transfers risk that did not need transferring.
3. 03Stretching the scopeBuying something adjacent to what the framework covers because it is convenient. The risk sits with you, not with the framework owner.
4. 04A call-off term the framework does not supportDiscovered late, expensive to unwind, and entirely avoidable by checking at the start.
5. 05No performance management after awardThe framework owner is not managing your supplier. If nobody in your organisation owns the call-off contract, nobody is.