Last Updated: October 29, 2026
Quick Summary
A fire engineering brief is an early document that gets stakeholders to agree in principle on the fire safety strategy, while a fire engineering report is the final technical submission that proves the design meets the agreed performance criteria. The brief comes first, and the report builds on it.
- The brief is prepared early, before detailed design is complete.
- The brief defines performance criteria and records any deemed-to-satisfy provisions the project cannot meet.
- The report presents the full analysis, design fire scenarios and evidence for certifiers.
- Keep every assumption in the report traceable to the agreed brief.
- Start with a brief whenever the design departs from prescriptive requirements.
Table of Contents
- Fire Engineering Report vs Fire Engineering Brief at a Glance
- What a Fire Engineering Brief Sets Out to Achieve
- Fire Engineering Brief Process: From Stakeholder Workshop to In-Principle Agreement
- Fire Engineering Report Contents: What the Final Submission Must Show
- Fire Engineering Brief Template: Core Sections to Include
- Fire Engineering Report Examples: How Finished Reports Differ by Building Type
- Choosing Between a Brief, a Report or Both for Your Next Project
- Frequently Asked Questions
Fire Engineering Report vs Fire Engineering Brief at a Glance
Most projects that need performance-based fire engineering eventually meet two documents: the fire engineering brief and the fire engineering report. Both come from the same engineering process, and both are often confused with each other. The confusion between them can cost projects time, so it is worth starting with a clear distinction. The brief is the early agreement on how fire safety will be approached, and the report is the final technical submission that proves the design works. Performance-based design guidance for structures in fire
The table below gives the practical differences at a glance. Use it as a quick reference before reading the detail that follows.
| Aspect | Fire Engineering Brief | Fire Engineering Report |
|---|---|---|
| Stage | Early, before detailed design is complete | Late, once the design is developed |
| Purpose | Reach in-principle agreement with stakeholders | Demonstrate the design meets performance requirements |
| Audience | Developers, architects, certifiers, fire authorities | Building certifiers and approving authorities |
| Level of detail | Strategy and criteria | Full analysis, modelling and evidence |
| Typical outcome | Agreed fire safety strategy | Documented basis for building approval |
Pros and cons at a glance
- Fire engineering brief
- Pros: Surfaces disagreements early, when changes are cheap. Creates a shared record of agreed criteria.
- Cons: Requires time from every stakeholder. Can feel like extra work before anything is built.
- Fire engineering report
- Pros: Provides the formal evidence certifiers need. Gives a defensible record of compliance.
- Cons: Costs more to produce and must be updated if the design changes. Weak briefs make reports harder to write.
What a Fire Engineering Brief Sets Out to Achieve
A fire engineering brief is a preliminary document. It mitigates project risk by bringing stakeholders together early to agree on the fire safety strategy. The aim is in-principle agreement, meaning everyone accepts the approach before the full analysis begins. Fire Engineering Brief guidance
In practice, the brief defines the performance criteria the design must meet. It also records which deemed-to-satisfy provisions the project cannot meet, and why. A brief that answers these questions well can save time, and a certifier who has already agreed to the approach is less likely to reject the final report.
Fire Engineering Brief Process: From Stakeholder Workshop to In-Principle Agreement
The brief usually starts with a stakeholder workshop. The developer, architect, builder, fire engineer and, where possible, the certifier attend. The group reviews the building’s use, layout and occupancy, then identifies where the design departs from prescriptive requirements.
Next, the engineer proposes performance criteria and the trial design fire scenarios that test them. Readers planning this stage can check what a fire engineering performance solution costs in Australia before committing. Stakeholders comment, and the brief is revised until the group reaches in-principle agreement. The typical timeframes for preparing and approving a performance solution show how long this stage and the wider approval process tend to take. The result is a written record that the final report can build on directly.
Fire Engineering Report Contents: What the Final Submission Must Show
The fire engineering report is the final technical submission. It presents the full performance-based analysis and shows how the design meets the agreed criteria. Where the brief sets the direction, the report provides the evidence.
A typical report covers the building description, the agreed performance criteria, the design fire scenarios, the analysis methods and results, and the conclusions. It also documents any assumptions and limitations. Certifiers read the assumptions closely, so unclear or missing ones are a frequent reason for queries. Keep every assumption traceable to the brief.
Fire Engineering Brief Template: Core Sections to Include
A useful brief is short and structured. We recommend the following core sections:
- Project overview: building use, classification, size and key constraints
- Departures from prescriptive requirements: each non-compliant element and the reason for it
- Performance criteria: the measurable goals the design must meet
- Design fire scenarios: the fires the analysis will test
- Analysis approach: the methods and tools to be used
- Stakeholder sign-off: the agreed positions and who agreed them
Keep each section to a few paragraphs or a clear table. A brief that runs to dozens of pages usually signals that the strategy is not yet settled.
Fire Engineering Report Examples: How Finished Reports Differ by Building Type
The depth of a report depends on the building. A small commercial fit-out may need a focused report on one departure from the code. A large mixed-use building may need analysis of evacuation, structural fire resistance and smoke control together.
For example, a hospital design calls for a different evidence base than a warehouse. A recent case study of a new hospital development showed how structured verification can support a complex design. Applying verification in fire engineering to hospital design The principle carries across building types: the report must match the level of risk and complexity in the project. Over-documenting a simple building adds cost, while under-documenting a complex one invites rejection.
Choosing Between a Brief, a Report or Both for Your Next Project
Most projects with a non-standard design need both documents. The brief secures agreement early, and the report then proves the detail. A straightforward project that stays within the deemed-to-satisfy provisions may need neither, so confirm the requirement with the certifier before commissioning work.
As a rule, start with the brief whenever the design departs from prescriptive requirements. It is the cheapest point to resolve disagreements. Then commission the report once the strategy is agreed. You can find out whether you need a fire engineer for your building project. Once you are ready to proceed, explore our fire engineering services to see how the work is delivered. For a view of the pathway choice itself, compare performance solutions with deemed-to-satisfy compliance to see which fits your project. Thornton Tomasetti’s work on performance-based fire engineering shows how large projects use this approach at scale. Performance-based fire engineering capability overview
Frequently Asked Questions
What is the difference between a fire engineering brief and a fire engineering report?
A fire engineering brief is an early, consultative document that records the proposed fire safety strategy and the performance criteria, so that stakeholders such as the building certifier and fire authority can reach in-principle agreement before detailed design. A fire engineering report is the final technical submission that demonstrates, with supporting analysis, that the building meets the performance requirements of the National Construction Code. The brief guides the design; the report proves it.
Is a fire engineering brief the same as a fire engineering report?
No. The two documents serve different stages of a project and have different purposes. The brief is a preliminary roadmap used to agree the approach, while the report is the detailed record of the analysis and justification submitted for approval. Some projects produce only a report, but where a performance solution is complex, preparing a brief first can reduce the risk of later redesign.
When should a fire engineering brief be prepared?
A fire engineering brief is usually prepared early in design, once the architectural concept is sufficiently developed to identify where the building will depart from prescriptive requirements. Preparing it before detailed analysis allows stakeholders to comment on the proposed strategy while changes are still inexpensive. Timing depends on the project, so confirm the sequence with your certifier and fire engineer.
What should a fire engineering report include?
A fire engineering report typically sets out the building description, the performance requirements being addressed, the design fire scenarios, the analysis methods used, the assumptions made, and the conclusions about compliance. It should also identify any conditions or ongoing maintenance requirements that the design relies on. Reviewers expect the reasoning to be traceable, so each assumption and result should be clearly supported.
