---
title: "Is this framework call-off worth pursuing?"
description: "Verify the framework, supplier, buyer, lot, scope and award route before spending on a call-off, then pass eligible cases to commercial review."
canonical: "https://zephior.com/insights/qualify-a-framework-call-off"
last-updated: 2026-09-03
---

# Is this framework call-off worth pursuing?

> Verify the framework, supplier, buyer, lot, scope and award route before spending on a call-off, then pass eligible cases to commercial review.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-03; updated 2026-09-03. 18 minute read.

## Definition

A framework call-off qualification determines whether one identified downstream contract can be pursued by one named supplier under one governing framework and lot. Its work product is a `framework_call_off_qualification_record`. The record fixes the jurisdiction and legal regime, framework and call-off identities, controlling versions, supplier legal entity and current party status, authorized buyer, lot, service scope, framework term, award method, invitation, deadline and response route. It separates hard participation gates from delivery, contract, economics and capacity decisions. The result is a cited state such as `eligible_for_commercial_assessment`, `eligible_with_call_off_conditions`, `supplier_not_on_required_lot`, `buyer_not_authorized_under_framework`, `scope_outside_framework`, `award_route_not_supported`, `framework_or_invitation_expired`, `source_conflict`, `clarification_required`, `legal_review_required` or `authority_missing`. It is not legal advice, an interpretation sent to the buyer, permission to accept terms or authority to submit.

## Problem

A call-off invitation looks ready for action because it names a project, a deadline and a portal. That appearance can hide the decisive questions. The invited trading name may not be the legal entity on the framework. The buyer may sit outside the named user group. The service may belong to another lot. A mini-competition may introduce deliverables or criteria that do not match the framework route. The framework may have expired, been replaced or remain subject to an earlier legal regime. Teams often discover these defects after solution design and pricing have begun. The opposite failure is to reject a valid invitation merely because no ordinary tender notice is visible. Under some regimes, a call-off uses the framework process rather than an open standalone competition. Qualification must therefore start from the framework source chain, not from the invitation headline.

## Point of view

Framework membership is necessary evidence, not a universal permission slip. First establish which rules govern the framework. In the United Kingdom, frameworks commenced under previous legislation continue under that regime, while later frameworks may use the Procurement Act 2023. Under the current Act, the framework must describe the supplies, price mechanism and selection process; current Cabinet Office guidance also directs buyers to check authorized users, scope and the permitted selection route. Article 33 of Directive 2014/24/EU and German and French implementing rules place their own boundaries around parties, buyers, terms and reopened competition. Read the actual framework, lot and call-off documents before applying any summary. An agent may retrieve, compare and structure cited facts. Legal conclusions, exceptions, buyer contact, commercial commitments and submission remain with authorized people.

## An invitation is not proof of a valid call-off

Start with two identities and the relationship between them. The framework side needs its official procurement identifier, title, contracting authority, executed agreement or award record, lot, term and current version. The downstream side needs its call-off or mini-competition identifier, inviting body, issue time, invitation version, deadline and portal route. Preserve the invitation as received. A repeated framework name, copied logo or shared portal is not enough to bind the records.

Next identify the governing regime. This matters most where a legal change sits between framework award and call-off. UK transitional guidance says commercial tools established under previous legislation continue to be managed under that legislation, including their call-off processes. A recent invitation therefore does not prove that the Procurement Act 2023 governs it. Record the founding event and the cited transition rule. For cross-border or devolved arrangements, capture the framework’s named rules and route uncertainty to a competent reviewer.

The identity gate is deliberately strict because every later comparison depends on it. If the framework link is missing, the lot is ambiguous, the agreement version cannot be recovered or two sources name different regimes, return `source_conflict` or `legal_review_required`. Do not fill the gap by copying a portal label into a field called fact.

**Identity evidence for one call-off**

| Object | Minimum evidence | Unsafe shortcut |
| --- | --- | --- |
| framework_identity | Official identifier and governing record | Matching title |
| lot_identity | Lot in award or executed agreement | Service keyword |
| call_off_identity | Invitation identifier and version | Email subject |
| relationship | Explicit framework and lot reference | Same portal |
| governing_regime | Founding event plus applicable rule | Current calendar year |
| source_state | Retrieved versions and observation times | Latest-looking file |

