Most projects do not lose money during execution. They lose it in the hours between award and mobilisation, when the scope that was priced is manually rebuilt as the plan that will be delivered.
Scope assumptions stay buried in the proposal narrative. Resource estimates are re-entered from memory. The commercial baseline sits in a spreadsheet nobody opens again. The delivery team inherits a project brief rather than the commitment that was actually sold.
The hidden cost of the handover
Ask a project engineer what was quoted and you will usually get a confident answer. Ask them to prove it against the tender clause it came from, and the conversation changes. The link between the two exists only in the memory of whoever wrote the proposal.
That gap is not administrative. It is where scope growth stops being recoverable, because a variation can only be claimed against a baseline that was recorded. If the delivery plan was rebuilt by hand at kickoff, the baseline is the plan, not the contract, and the difference is absorbed as cost.
What is commonly lost after award
Five things disappear in the rebuild, and each one has a price. The assumptions that justified the estimate. The exclusions that limited liability. The resource grade the rate was based on. The risks that were priced but not written down. And the traceability back to the clause the client will quote at acceptance.
None of these are lost through carelessness. They are lost because the systems on either side of award do not share a record, and no one is paid to carry them across.
Turning the approved quotation into a baseline
The alternative is straightforward to describe and harder to build: the approved scope becomes the project structure directly. Deliverables stay linked to the line items that fund them. The schedule inherits the durations that were estimated. The resource profile matches the grades that were priced.
The measure of success is simple. At any point during delivery, anyone should be able to select a tracked item and see the priced line behind it, and the clause behind that.
Closing the loop back to the next tender
The final step is the one most organisations never reach. Completed projects hold the most reliable pricing data an engineering firm owns: what the work actually cost, by discipline, against what was estimated.
When that history feeds the next tender, estimating stops being an act of recall and becomes an act of evidence. Bids get sharper where you have been under-pricing, and more competitive where you have been padding.
An operator issues a 34-page tender for reliability-centred maintenance across three process trains. The proposal team extracts 14 scope items, prices 940 engineering hours against the current rate card, and notes two assumptions about data availability that materially affect effort.
The bid wins. Under a manual handover, a project engineer rebuilds the plan from the proposal PDF over two days. The two data-availability assumptions are not carried across, because they lived in a narrative section rather than the pricing table. Four months later the client supplies incomplete equipment history, effort overruns by 180 hours, and there is no recorded assumption to support a variation.
Under a connected handover, those assumptions are attached to the scope items they qualify. The overrun is identified against a recorded baseline in week three, and recovered as a variation rather than absorbed.
What changes in practice
Delivered scope provable against contracted scope
Every tracked item traces to its priced line and source clause.
Scope growth identified rather than absorbed
Changes are recorded against the priced baseline, not merged into a revised plan.
Project setup without manual rebuild
The approved scope becomes the project structure on award.
This is the transition Athervia was built around. A tender processed through QuoteFlow carries its scope, assumptions, resource profile and commercial basis into ProjectFlow on award, as one record, not two documents.
See how the handover works →