FRNSW Splits PBDB Consultation into Two Forms: July 2026 Update
The July 2026 update to FRNSW PBDB forms affects how a performance based design brief NSW submission is prepared, priced, and tracked. On 16 July 2026, Fire and Rescue NSW announced that the PBDB consultation application, Version 01, was separated from the working PBDB document, Version 22. The arrangement supports application and fee processing across financial years. For fire protection firms, electrical contractors, building designers, retail operators, and asset managers, this change is less about a single document and more about how the early stage of a PBDB project is organised. It helps separate the administrative intake, the fee handling, and the technical design work into clearer stages. The official building fire safety information from Fire and Rescue NSW should be used as the primary reference for current form availability, submission requirements, and guidance updates.
FRNSW PBDB Forms and Performance Based Design Brief NSW: What Changed in July 2026
The key change is that the PBDB consultation application is no longer treated as the same document as the working PBDB document. The consultation application is now Version 01, while the working PBDB document is Version 22. This separation supports application and fee processing across financial years, which is important for project teams that prepare submissions near the end of a financial year.
In practical terms, the two documents serve different project stages. The consultation application supports the intake and administrative process. The working PBDB document supports the technical design and consultation work that follows. Keeping the two documents separate helps project teams avoid mixing fee related information with evolving design content.
| Document | Role in the Updated Process |
|---|---|
| PBDB consultation application, Version 01 | Supports the consultation application and fee processing stage. |
| Working PBDB document, Version 22 | Serves as the working document for PBDB design and consultation content. |
Project teams should confirm the current version of each form before preparing a submission. Version control is important because the consultation application and the working document may be updated separately.
Practical Workflow for Preparing a PBDB Submission
The split between the two FRNSW PBDB forms gives project teams a clearer workflow. The following approach helps fire, electrical, building, and facilities teams manage the submission without duplicating effort or mixing administrative and technical information.
- Confirm project ownership. Identify who is responsible for the consultation application, who is responsible for the working PBDB document, and who will coordinate fee related information.
- Prepare the consultation application separately. Use the PBDB consultation application, Version 01, for the intake and fee processing stage. Keep this document focused on the application details required for that stage.
- Maintain the working PBDB document independently. Use the working PBDB document, Version 22, for the technical design content, consultation notes, and evolving project information.
- Align the submission with the financial year. Because the arrangement supports fee processing across financial years, teams should record the relevant financial year for the application and any associated fee handling.
- Apply version control. Store the consultation application and working PBDB document in separate project folders or document registers. This makes it easier to track which version was used for each stage.
- Keep a submission record. Record the date of preparation, the names of responsible parties, the form versions used, and any later updates. This supports clear communication between designers, contractors, building owners, and fire safety stakeholders.
This workflow is especially useful where multiple professionals are involved, such as a fire protection consultant, an electrical contractor, an architect, a building owner, and a facilities manager. Each party can work from the correct document without assuming that one form covers the whole process.
What the Form Split Means for Fire, Electrical, and Retail Clients
For fire protection firms, the separation supports a cleaner division between administrative and technical work. Fire safety design teams can maintain the working PBDB document without carrying application details that are not part of the design content. This is useful when the project moves from early consultation to later stages where equipment selection, system design, and documentation become more detailed.
For electrical contractors and fire alarm or detection specialists, the change supports clearer project records. Electrical design notes, system documentation, and product information should be managed in a way that supports the working PBDB document rather than being mixed into the consultation application. This helps teams keep design intent, specification data, and project correspondence in the correct place.
For retail and commercial facility teams, the update is relevant wherever fire safety documentation needs to be managed across fitout, expansion, refurbishment, or operational changes. Retail environments often have changing layouts, trading hours, and occupancy arrangements. A well organised PBDB file helps the facility team track what was consulted, what was applied, and where later documentation may be needed.
The common thread is documentation discipline. The two FRNSW PBDB forms give project teams a reason to separate application records from working design records. That separation supports better communication, clearer accountability, and a more manageable project file.
How FireFactory Supports PBDB Related Product Sourcing
Where a performance based design brief NSW process leads to fire protection equipment selection, project teams need reliable product information and a clear supply path. FireFactory supports B2B fire protection buyers across Australia with product sourcing, specification support, and delivery coordination. This is useful when the working PBDB document moves from design discussion to product selection and installation planning.
For fire protection firms, electrical contractors, and building owners, the practical value is consistency. Product data, specification details, and order records help keep the project file aligned. FireFactory B2B teams can assist with identifying suitable fire protection products and equipment for commercial facilities, supporting project documentation, and coordinating supply for Australian sites.
Conclusion
The July 2026 separation of the PBDB consultation application and the working PBDB document gives project teams a clearer structure for application, fees, and technical work across financial years. The practical step is to treat the two FRNSW PBDB forms as separate workstreams, maintain current versions, and confirm the latest guidance before submission. For fire, electrical, and building teams, this reduces confusion and supports a more predictable project timeline.
FireFactory supports B2B fire protection buyers across Australia with product sourcing, specification support, and delivery coordination. Visit FireFactory to connect with a team that understands commercial fire protection requirements.
Frequently Asked Questions
What are the two FRNSW PBDB forms announced in July 2026?
The two forms are the PBDB consultation application, Version 01, and the working PBDB document, Version 22. They are now separated to support application and fee processing across financial years.
When did Fire and Rescue NSW announce the PBDB form split?
Fire and Rescue NSW announced the change on 16 July 2026. The announcement confirmed that the consultation application and the working PBDB document are separate documents.
How does the split help with fee processing?
The arrangement supports application and fee processing across financial years. This helps project teams separate the administrative application from the working design document.
Should the PBDB consultation application be the same as the working PBDB document?
No. The July 2026 update separates the two documents. The consultation application, Version 01, and the working PBDB document, Version 22, should be managed as distinct project records.
Where should project teams check current FRNSW PBDB guidance?
Project teams should check the current guidance on the Fire and Rescue NSW building fire safety page. This helps confirm the latest form versions and submission requirements before preparing a PBDB file.