## Clear supplier, buyer, lot and scope before scoring the opportunity

Match legal entities, not familiar names. The supplier record should show the entity that signed or was awarded the framework, its current status and the lots for which it is a party. Record any novation, removal, suspension, exclusion issue or affiliate rule as its own sourced event. An invitation sent to a group mailbox cannot repair an entity mismatch. The buyer side receives the same treatment. Compare the calling body with the authorities named in the original notice or agreement, or test it against the exact objective category and date boundary used there.

Then decompose the requested work. Map each material service, product, work package, location and contract form to an in-scope passage in the framework and lot. Do not let an in-scope majority hide one decisive addition. A cloud migration lot may cover discovery, build and transition while excluding managed network operations. If the buyer bundles both into a non-severable award, the entire opportunity needs review. A supplier-side capability match does not cure a framework scope failure.

Validity is a separate gate. Record the framework start and end, permitted extensions, the date on which the downstream award process began and any rule concerning performance after framework expiry. Different regimes distinguish the ability to award during the framework term from the later performance period. An agent should expose those dates and passages, not convert them into a legal conclusion. Where the permitted timing is not plain, return `legal_review_required`.

**Participation gate states**

| Gate | Pass evidence | Failure state |
| --- | --- | --- |
| Supplier | Named entity is a current framework party | supplier_not_on_required_lot |
| Lot | Awarded lot covers the supplier and work | supplier_not_on_required_lot |
| Buyer | Named authority or objective category matches | buyer_not_authorized_under_framework |
| Scope | Every material deliverable maps to the lot | scope_outside_framework |
| Timing | Award process begins within permitted use | framework_or_invitation_expired |
| Evidence | Controlling sources agree and are current | source_conflict |

## The framework decides how this contract may be awarded

Read the framework’s downstream selection clauses before treating the invitation as a mini-competition. The route may be an award under a single-supplier framework, a competition among capable lot suppliers, an allocation without further competition under an objective mechanism, or another route expressly defined by the governing documents and law. Record the trigger that made this route applicable. A buyer’s preference for speed is not an objective mechanism.

Under the Procurement Act 2023, a multi-supplier framework generally requires a competitive selection process unless the framework contains the core terms and an objective supplier-selection mechanism. The current guidance says the framework must set out the selection process and restricts proposal assessment to framework award criteria, although those criteria may be refined. Article 33 of Directive 2014/24/EU and national implementations use related but not identical rules. Apply only the regime already proved for this record.

For a competitive route, compare the invitee set with the suppliers capable of performing the contract under the relevant lot. Capture conditions of participation, evaluation criteria, weightings, price basis, permitted refinements, response deadline and submission channel. For a route without further competition, capture the objective mechanism and the facts it consumes. If the invitation appears to invent a new criterion, skip an eligible supplier or use a route the framework does not support, return `award_route_not_supported` or `legal_review_required` rather than estimating win probability.

**Award route reconstruction**

| Route element | Question | Record |
| --- | --- | --- |
| Route type | Competition or documented allocation? | route_type and clause |
| Trigger | Why does this route apply now? | trigger fact and source |
| Invitees | Which lot suppliers must or may be consulted? | invitee rule and observed set |
| Conditions | What must be true at award? | condition, evidence and due time |
| Criteria | Which framework criteria are used or refined? | crosswalk and variance |
| Channel | Where and when is a response received? | event, timestamp and authority |

## A call-off completes the framework; it does not replace it

Build a two-source requirements register. One column holds obligations inherited from the framework, supplier tender and lot schedules. The other holds call-off-specific details. Link every requirement to a clause, version and status. Mark an addition as a permitted completion only when the governing documents reserve that field for the downstream award. Mark apparent changes to liability, charging, service scope, termination, intellectual property, security or performance standards for contract or legal review.

