Briefing season begins: Brisbane confirms the Estate Works forecast is not a bid pipeline

By Darian Macey, August 7 2026

Defence opened its 2026 Estate Works Program roadshow in Brisbane yesterday. Attendees received useful guidance on procurement, tender evaluation and project delivery—but little of the project-level status information needed to make bid decisions.

That distinction matters. Defence’s published forecast remains a starting point. It does not reliably show which opportunities are still proceeding, which have moved, which have been withdrawn or which are no longer accessible to the wider market.

A briefing explains how Defence buys. A bid pipeline must also show what remains live, when it is moving and who can compete.

What Brisbane actually covered

The Brisbane session was less a pipeline briefing than an introduction to the transformed Estate Works Program delivery model.

The Estate Works Program delivers facilities and infrastructure work intended to restore or sustain existing Defence capability, with safety and compliance at its centre. It generally does not deliver the facilities required for entirely new capabilities, which sit within the capital facilities program.

Defence explained the roles of the service providers now operating across the estate:

These organisations occupy different points in the opportunity lifecycle. Property and Asset Services providers help identify and assess requirements. JLL supports national programming. Project Delivery Services providers develop and deliver individual projects.

For contractors, consultants and suppliers, these are not interchangeable relationships. Each provider sees a different part of the pipeline and influences it at a different stage.

The project-status gap remains

The briefing included high-level state pipeline charts, but it did not provide a project-by-project update or test the status of individual forecast opportunities.

Defence reiterated that:

• the February–December 2026 tender forecast is indicative;
• projects may be changed, deferred, withdrawn or cancelled;
• the forecast will be updated periodically;
• AusTender becomes the authoritative source once an opportunity is released;
• there is no dedicated EWP works panel; and
• Defence also uses limited tenders that are not publicly accessible.

Questions were collected through an online form rather than answered during the session. Defence intends to consolidate responses after completing the national briefing series.

This leaves industry with the same underlying problem: a project can remain visible in the forecast after its timing, scope or route to market has changed.

The problem is most acute when Defence moves a forecast project into limited tender. Businesses that are not invited cannot access the tender documents and may not be told that the opportunity is no longer available to them.

This is particularly relevant to Indigenous procurement. The Indigenous Procurement Policy requires Indigenous businesses to be considered first for work delivered in remote Australia and for other eligible Australian procurements valued between $80,000 and $200,000. Indigenous participation requirements also apply to certain contracts valued at $7.5 million or more. NIAA explains the current requirements here.

The policy is not the problem. The transparency gap is. If a forecast project has been set aside or released through limited tender, the wider market should be told that its addressability has changed.

Even Defence’s published descriptions of the program are inconsistent. Its main Estate Works Program page currently describes projects as ranging from $100,000 to $20 million, with most between $1 million and $5 million. The separate tender forecast page states a range of $10,000 to $15 million. The Brisbane presentation appeared to use a wider range again.

These differences should not be treated as harmless editorial noise. Project value affects market relevance, likely procurement method, contract form, Indigenous procurement requirements and the tender effort a business should reserve.

New contracts for lower-value works

Defence used much of the session to explain its Micro Works and Minor Works contracts.

The Micro Works Contract is intended for low-value, low-risk, relatively simple and non-time-critical projects. The Minor Works Contract supports somewhat larger or more involved work but remains simpler than the Medium Works Contract.

The Brisbane presentation indicated guide values of approximately:

• below $2 million for Micro Works; and
• below $4 million for Minor Works.

These are guides, not automatic thresholds. Defence may select a more substantial contract where security, staging, design, access or operational risks warrant it.

The wider use of simplified contracts may reduce the burden on smaller projects. It may also support greater use of limited tendering. Contractors should therefore monitor the procurement route as closely as the anticipated release date.

The current templates are available through Defence’s Estate Works Program contract template page.

Defence’s tendering advice was blunt—and useful

The strongest practical content concerned tender compliance and evaluation.

Defence’s central message was that a technically capable contractor can still lose before its proposal is properly considered. Mandatory requirements are checked first. A materially non-compliant submission may not progress to technical evaluation.

Defence warned tenderers to:

