The pack: five documents, one governance structure
The tender pack was supplied as five documents: an Alliance Conditions document setting out governance and liability, a Technical Requirements document covering the engineering scope, a Tender Conditions document with the submission timetable and mandatory gates, a Commercial Framework document defining the pricing model, and a schedule of alliance participant financial capacity statements that — critically — was referenced throughout the pack but never actually supplied.
That last point matters more than it sounds. A tender pack is not the documents you were sent; it's the documents the tender says you need, cross-checked against what actually arrived. Missing a referenced-but-unsupplied document is one of the most common ways a compliant bidder becomes non-compliant without realising it until the debrief.
What the tender actually required
Once read, the pack broke down into nine distinct requirements and two mandatory gates — a materially different shape from "read the RFP and start writing," because requirements and gates carry different consequences if missed.
| Requirement | Category | Status | Source |
|---|---|---|---|
| Demonstrate an alliance governance structure with a single accountable lead organisation and named delivery partners | Technical | Mandatory | Alliance Conditions.pdf · Governance · p. 4 |
| Hold and maintain a current ISO 45001 (or equivalent) H&S management certification for every alliance member undertaking site works | Health & Safety | Mandatory | Tender Conditions.pdf · Health & Safety · p. 9 |
| Hold current resource consents, or demonstrate a consenting pathway, for all discharge and earthworks activities | Environmental | Mandatory | Tender Conditions.pdf · Environmental · p. 14 |
| Confirm an executed alliance agreement (or heads of agreement capable of execution) prior to contract award | Governance | Mandatory gate | Alliance Conditions.pdf · Governance · p. 5 |
| Acknowledge every issued addendum on behalf of all named alliance participants | Submission | Mandatory gate | Tender Conditions.pdf · Returnables · p. 3 |
Three of the nine were flagged mandatory in the plain requirements sense; two more were structured as mandatory gates — conditions that don't just score badly if missed, they can take the whole submission out of contention. Getting that distinction right, early, changes what a bid manager does in week one versus week six.
Critical dates: three, all mandatory
Questions closed 18 September 2026. A mandatory alliance workshop — attendance required — was set for 25 September 2026. Tender closing was 9 October 2026. All three carried a "mandatory" flag: miss the workshop and there is no fallback path to compliance, regardless of how strong the written submission is.
Three risks that would not have been obvious from a skim read
This is where a document-by-document read earns its keep. Skimming an alliance pack for "the requirements" tends to surface the technical scope and miss the risk sitting in how the documents interact with each other.
- Undefined liability for delivery partner defects (High). The Commercial Framework document did not clearly state the lead organisation's liability exposure if a delivery partner's work was defective. For an alliance-wide commercial structure, that is a real exposure to resolve before submission, not after award.
- Thin ground condition data (Medium). The geotechnical scope in the Technical Requirements document was supported by a single borehole log. Pricing and methodology risk follows directly from that if actual ground conditions differ.
- Misaligned commissioning sequence (Medium). The mechanical/electrical commissioning sequence in the Technical Requirements document wasn't aligned with the civil works programme elsewhere in the same document — a programme risk between two delivery partners that a single-pass read easily misses because the two references sit dozens of pages apart.
The one evidence gap that could have been submission-critical
The alliance participant financial capacity statements — referenced as a required attachment in the Tender Conditions document — were not among the five documents supplied. Left unresolved, that's not a minor omission: financial capacity evidence is exactly the kind of mandatory-adjacent document an evaluator checks first.
From findings to a response plan
Turned into a response plan, this pack becomes real assigned work rather than a shared folder of PDFs: a governance narrative and commissioning-method write-up for the technical lead, health & safety compliance evidence for the HSEQ manager, liability and contract-term resolution for the commercial lead, and the addenda/submission checklist for the bid manager — each with its own status, owner and evidence trail back to the exact page it came from.