wollopit Got a problem? →

Fire engineering software: reports, FEBs & approvals

Fire engineers: know where every report sits. Model more, chase less.

Fire engineering briefs, brigade comments and certifier approvals are spread across email chains, marked-up PDFs and somebody's memory. We build report and approval tracking for fire engineers that shows where every performance solution is up to, from the first FEB to the final inspection letter. Then we host it and look after it.

Looking for fire engineering report tracking software?

A single performance solution goes through the brief, the analysis, the brigade review, certifier sign-off and a final inspection. Every step brings its own comments, revisions and approvals. Most fire engineering firms track all of it with Outlook folders, a job spreadsheet and a SharePoint structure only one person fully understands. When the design team moves a stair three weeks before construction, nobody can say quickly which solutions it breaks.

Wollopit builds custom software for fire engineers around how your firm actually runs jobs. Every report has one record showing its stage, its stakeholders, its current revision and its evidence of approval. Comments get logged and answered against the right version. Reports start from your own templates and clause library. Inspections happen on a tablet and the letter writes itself. We connect your modelling outputs, project files and accounting, then host and maintain the lot so your engineers can get back to engineering.

01The problems

What we hear from fire engineers

Does your fire engineering firm have these problems? Here's how we'd fix them.

Most fire engineering firms we talk to do seriously technical work, then lose hours every week chasing emails and working out which revision is current. The engineering is the easy bit. Keeping track of it is the hard part.

  • The problemFEBs stall for weeksThe brief goes out to the certifier, the brigade and the client. Then it sits there because nobody is chasing it.
    How we fix itBrief tracking with due dates per stakeholder, automatic reminders and a log of who has agreed to what.
  • The problemBrigade comments everywhereFeedback turns up as a marked-up PDF, a phone call and a follow-up email that contradicts both.
    How we fix itA comment register where every comment gets logged, answered and closed against the report version it relates to.
  • The problemThe certifier is reading Rev BRev D went out on Tuesday but the certifier is still working from an old attachment.
    How we fix itControlled report versions with an issue register showing who received which revision and when.
  • The problemDesign changes break solutionsA stair gets moved or a mezzanine appears and nobody checks it against the solutions already agreed.
    How we fix itA design change register that flags which performance solutions a change touches and drafts a variation for the client.
  • The problemEvery report starts as a copyReports begin by copying the last similar job, complete with the wrong address and an outdated NCC reference.
    How we fix itA report builder that pulls in project details, DtS departures and your approved standard clauses.
  • The problemModel runs nobody can traceCFD and egress runs live on a workstation in folders called FINAL_v3_new. Nobody can say which run fed the report.
    How we fix itA model log for every job showing inputs, assumptions, results and the report revision each run supports.
  • The problemApprovals you can't proveThe sign-off is buried in someone's inbox. Two years later a certifier or insurer asks for it.
    How we fix itApproval records stored against every performance solution with the email, letter or form attached.
  • The problemInspections on scraps of paperCompletion inspections get noted on a phone, typed up days later and the builder is ringing for the letter.
    How we fix itTablet inspection checklists tied to each solution, with photos, defects and an inspection letter generated on the spot.
  • The problemFees quietly blownExtra brigade rounds and redesign work get done for free because nobody tracked them against the fee.
    How we fix itFee tracking by stage, timesheets per job and variations raised before the work starts, with invoices into Xero or MYOB.
  • The problemWorkload nobody can seeDirectors can't tell how many reports are in review or which engineer is buried until something slips.
    How we fix itA pipeline board of every job by stage, engineer and due date, with overdue items flagged.
  • The problemOwners never get the maintenance listThe solution depends on certain safety measures being kept up but the owner and their fire contractor never see it clearly.
    How we fix itHandover packs that list every measure and maintenance requirement the solutions rely on, ready for the fire safety schedule.
  • The problemRegistrations creep up on youPractitioner registrations, insurance and CPD hours live in a spreadsheet until a renewal is overdue.
    How we fix itA registration and CPD register for every engineer with expiry alerts well ahead of time.
02What we build

Solutions

What we build for fire engineers. Usually all talking to each other.

Pick the one that's hurting most or join the whole lot up. Everything is built around how your team works, not the other way round.

01

Performance solution tracker

Every solution on every job with its stage, its stakeholders, its current revision and its approval status.

02

FEB manager

Briefs issued to stakeholders with due dates, reminders, agreed items and a record of every meeting.

03

Stakeholder comment register

