Welcome to the
Strike
Intelligence
Bureau
Every utility strike investigated properly, with evidence, and turned into the learning that prevents the next one.
We can't reduce what we don't understand.
A specialist investigation tool for any contractor, utility or altnet that digs near buried services. Built by Sygma Solutions, sister of the Underground Intelligence Bureau. In build now.
60,000strikes / yr
the UK estimate everyone still quotes. It dates from 2014, because nobody is counting properly.
+17%in 2025
HSE-recorded electrical strikes rose to 3,025 last year. The direction of travel is the wrong way.
One
Strike Intelligence Bureau. The investigation, the evidence and the learning in one place.
What it's about
Strikes into learning.
Most strike investigations are a form filled in after the event. A cause gets picked from a dropdown, the paperwork gets filed, and the next strike happens the same way.
The Bureau runs the investigation the way a specialist would. What plans were held. What the locator actually showed. Was the genny connected, and to what. What was visible above ground, and what did each feature imply underground. What did the operative believe at the time.
Then the HSG47 lens is applied to the answers, and the tool pushes back where they do not hold together. Reports, themes and corrective actions fall out the back.
The difference
A claim is not evidence. "The genny was used" is a claim; the device log is the evidence. In the Bureau every answer has an evidence slot beside it, and a cause cannot be selected until the plan, locate and dig questions carry evidence.
That is the whole product in one sentence: investigations you can stand behind, because every finding names its source.
Why we're doing it
Nobody else does this.
Strike investigation is not a workflow anywhere
The industry portal takes statistics in and gives a dashboard out. Incident platforms have a strike as one incident type among many. Nothing walks an investigator through a strike properly.
Nobody joins the locator's own data to the strike
Every locator manufacturer logs usage in its own silo. No product on the market reads the device log for the window of the strike and puts it beside the operative's statement.
Generic AI tools do not know this trade
AI-assisted investigation products exist, but none of them knows HSG47, PAS 128 or EUSR. Ours is built from a specialist training business that teaches this for a living.
The loop to training never gets closed
Root cause says one thing, the training record says nothing. The Bureau types actions, so a training action carries its owner, its course and its closure evidence.
Nobody is counting properly
There is no general legal duty to report a strike, and the numbers the industry quotes are a decade old. Investigated strikes, properly recorded, are better data than anyone holds today.
What we're building
The product.
The guided investigation
A question tree that adapts to the answers. The assistant reads the uploaded plans, permits, statements and device logs, pre-fills what it can, and challenges what does not reconcile.
The Strike Intelligence Standard
A published core standard for what a proper strike investigation asks and records. Compatible with the industry's own reporting, so the regulator return is a button, not an afternoon.
The device data, never typed
The locator log for the exact window of the strike, pulled by the system. Seconds per mode, mode order, depth readings and alerts, beside comparison days for the same unit.
Evidence beside every claim
Photos, plans, permits, statements and video all read and extracted by the system. Findings name and quote their document, and record what a document does not say.
Reports that hold up
A proper investigation report per strike, and period reports across the register: themes, causes, assets, environments. Every conclusion cites its evidence.
Your own agent
Each tenant gets a built-in AI agent that has read their register and answers with citations. Ask it what changed, what repeats and where the next strike is coming from.
Your standard, cited by clause
Upload your own safe digging standard and procedures. The investigation and the report quote your clauses first, with HSG47 as the fallback.
Actions with teeth
Typed actions: training, procedural, kit. Owner, due date and closure evidence required. Closing everything the same afternoon gets flagged, not filed.
Multi-tenant, properly
Your strikes are yours. Own database boundary, row-level security, full audit trail, UK hosting. Access is scoped to the person, not just the company.
What comes out of it
Fewer strikes.
For the companies that use it: investigations that stand up, reviews backed by device data rather than opinion, themes you can act on across the whole register, and the regulator return handled on the way through.
Retraining aimed where the evidence points, not spread thin across everyone. And a countable record of the stops your stop rule produced: the strikes that did not happen.
Sold with Sygma training, so the people running the investigations are trained investigators. At the top tiers, Sygma's own reviewers read and sign off every strike.
The review ladder
- Toolrun your own investigations, the AI reviews underneath
- QuarterlySygma reads a sample and writes the themes report
- Monthlythe same, monthly, with a call
- Every strikea Sygma reviewer signs off each investigation before close
In build now
Want in early?
We are building this with a small number of early partners who shape the flow, the questions and the reports. If your company hits buried services and wants to understand why, talk to us.