Common questions, answered without a demo.

CLRD is the compliance infrastructure layer for the UK renewable industry. It routes every job to the right DNO process, generates regulator ready packs and SLDs, and records a complete audit trail, so installers, ops teams and asset owners stay compliant by default.

Solo installers shipping their own DNO packs, ops teams managing multi installer pipelines, and enterprise operators (housing associations, asset owners, EPCs, multi branch installers) who need governance and auditability across regions.

No, it complements your workflow rather than replacing it. CLRD owns the compliance layer alongside your CRM or job system, syncing status both ways, with an API for larger operations.

No to both. CLRD is an independent technology company, designed by an MCS certified installer who has worked in the field and built by engineers around the DNO and ENA documentation. We don't install, certify or represent any of them.

All six GB DNO groups, UKPN, NGED, SSEN, NPg, ENWL and SPEN, plus virtually all IDNOs. Northern Ireland is not yet supported. Routing is deterministic per region and per route (G98 or G99, including the Fast Track procedures), with G100 attached wherever export limiting applies.

Yes. The routing engine decides the correct route per job, pulls the right pack template, and generates the SLD and supporting evidence that route expects.

The form is free; being auto approved first time is not. Connect Direct moves your application but doesn't make it correct, and it only auto approves when every check passes, otherwise it escalates to a DNO engineer. That slow path is what CLRD removes: deterministic routing and a complete, correct pack, right first time. We feed Connect Direct, we don't compete with it.

Yes. CLRD generates every application as one standardised pack, produced right first time to remove the human error and inconsistency behind most DNO rejections. Generate it, review it if you want to, then submit straight from the platform, with the pack there to download whenever you need a copy.

DNO responses come back to both the platform and the installer, who is notified, so nothing is missed. The job stays in CLRD with a continuous audit trail, and a revised export limit, for example, can be updated and resubmitted in minutes.

Yes, for National Grid, SSEN, UK Power Networks and Northern Powergrid today. When their approval letter lands on the job's thread, CLRD detects it, says so on the job, and fills in the DNO reference and any export limit the DNO has set. It isn't AI: the reading is coded, so the same letter always reads the same way. You check the details and press Confirm Approved, so nothing is recorded without you, and then one click sends the approval letter to your client. Other operators' approvals are recorded by hand, as before.

The ENA framework (G98, G99, G100) runs to around 700 pages and keeps changing. CLRD keeps routing and reference data tied to the current regulations, so every job is routed against the rules in force and stays defensible at audit.

CLRD produces both stages of the job: the pre install application pack and the post install commissioning pack. Inside: a cover letter, the fully filled out G98, G99 or G100 forms for that stage, a generated single line diagram (SLD), a site boundary plan, a Letter of Authority for the customer to sign, a device schedule where the job needs one, and commissioning forms and documentation. Submit from the platform or download at the press of a button.

Domestic and small commercial installs up to 50 kW: solar PV, battery storage including battery only jobs, EV charge points including V2G, and heat pumps. A job can be generation, load, or a mix of both, and CLRD produces the right forms for each, including the ENA EVCP and HP Connections Form.

CLRD mirrors the ENA generation register, around 9,200 devices, and supports every Fully Type Tested inverter on it, single and three phase. A three phase supply can mix single and three phase devices. Where an inverter's Intrinsic Design Capacity is above its Registered Capacity, CLRD fills the IDC in for you: the ENA register doesn't publish it, so we analysed over 4,000 inverter datasheets and checked every figure by hand. Microinverters are supported as one row with the quantity installed, totalled for routing and printed as one line on the forms. Bespoke or non FTT inverters are not supported for new installs. An existing device stays under the standard it was commissioned to, so a lapsed listing or a FIT era G83 or G59 device can still be recorded on the existing device row. EV chargers and heat pumps, around 3,200 of them, are picked from the ENA registers the same way.

