Published

A procurement officer is preparing a Contract Details Notice for steel-cladding works. The prime contractor has not appointed the subcontractor that will source the steel, so origin is still unknown. The buyer needs a supported notice entry now and a way to connect the certificates that arrive with later deliveries.
Where PPN 022 applies, record the origin status supported at award and keep its rationale with the notice. The Cabinet Office’s guidance allows a “not known” entry with a reason. Link later delivery evidence to that award record so the file explains what was known then and what was subsequently received.
The PPN’s scope and timing provisions cover central government departments, their executive agencies and non-departmental public bodies. Other public authorities may adopt the approach. The new notice measure concerns covered steel procurements under the Procurement Act 2023, including steel bought through the supply chain, commencing on or after October 1, 2026. It applies where the project or programme is worth at least £10 million or is expected to require more than 500 tonnes of steel.
Record that assessment at project or programme level. A smaller individual contract can belong to a qualifying programme. The notice and actuals thresholds do not define the scope of every PPN action: catalogue consultation and other requirements need their own checks. PPN 022 also states that it does not mandate UK-produced steel.
Paragraph 13 of the Cabinet Office guidance specifies four entries for the procurement-description field. The evidence column below is a practical filing model for the buyer’s review.
| Notice entry | Guidance meaning | Suggested review evidence |
|---|---|---|
[STEEL-ORIGIN: YES] | All steel will be UK-produced. | Statements covering the relevant steel and supply-chain scope. |
[STEEL-ORIGIN: NO] | All steel will be non-UK-produced; provide a rationale. | Supplier statement and the accepted reason for that sourcing decision. |
[STEEL-ORIGIN: MIXED] | A combination of UK and non-UK steel; explain the non-UK elements. | Identified elements, their expected sources and the reviewed rationale. |
[STEEL-ORIGIN: NOT KNOWN] | Origin is not yet known; provide a rationale. | The unresolved information, its reason and an owner for later evidence collection. |
Retain who supplied the statement, what it covered, when it was received and who accepted the proposed wording. If new information requires a notice correction, use the authority’s publication process and retain the earlier entry and the reason for the change.
Retain the scope assessment, supplier information, selected notice entry and approved rationale.
Connect the certificate and its stated facts to the actual delivery, contract and project.
Keep the delivery rows, review, submitted version and available submission evidence together.
The Cabinet Office FAQs define actuals as steel procured and delivered to the site within the reporting financial year. An order awaiting delivery is not an actual. They also distinguish certificate origin from where steel was melted and poured: use the accompanying EN10204 Type 3.1 certificate, and indicate whether it establishes both.
Preserve the origin as stated and the basis for the melted-and-poured indicator. An absent statement should not become an inferred location. For domestic projects and programmes, paragraph 14 of the PPN places the contractor’s actuals submission to the in-scope organisation no later than ten weeks after financial year-end; the organisation then consolidates its return to DBT. Record each handoff’s owner and evidence.
Fictional programme, contracts, certificates and quantities. An in-scope central government body has a £12 million domestic programme. A covered £8 million steel-cladding contract commences procurement on October 5, 2026. The project-level value meets the transparency threshold even though that individual contract is smaller.
The commercial team links the organisation, covered procurement, commencement date and £12 million programme valuation. It records the applicable steel scope and assigns the contract manager to collect supplier evidence.
At award, the prime contractor has not appointed the steel-cladding subcontractor and cannot confirm origin. The reviewer accepts [STEEL-ORIGIN: NOT KNOWN] with a rationale explaining that appointment gap. The file retains the contractor’s dated statement, reviewed wording and notice publication reference.
Later, delivery D-01 brings 20 tonnes with a certificate stating UK origin and an explicit UK melt-and-pour statement. Delivery D-02 brings 10 tonnes with a certificate stating German origin but no melt-and-pour location. The team records each certificate’s facts and the corresponding indicator without inferring a missing location.
At the reporting cutoff, a further 15-tonne order has not reached the site. The example’s delivered population is 30 tonnes: 20 plus 10. The outstanding order stays visible for follow-up and a later period. Reviewers trace the return’s rows to the two delivery references and their certificates.
The award record still explains why origin was unknown when that notice was prepared. The reporting package contains the later delivered-steel evidence and approved return. Staff retain the exact submission and available receipt, with any notice correction recorded separately through the authority’s process.
A certificate may cover several delivery lines, or one delivery may need several certificates. Keep the actual references and covered quantities explicit. If the document does not clearly cover the steel received, assign a request to the supplier and keep the gap visible to the reporting owner.
Retain the reviewed version used for a statement or return. A replacement certificate can change the current evidence without erasing what supported the earlier submission. Give commercial reviewers, receiving staff, suppliers and publication owners access appropriate to their tasks; the public notice need not expose the whole internal supplier file.
Keep the notice entry tied to what the buyer knew at award. Connect later certificates to the steel actually delivered and the reporting return they support. That gives the procurement team a traceable answer at both stages, including information gaps and authorised corrections.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.