Compliance infrastructure for UK solar, battery, EV charge point and heat pump installers: definitive G98/G99/G100 documentation, generated and submitted with zero repeat data entry.
UK renewable electrical connections are governed by definitive legal documentation — around 700 pages of complex technical specification (ENA EREC G98, G99 and G100, the EVCP & HP Connections Form and the Standard Application Form). CLRD ensures complete compliance with it, while giving you the most efficient, friendly interface to comply confidently — from full-lifecycle data intake to automated DNO submission.
Purpose-built for accurate, convenient entry:
Yes — routing is always-correct and instant, in accordance with the regulatory documentation, with full auditability. You don’t decide which forms apply; CLRD does, deterministically. The full catalogue, by procedure:
CLRD produces the complete documents and submits them automatically to all DNOs and nearly all IDNOs — both pre-install applications and post-install notifications, with commissioning forms and documentation.
Every job moves through a fixed sequence of states — each step is validated, nothing can be skipped, and the full history is kept on the job:
If validation fails, the job is blocked with the exact corrective action shown — and a DNO rejection or cancellation is recorded as its own terminal state, ready to duplicate into a corrected resubmission.
Complete DNO paperwork, filled out for you — ready to review, then submitted automatically:
Domestic and small-commercial PV solar (with or without attached storage), battery-only installations, and — with or without generation on site — EV charge points, V2G chargers and heat pumps.
Yes — first-class support. EV charge points and heat pumps are picked from the imported ENA charge-point and heat-pump registers, and any job that includes one produces the official ENA EVCP & HP Connections Form alongside (or, for load-only jobs, instead of) the G98/G99 forms — deciding connect-and-notify versus apply-before-install by the form’s own criteria.
A V2G charger is handled as electricity storage on the generation side, routing on its export capacity like any battery.
The Premises Maximum Demand asked for in Supply Details is the highest current the whole property draws at once including the new equipment — count battery and V2G charging too (they draw from the grid), and don’t deduct an import/load-limiting device (declare the scheme instead, and CLRD states the limited figure wherever a form wants it). The ENA EVCP & HP Connections Form weighs it against the cut-out fuse rating — and, for an EV charge point with no load limiter, against 60 A per phase — to decide connect-and-notify versus apply-before-install. There are three accepted ways to assess it:
In practice installers mix them: measure the existing baseline where a smart meter exists, calculate where it doesn’t, and always add the proposed equipment at rating. Enter the result in amps — or, on a CT-metered premises, in kVA totalled across the phases.
For the full method — the diversity allowances, the smart-meter arithmetic and a worked example — see the step-by-step guide: How to do a load survey.
Full document lifecycle for:
Yes. Mark an existing device Will be decommissioned by this Job and CLRD assesses the installation as it will stand after the works, records the removal on the relevant forms and includes the official decommissioning confirmation — G98 Form D or G99 Form D1 — in the pack, together with the updated single line diagram.
Both mixed jobs (old equipment out, new equipment in — a replacement) and decommissioning-only jobs (removal with nothing new installed) are supported.
The DNO never requires approval before decommissioning — but it does require notification of the decommissioning within 28 days, and CLRD produces and submits exactly that.
Yes. A batch job takes one client and an identical system across several sites and creates a job per premises. Where those premises route G98 and form a Close Geographic Region, CLRD produces the shared pre-install G98 Form A covering every premises, submits it to the DNO from the batch’s own contact address, and holds each premises’ installation until that one application is approved. Each premises then carries its own post-install Form B.
CLRD decides whether Form A is required from the postcodes: premises sharing a postcode sector are a Close Geographic Region and Form A is mandatory. Where they don’t share one, you confirm whether another CGR condition applies (a single LV feeder, within 500 m, or DNO-confirmed) — if none does, the premises are notified separately with Form B instead. Beyond the form’s ten printed rows the pack adds a Premises Schedule listing every premises.
No.
Yes — both. Export and import limitation schemes get full-lifecycle G100 support: the official Form A application and Form C commissioning enclosure, for inverter-integrated schemes or stand-alone ENA-registered limiter devices, carried across the forms and the SLD.
All ~7,000 ENA-registered Fully Type Tested single- and three-phase inverters. Single-phase inverters on a single-phase supply; on a three-phase supply, single- and three-phase devices mix freely, with generation and demand totalled per line.
Bespoke / non-FTT inverters aren’t supported.
Up to 15 devices per installation — up to 5 proposed (new) and up to 10 existing on site, mixing solar inverters, batteries, V2G chargers and EV charge-point / heat-pump load devices (load devices don’t count against the generation limits). Where a device list outgrows an ENA form’s printed table, the pack automatically includes a Device Schedule with the complete list.
CLRD generates a configurable SLD and can regenerate it for minor install-time changes (panel configuration, isolators). It handles imbalanced inverters and string arrangements, and you can optionally upload your own SLD instead.
Document packs include a Letter of Authority and collect the customer’s signature whichever way suits — signed in-app on your device, uploaded as an image, or by sending the customer an email or shareable link (e.g. by WhatsApp) so they can sign it themselves. The installer signature is captured in-app or by upload.
The post-install commissioning declaration is signed by whoever actually commissioned the installation — you, a teammate sent their own signing link, or an external commissioner signing under their own company and role.
CLRD supports installer and non-installer commissioning — including 2nd-party team members and 3rd-party external commissioners. Whoever commissioned the installation is recorded and signs the commissioning declaration: record yourself, send a teammate their own signing link, or send an external / subcontracted commissioner a link to sign under their own company and role. Each declaration prints that commissioner’s name, role and company, and a Commissioning Requests inbox keeps a designated engineer from missing a request.
Yes — the CLRD API (v1; the Volume Operations and Enterprise plans) lets your CRM or own tooling manage clients, sites and full-lifecycle compliance jobs, upload and download document packs, read and reply to the DNO message thread, and receive signed webhooks as jobs progress. Records created through the API live in CLRD just like ones created in the app — the full lifecycle on every record, not a one-shot “data in, PDF out” call.
The API is for your own company’s benefit — your team, and people building on your behalf, through your own software or third-party tools connected to your account. Reselling API access, or building CLRD into a commercial software product sold to its own customers, requires our prior approval — get in touch about a partner agreement before you integrate.
See the API documentation for the full reference.
Yes — every CLRD account includes CSV import and export, no API or plan requirement. Bring your client and site book in from any spreadsheet or CRM export (each row is validated like the normal forms, and skipped rows are reported by line number), and export it back out any time as plain CSV files that round-trip through import — your data is never locked in. The Jobs page adds a reporting export: one row per job with its status, G98/G99 routing, client and site, and system totals.
See the CSV documentation for the format and column reference.
Ready to see it on your own jobs?