The Tender Was Won. Which Assumptions Must Survive the Handover?
Tender assumptions about scope, rates, exclusions, resources, subcontracting, programme and risk can disappear when estimating hands the job to delivery. A controlled handover turns those assumptions into an explicit project baseline.
The short answer
A tender-to-project handover fails when the delivery team receives the price but not the logic behind it.
The winning estimate usually contains hidden assumptions about access, productivity, supplier validity, subcontract coverage, temporary works, sequencing and risk. If those assumptions disappear after award, the project can start from a commercial baseline nobody truly understands.
The handover should therefore answer one question clearly: what did we believe had to be true for this job to work at the price we offered?
The tender total hides the story management actually needs
A tender compresses thousands of decisions into one commercial number.
The number may look precise, but the route to it is full of judgement. One labour allowance may depend on repetitive work and unrestricted access. One subcontract quote may exclude testing. One supplier may have priced on a quantity that no longer matches the awarded scope. One section of preliminaries may assume the site can mobilise once rather than several times.
When estimating hands the job to delivery, those conditions matter more than the arithmetic.
A common failure is to treat handover as document transfer. Drawings, quotations and spreadsheets are uploaded, a meeting is held, and the project team is expected to work out the rest.
The result is not usually immediate disaster. The project simply begins making decisions without understanding which ones alter the tender logic.
The key question is not “what was included?” but “what was assumed?”
Scope is important, but assumptions are often where margin risk lives.
An item can be included and still be priced on an assumption that later proves false.
For example, the contractor may have included labour but assumed normal daytime access. It may have included a subcontract package but assumed the specialist would carry temporary works. It may have included a material but priced it against a supplier quote that was only valid for thirty days.
These are not necessarily estimating errors. They are conditions that need to survive the handover.
A strong handover separates:
- confirmed facts;
- commercial exclusions;
- operating assumptions;
- unresolved risks;
- clarifications agreed during tender.
That distinction gives the project a much better chance of recognising when delivery has moved away from the winning basis.
The programme carries assumptions too
Tender programmes often look more solid than they are.
The completion date may depend on early access, timely design information, a specific procurement sequence or a productivity rate that was never fully tested.
When the project planner receives the tender programme, the temptation is to treat it as a starting schedule and refine it. But if the assumptions behind the dates are not carried forward, the refined programme can become more detailed while becoming less commercially connected.
The handover should therefore identify the conditions behind the critical durations and sequence.
If the awarded contract changes access, approvals or sectional dates, the delivery team should understand what that does to the tender basis before the programme becomes the live baseline.
The same logic applies to labour and plant. A change in sequence can change resource efficiency even when total quantities remain the same.
Supplier and subcontract quotations deserve more attention than their headline price
Tender teams often work with quotations that include conditions which disappear when values are transferred into an estimate.
A supplier may exclude freight. A subcontractor may price one mobilisation. A specialist may assume client-provided access. A quotation may expire before award.
If the project team does not see these conditions, procurement can later appear to “overspend” against a budget that was never executable on the same basis.
This is why a few critical quotations should be reviewed at handover, especially where they influence programme or margin significantly.
The goal is not to re-audit the whole tender. It is to identify the small number of commercial assumptions that the project needs to protect or revalidate quickly.
The first month is the first real test of the tender
Some assumptions cannot be confirmed before delivery starts.
That is normal.
What matters is whether the project knows which assumptions it is testing.
The first weeks can reveal whether access is as expected, whether key suppliers still stand behind their pricing, whether the proposed subcontract strategy is workable and whether early productivity is consistent with the tender.
If the evidence is different, the project should update its forecast rather than allow the tender assumption to remain silently embedded.
That is not a failure of control. It is what control looks like when new information becomes available.
The original tender remains the historical commercial baseline. The live forecast becomes the best current view of where the project is heading.
Handover should end with decisions, not a presentation
A good handover is not complete when estimating finishes talking.
It is complete when the project team knows what needs to happen next.
That usually means a concise set of decisions and actions: which assumptions must be confirmed, which procurement packages require immediate attention, which risks need owners, which budget areas need mapping and which programme conditions need management review.
The unresolved items should have names and dates attached to them.
This is where handover becomes valuable. It stops being a ritual between departments and becomes the first management process of the project.
The project should still be able to explain the winning price six months later
A strong handover leaves a traceable commercial story.
When the project later sees a subcontract overrun, procurement variance or productivity problem, management should be able to ask whether the cause came from the original estimate, a changed condition or execution.
That is difficult if the project budget was rebuilt with no relationship to the tender.
The delivery structure can absolutely differ from the estimating structure. It often should. But the bridge between the two should remain visible.
That bridge turns handover into organisational learning as well as project control. Future estimating teams can see which assumptions proved robust and which repeatedly failed after award.
The wider significance of this becomes clearer when the project is viewed as a chain of later decisions. Procurement will use the tender allowance to judge supplier prices. The project manager will use the programme assumptions to decide resource levels. Commercial teams will interpret scope boundaries when the first variation appears. If the assumptions behind those decisions were never transferred, each function begins inventing its own version of the tender.
That is why the handover is one of the first controls in the wider question of whether a newly won project is actually ready to start.
A good handover also creates useful tension. Delivery teams should be encouraged to challenge the estimate, not simply accept it. If the estimator assumed a productivity rate that site leaders believe is unrealistic, that difference should surface immediately. If procurement believes a key supplier quotation can no longer be achieved, that should be visible before the purchase decision. If the programme depends on access the contract does not clearly provide, the issue should be escalated while options still exist.
This is not about proving the tender wrong. It is about testing the commercial hypothesis against the people who now have to deliver it.
The strongest projects do this without turning handover into a forensic audit. They focus on the few assumptions with the largest consequence, document the decisions, and move on. The value comes from clarity, not volume.
Where Epicor Saturn fits in tender-to-project handover
Epicor provides the enterprise-grade ERP foundation for purchasing, finance, approvals and core business governance. Epicor Saturn adds the construction and engineering industry structure needed to carry tender assumptions, contract context, project budgets and delivery controls into one project-centric model.
That matters because handover is not primarily a document-storage problem. It is a continuity problem.
Epicor Saturn helps keep the commercial basis of the job connected to procurement, project resources, site activity and cost while Epicor provides the enterprise-grade transactional backbone beneath those processes. Explore Epicor Saturn for construction and engineering.
Frequently asked questions
Should every estimator note become part of the project record?
No. Preserve the assumptions and clarifications that can materially affect scope, cost, time or risk.
Can the project budget be structured differently from the tender estimate?
Yes. The delivery structure can differ, but the bridge back to the winning estimate should remain traceable.
Who should be involved in the handover?
Typically estimating, commercial, project management, procurement and relevant technical or site leaders.
What is the biggest warning sign of a weak handover?
The project team knows the tender value but cannot explain the assumptions behind major cost or programme allowances.