Validate before Openreach does

Compliance validation built specifically for A55 PIA submissions.

Two API calls. Backend-only. Your contractors keep using the field app they already have.

Request a walkthrough
POST/api/v1/submissions

The problem

Submissions fail.

PIA rejection rates are stubbornly high across the supply chain. Each rejected submission carries a cluster of cost.

  1. 01£ per reject

    Penalty fees

    Openreach charges back on failed submissions.

  2. 02weeks added

    Cycle time

    Weeks added while sites cool and rework gets scheduled in.

  3. 03compounding

    Contractor goodwill

    Crews get paid on acceptance, and every rejection delays that.

For contractorsin the field

Field engineers don't get told what's wrong until the back-office has already looked at it, batched it, and bounced it back. By then the team has moved on and the site is two days cold.

  • No feedback at the point of submission
  • Re-mobilisation cost on every reject
  • Defects discovered too late to fix cleanly
For platformsback-office QA

QC sits with a small back-office team trying to catch defects across thousands of submissions. The maths doesn't work. Things slip through. Openreach notices.

  • Sampling lets defects through by design
  • Headcount can't scale with submission volume
  • Reputation with Openreach erodes
“The platforms that fix this don’t just reduce rejections — they earn the kind of submission record Openreach learns to trust.”

What Fibreflo does

A backend API. Submission in, score out.

One pipeline runs on every submission. Four layers, each doing one job well. The output is a compliance score, a risk band, and a defect list with severity.

01

Quality gate

Image and metadata sanity checks. Bad inputs are rejected before they reach the model.

02

Classification

Each evidence artefact is identified and routed to the correct rule path.

03

Detection

Computer-vision models tuned for A55 evidence types call out defects with severity.

04

Rules engine

Encoded against actual A55 structures. Per-platform rule selection is configurable.

Engineer onsite

Defects come back in the same flow the engineer is already in. Re-shoot, re-submit, walk off site clean.

Back-office amendment

Soft defects route to the platform’s existing amendment workflow. Nothing new for the back-office team to learn.

How it integrates

Two endpoints. Backend-only.

Your platform posts a requirements set, then posts the submission. We respond with the score, band, and defect list. Your app decides what to do with it.

No SDKs to ship. No client surfaces to redesign. No new app for field engineers. Most teams ship a working integration in a sprint.

request.sh
curl -X POST https://api.fibreflo.io/api/v1/submissions \
  -H "Authorization: Bearer $FIBREFLO_KEY" \
  -H "Content-Type: application/json" \
  -d @submission.json

{
  "submission_id": "sub_01HW4...",
  "score": 90,
  "band": "green",
  "defects": [
    { "point_id": "cd99f0d9-6824...", "severity": "warning",
      "note": "blockage start point has a blurred image" }
      ...
  ]
}

Backend-only

Server-to-server. Field engineers never see Fibreflo. Their app does not change.

Graceful degradation

If our API is unreachable, your platform proceeds. No hard dependency. No blocking.

Sprint-sized

A first integration is a sprint of work, not a quarter. Two endpoints, OpenAPI spec, partner dashboards.

The approach

Built for one job and one regulator.

01

Rules engine

Encoded against actual A55 structures, not generic compliance heuristics. Updates as the standard moves.

02

Image models

Tuned for A55 evidence types — joint chambers, dp tags, blockage markers, tm signage, site overviews.

03

Quality gate

Calibrated for field-captured imagery: low light, awkward angles. Bad inputs are rejected before models see them.

04

Rule selection

Shaped to your data, not imposed on it. Each partner configures which rules apply to which jobs.

If your submissions don’t fit our shape, we’ll say so. The product is narrow on purpose — that’s why it works.

Architectural foundation

One engine. One commercial product, today.

Helios Core is the underlying compliance-validation engine. Fibreflo is its PIA application — the only commercial product on the public site.

FibrefloLive
PIA / Fibre
AppFuture
Water
AppFuture
Gas
AppFuture
Highways
AppFuture
Electricity
Helios Coreunderlying compliance pipeline
01Quality gate
02Classification
03Detection
04Rules engine

What’s live today

Status, plainly.

As of May 2026

Live
  • —Validation engine in production
  • —OpenAPI specification published
  • —Partner platform dashboards
In progress
  • —First platform pilot integration
  • —Cyber Essentials certification
  • —Partner documentation site
On roadmap
  • —Cyber Essentials Plus
  • —ISO 27001
  • —Additional platform integrations

About

The company behind the product.

Fibreflo is structured as two companies, by design.

Contracting entity
Fibreflo Technology Limited — UK registered. Signs every customer contract.
IP holder
Arvexis Limited — owns the underlying Helios Core and licenses it to Fibreflo as a vertical brand.

Built to be the kind of supplier procurement teams approve.

  1. 01Cyber Essentialsin-progress
  2. 02Cyber Essentials Plusplanned
  3. 03ISO 27001planned

Frequently asked

Five questions, one answer each.

  1. All submission data is held in the UK. Partners remain GDPR controllers; Fibreflo acts as processor under a standard DPA.

  2. Your platform proceeds. The integration is non-blocking by design — submissions queue or pass through, your app decides.

  3. No. Fibreflo is backend-only. Engineers continue using the field app they already have, unchanged.

  4. UK PIA only. Other utilities sit under separate Arvexis products and are not on the Fibreflo roadmap.

  5. Pilot terms are available for qualifying platform partners. Talk to us about volume, scope, and integration timeline.