How to Read a UK Contract Award Notice (Fields Explained)

Award notices are the only published proof of who holds a contract — essential for incumbent mapping, displacement qualification, and renewal forecasting.

Misreading value fields (contract vs lifetime, VAT inclusive vs exclusive) leads to wrong pipeline sizing and unrealistic bid pricing assumptions.

Award date plus stated duration is the foundation of contract expiry estimates — errors here cascade into missed re-tender windows.

Buyer intelligence teams use award history to prioritise accounts; inconsistent field extraction makes cross-buyer comparison unreliable.

Under the Procurement Act 2023, more awards flow through the Central Digital Platform — teams that standardise field reading scale intelligence faster.

Analysts open each notice in the portal and copy supplier name and value into spreadsheets — different people capture different fields.

PDF downloads are filed in SharePoint without structured metadata, so renewal teams cannot search by buyer or CPV.

Teams confuse contract award notices with contract details or modification notices — mixing lifecycle stages in one tracker.

CPV codes are skipped because titles look descriptive enough — then sector filters miss related awards at the same buyer.

Framework call-off awards are treated like standalone contracts, hiding parent framework end dates that drive re-procurement.

No shared glossary: one person logs 'start date', another logs 'award date', breaking expiry maths across the CRM.

Notice type: Contract Award Notice (CAN) on Find a Tender or Contracts Finder — distinct from tender, PIN, or modification notices.

Awarded supplier(s): legal name as registered; check for joint ventures, consortium leads, and trading names in awards section.

Contract value: initial value, optional estimated total including extensions, and currency — read footnotes for VAT treatment.

Award date and contract start/end or duration in months — extension options often appear in free text or structured period fields.

Buyer organisation: contracting authority name and identifier — link to other notices from the same buyer.

CPV codes and procurement procedure (open, framework call-off, direct award) — context for how the next competition may run.

Using tender notice fields to infer award outcomes — always confirm with the published award notice.

Recording headline value without checking whether extensions are included in the stated total.

Ignoring lot-level awards on multi-lot frameworks — incumbent may differ per lot at the same buyer.

Assuming award date equals contract start — mobilisation gaps are common in construction and FM.

Skipping modification notices after award — extensions and value changes affect renewal timing.

Not storing notice OCID or URL — impossible to audit intelligence back to source in bid reviews.

TenderLedger normalises award data from Find a Tender and Contracts Finder — supplier, buyer, value, date, and CPV in consistent views.

Contract award tracking links awards to open tenders and buyer profiles so field context is visible without re-opening each notice.

Renewal timing derives from structured award and duration fields rather than one-off spreadsheet interpretation.

Sector and buyer filters let teams query award history the way portals do not — incumbent maps at scale.

Source lineage to official notices keeps buyer intelligence explainable for internal governance and client work.

A professional services firm mis-sized a council opportunity because the team logged estimated framework value instead of the call-off award value — bid pricing was wrong until they re-read the CAN.

After adopting a standard field checklist, a bid consultancy cut award logging errors by half and aligned renewal forecasts with published end dates.

Create a one-page field checklist: notice type, buyer, supplier, award date, value basis, duration, extensions, CPV, procedure, notice ID.

Train BD and bid staff on the difference between CAN, contract modification, and contract details notices.

When logging awards in CRM, always paste the notice URL and OCID alongside human-readable fields.

For framework call-offs, record parent framework reference and lot number in the same record as the award.

Monthly audit: sample ten logged awards against live notices — fix systematic field errors.

Connect award reading to renewal playbook steps: award date plus term feeds your re-tender watchlist.