UK frameworks and dynamic markets govern different access models

Compare the three commercial-tool records

Source basis: ^{[1] [2]}

Choose the access model before configuring the workflow

The direct answer is conditional. A standard framework supports future call-off contracts from the supplier set appointed to that framework. An open framework is a scheme of successive frameworks and allows new suppliers to enter when the framework is formally re-opened. A dynamic market is a list of qualified suppliers that must remain open to applications throughout its life. These are different commercial-tool architectures, not three interface labels for the same sourcing event. ^{[1] [2]}

Start with the requirement, relevant contracting authority, jurisdiction and territorial reach, expected market entry and change, desired supplier-access cadence, call-off or contract-award route, contract scope, operating capacity, notice obligations, transition position, and applicable thresholds or exclusions. Do not select a tool merely because a platform exposes a framework, marketplace, vendor list, or dynamic event option. Product configuration cannot decide which statutory route applies to a particular procurement.

Keep contract award, framework refresh, and market admission separate

The framework guidance defines a framework as a contract between a contracting authority and one or more suppliers that provides for future contract awards. It defines an open framework as a scheme of successive frameworks on substantially the same terms. The dynamic-markets guidance instead describes a list of qualified suppliers and states that documents establishing or modifying it are not a contract for the Act's contract-award and modification rules. Calling every object an awarded supplier list would erase the legal and operational distinction. ^{[1] [2]}

Model at least four linked but separate records: the commercial tool and its governing documents; supplier application, tender, assessment, and admission or framework-award state; each selection or competitive procedure for a later contract; and the resulting call-off or public contract. Preserve identifiers, parts or lots, participating authority, supplier, scope, effective dates, source notice, conditions, assessment, decision owner, exceptions, and history for each object. Membership or framework appointment creates eligibility within its actual terms; it does not prove that a later contract was awarded or performed.

Supplier entry follows three different clocks

A standard framework generally fixes its appointed supplier population for the framework term. An open framework creates planned opportunities to award successive frameworks on substantially the same terms; the guidance says new suppliers can be added when it is re-opened and explains re-opening intervals, existing-supplier options, and a separate single-supplier rule. A dynamic market goes further on admission cadence: authorities must accept applications at any time, consider them within a reasonable period, admit qualifying suppliers as soon as reasonably practicable, and cannot cap supplier numbers. ^{[1] [2]}

Those clocks create different service obligations. For an open framework, the system should hold the scheme, each successive framework, re-opening timetable, terms that must remain substantially the same, supplier election or tender basis, assessment, award, expiry, and any in-progress call-off treatment. For a dynamic market, it should support continuous application intake, proportional membership conditions, decision reasons, parts, admissions and removals, current public membership, and applications that arrive near a procurement deadline. A single onboarding status cannot reliably represent all three. ^{[1] [2]}

Map the later award route and notice chain

Framework appointment and dynamic-market membership do not authorize the same later action. The framework documents must contain the selection process for call-off contracts, and responsibility remains with the authority making a call-off. For a dynamic market, the guidance says an award by reference to an appropriate dynamic market uses the competitive flexible procedure; membership is required for participation, but admission is not the contract award. The intended award route, authority, competition state, notices, conditions, criteria, contract record, and downstream implementation should therefore remain explicit. ^{[1] [2]}

Fees also need their own governed fields. The framework guidance says supplier fees can be charged only to suppliers awarded a call-off, as a fixed percentage of the call-off's estimated value, when the required details are set out. For a non-utilities dynamic market, the guidance likewise ties a fixed-percentage fee to suppliers awarded a contract rather than membership. The exact rule depends on tool and scope. A software total should never make a membership fee, framework-management charge, award-based fee, contract value, and supplier invoice look equivalent. ^{[1] [2]}

Test the design without flattening statutory exceptions

Run three representative designs through the product: a standard framework with a later call-off selection, an open framework re-opened for an entrant while an earlier call-off is already under way, and a dynamic market receiving a qualifying application near a tender deadline. Inspect the legal object, authority and scope, notice versions, supplier eligibility, admission timing, assessment basis, later award route, reasons, fee basis, expiry or cessation, publication output, and an exportable chronology. Add an excluded supplier, changed market part, failed notice, late application, single-supplier outcome, and attempted administrator overwrite.

The Cabinet Office pages are guidance current on October 6, 2026; they do not decide a buyer's lawful route or exhaust every route, special regime, exception, transition, or territorial issue. Defence and security, utilities, light-touch, single-supplier, below-threshold, exempt, concession, third-party-framework, centralised-authority, and intra-UK circumstances can change the analysis. This comparison does not establish that any tool, supplier, authority, framework, open framework, dynamic market, call-off, notice, fee, or contract is lawful, suitable, current, complete, or correctly configured. ^{[1] [2]}

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Procurement Technology Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.