A NSW Gateway review is not a schedule exam. It is an advisory review that weighs value for money, governance, risk, interfaces, stakeholders and asset-owner needs, and the programme is one input among those. A sound programme will not, on its own, secure a favourable review. A weak one, though, is a fast route to findings that dent delivery confidence. This is the schedule evidence worth having ready at each Gate, and the checks worth running before the review.
What the IIAF is, and when it applies
Infrastructure NSW administers the Investor Assurance Framework, the IIAF, for NSW Government projects. It applies to capital projects of $20 million and above being developed, procured or delivered by general government agencies and state-owned corporations, registered through the NSW Assurance Portal. The state's pipeline sits at $116.7 billion over four years in the 2026-27 NSW Budget. The project's tier shapes its assurance pathway and reporting; its lifecycle stage, the applicable workbook and the terms of reference shape the individual review. So there is no single schedule test applied at every Gate. Preparing for it well is project controls discipline aimed at the funder's questions.
What each Gate is deciding, and the schedule evidence for it
Gate 0, strategic assessment. The decision is whether the service need is defined and evidenced. Schedule evidence stays modest here: an indicative timeframe that shows the need is understood, not a comparison of delivery durations.
Gate 1, options. The decision is whether the options have been properly examined. Schedule evidence worth preparing: indicative durations for the shortlisted options and their major sequencing constraints, enough to show each has been tested in time, not only in cost.
Gate 2, the business case. This is the pivotal Gate: it tests the agency's readiness to submit the Business Case for the investment decision and move to procurement. For Gate 2, prepare a programme that makes the business case's delivery dates credible: show the logic and critical path, explain the material duration and interface assumptions, and show how schedule risks affect the key milestones, drawing on a schedule risk analysis. Where relevant to the project, reconcile the resource assumptions with the cost plan and the milestone timing with the proposed funding profile. These are recommended ways to support the case, not a substitute for the current Gate 2 workbook's document requirements.
Gate 3, procurement readiness. Decision: is the project ready to go to market. What should reconcile: procurement and tender dates against the delivery strategy and the programme's front end.
Gate 4, tender evaluation. Decision: does the preferred bid hold up. What should reconcile: the tenderer's programme against the business-case baseline, with the differences understood.
Gate 5, operational readiness. Decision: is the project ready to commission and hand over. What should reconcile: commissioning dates against operator and asset-owner readiness.
Gate 6, benefits realisation. Decision: are the benefits being tracked and managed as intended. What should reconcile: actual dates against the benefits management plan and the business-case assumptions.
Treat these as practical preparation guidance unless the applicable workbook explicitly requires them.
A concrete Gate 2 example
Consider a utility-relocation completion date recorded in the risk register but absent from the programme's logic. Say it carries a February date. If that date is not a linked predecessor to the works that depend on it, the programme cannot show what happens when it moves. Prepare it the other way round: the relocation activity in the logic, its finish linked to the dependent works, the responsible party named, the date assumption stated, and the consequence for the completion milestone if it slips. That single link demonstrates more scheduling judgement than any general talk of interfaces.
Checks worth running before the review
A Gateway review is evidence-and-interview based, not a detailed quality check of your programme file, so the schedule weaknesses that undermine confidence are yours to find first. A pre-review schedule audit can use the standard checks to expose them: missing logic and open ends, hard constraints forcing dates the logic should set, float distribution and any negative float, and baseline variance under proper change control. A controlled baseline does double duty: it also preserves a reliable record if delays later need forensic delay analysis. It is worth building the programme in Primavera P6 to that standard from the outset. Whether digital engineering also applies is a separate question, set by the project's contract and agency, not by a blanket NSW rule. Some agencies, Transport for NSW among them, run their own digital engineering standard based on BIM. Where that applies to your project, link the programme's milestones and interface dates to the dates its model and information deliverables are due. Where it does not, do not assume the obligation.
What the review produces, and what it does not
The review is advisory. It gives an overall confidence assessment and recommendations of differing urgency, and even the most urgent recommendation is a call to act on a risk, not an instruction to stop the project. The review informs the investment decision; it is not itself the funding or approval. So the goal is not to "pass" or to dodge a rating. It is to go in with credible evidence and to have addressed the material risks before the reviewer raises them. That is the discipline behind the construction scheduling we run for our infrastructure clients.
Frequently asked questions
What is the IIAF?
Infrastructure NSW's Investor Assurance Framework, which independently reviews NSW Government capital projects at set Gateways to inform the government's investment decisions.
Which projects fall under the NSW IIAF?
Capital projects of $20 million and above, developed, procured or delivered by general government agencies and state-owned corporations, registered through the NSW Assurance Portal. The project's risk tier then sets the assurance pathway and how often it is reviewed.
What schedule evidence should a Gate 2 business case carry?
The current Gate 2 workbook sets the mandatory documents. As recommended supporting evidence, a programme that makes the delivery dates credible: clear logic and critical path, stated duration and interface assumptions, and the effect of schedule risks on the key milestones.
Does a Gateway review approve or fund a project?
No. The review is advisory. It gives a confidence assessment and recommendations that inform the investment decision, but the funding decision is made separately.