Article 33 of the EU directive says framework-based contracts must not substantially modify the framework terms. Germany’s VgV section 21 contains the same boundary and describes when an authority may request a supplier to complete its offer or reopen competition. France distinguishes agreements that leave terms for subsequent contracts from agreements executed through purchase orders, and its current rules specify how holders of the corresponding lot are consulted. These provisions help frame the evidence check. They do not let a supplier agent decide whether one disputed clause is lawful.

Capture the stated order of precedence. If the call-off says its schedule overrides the framework while the framework says the opposite, preserve both clauses and return `source_conflict`. Do not normalize them into one convenient term. The same discipline applies to pricing. A framework rate card, maximum, indexation formula, discount, competition price and call-off ceiling are different objects. Send the permitted price basis to pricing; do not infer margin or accept a revised mechanism here.

**Call-off term crosswalk**

| Classification | Meaning | Next action |
| --- | --- | --- |
| inherited | Framework term applies unchanged | Carry with source |
| completed | Reserved detail is supplied for this contract | Test evidence and fit |
| refined | Permitted criterion or requirement gains detail | Verify stated boundary |
| new_material_term | Call-off adds a material obligation | Contract and legal review |
| conflict | Sources give incompatible instructions | Block silent resolution |
| missing | Required downstream detail is absent | Clarify before commitment |

## Eligibility earns a commercial review, not an automatic bid

Once the hard gates pass, freeze the eligible scope and route it to the decisions that own the remaining questions. Delivery fit tests people, locations, dependencies and dates. Contract review tests the inherited and new risk. Pricing works from the permitted mechanism and documented demand assumptions. The bid investment decision compares remaining avoidable response cost with finance-approved contribution. Portfolio capacity resolves collisions with other pursuits. Import those records rather than rebuilding them inside the call-off decision.

Framework figures need disciplined treatment. Estimated aggregate value or ceiling does not prove the value available to this supplier. A call-off estimate may include options, uncommitted volume or multiple award scenarios. Record the attainable contract state, minimum or guaranteed amount if any, maximum, options, term and fees separately. Also capture any duty to respond, permitted no-bid route, performance score consequence or management fee stated in the framework. An attractive headline value can still be uneconomic after those terms are applied.

The final state should explain sequence. `eligible_for_commercial_assessment` means every participation gate passed, not that the bid is approved. `eligible_with_call_off_conditions` names conditions that later owners must price or satisfy. A hard failure returns its specific state and blocks response investment. `clarification_required` is time-bounded and names the official channel, question owner and last useful response time. `authority_missing` prevents analysis from becoming a de facto decision.

**Decision routing after framework checks**

| State | Meaning | Allowed next step |
| --- | --- | --- |
| eligible_for_commercial_assessment | All framework gates pass | Run specialist bid reviews |
| eligible_with_call_off_conditions | Pass with explicit downstream conditions | Review and price conditions |
| clarification_required | A resolvable official fact is missing | Draft authorized clarification |
| legal_review_required | Regime or term boundary needs counsel | Obtain scoped opinion |
| hard_gate_failed | Supplier, buyer, lot, scope, route or time fails | Do not invest in response |
| authority_missing | No role may approve the next action | Hold without external action |

## Return the evidence chain, not a confident green badge

Publish the record in a stable structured form and a readable explanation. Required fields include object identifiers, jurisdiction, governing regime and basis, supplier and buyer legal entities, party and lot status, scope mappings, framework term, route, invitation, dates, document versions, clause crosswalk, gate results, contrary evidence, unresolved questions, decision state, owner, authority, expiry and allowed next action. Each material fact needs a source URL or controlled document reference, exact passage, retrieval time and verifier.

Consider a fictional cloud-services supplier admitted to Lot 2 for application migration. A city-owned company sends a mini-competition for migration plus continuous network-security operations. The agreement names city departments and certain controlled bodies, but the company’s eligibility under that category is unclear. Network operations appear in Lot 4, where the supplier is not appointed. The record does not average two red gates into a moderate fit score. It returns `buyer_not_authorized_under_framework` as unresolved and `supplier_not_on_required_lot` for the non-severable scope, with cited passages. No price or win score is calculated.

