An evidence register for construction bids

Make claims traceable to approved material that is current and relevant to the buyer's question.

Record the relevant trade, project scope and delivery role rather than relying on the headline project value.

The practical outcome is a usable claim-to-source register connected to the buyer's stated needs. In this setting, the focus is a deliverable programme with realistic site, supply-chain and commercial dependencies.

Scope: General bidding practice; follow the specific tender and applicable local requirements

Start with proposed claims and drawings, specifications and scope boundaries. Check the remaining inputs before treating the plan as confirmed.

Keep buyer-supplied facts separate from your own assumptions. For construction work, supply-chain quotations and cost assumptions can change the approach and the time needed.

• proposed claims
• source documents and dates
• client approval permissions
• drawings, specifications and scope boundaries
• site access, surveys and programme constraints
• supply-chain quotations and cost assumptions

Scope: General bidding practice; follow the specific tender and applicable local requirements

Use a short, controlled sequence that produces claim-to-source register and resolves the important delivery dependencies.

Record the relevant trade, project scope and delivery role rather than relying on the headline project value.

• Create a record for each material claim
• link the record to its source and limitations
• approve the wording and permitted use

Scope: General bidding practice; follow the specific tender and applicable local requirements

Keep claim-to-source register, evidence approval notes and expiry or review dates so a reviewer can trace the decision and its supporting facts.

Useful sector evidence includes relevant project records and approved references. Check that its service scope, dates and permissions fit this opportunity; an impressive but unrelated record adds little.

• relevant project records and approved references
• resource, sequencing and supply-chain evidence
• task-specific assurance and inspection arrangements

Scope: General bidding practice; follow the specific tender and applicable local requirements

Use the evidence owner with subject expert approval to coordinate the decision and its approval. Relevant sector contributors include the project manager, estimator and the relevant design or safety specialists.

Agree who prepares claim-to-source register, who checks the facts and who can approve the resulting commitment. Record a deputy or escalation route where a missing decision could stop progress.

For this service, the operational owners also need to confirm site access, surveys and programme constraints.

Scope: General bidding practice; follow the specific tender and applicable local requirements

Reusing an impressive number without knowing its population, period or permission status.

An unclear design or site assumption can change both the programme and cost, even when the headline work description stays the same.

A practical control is to ask: Can the source be opened? Check the answer using claim-to-source register. Escalate an unresolved material gap before release rather than concealing it with confident language.

Scope: General bidding practice; follow the specific tender and applicable local requirements

Review the actual working record and its supporting evidence. A useful check is whether claim-to-source register can be reconciled with relevant project records and approved references.

The reviewer needs enough independence and relevant knowledge to challenge the assumptions. Record material findings, their owner and the evidence that closes them.

• Can the source be opened?
• is the comparison relevant?
• does the claim preserve its original scope?

Scope: General bidding practice; follow the specific tender and applicable local requirements

Consider a refurbishment with restricted access and work that must be sequenced around an occupied site. The question is how the decision changes the proposed work, rather than whether a generic policy exists.

A service result covering one location for six months must retain that scope; it cannot silently become a group-wide annual result.

Record the relevant trade, project scope and delivery role rather than relying on the headline project value.

Scope: General bidding practice; follow the specific tender and applicable local requirements

This is a planning example. Apply the actual buyer requirements, costs and delivery conditions.

Track material claims with an accessible approved source.

Read that measure alongside programme dependencies, inspection outcomes and the status of approved scope changes. Define the period, unit, denominator and exclusions before comparing results.

Keep the baseline and explain material changes in workload or scope. A better-looking number without a comparable definition does not establish an improvement.

Scope: General bidding practice; follow the specific tender and applicable local requirements

Start by assigning one person to create a record for each material claim. Keep preparation, factual checking and approval responsibilities clear even if people cover several roles.

Use claim-to-source register as the shared working record. Ask the project manager, estimator and the relevant design or safety specialists for defined inputs rather than circulating the whole bid without a specific question.

Protect time for the key review: Can the source be opened? The aim is a manageable decision, not a larger collection of documents.

Scope: General bidding practice; follow the specific tender and applicable local requirements

When you cannot confirm proposed claims, record the gap, who can resolve it and how it affects claim-to-source register. Avoid converting an unconfirmed input into a contractual promise.

For this setting, also check supply-chain quotations and cost assumptions. Use the buyer's permitted clarification route when the uncertainty comes from the invitation.

The evidence owner with subject expert approval should decide whether a supported assumption, a scope change or stopping work is appropriate. Preserve the reason for that decision.

Scope: General bidding practice; follow the specific tender and applicable local requirements

Near the deadline, record the relevant trade, project scope and delivery role rather than relying on the headline project value. The release check for this work is: Can the source be opened?

Triage with the evidence owner with subject expert approval. Confirm proposed claims and resolve material issues in claim-to-source register before spending the remaining time on presentation.

Keep this specific failure in view: Reusing an impressive number without knowing its population, period or permission status. Record anything still unresolved and obtain the required release decision; a deadline does not remove the uncertainty.

Scope: General bidding practice; follow the specific tender and applicable local requirements

Transfer the approved claim-to-source register with its assumptions, unresolved issues and decision owner. For this sector, the handover must account for scope exclusions, design responsibilities, site assumptions, sequencing and supply-chain commitments.

Link the handover to expiry or review dates so the receiving team can distinguish an approved commitment from a working suggestion.

Record the relevant trade, project scope and delivery role rather than relying on the headline project value.

Scope: General bidding practice; follow the specific tender and applicable local requirements

Compare the original claim-to-source register with what happened in delivery and with any relevant buyer feedback. Use the difference to identify a specific change to the next working method.

A useful review measure is: Material claims with an accessible approved source. Recheck it alongside programme dependencies, inspection outcomes and the status of approved scope changes before drawing conclusions.

Assign an owner to the improvement, update the reusable evidence approval notes where appropriate and test whether the change was used in the next opportunity. Keep client-specific facts and permissions out of reusable generic content.

Scope: General bidding practice; follow the specific tender and applicable local requirements