Brigade, certifier, client and peer review comments logged, answered and closed against the right revision.

04

Report version control

Draft, issued and superseded revisions clearly marked, with an issue register for every transmittal.

05

Report builder & clause library

Your Word templates filled with project details, DtS departures and approved standard text.

06

Modelling & analysis log

FDS, PyroSim and Pathfinder runs recorded with inputs, assumptions, results and linked report revisions.

07

Design change & variation register

Design changes checked against agreed solutions, with variations drafted and sent for approval.

08

Site inspection app

Checklists on a tablet, photos, defects and inspection letters ready before you leave site.

09

Approvals & evidence vault

Sign-offs, brigade letters and compliance forms stored against each solution and easy to find years later.

10

Client & certifier portal

Stakeholders log in to see the current revision, open comments and what's waiting on them.

11

Fees, timesheets & job costing

Fee proposals, time by stage, budget burn and invoices flowing into Xero or MYOB.

12

Job pipeline & workload board

Every job by stage, engineer and due date so directors can see the load at a glance.

13

Handover packs

Safety measures and maintenance requirements from each solution, packaged for owners and fire protection contractors.

14

Registration & CPD register

Practitioner registrations, insurance and CPD hours with renewal alerts for the whole team.

15

A website that wins briefs

Hand-built, quick on mobile, showing your project types and expertise to the people who engage you.

03The systems

The big ones

Every report and approval, on one system.

These are the systems fire engineering firms ask us about most. Each one works on its own. They get properly useful when they're joined up.

Report & approval tracking

Every performance solution, brief to sign-off.

Each job holds its performance solutions with their DtS departures, current stage, stakeholders and approval evidence. Anyone in the office can see exactly where a solution is up to without asking the engineer who wrote it.

  • Solutions listed per job with DtS departures
  • Stages from brief to final inspection
  • Who it's waiting on and since when
  • Current revision always on top
  • Approval evidence attached to each solution
  • Overdue and stalled items flagged
  • Search by NCC clause or building class
  • Links to model runs and drawings
  • Full history of every change

FEB & stakeholder review

Briefs agreed in days, not months.

Issue the FEB to every stakeholder from one place with due dates and automatic reminders. Comments get logged against the right revision, answered by the engineer and closed off so nothing gets lost between rounds.

  • Issue FEBs with stakeholder due dates
  • Automatic reminders when items go quiet
  • Comment register per revision
  • Responses and close-out recorded
  • FEB meeting minutes and actions
  • Agreed acceptance criteria logged
  • Peer review workflow
  • Stakeholder portal logins
  • Every round kept on the record

Reports & version control

Reports that start half written.

New reports open in your own template with the project details, building class and DtS departures already in. Standard clauses come from a library your senior engineers control. Every issued revision is locked and logged so the certifier never reviews the wrong one.

  • Your Word templates, filled automatically
  • Approved clause library
  • Project details pulled from the job
  • Model runs linked to each section
  • Internal review and sign-off before issue
  • Issued revisions locked
  • Transmittal and issue register
  • Superseded versions clearly marked
  • Exports to PDF with your title block

Site inspections & handover

Inspect it, letter it, hand it over.

Engineers walk the building with a checklist built from the agreed solutions, taking photos and noting defects as they go. The inspection letter is drafted before they reach the car. The owner gets a clear list of what has to be maintained.

  • Checklists built from each solution
  • Works on a tablet or phone
  • Photos and markups against each item
  • Defects issued to the builder
  • Reinspections tracked to close-out
  • Inspection letters generated on site
  • Handover pack for the owner
  • Maintenance requirements for the fire contractor
  • Inspections booked on a shared calendar

Fees & workload

Know which jobs are making money.

Fee proposals set the stages and timesheets record against them. Extra brigade rounds or design changes turn into variations before the work gets done. Directors see every job by stage, engineer and budget used on one board.

  • Fee proposals by stage
  • Timesheets per job and stage
  • Budget used versus fee
  • Variations raised and approved
  • Invoices into Xero or MYOB
  • Pipeline by stage and engineer
  • Due dates and overdue alerts
  • Workload per engineer
  • Win rate on fee proposals
04How it changes

Before and after

A brigade review, wolloped.

Here's how one round of brigade comments could change. Every firm runs jobs a little differently, so we map yours first.

Before

  1. Realise the brigade has had the report for five weeks
  2. Dig through Outlook for the marked-up PDF
  3. Retype the comments into a Word table
  4. Find out the certifier has been reading Rev B
  5. Hunt for last year's sign-off email for a similar job
  6. Do the extra round without telling the client it's outside the fee

