CLRD converts structured installation data into regulator-ready DNO documentation — routed, formatted, and audit-defensible across G98, G99, G100, and SLD workflows.
Manual DNO process: 45–70 minutes · CLRD: ~3 minutes
Structured interpretation of regulation into deterministic execution.
We are working with a small number of professional installers to validate operational workflows before full launch.
Manual routing, ENA checks, DNO templates, and document control slow the job before it reaches the network.
A G98, G99, or G100 misroute is not just admin. It delays submission, creates rework, and adds cost before the job reaches approval.
G98 / G99 / G100ENA references, DNO formats, export limits, and supporting documents are checked manually job after job. That is where missing data, wrong formats, resubmissions, and cost enter the process.
ENA / DNO / SLDProof matters at audit. Inbox searches, copied templates, and spreadsheet notes do not scale as a compliance trail.
Audit DefensibilityEvery misroute, missing reference, rebuilt document, or weak audit trail adds time, cost, and exposure before the submission reaches the network.
Every submission built manually consumes time before the job reaches the network. Adjust the slider to estimate your monthly recoverable admin value, net of the CLRD plan that covers your volume.
The saving is not only the minutes recovered. It is the reduction in rework, delayed submissions, and repeated manual checks across every job — all before any plan cost is deducted.
CLRD controls routing, ENA reference handling, document generation, and audit evidence from one structured workflow before submission.
The submission pathway is resolved from the job data, reducing reliance on memory, habit, or manual route selection.
ENA reference data is applied from the selected equipment, removing a repeated manual lookup step from the submission process.
Forms, SLD, declarations, and submission records are produced from the same structured job record and retained as part of the audit trail.
No judgement calls. No variation between engineers. The same input produces the same correct output, every time. Compliance doesn't depend on who ran the job.
Every routing decision is traceable. You can show exactly why a G99 was filed rather than a G98 — down to the threshold values that triggered the determination.
Documents are version-stamped and locked at generation. The compliance record is complete before the installer leaves site — not assembled later from memory.
CLRD translates direct UK solar installation experience into structured compliance infrastructure — shaped by the operational pressure behind DNO submissions, ENA checks, document control, and the cost of rework.
Currently available through a controlled UK pilot for MCS-accredited installers before full release.
Open to MCS-accredited UK solar installers who want to reduce DNO admin time, rework, and submission friction.