An agent may retrieve public sources, compare versions, extract clauses, map deliverables, calculate dates and assemble the draft record. It should show when a source was inaccessible or a match relied on an assumption. It may not log into a restricted portal without delegated access, accept terms, impersonate the supplier, contact the buyer, choose a legal interpretation, waive a condition, commit capacity or submit. The next agent or person should receive a bounded task, not hidden permission.

- Use exact framework, lot and call-off identifiers in every machine-readable object.
- Keep observed facts, legal interpretation and commercial judgment in separate fields.
- Attach contrary evidence and unresolved states, not only the preferred answer.
- Expire the record when the invitation, framework source or supplier status changes.
- Require explicit authority before any external communication or submission.

## Useful outcomes

- One immutable record identifies the framework, call-off, lot, invitation and current document versions.
- The governing jurisdiction, regime and transition basis are cited rather than inferred from publication date.
- The supplier legal entity is proved to be a current party to the relevant framework and lot.
- The calling buyer is matched to the users named or objectively described by the governing documents.
- The requested goods, services or works are traced to the framework and lot scope.
- The proposed award route is compared with the route and objective mechanism allowed by the framework.
- Inherited terms, call-off additions, criteria, prices and order of precedence remain distinguishable.
- Eligibility failures stop response investment before revenue, probability or strategic value is scored.
- Eligible cases carry explicit conditions into delivery, contract, capacity and investment reviews.
- Agents return evidence, uncertainty, prohibited actions and the next authorized decision.

## Workflow

1. **Bind the two procurements.** Record the framework identifier, lot, supplier award or executed agreement, call-off identifier, invitation version and every explicit link between them. Similar titles do not prove the relationship.
2. **Establish the governing regime.** Identify jurisdiction, founding procurement date, transition rule and the framework clause that controls downstream awards. Preserve the cited basis and send ambiguity to legal review.
3. **Prove both parties.** Match the invited supplier to the admitted legal entity and relevant lot. Match the caller to the named authority or objectively delimited buyer category.
4. **Test scope and validity.** Compare every material deliverable, geography, contract type and timing with the framework and lot. Check the framework was valid when the downstream award process began.
5. **Reconstruct the award route.** Classify single-supplier award, competition, objective allocation mechanism or another documented route. Verify invitees, conditions, criteria, response period and channel against the governing documents.
6. **Map inherited and new terms.** Build a clause and requirement crosswalk showing which terms are fixed, refined, completed, conflicted or missing. Do not silently choose an order of precedence.
7. **Run the participation gates.** Return a failing or indeterminate state before scoring opportunity value. Give every unresolved gate an owner, permitted route, deadline and evidence required to clear it.
8. **Hand off the eligible case.** Send the bounded scope, inherited obligations and call-off conditions to delivery fit, contract risk, pricing, portfolio capacity and remaining-investment decisions. Preserve the framework record as their input.

## Key decisions

- Which exact framework, lot, call-off and invitation version does this record govern?
- Which jurisdiction and procurement regime apply to the downstream award?
- What source proves the transition position where legislation changed after the framework began?
- Is the invited legal entity currently a party to the required framework and lot?
- Is the caller a buyer permitted to award under this framework?
- Does every material deliverable sit inside the framework and lot scope?
- Was the award process initiated while the framework could be used?
- Which call-off method does the framework permit for this purchase?
- Do the invitee set, objective mechanism, conditions and criteria follow that method?
- Which terms are inherited, which may be completed or refined, and which appear inconsistent?
- Does the supplier have a response obligation, a permitted decline route or a framework fee?
- Who may clear an exception, request clarification, approve investment and authorize submission?

## Risks

- A portal invitation may address a brand or affiliate that is not the framework supplier.
- A supplier may be on the framework but not on the lot that owns the requested work.
- A buyer name may resemble an eligible body without falling inside the governing category.
- A public listing may be mistaken for an open tender available to non-framework suppliers.
- A legacy framework may be assessed under the Procurement Act 2023 solely because the call-off is recent.
- A framework end date may be confused with the permitted duration of a properly awarded call-off contract.
- A mini-competition may add work outside the described goods, services or works.
- New criteria may be treated as a harmless refinement without checking the governing framework.
- Framework ceiling or estimated value may be modeled as available call-off revenue.
- A mandatory response rule or management fee may be omitted from the economic case.
- A clarification deadline may pass while the team debates an unresolved participation gate.
- An agent may contact the buyer, accept a contract term or start a submission without authority.

