Tender-notice reading guide

Read the evidence before you read opportunity into it.

A notice is a published source record, not a complete bid pack or a recommendation. Retain its identifiers, read the fields in a deliberate order and verify the live documents before deciding what the opportunity means for your organisation.

Published
Updated
Next review
Published evidenceSource notice
Supplier workVerify and judge

Reading order

Six checks before the bid question.

Move from identity to instructions. A promising title is not a substitute for the complete route.

  1. 1

    Identity and version

    Record the official service, notice identifier, OCID or source reference, publication date and whether a later version exists.

  2. 2

    Buyer and scope

    Confirm who is buying, what outcome or supply is described, whether the requirement is a contract or framework, and which organisation owns the response.

  3. 3

    Lots and value

    Read each lot separately. Treat an estimated value as the buyer's published estimate—not the award value, guaranteed revenue or spend available to one supplier.

  4. 4

    Dates and route

    Separate enquiry, submission, award and contract dates. Follow the named portal and documents; the summary page is not the response workspace.

  5. 5

    Participation

    Check conditions of participation, framework or dynamic-market membership, geography, contract category and any lot-specific restrictions.

  6. 6

    Evaluation and documents

    Read the visible award criteria, then open every attachment for the specification, pricing, terms, response format and clarification rules.

Four evidence layers

Do not let presentation become proof.

Scout retains the source trail and provides consistent fields. Supplier judgement remains a separate act.

LayerWhat belongs there
Source factThe official record publishes a £500 million estimated framework value, five lots, a 27 March 2026 deadline and a named SAP Ariba route.
Normalised fieldScout may present that value in GBP, group revised publications and map dates, stages, buyers and CPV codes into consistent fields.
Supplier inferenceA relevant lot may justify reading the documents. It does not prove that your organisation qualifies, can win work or will receive any share of the estimate.
Supplier decisionOnly your evidence, capacity, route eligibility, economics and the complete official documents support a bid/no-bid decision.

Source-linked examples

Different markets expose different traps.

These examples were checked on 1 September 2026. They are historical reading exercises; deadlines and status must be checked at source.

Construction: Kendal Close repair works

The source exposes works CPVs, North West location, a 55% quality / 45% price split and an external response portal. Its £0 estimate is a published source value to investigate, not evidence that the work is free or valueless.

Read notice 2026/S 000-000832

Health and equipment: a five-lot framework

The revised notice separates lot scope, a framework-wide estimate, participation conditions, criteria and a required SAP Ariba route. Read the lot that fits; do not apply the headline value to every supplier or lot.

Read notice 2026/S 000-018890

Professional services: a Northern Ireland route

The council's mechanical and electrical consultancy notice says submissions must go through eTendersNI. A Find a Tender record can therefore be useful evidence without owning the response journey.

Read notice 2026/S 000-014709

Choose one notice and build a source sheet.

Record its source ID, buyer, lot, value basis, deadlines and criteria. Then verify the official notice, documents and submission route, keeping unanswered questions visible instead of filling them with assumptions.

Learn what an award notice supports, or use the procurement glossary for a field or term.