No. CLRD covers domestic and small commercial systems. Above 50 kW three phase (or 17 kW single phase), the DNO requires its full Standard Application Form, which CLRD doesn't generate, so larger systems are not supported.

Yes, and on every route. You describe the client and the system once and list the plots; each one then runs as its own job with its own MPAN, documents and history, routed G98 or G99 on its own merits. Where the plots are close enough together to count as one close geographic region, the DNO wants a single shared G98 Form A approved before anything is installed, and CLRD produces it and holds the batch until the approval lands. Available on Small Team plans and above.

For most installers it is as simple as creating an account, self serve or set up with you during a demo. Larger companies we onboard in person. For enterprise and custom API integrations we handle the API and work alongside your tech team, at the pace you need, complementing your existing workflow rather than disrupting it.

No. CLRD is built to hard block human error, so anyone can use it at any level without training. It takes DNO compliance off your most skilled people, and even an admin with no prior experience can produce standardised packs from day one.

No. CLRD doesn't import old jobs or vouch for packs it didn't produce. From the jobs you run through it, everything sits in one place, explainable and defensible at audit: who did what, under which regulation, tied to the version in force.

CLRD is a multi tier subscription you can cancel anytime, built to scale with you, with bolt on packs of 10 extra submissions for £40 when you need more, and they never expire. Current pricing per tier is listed under Solutions.

Yes — that's Managed Jobs. Hand a job to the CLRD compliance team — paste the site survey, attach what you have — and we complete the paperwork and file it with the DNO in your name. A fixed fee per job (£10 connect and notify, £50 application, £75 mixed technology), with no subscription needed and no job credits used.

Yes, and it is matched to your scale. Smaller installers can run real jobs on a few credits, while a higher volume operator gets a trial sized to their needs, enough to test CLRD properly and clear a backlog. We set one up to fit you.

No. All plans are month to month, so you can cancel anytime, with annual billing around 17% cheaper. National operators with API integration move onto a custom contract.

We take security and data handling seriously. CLRD is not built by AI and does not rely on it: routing, forms and packs come from a deterministic rules engine written and maintained by our engineers, and our lead engineer has 25 years of experience building robust, reliable, enterprise grade software. All data is encrypted in transit and at rest, and protected by strict permission controls, so your team members see only the jobs you have given them access to. Every account supports two factor authentication, you can see and sign out every device signed in to your account, and every job keeps a tamper evident audit record of what happened and when. Your data is backed up continuously to encrypted storage, and it stays yours: export it or delete your account at any time, in accordance with our Privacy Policy. Our systems run on reliable, high uptime infrastructure with seamless upgrades and automatic rollback for safety.

Not for the compliance work. Which forms a job needs, what goes on them and what the DNO receives are decided by a deterministic rules engine, so the same inputs always produce the same pack and nothing is inferred or guessed. We do offer two AI features for convenience, and both are optional. The Dashboard Summary gives a plain language digest of your open jobs, built with your privacy respected. The AI Assistant answers technical questions about CLRD, the ENA forms and the concepts behind them; it cannot see your jobs or your data, and it never touches a document. Reading a DNO's approval letter isn't AI either: it's coded, and reads the same letter the same way every time.

Every meaningful change to a job, who did what, when, and with which inputs and outputs, is recorded and immutably hashed, so the record cannot be altered without trace. A project's full audit trail can be exported as one continuous report.

Your data is held on UK based cloud infrastructure, encrypted in transit and at rest.

You do. CLRD processes it on your behalf in line with UK data protection law and ICO guidance, and you can export it at any time. On a multi user team, the team owner owns the data: an installer who leaves loses access while the job data stays with the team, and ownership can be transferred to another member by the team owner.

Yes. CLRD ships a documented v1 JSON REST API with signed webhooks, included on Volume Operations and Multi Team Operations, and CSV import and export on every plan. Beyond the standard endpoints, bespoke integration work is scoped and built by our engineers around your systems.