Construction quote assumptions and exclusions: make the scope executable

A technically detailed quote can still create a poor project handover when assumptions and exclusions are scattered through notes. Site access, client-supplied information, provisional quantities and third-party work all affect price and programme. The practical test is whether the customer and future project manager can make the same scope decision from the accepted version without relying on the estimator's memory.

Write assumptions as testable conditions

Replace vague phrases such as “normal access” with conditions that can be checked: unloading distance, working hours, available power, substrate condition or information due from the client. State who verifies each condition and when. If an assumption fails, the team should know whether to pause, price a change or use an agreed alternative.

Keep assumptions close to the affected work package. A general disclaimer at the end of a long quote rarely guides the crew or explains a later cost difference.

Separate exclusions from client responsibilities

An exclusion says what your price does not include. A client responsibility says who must provide or complete something for your work to proceed. List both clearly and avoid hiding essential enabling work in boilerplate. Name third-party interfaces such as scaffolding, permits, utility isolation, structural preparation or final decoration where relevant.

Explain the operational consequence: missing access may move a date, while missing design information may block ordering. Do not pre-price an unknown consequence as if it were certain.

Control provisional sums and options

For provisional quantities or allowances, state the basis, unit rate, measurement rule and approval point. Keep optional work out of the accepted total until the customer selects it. When an option affects programme or another package, show that dependency before signature.

Version every commercial change. The accepted quote should identify which assumptions were resolved, which options were chosen and which items remain provisional, without rewriting the earlier proposal.

Hand the scope into project control

At acceptance, transfer the scope, open decisions, evidence and owners into the project. Link tasks, purchase needs and billing milestones back to the quoted basis. The project manager can then identify a genuine change before work starts instead of reconstructing it after the final invoice.

The Belgian renovation quote guide covers the broader document. Use Enfin for quotes and project follow-up to keep the accepted commercial basis connected to execution.

Review the quote from the site team's perspective. Before sending, ask someone who did not prepare the estimate to identify what the crew can start, what information they still need and which adjacent work belongs to others. If that reader cannot answer from the document, the customer is unlikely to infer the intended boundary either. Correct the scope language rather than adding another generic disclaimer. Preserve the review result with the quote version and carry unresolved choices into a decision list. This practical read-through also exposes commercial contradictions, such as an excluded access provision that the programme assumes will exist. A quote becomes executable when scope, responsibility, price basis and timing tell one coherent story.