BuildPath NZ logo

Procurement

Quote exclusions discovered

This can change development yield, consent pathway, purchase price, funding, construction cost, settlement timing, or legal risk. Treat it as a decision point, not background noise.

Tendering / contractor appointmentHighquote exclusionstender comparisonscope gapvariationLast reviewed 11 August 2026

What it looks like

  • A low quote excludes design, access, plant, temporary works, testing, disposal, delivery, making good, approvals, certificates, or close-out evidence.
  • The excluded work appears only after appointment or construction starts.

Likely causes

  • Scope was not issued consistently
  • Clarifications were not closed
  • Quotes were compared by total only
  • Drawings or specifications were incomplete
  • Provisional sums and assumptions were not normalised

Immediate action

  1. 1Pause the affected decision or commitment until the issue is understood.
  2. 2Record the issue in the risk register with date, source, owner, and next action.
  3. 3Send the relevant documents to Quantity surveyor, Project manager, Contractor or consultant and ask for written advice.
  4. 4Update feasibility, programme, budget, and decision register if cost, time, yield, consent, title, finance, or sales assumptions may change.

Step-by-step solution

  1. 1Define the problem in one sentence and identify which project decision it affects.
  2. 2Check the controlling documents: RFQ, Quotes, Clarifications, Exclusions and assumptions, and related project records.
  3. 3Ask the responsible professional to confirm whether the issue is real, minor, manageable, or project-changing.
  4. 4List the available options: redesign, renegotiate, seek consent, add cost allowance, change programme, change sales strategy, or abandon.
  5. 5Price and programme each option using the current feasibility model.
  6. 6Make a written decision with source references and approval from the developer or project owner.
  7. 7Notify affected parties such as lender, lawyer, consultants, builder, agent, buyer, or council when required.

What not to do

  • Do not rely on a seller, agent, or builder comment when a planner, lawyer, accountant, engineer, surveyor, valuer, lender, or council needs to confirm it.
  • Do not hide the issue from the feasibility just because the project looked profitable yesterday.
  • Do not waive due diligence, lodge consent, sign a contract, approve a variation, or promise settlement while the issue is unresolved.
  • Do not give legal, tax, finance, planning, engineering, or council advice to others unless a qualified professional has confirmed it.

Verification

Source / where to check

Use current official information and the controlled documents for the actual project.

Relevant professional advice

Planner, surveyor, architect, engineer, quantity surveyor, lawyer, accountant, lender, valuer, real estate agent, and other project specialists must confirm site-specific decisions.

Project-specific consented documents and professional advice override generic guidance.

Cost impact

High when several omitted packages must be added after the preferred price has been reported or funding approved.

Programme impact

Medium to high where excluded design, approvals, temporary works, or long-lead supply must be procured separately.

Risk level

High

Compliance and contract impact

Check whether the issue changes the resource consent pathway or conditions, building consent documents, consultant scope, sale and purchase conditions, finance terms, construction contract scope, notice requirements, variation process, or settlement obligations.

Example email / decision wording

Subject: Quote exclusions discovered — advice and decision required. We identified this issue during tendering / contractor appointment. The current evidence is listed in the attached record. Please confirm the controlling requirement, available options, cost/programme implications, further information needed, and whether any consent, contract, funding, or settlement action must pause. No assumption has been approved pending written advice.

Back to development problem solver