How to Review an NZ Tender Package Before You Start Pricing

Tender review is a decision process, not just document reading

A tender package can look simple on the first screen: a notice, a deadline and a set of downloadable files. In practice, the key information may be spread across conditions of tendering, a form of tender, drawings, specifications, schedules, pricing workbooks and later addenda. A good review process makes that spread visible before estimating work begins.

For government opportunities, GETS is the official service used by agencies to publish contract opportunities. Suppliers use it to identify opportunities and submit responses. GETS calls the documents and process an RFx, which can include an RFT, RFP, RFQ, ROI or another form of market approach.^[1] The exact document set will differ from job to job, so the first rule is not to assume that the same file order or pricing structure will apply every time.

The most useful first question is not “what should we price?” It is “what does this package require us to understand, price, provide and submit?”

This guide provides a repeatable review sequence. It helps you find the facts in the package. It does not decide whether a tender is commercially right for your business.

Step 1: Create one complete working package

Start by collecting the tender notice and every attachment in one project folder. Include spreadsheets and Word documents, not just PDFs. Record the notice number, purchaser, title, issue date, closing date and closing time. Then create a simple file register with the document title, version or revision, date and file type.

Subscribe to the notice in GETS if you intend to access attachments, raise questions or submit a response. GETS states that a supplier must subscribe to obtain full access to attachments and questions for a notice.^[1] Subscription also matters because addenda can introduce new material after your first download.

Step 2: Lock down dates before reviewing detail

Record every date separately: deadline for questions, tender close, site visit, briefing, proposed start, milestones and completion date. Do not rely on memory or on a date appearing in a single document. Compare the notice, conditions and programme because different documents may deal with different dates.

GETS explains that closing dates and times are set by the purchasing agency and there is no standard closing time.^[1] It also states that questions and responses relating to a tender should be submitted in the way directed by the purchasing agency in the tender documents.^[1] If a requirement is unclear, use the stated clarification channel rather than assuming a practical answer.

A simple calendar is enough at this stage. The important point is to turn dates hidden in several files into a visible sequence before the estimating team commits time.

Step 3: Separate mandatory requirements from information

Read the conditions of tendering and the response schedules before diving into technical quantities. Mark every item that uses words such as must, shall, required, mandatory, include, submit, or provide. These may relate to insurance, health and safety, quality plans, personnel, programme, references, price schedules or declarations.

New Zealand Government Procurement explains that tender documents should provide the information suppliers need to prepare a response.^[2] That does not mean the supplier should treat every statement as equally important. A useful review distinguishes three categories:

This classification is one of the fastest ways to reduce missed submission requirements. It also makes it easier to see which facts must be found in the package before pricing begins.

Step 4: Read the commercial structure before building the estimate

Find the contract form, pricing mechanism and contract schedules. The New Zealand Government Procurement construction guidelines describe pricing mechanisms and standard construction contract types as parts of construction procurement planning.^[3] A tender may use lump sum, measure and value, target cost or another arrangement. The documents, not a generic label, determine the actual commercial position.

For a review, identify where the package states the following:

• The form of contract and the stated edition or version.
• Special conditions, amendments and document priority.
• The contract period, milestones and any working-day wording.
• Security, bonds, retention and insurance requirements.
• Cost fluctuation, provisional sums, variations and payment provisions.
• Any limits, caps, indemnities or project-specific allocations of risk.

Do not convert an unclear clause into a yes/no conclusion just because the summary needs a short label. If the document lists different positions by site, stage or work package, preserve that detail in the note and cite the source.

Step 5: Map the technical scope to the price schedule

Now compare the drawings, specifications and scope wording with the pricing workbook or Schedule of Prices. The purpose is not to measure every item at this first pass. It is to identify where the package expects a price and where the documents may need clarification.

For each major work area, record the drawing or specification reference, the matching price item and any apparent gap. This creates a traceable map between technical requirements and commercial response. It is especially useful for temporary works, traffic management, environmental controls, service relocations, earthworks, drainage, pavement, structures and reinstatement.

The construction procurement guidelines include official guidance on risk management, tendering, measurement contracts, lump sum contracts and target cost pricing.^[3] Use those materials as context, but always treat the actual RFx documents as the source of the project requirement.

Step 6: Review the evaluation approach and question deadlines

Look for the stated evaluation method, non-price information and price schedule. Do not assume that price is the only decision factor. For applicable government procurements, the procurement rules and tender documents may require the purchaser to consider matters beyond the lowest total price. The right response is to read the stated evaluation section and give each response component an owner.

If a conflict, omission or ambiguity could affect price, programme or compliance, prepare a short clarification question. Keep the question factual and refer to the document, clause, drawing or workbook tab. GETS says suppliers raise questions through the notice after subscribing, where that functionality is available.^[1]

Step 7: Finish with a fact sheet, not a guess

Before moving into pricing, produce a one-page internal tender fact sheet. It should show the tender title, purchaser, deadlines, contract form, pricing document, main deliverables, critical risks to investigate and questions to raise. Every factual point should point back to the file and page, sheet, tab or cell where it came from.

That is the useful boundary between document review and commercial judgement. Review turns a package into traceable facts. Management then decides whether and how to bid.

Where TenderBrief fits

TenderBrief is designed to help civil contractors, estimators and contract managers review a tender package more quickly. It reads supported PDF, Word and Excel tender documents as one package and returns a structured review with source citations. It does not replace the tender documents, professional judgement or specialist advice.

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