What sustainability requirements need to go into subcontractor scopes?
A sustainability requirement becomes difficult to deliver when the trade package does not identify the product, evidence, interface and deadline. “Support Green Star” tells a trade the objective. It does not tell them what to submit or who must check it.
Direct answer
Translate each project sustainability commitment into trade-specific evidence, deliverables, interfaces and hold points inside the subcontract - then check incorporation, document hierarchy and design responsibility before you rely on them.
Start by reading the incorporated documents. A requirement may already exist in a specification even if the trade scope does not repeat it. The purpose of the map is to expose gaps and conflicts, not to assume that missing words erase an obligation.
Use this as a coordination aid for the scope drafter. Contractual responsibility and enforceability depend on the executed documents and applicable law.
Decision tool: commitment → trade deliverable map
Complete one row for each relevant commitment. Name one person to coordinate each interface, even where several trades contribute. Agree review turnaround and correction time before the affected procurement or installation date. Use the contract’s change process for packages already awarded.
Commitment (source + revision) | Responsible trade + interfaces | Evidence to submit | Deliverable | Reviewer | Timing / technical hold point | Trade owner |
|---|---|---|---|---|---|---|
Low volatile organic compound (VOC) finishes - where required | Painter, flooring, waterproofing, fire-stopping | Evidence of the specified VOC performance; safety data sheet where relevant; purchase records | Marked finishes / product schedule | Finishes / sustainability reviewer | Proposed gate: evidence reviewed before order and application | |
Low-formaldehyde engineered wood (where required) | Joiner, carpenter, door supply | Certificates for exact boards | Fabrication release pack | Design / sustainability reviewer | Proposed gate: product evidence cleared before fabrication | |
Responsible Products / finishes pathway (where used) | Supply-install trades + quantity surveyor | Certificates recognised by the project calculator pathway; cost evidence format | Monthly product evidence register | Sustainability lead | Eligibility before order; cost records as invoiced | |
Declared concrete / steel content claims | Concreter / structural | Approved mix or mill declaration + dockets | Pour / install records linked to approved ID | Design | Proposed gate: approved mix confirmed before pour | |
Timber chain of custody (where required) | Carpentry / furniture | Chain-of-custody invoices | Delivery log | Design / sustainability reviewer | Check scheme claim at delivery; escalate mismatches before use | |
Construction and demolition waste (where targeted) | All trades + waste contractor | Project waste records with quantities, destinations and accepted recovery evidence | Records to environmental management plan owner | Environmental management plan owner | Clear segregation duties, supervision and evidence ownership | |
Metering and monitoring | Electrical, mechanical, controls, hydraulics | Meter schedule; validation; proof readings reach the building management system | Commissioning extracts | Commissioning lead / independent agent, if appointed | Proposed gate: prove required data path before system acceptance | |
Commissioning attendance | Services trades + commissioning agent | Attendance at approved integrated witnesses; defect close-out | Signed witness sheets | Commissioning lead | Per approved commissioning plan | |
Site environmental management | Each trade | Induction and environmental plan duties | Induction records | Site management | Access after induction | |
Operation, maintenance and training | Each services trade | As-installed data in required template | Manual chapter + training | Services lead | Before system acceptance |
Agree technical hold points in the project documents. Identify who can release each one and what evidence they need. A technical hold point does not itself create a payment-withholding right or change the contractual definition of practical completion.
Drafting pattern for project-specific review: “Before ordering engineered wood for package [ID], submit evidence demonstrating compliance with [requirement, test method and revision]. Identify each covered product. Allow [review period] for review and [correction period] for resubmission. Obtain written release from [authorised role] before fabrication. Submit purchase records and installed-location records by [milestone].” Replace every bracket and reconcile the clause with the contract. If the reviewer has not responded, escalate through the agreed process; silence is not the proposed release mechanism.
NATSPEC’s guide maps sustainability topics to specification worksections. Use it to locate related clauses, then reconcile them with the project’s requirements. It is guidance, not a guarantee of Green Star certification.
Resolve the interfaces before award
- For each shared deliverable, identify who supplies the inputs, who combines them and who checks the result. For metering, this may involve electrical installation, controls configuration and the facilities team’s data access. “By others” needs a named other.
- Give each reviewer a defined output: accepted, rejected with reasons, or further information required. Record conditions and the next review date. The trade needs a decision they can act on.
- Check whether the requirement is priced in the package. If it is excluded or duplicated, resolve that before award. A technically complete requirement is still a coordination gap if every party assumes another party priced it.
- For agency projects, attach the applicable requirement reference and edition to each relevant row. NSW School Infrastructure explicitly links EFSG versions to project timing; do not substitute the newest handbook without checking applicability.
Failure mode (illustrative - not a real project)
Illustrative example: electrical and controls trades both price their own meter tasks. Neither prices the final test that traces a known reading through to the operator’s dashboard. Each completes its individual scope, but the builder still lacks proof of the combined result. Naming an interface coordinator and the required test before award makes that missing deliverable visible.
Assign the complete outcome as well as the individual tasks. Otherwise, everyone can finish their task while the interface remains unproven.
Concrete next action
At the next scope review, select three high-consequence commitments. Ask: can the trade identify the exact requirement, price the work, submit the evidence and obtain a decision before the hold point? Resolve each “no” before award. Keep the completed rows with the package and use them during delivery.
Turn each package requirement into a dated evidence gate using the procurement evidence matrix and name the person who can release it.
Where the deliverable crosses trades, use the installed, tested and integrated commissioning matrix to make the complete outcome visible.
Sources
- NATSPEC - Specifying for Green Star Buildings using NATSPEC, v1.2, pp. 4, 9–16: worksection and evidence prompts.
- School Infrastructure NSW - EFSG home: edition applicability.
- Australian Government - Prepare a contract, sections 8 and 13: subcontracting and documenting changes.
- The map, proposed gates and drafting pattern are Makao’s recommendations. They require adaptation to the project and do not settle legal entitlement.
- Project-specific documents control technical criteria and appointed responsibilities.
- The example is hypothetical. No measured cost saving or client outcome is claimed.
Questions or corrections: contact Makao.
