NZS 3910 Tender Document Checklist: What to Locate Before You Price

Start by confirming the version actually named in the tender

NZS 3910 is a widely used New Zealand standard form for construction contracts. But a tender package may refer to different editions, amendments, special conditions or project-specific schedules. That makes the version named in the actual documents the first item to record.

Standards New Zealand lists NZS 3910:2023 as a published standard, dated 28 November 2023, and lists NZS 3910:2013 as a previous version.[1] Tender documents using the 2023 edition may refer to a Contract Administrator and an Independent Certifier rather than the Engineer to the Contract terminology familiar from NZS 3910:2013. Engineering New Zealand confirms the revised terminology, while a New Zealand construction-law review describes the separation of the former Engineer functions between these two roles.[2] [3] A tender review should still rely on the stated standard, schedules and amendments in the live package, because project appointment details determine who holds each role and the two roles may be held by the same person.[3]

Treat an NZS 3910 reference as the beginning of a document check, not the end of one.

This checklist helps locate the contract facts that a team should understand before pricing. It does not reproduce the standard or give legal advice about how any clause applies.

1. Identify the contractual document set

Locate every file that forms part of the proposed contract. This may include conditions of tendering, the form of tender, general conditions, schedules, special conditions, drawings, specifications, the Schedule of Prices and addenda.

A useful tender register should identify the stated edition or version and each project-specific change. The construction procurement guidelines note that standard construction contract types, pricing mechanisms and risk allocation should be considered in construction procurement planning.[4] In a bid review, the practical question is simpler: which documents form the contract package for this particular job?

Checklist itemWhat to recordWhy it should be visible early
Contract formThe title and stated edition/versionDifferent editions and documents can change the commercial framework.
Special conditionsThe document name and section referencesThese often modify the project position.
Document order or priorityWhere the tender explains which document prevailsConflicts can arise between drawings, specifications and schedules.
AddendaNumber, date and affected documentsThey may update the base package.
Contract schedulesEach schedule and its purposeKey project data may sit outside the general conditions.

2. Build a project-data checklist

Project-specific data is often scattered through schedules and special conditions. Do not leave this information in the documents until the end of the tender period. Pull it into a fact sheet with citations.

Fact to locateExamples of source locationsReview question
Contract periodContract data, programme or special conditionsWhat are the stated start, completion and milestone dates?
Working timeContract data, programme or conditionsAre working days or access constraints stated?
Liquidated damagesContract schedule or special conditionIs an amount, rate or formula stated?
Retentions and securityTender schedules, insurance/security sectionsWhat form and amount are requested?
InsuranceConditions, schedules or tender returnablesWhich covers, limits and evidence are called for?
Price basisSchedule of Prices and conditionsIs the package lump sum, measure and value, target cost or another model?
Variations and provisional itemsPrice workbook and contract conditionsHow are unidentified or provisional components described?

If the package contains a checkbox, table or multiple site-specific positions, preserve the original detail. A single green or orange label is less useful than the cited wording when the actual answer is mixed.

3. Check the people and decision roles named in the package

For NZS 3910:2023 packages, do not assume that terminology from an earlier tender will appear in the same way. Engineering New Zealand says that the revised version refers to the former Engineer to the Contract as an Independent Certifier, and a New Zealand construction-law review explains that the functions previously held by the Engineer are separated between a Contract Administrator and an Independent Certifier.[2] [3] The same person may hold both roles, so the tender documents should identify the actual people, roles and authorities that apply on the project.[3]

Locate the names or titles used for the principal, contractor, contract administrator, independent certifier, designer, engineer, superintendent or other project roles. Record what the tender actually calls them. This helps avoid drafting a response around the wrong contractual language.

4. Look for commercial risk shifts

Special conditions are not automatically bad; they are the place where a project may define its particular allocation of risk. The review task is to identify them clearly enough that the business can decide how to price, qualify, clarify or escalate them.

Focus on changes relating to site conditions, access, utilities, environmental responsibilities, programme, delay, price fluctuation, variations, indemnities, liability limits and dispute processes. Where a clause seems unclear, record the text and source, then obtain appropriate contract or legal advice before deciding its consequence.

The government construction guidelines include a risk-management focus area and a risk allocation table template for construction procurement.[4] Those tools are useful context for identifying risks, but they do not replace reading the tender's own allocation of responsibility.

5. Confirm response requirements before submission work begins

An NZS 3910-based package still has a tender process around it. Confirm the returnable documents, signature requirements, pricing schedules, programme information, proposed personnel, insurance evidence and any health and safety or quality materials the purchaser requests.

GETS describes the tender process as document and response management; suppliers must follow the purchasing agency's directions for questions and submissions.[5] A supplier can access attachments and tender-response functionality after subscribing to an open notice.[5] The final submission checklist should therefore use the tender instructions, not a generic internet list.

A final pre-pricing checklist

Before significant estimating work starts, the internal tender lead should be able to answer these questions with a citation:

  1. Which NZS 3910 edition or contract form does the package name?
  2. Which documents and addenda make up the proposed contract?
  3. Where are contract period, milestones and working constraints stated?
  4. Which schedules contain price, security, retention and insurance information?
  5. What special conditions modify the base position?
  6. What document order or priority wording appears in the package?
  7. What is required in the tender return, and by when?
  8. Which points need formal clarification before pricing is finalised?

Where TenderBrief fits

TenderBrief helps turn a multi-file tender package into a source-linked review of the facts your team needs to find. It can identify relevant fields in supported PDF, Word and Excel documents, while linking each extracted result to the source. It does not interpret the legal effect of NZS 3910 clauses or replace contract advice.

Create a free TenderBrief account to review your next package with cited source references.

TenderBrief provides document-review assistance, not legal, engineering, procurement or pricing advice. Always follow the tender documents and obtain specialist advice where needed.