Comparing construction tenders beyond the headline price
Admin · 22 October 2026
Illustrative image. Photo by Jonathan Borba on Unsplash. Unsplash License.
A tender total is meaningful only when the evaluation team understands what it buys. Two submissions can respond to the same invitation while making different assumptions about access, temporary arrangements, design responsibility and completion. Comparing their totals without examining those differences risks recommending an offer on a basis the bidder has not actually accepted. A disciplined evaluation connects the price to the scope, evidence and conditions behind it.
For client teams and commercial managers, the task is to make differences visible through the procurement process that applies to the project. It is not to invent new selection criteria after bids arrive or casually rewrite a supplier’s offer. Establish the evaluation method beforehand, use the appropriate review expertise and maintain a record that explains how the recommendation follows from the submissions received.
Confirm the information each bidder used
Start with the tender issue record. Identify the documents, revisions and clarifications that bidders were expected to address. Check the returned submissions for acknowledgement of relevant amendments and for statements that indicate a different basis. A late clarification may have been received but not fully reflected in a price or programme. Record the question and resolve it through the authorised procurement route.
Preserve each original submission before beginning the working comparison. Evaluation spreadsheets, notes and subsequent clarifications should remain distinguishable from the offer received. This helps reviewers understand where a figure came from and prevents an internal adjustment from being mistaken for a bidder’s commitment. Keep a clear trail from the original return to the position presented in the recommendation.
Map the scope package by package
Compare inclusions, exclusions and qualifications against the required scope. Pay attention to interfaces, where an apparently complete package may assume another party provides enabling work or supporting information. Identify who is expected to design, supply, install, test and document significant elements. The appropriate level of detail depends on the project, but the comparison should expose gaps that could affect delivery.
Use a common structure for recording differences without assuming that every difference can be reduced to a simple monetary adjustment. Some departures may require technical review or may be unacceptable under the procurement requirements. Others may represent permitted alternatives. Establish their status through the relevant process before treating them as interchangeable with the specified solution.
Read qualifications with the price
Important conditions can appear in covering letters, schedules or attachments rather than in the pricing document. Review the submission as a whole. A bidder may have priced a defined working pattern, assumed uninterrupted access or excluded an activity described elsewhere in the tender information. Bring these conditions into the comparison so that the apparent price is not considered separately from its limitations.
Route material contractual or commercial departures to the appropriate advisers. An evaluation team should not assume that a qualification is harmless because it looks familiar or appears in standard wording. Equally, it should avoid assigning an unsupported cost to a departure merely to complete a spreadsheet. Record the issue, the advice obtained and the treatment adopted through the project’s authorised procedure.
Examine the delivery proposal
Review the programme and method information against the project’s actual constraints. Ask what the proposed completion date depends on, including client decisions, supplier inputs and access arrangements. A short duration may be credible, but the team needs to understand its basis. Compare the evidence offered rather than rewarding an attractive date that relies on unresolved assumptions.
Consider a hypothetical occupied refurbishment. One bidder proposes phased working while another assumes the building will be vacant for a defined period. The second price may be lower because it reflects a different operating condition. Before drawing a conclusion, the client must establish whether that condition is acceptable and how it is treated under the tender rules. The difference cannot be understood from the total alone.
Assess resources and specialist dependencies
Where the evaluation requires delivery capability evidence, examine how the proposed resources relate to the work. A list of experienced personnel may not explain their availability or responsibilities on this project. Look for the information requested in the tender and assess it consistently. Avoid filling gaps with assumptions based on the bidder’s general reputation.
Identify significant specialist dependencies in the offer. A proposal may rely on a particular supplier, design contribution or manufacturing arrangement. Record what is confirmed and what remains provisional. Clarification should establish the relevant position through the permitted process. This helps the team understand whether the offer’s delivery basis is developed enough for the decision being made.
Keep evaluation assumptions visible
Sometimes the team needs an internal assessment to understand the consequence of a difference. Label it clearly as an evaluation assumption and explain its basis. Do not present an estimated adjustment as a price the bidder has agreed. If further agreement is needed, identify that step and its status before the recommendation proceeds.
Review the combined effect of differences rather than treating every line independently. A scope omission may also affect programme, supervision and operational arrangements. Counting only the apparent direct cost can miss those connections, while adding overlapping allowances can exaggerate them. The relevant technical and commercial reviewers should coordinate their assessments and explain where uncertainty remains.
Apply the established criteria consistently
Use the evaluation criteria and process established for the procurement. Reviewers should understand the evidence required and the meaning of any scoring scale. Where several people assess submissions, agree how differences in interpretation will be discussed and recorded. The aim is a reasoned assessment supported by the tender evidence, with a transparent explanation of significant judgements.
The Construction Playbook sets out a public works procurement context, including the government’s expectations for relevant contracting authorities and suppliers. It does not remove the need to follow the specific rules and documents governing an individual competition. The comparison workflow described here is editorial management guidance; project-specific procurement and legal questions require the appropriate professional review.
Write a recommendation that explains the choice
The award recommendation should describe the offer being recommended, the reasons under the evaluation method and the material qualifications or unresolved matters. Summarise consequential differences between submissions without reducing the explanation to a ranking of totals. Decision makers need to understand both the evidence supporting the choice and any conditions that must be addressed before commitment.
Separate completed evaluation from future actions. If the recommendation depends on a clarification, approval or agreed scope adjustment, name the owner and required outcome. Avoid describing the offer as fully settled while relying on an unresolved condition. The decision record should state what has been authorised and what remains to be completed through the applicable process.
Hand the agreed basis to delivery
Once the award arrangements are complete, transfer the relevant scope, accepted clarifications and delivery assumptions to the project team. Identify the final contractual documents through the proper procedures. Site managers and package leads need to understand the commitments that shaped the appointment, not just receive a copy of the original tender invitation.
Review the tender process after mobilisation. Note where unclear documents produced repeated qualifications and where evaluation questions exposed a weakness in the initial scope. Use that evidence to improve future invitations. A thorough comparison earns its value when the chosen offer is understood, its boundaries are explicit and the delivery team can trace the work it is expected to provide back to a coherent agreement.
Keep the evaluators’ working notes with the recommendation under the project’s records arrangements. Record the source of significant figures and the resolution of conflicting interpretations. A later reviewer should be able to follow the reasoning without depending on the availability of the original evaluation team.