• observe page limits;
• remove references left over from previous bids;
• use relevant and recent project examples;
• connect nominated personnel to those examples;
• quantify each person’s availability in hours or percentage FTE;
• explain responsibilities, site attendance and support for remote locations;
• address Defence management processes, not only construction methodology;
• submit RFIs at least seven days before tender close; and
• provide a credible critical path covering approvals, design reviews, procurement, long-lead items, construction, commissioning and contingency.

The evaluation process also deserves attention. Defence described technical submissions as being assessed without the evaluation board seeing the tendered price. Prices are introduced after technical ratings have been agreed, with the final decision based on overall value for money.

That weakens the assumption that the lowest compliant price will win. A cheap submission with generic methodology, thin resourcing or an implausible program can still be poor value.

Do not attend the remaining sessions expecting a project read-out

The Adelaide and Perth sessions are likely to repeat the Brisbane presentation. That does not make them pointless, but it changes the reason to attend.

The value lies in:

• questioning assumptions about particular projects;
• understanding how local delivery providers operate;
• identifying teaming and subcontracting relationships;
• testing base-access and staging constraints;
• meeting the people administering the program; and
• recording matters that Defence must answer after the national series.

The remaining state sessions are:

• Adelaide: Monday 10 August, Pullman Adelaide
• Perth: Tuesday 11 August, Four Points by Sheraton
• Darwin: Tuesday 18 August, Adina Vibe Darwin Waterfront
• Sydney: Wednesday 19 August, venue to be confirmed
• Melbourne: Monday 7 September, venue to be confirmed
• Townsville: Tuesday 22 September, venue to be confirmed

The Canberra briefing on 25 August is different. It covers planned procurement across the broader Defence capital facilities and infrastructure program, with EWP included as one agenda item. It also permits virtual attendance. In-person and virtual registrations close at noon AEST on 12 August.

Dates, venues and registration requirements should be checked on the official Defence briefing page before making travel arrangements.

Industry can also submit questions directly through Defence’s national briefing question form.

Turn the briefing into a monitored pipeline

A presentation does not become market intelligence merely because someone attended it.

Before each session, businesses should prepare a ranked list of projects by state, base, work type, value and expected approach-to-market quarter. Each project should identify the assumptions that remain untested:

• Is the forecast quarter still current?
• Has the scope been split, combined or reduced?
• Will the opportunity be open or limited?
• Has an Indigenous set-aside decision been made?
• Has the value band or contract form changed?
• Which PDS provider is managing the project?
• What access, security, shutdown or staging constraint will shape the tender?

Within 24 hours of the briefing, each answer should be reconciled against the existing project record. Changes in scope, timing, procurement route and status should be dated, sourced and assigned a confidence level.

This is where Helyx fits. It brings together the EWP forecast, AusTender activity, restricted-access signals, tender closing dates, contract awards and other market evidence. Watchlists and notifications allow users to monitor selected projects, locations and work types rather than repeatedly searching the entire program.

Helyx cannot reveal a decision Defence has not published. No platform can. Its value is in exposing uncertainty, identifying evidence that a forecast project has changed and preventing outdated assumptions from remaining buried in spreadsheets or personal notes.

Live Helyx demonstrations in Adelaide and Perth

Immediately after the Adelaide and Perth Defence briefings, I will give a live demonstration of Helyx in a separate room booked within the same venue:

• Adelaide: Monday 10 August, 11:30 am–12:30 pm, Hindmarsh 3, Pullman Adelaide
• Perth: Tuesday 11 August, 11:00 am–12:00 pm, Wanju meeting space, mezzanine level, Four Points by Sheraton

The demonstrations will show how to build an EWP pipeline, follow individual projects and receive alerts as the available evidence changes.

What this means for industry

Contractors should attend with a ranked project list, not a broad request for “more detail”. Designers and specialist suppliers should identify likely delivery partners before tender release. Business-development teams should reserve estimating effort only where the evidence supports the timing, scope and route to market.

Brisbane did not resolve the EWP pipeline problem. It demonstrated why the problem exists.

The advantage will not come from hearing the same presentation as everyone else. It will come from identifying what Defence did not answer, reconciling new evidence quickly and changing pursuit priorities before competitors realise that the forecast has moved.

Author: Darian Macey

Darian is a former Engineering Officer with the RAE with tertiary qualifications in Engineering and Project Management. He is a leading practitioner within Australia's NSI sector with previous employment in Government, project management and building contractor organisations.