After

  1. Automatic reminder went out after ten days
  2. Comments logged against Rev C on arrival
  3. Engineer answers each one in the register
  4. Rev D issued and logged to every stakeholder
  5. Past approvals found in seconds by clause
  6. Variation sent to the client before the work starts
05Services

Everything under one roof

Software, websites and systems for fire engineers.

Whether you're starting fresh or upgrading what you've got, it's one team from the first sketch to the support call.

Custom software for fire engineers

Built around how your fire engineering firm actually runs: performance solution tracker, fEB manager and the admin in between, in one system you own.

Websites for fire engineers

Fast, hand-built websites that rank for the searches your customers make and turn visits into enquiries, bookings or orders.

Fire engineering firm system upgrades

Running on spreadsheets, old software or a platform you've outgrown? We move your data across and upgrade in stages so the business never stops.

Apps and portals for fire engineers

Stakeholder comment register and report version control: customer and staff portals that work on any phone without an app store.

Integrations and automation

We connect Microsoft 365, SharePoint and Microsoft Teams so information moves on its own and nobody retypes it.

Hosting, support and care

Managed hosting, updates, backups and security for your fire engineering firm, looked after by the people who built it.

06Integrations

Connections

Plays nicely with what you already use.

We connect to the tools your engineers already rely on, work alongside the platforms you're happy with or replace the ones holding you back.

  • Microsoft 365
  • SharePoint
  • Microsoft Teams
  • Google Workspace
  • Dropbox
  • Xero
  • MYOB
  • Procore
  • Aconex
  • Bluebeam Revu
  • Adobe Acrobat
  • PyroSim
  • Pathfinder
  • FDS
  • Smokeview
  • Revit
  • Synergy
  • DocuSign
  • Stripe
  • Google Maps
07How we work

The process

Some people dip their toe in. We turn up in a rebreather.

We get properly below the surface of your fire engineering firm: the systems, the busy days and the jobs everyone hates. Then we fix the bits that matter most first.

  1. 01

    Think

    We sit with your engineers and admin team, follow a job from fee proposal to final inspection and find where the time actually goes.

  2. 02

    Archi-tech

    We plan it before writing code: your solutions, stakeholders, report templates, model outputs, inspections, fees, hosting and cost.

  3. 03

    Build

    Real engineering, shown to you early and often. Usually the report and approval tracker first, so you get a win before the next brigade round.

  4. 04

    Look after

    We host it, maintain it and keep improving it. When something breaks you call the people who built it.

08Questions

FAQ

Things fire engineers ask us.

Something else on your mind? Ring 0423 011 252 and ask the people who'd build it.

Can it work with our modelling tools and project files?

Usually, yes. Results from PyroSim, Pathfinder and FDS can be logged and attached to each report. Project files can stay in SharePoint or Dropbox and invoicing can sync with Xero or MYOB.

Can it produce reports in our own Word template?

Yes. We build the report builder around your existing templates and standard clauses, so issued reports look exactly like yours do now. They just take less time to put together.

Can certifiers, brigades and clients log in?

Yes, if you want them to. A stakeholder portal shows them the current revision, their open comments and what's waiting on them. You control who sees what.

We work across different states. Can it handle that?

Yes. Each job can follow the referral process and paperwork for its state, so a Queensland job and a NSW job each get the right stages and forms.

We already use Synergy and SharePoint. Do we have to switch?

No. If your existing platforms are doing their job we build around them and connect to them. If something is holding you back we'll show you what replacing it would involve before anything changes.

Is our project information kept secure?

Yes. It runs on our own managed servers with proper logins, access controls and backups. Staff and stakeholders only see the jobs they're meant to.

How much does a system like this cost?

It depends on what you need, so we quote up front once we understand it. No surprise invoices, no lock-in and you own what we build.

How long does it take?

Smaller pieces like a report tracker or comment register can be quick. Bigger systems are planned in stages so you get the first win early instead of waiting for everything at once.

Who looks after it once it's built?

We do. We host it on our own managed servers and keep it updated and secure. When you need something you ring the people who built it.

We already have systems. Can you upgrade them instead of starting again?

Usually, yes. We keep what's working and upgrade the rest in stages. We move your data across, connect the old and new while we switch and retire the old system only when the new one is proven.

Contact

Got a fire engineering firm problem? Consider it wolloped.

Tell us what's slow, broken, manual or missing. You don't need a spec, just describe what's going on.

I've got