ENTERPRISE
Framework delivery, multi client portfolios, white labelled DNO compliance for installer networks. When you carry the compliance risk for work other people install, the platform has to be built around that.
WHY ENTERPRISE EXISTS
A framework holder is accountable for every submission made under its name, by installers it does not employ. A portal operator carries whatever its users file through it. A bureau answers for a portfolio it never visited. The exposure sits with the head entity, while the work happens somewhere else entirely.
At that point compliance is not a workflow question, it is a governance one. You need every submission made the same way, every decision attributable, and the evidence to prove it without phoning the installer who filed it.
WHAT YOU GET OUT OF IT
Every member installer works to the same routing and produces the same pack, and the head entity can prove it.
One process, however many installers
Routing and documents are derived from the job data and the published rules, so a submission filed by a member you have never met comes out to the same standard as your own.
Evidence at head entity level
Every action attributable to a named user and account, under the regulation version in force. When the accountability sits with you, so does the proof.
Built into your stack, or your product
Bulk CSV ingest, custom API hooks, multi client account structures and white label embedding, wrapped around the systems you already run.
Network
SCALE
Multi client and multi entity account structures.
Evidence
AT HEAD LEVEL
Every submission attributable, under the rule in force.
1:1
ACCOUNT MANAGEMENT
A dedicated account manager from the first call.
WHAT'S IN THE BOX
01
A programme of hundreds of plots stays auditable plot by plot: every premises keeps its own MPAN, documents and hashed history, while the close geographic region application that covers them is produced and tracked once. No other UK platform automates this.
02
Every action across the network attributable to a named user and account, under the regulation version in force, with cryptographic checksums on every exported pack.
03
Account structures for installer networks, framework delivery partners and compliance bureaux operating on behalf of others.
04
Beyond the standard endpoints, integration work is scoped to your stack and built by our engineers rather than picked from a menu.
05
Bulk client and site intake from spreadsheets and exports out of housing stock or framework systems, with jobs created through the API, mapped to your fields rather than ours, with a preview before anything is created.
06
For portal operators and framework holders surfacing CLRD inside their own product, branded as theirs.
07
The same job produces the same route and the same documents whoever files it, derived from the job data and the published rules rather than local habit.
08
Scoped to your actual throughput, with explicit burst handling and over cap commercials defined upfront.
09
Where the scale justifies it, we shape things around how you already work. What that involves in practice is scoped with you rather than picked off a list.
10
Encrypted storage, two factor authentication, role based permissions and a tamper evident record on every job. Routing and documents come from a deterministic rules engine, never from AI, so every decision is reviewable.
11
A dedicated account manager who knows your network and your install patterns, with defined response SLAs and an escalation path.
12
Annual contracts, framework aligned terms, multi entity invoicing, data processing addenda and security questionnaires.
AFTER YOU SEND IT
Filing is half the job. The other half is waiting on the DNO, reading what comes back and acting on it. CLRD tracks all of it on the job.
DNO replies
Replies land on the job's own thread. Approval letters from all six DNO groups are read, in the formats CLRD has seen: the reference and any export limit filled in, and one click sends it to your client.
Follow up
No acknowledgement within 2 working days (10 at operators that don't send one automatically), or no decision after 28 days, and the job tells you. Nobody has to remember to chase.
Amend
Need to correct an application the DNO already holds? Amend it on the same job. Only the changed documents go, with a letter saying what changed, on the same DNO thread.
THE PLAN
Book a demo and we'll scope it with you: volume, terms and integration, then a supported two week pilot with 25 of your own jobs before you commit.
ENTERPRISE
Bespoke
Volume, terms and integration scoped to you
For framework holders, multi client operators, portal builders and large installer networks whose operating shape doesn't map cleanly to a published plan.
What's included
How we work with you
FAQ
From an installer
“This is one of those bits of software that is now considered an essential tool of my business.”
From our job records
9working days
Median from filing to a G99 Type A approval
From our job records
99 of 100
Connection offers first time, across the last 100 applications submitted through CLRD
We'll come back with an architecture, an integration plan and a commercial shaped around your operation.