Managing a fire protection business on Simpro gives you a strong foundation for job scheduling, engineer allocation, and invoicing. What it does not give you is a direct connection to what is actually happening on site during a fire alarm test.
Field testing data still has to be entered manually. Asset records have to be updated separately. Compliance reports have to be prepared after the fact. For many contractors, that means engineers recording results on paper or in a separate system, and someone in the office transcribing that information into Simpro later.
The nimbusGo and Simpro integration, powered by Dokkit, is designed to close that gap. Test results, asset records and compliance reports captured on site by nimbusGo flow automatically into the corresponding Simpro job, without a manual transcription step. This guide explains how the integration works, what it changes in practice, and what fire protection businesses typically want to know before adopting it.
nimbusGo is a compact, portable device that connects to compatible fire alarm control panels on arrival at site. No panel replacement, no specialist re-wiring, no changes to existing infrastructure are required.
Once connected, nimbusGo reads live panel events and captures testing information as work is carried out. Engineers work through a structured testing workflow on the handset, which reduces reliance on manual recording and gives them access to panel information while moving around the building. From the first visit, the device builds a digital asset register, capturing every device, zone and test outcome automatically.
nimbusGo has been developed around the requirements of BS 5839 Clause 43.3.25, the British standard governing fire alarm servicing and record-keeping.
On suitable sites, nimbusGo can reduce engineer labour time by up to 50% and support work that may otherwise require two engineers. Whether a one-engineer approach is appropriate will depend on the site, system and scope of work, but for contractors running several large-site visits per month, the reduction in labour time is typically significant.
"nimbusGo brings total transparency to fire system testing. It's a smart, scalable solution that gives us the compliance assurance our clients demand and our engineers trust." — Marlowe Fire & Security Group
The integration is powered by Dokkit, a specialist compliance reporting platform that sits between nimbusGo and Simpro. Understanding the role each part plays helps clarify what the integration actually delivers.
|
Layer |
Platform |
Role |
|
Field data capture |
nimbusGo |
Tests devices, logs results, captures photos and faults on-site |
|
Compliance reporting |
Dokkit |
Generates automated, fully formatted compliance reports from raw test data |
|
Job management |
Simpro |
Receives synced asset records, updates job status, drives invoicing |
Dokkit does more than pass data through. It transforms raw test results into structured compliance documentation before anything reaches Simpro, so what arrives in your job management system is already formatted, labelled and audit-ready.
As listed on the Simpro Marketplace, the integration covers:
Device data is automatically mapped to the correct sites and assets in Simpro, removing the manual matching step that often introduces errors when field data is transferred into a job management system.
Setup is handled through Dokkit and the Nimbus onboarding process — it is included in the starter package, not a separate technical project. There is no requirement to change your existing Simpro configuration or rebuild your site and asset structure. The integration is available across:
The practical impact shows up across field operations, back-office administration, and client-facing compliance delivery.
Without the integration, a typical fire service visit generates data in two places: the engineer's on-site notes, and whatever gets entered into Simpro back at the office. Those two records are rarely identical, and the gap between them is where information gets lost.
With nimbusGo connected to Simpro, the engineer's on-site activity becomes the record. Test results, device outcomes, fault findings and photos are captured once and flow automatically into the corresponding Simpro job. There is no separate transcription step, and no administrative backlog to clear at the end of the week.
Simpro jobs update as testing activity happens, rather than when an engineer submits a report later in the day. For operations managers coordinating multiple active sites, that visibility supports more informed decision-making. It also has a direct commercial benefit: when a fault is captured on site and immediately visible in Simpro, remedial work can be quoted and scheduled the same day rather than waiting for the engineer to report back.
Invoicing accuracy depends on job records being complete. When field data arrives automatically, invoices can be raised more quickly and with less back-and-forth to confirm what was done on site.
"Nimbus gives us great traceability and evidence for all our servicing contracts. It's a huge benefit to us." — M&G Fire Protection
The engineer connects nimbusGo to the panel on arrival. The device reads the panel configuration and presents a structured testing workflow. As each device is tested, results are logged automatically and synced to the Nimbus cloud. By the time the engineer leaves site, the Simpro job has been updated, the asset register is current and Dokkit has generated the compliance report. The client receives proof of testing the same day.
On suitable sites, this is the workflow that supports the reduction in labour time. Whether a one-engineer approach is appropriate will depend on the site and scope of work, but the administrative saving applies to every visit regardless of site size.
When a device fails, the engineer captures the fault on the nimbusGo handset, including photos, part numbers and location details. That information flows into Simpro immediately. The office has what it needs to raise a remedial quote without a follow-up call to the engineer. For contractors where slow remedial quoting is a margin issue, removing that delay has a direct commercial effect.
See how M&G Fire Protection reduced labour costs and improved zone plan verification after adopting nimbusGo.
Dokkit generates fully formatted compliance certificates automatically when test data flows through the integration. These attach to the relevant Simpro job record and can be delivered to clients directly from the portal, attached to invoices or stored for audit purposes. There is no manual formatting step and no risk of a certificate being issued with incomplete information.
|
Capability |
Simpro alone |
Simpro + generic form tool |
Simpro + nimbusGo (via Dokkit) |
|
Fire alarm asset register |
Manual entry |
Manual or CSV import |
Auto-synced from panel config |
|
Test result logging |
Manual entry |
Manual on mobile form |
Automatic from panel events |
|
BS 5839 Clause 43.3.25 compliance |
Not addressed |
Partial |
Built-in, non-editable records |
|
Compliance report generation |
Manual |
Manual or template-based |
Automated via Dokkit |
|
One-engineer testing |
Not supported |
Not supported |
Supported |
|
Real-time job updates |
Not applicable |
Delayed |
Real-time from site |
|
Client-facing proof of testing |
Manual delivery |
Manual delivery |
Client portal included |
Simpro is a capable job management platform. What it is not is a fire alarm compliance tool. It has no mechanism for capturing test data directly from a panel and no built-in understanding of BS 5839 requirements. That is not a limitation of Simpro; it is simply not what the platform was designed to do.
Generic mobile form tools reduce the paperwork problem but do not eliminate it. Data still has to be manually mapped to the correct Simpro job, and compliance reports still have to be formatted separately. The double-entry problem is reduced, not resolved.
The more significant difference with nimbusGo is that test results are driven by panel events rather than engineer input. A record produced because the panel confirmed a device response carries a different weight from one produced because an engineer ticked a box. For contractors working in sectors where that distinction matters to auditors, insurers or clients, it is worth understanding before choosing a solution.
For more on how nimbusGo fits within a broader fire safety technology strategy, see the Nimbus System Integrators page.
What does nimbusGo cost?
The Starter Package is priced at £545, which includes onboarding and training services. Platform access is £70 per month. For a business currently spending engineer time on post-visit admin and manual compliance reporting, the calculation is straightforward: if a single large-site visit previously required two engineers and now requires one, the saving on that visit alone can exceed the monthly platform cost.
How long does onboarding take?
Onboarding is included in the Starter Package. nimbusGo builds the asset register automatically from the first site visit, so there is no data migration, no pre-loading of site information and no specialist IT involvement required. Most teams are working confidently within a few days of device delivery.
Does it work with an existing Simpro setup?
Yes. The integration does not require changes to your existing Simpro configuration, site structure or asset hierarchy. Dokkit handles the mapping between nimbusGo data and your Simpro records as part of the integration setup.
What panels does it support?
nimbusGo is compatible with panels from more than 20 major manufacturers, including Advanced, Kentec, Notifier, Gent, Morley, Siemens, Honeywell and Tyco. The full list of compatible panels is available on the Nimbus website. Contractors should check the current list or speak with the Nimbus team to confirm support for the panels within their client estate.
What ongoing support is available?
Nimbus provides support covering both the device and the platform, giving contractors a single point of contact rather than being directed between Nimbus and Dokkit separately. The team can be reached at sales@nimbusdigital.com or on +44 (0) 1159249537.
nimbusGo does not replace Simpro. It supports the part of the workflow that Simpro was not designed to handle: what happens on site during a fire alarm test, and how that information makes its way into the job record accurately and without manual intervention.
For fire protection businesses already on Simpro, the integration is worth understanding in the context of your own operation. How much time do engineers currently spend on post-visit admin? How quickly can the office raise a remedial quote after a fault is found? How confident are you in the completeness of your compliance records?
If those questions are relevant to your business, the conversation starts with a demo. Book a demo at nimbusdigital.com, or review how other contractors have approached the decision through the M&G Fire Protection case study and the Marlowe Fire & Security case study.