Compare home quotes on a like-for-like scope
Home proposals become comparable only when they use the same drawing revision, completion stage and assumptions. Transfer every package into a common matrix, flag absent or provisional items, and assign every interface to a party. Until that work is done, the lowest headline total does not establish the lowest whole-project cost or the best fit.
Editorial responsibility: KanadaHomes
Issue one consistent comparison brief
Give each provider the same dated drawing set, requirement schedule and available site information. State the intended completion stage, quality expectations and work retained by the owner. Two proposals based on different layouts or revisions are answers to different questions.
Check validity periods, adjustment mechanisms, payment milestones and stated preconditions. A common brief supports a fair technical and commercial review. Its limitation is that identically named lines may still contain different materials, quantities, design input or installation boundaries.
- Same drawing revision and issue date
- Same dimensions and area definitions
- Same available plot and ground information
- Defined finish level and selection assumptions
- Clear supply, installation and completion boundaries
Decision test: what counts as equivalent?
Equivalent does not mean similarly labelled. Function, quality, quantity, evidence, installation and interfaces should meet the same requirement. A valid alternative can remain, but record it as a deliberate option rather than hiding it inside a comparison line.
Normalise every proposal in one matrix
Create lines for design, compliance information, approval support, structure, envelope, windows, building services, internal finish, site setup, transport and handover. Against each provider mark included, excluded, optional, provisional or unclear, with a page or clause reference.
Do not invent a price for a gap. Request clarification or a separate priced option. Normalisation reveals when an apparently lower proposal transfers work to the owner or another contractor. It helps expose scope, but cannot by itself assess contract risk, workmanship or whether a provider suits the project.
- Material or system and required performance
- Quantity and measurement basis
- Design, supply, installation and checks
- Required preceding and follow-on work
- Exclusions, options and provisional items
- Responsibility at every trade boundary
Close clarifications before selection
Send consolidated questions in writing and update the matrix only from traceable responses. Alongside normalised scope, consider programme assumptions, change control, handover information and how clearly responsibilities are expressed. Keep unresolved matters in a decision log rather than treating silence as inclusion.
Contract forms and specific wording can have legal consequences. For a German project, obtain review in the German legal context where appropriate; elsewhere, check the law and practice of that location. A matrix supports procurement decisions but is not legal advice.
- Which five packages show the largest scope differences?
- Which assumptions may change after site investigations?
- Who delivers each excluded design or site task?
- Have verbal explanations been confirmed in writing?
- Which questions must be closed before appointment?
Hypothetical example: normalising a window line
Proposal A says “windows included”; Proposal B describes units, installation, perimeter interfaces and preparation for shading. The buyers ask A to confirm quantity, performance basis, installation scope and facade connection. Hypothetically, the response excludes the shading preparation. They then show that item separately in the matrix and compare the resulting responsibilities instead of relying on the headline totals.
Pitfalls to avoid
- Comparing totals based on different drawings or completion stages.
- Accepting “included” without testing quality, quantity and installation boundaries.
- Crediting verbal assurances that are not reflected in the written proposal.
Frequently asked questions
How many proposals should I request?
There is no universal number. Seek enough genuinely comparable responses to test the market while retaining time to clarify each one properly.
How should lump-sum lines be treated?
Ask for the scope, quantity basis, exclusions and adjustment rules. A lump sum may be useful, but an undefined package remains difficult to compare.
Can an alternative system stay in the comparison?
Yes. Test it against the functional requirement and show the departure explicitly as an alternative, not as an identical line.
Is the lowest normalised proposal automatically best?
No. Also assess clarity, programme logic, change process, responsibilities, documentation and suitability for your particular project.
Related guides
Sources
These sources explain general planning principles, mainly in the German context. They do not confirm project scope, permission, funding or technical suitability. Local requirements need separate professional assessment.
See how clear specifications, execution expectations and documented quality support a sound comparison.