## Metrics

- records with framework, lot, call-off and invitation identifiers
- governing regimes supported by a transition or commencement source
- supplier and buyer matches supported by exact document passages
- material deliverables mapped to framework and lot scope
- award routes reconstructed before response investment
- call-off additions classified as permitted, conflicted or unresolved
- ineligible cases stopped before solution and pricing work
- eligible cases handed off with inherited obligations intact
- unresolved gates carrying owner, deadline and allowed next action
- unauthorized buyer contact, commitment or submission; target zero

## Frequently asked questions

### Can a supplier bid simply because it appears on the framework?

No. Confirm the named legal entity, relevant lot, current party status, authorized buyer, scope, award route and call-off conditions. Framework membership alone does not answer those questions.

### Can a supplier outside the framework enter a call-off competition?

Do not assume an open route. Check the governing regime and documents. Framework call-offs commonly operate among suppliers already party to the framework or relevant lot.

### Why might a valid call-off have no ordinary tender notice?

Some regimes use the framework’s downstream selection process instead of a new open tender notice. For example, current UK guidance says tender notices are not published for call-off contracts under the Procurement Act 2023.

### Does the Procurement Act 2023 govern every UK call-off issued now?

No. UK transitional guidance preserves previous legislation for frameworks commenced under the earlier regimes and for their downstream call-off processes. Prove the framework history before selecting the rule set.

### May a call-off add requirements not written word for word in the framework?

It may be able to complete or refine matters the framework leaves for the downstream contract, depending on the governing rules and documents. Material additions or conflicts need contract or legal review rather than an automated conclusion.

### Does the framework ceiling show the revenue available from this call-off?

No. Keep aggregate framework value, call-off estimate, maximum, committed volume, options and the supplier’s attainable award state separate.

### Can an agent decide that a buyer category includes the inviting body?

An agent can compare the legal entity and category wording and expose the evidence. Ambiguous category boundaries should go to an authorized procurement or legal reviewer.

### What happens after all framework gates pass?

The case moves to delivery, contract, pricing, capacity and remaining-investment decisions. Passing framework qualification is not bid approval.

### Can the qualification agent submit the response?

Only a separately authorized submission workflow may do that. This record supports a decision and must not itself grant portal access, accept terms or authorize submission.


## Primary sources

- [Procurement Act 2023, sections 45 and 46](https://www.legislation.gov.uk/ukpga/2023/54/pdfs/ukpga_20230054_en.pdf), The National Archives
- [Guidance: Frameworks, updated 13 July 2026](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-define-phase/guidance-frameworks-html), UK Cabinet Office
- [Guidance: transitional and saving arrangements](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-plan-phase/guidance-transitional-and-saving-arrangements-html), UK Cabinet Office
- [Directive 2014/24/EU, Article 33, consolidated 1 January 2026](https://eur-lex.europa.eu/eli/dir/2014/24/2026-01-01/eng), European Union
- [VgV section 21, framework agreements](https://www.gesetze-im-internet.de/vgv_2016/__21.html), Federal Ministry of Justice, Germany
- [French Public Procurement Code, subsequent contracts](https://www.legifrance.gouv.fr/codes/section_lc/LEGITEXT000037701019/LEGISCTA000037724350/), Légifrance


## Related articles

- [Framework agreement: call-offs, value and bidder risk](https://zephior.com/glossary/framework-agreement)
- [Which tender lots should you bid?](https://zephior.com/insights/choose-which-tender-lots-to-bid)
- [Can you qualify a tender without speaking to the buyer?](https://zephior.com/insights/qualify-a-tender-without-buyer-access)
- [How to qualify a tender when the budget is missing](https://zephior.com/insights/qualify-a-tender-without-budget-information)