UK tenders must separate participation from award criteria

Model two questions, not one blended score

The direct answer is that a procurement system should hold conditions of participation and award criteria as separate governed objects. For participation, preserve the legal, financial, or technical capacity being tested; proportionality rationale; supplier and associated-person scope; required evidence; pass, fail, or unresolved state; reviewer; clarification; exclusion interaction; and decision time. The record should show why the supplier may proceed without implying that its tender has won. ^[1]

For award, preserve the requirement, criterion, assessment methodology, relative importance, evaluator instruction, tender response, evidence, individual evaluation, moderation, arithmetic, conflict declaration, reason, and approved result. A supplier can satisfy participation conditions and still submit a weaker tender. Conversely, a strong-looking solution cannot cure a failed participation condition unless the Act, notice, documents, and controlled decision path permit the relevant treatment. ^[1]

Bind each rule to the published procedure

The guidance says the tender notice commences the procedure and provides access to associated tender documents or explains how they will be provided. It also permits authorities to design a competitive flexible procedure while meeting applicable procedural, transparency, time-limit, and proportionality requirements. Technology should therefore retain the procedure design, stages, entry and exit rules, negotiation or dialogue boundaries, deadlines, demonstrations, decision authorities, and the exact notice and document versions communicated to suppliers. ^[1]

Changes require a controlled chronology. Store the author, approval, publication time, affected stage, affected suppliers, revised deadline, communication, and superseded version. A configuration edit is not proof that the public notice or associated document changed, and an email is not necessarily the central-platform record. Evaluators should see which version governed each response and whether the change altered participation, award, or a procedural requirement that could cause a tender to be disregarded. ^[1]

Preserve the path from assessment to contract

The guidance describes assessment summaries, a contract award notice, standstill, contract entry, and a later contract details notice as distinct steps. Systems should not collapse a preferred bidder, approved evaluation, published award notice, ended standstill, signed contract, and published contract-details notice into one awarded flag. Preserve the responsible actor, time, receipt, exceptions, challenge or correction, and authority for each transition. ^[1]

Assessment summaries need the evidence and reasoning required for the relevant supplier without leaking another supplier's protected material. The internal record should still support consistent explanations, moderation, approvals, conflicts, and corrections. If a calculation or decision changes after summaries or notice publication, the workflow should stop dependent actions, preserve the original release, identify affected suppliers, obtain qualified review, and issue any required correction through the proper channel. ^[1]

Test a supplier that passes one gate and loses another

A representative evaluation should create a two-stage competitive flexible procedure, publish a notice and documents, amend one participation condition, receive tenders, pass one supplier on capacity, score that supplier below another on award criteria, disregard a late response under a disclosed procedural rule, correct one moderation value, and release assessment summaries. Reviewers should reconstruct every governing version, decision, reason, notification, standstill trigger, approval, and downstream state. ^[1]

The Cabinet Office guidance supports the attributed statements about the two procedure types, tender notices, procedure design, conditions of participation, award criteria, assessment summaries, award notices, standstill, and contract-details notices. It does not determine the legality, proportionality, evidence sufficiency, exclusion, evaluation, remedy, or outcome for a specific procurement. Contracting authorities, procurement professionals, evaluators, finance, information-technology, records, policy, and qualified legal advisers retain those decisions. ^[1]

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.