Retrofit programmes
Retrofit at scale means
DNO applications at scale.
A programme fitting heat pumps, solar and batteries across hundreds of homes creates a DNO application for every property. CLRD handles that layer, so connection paperwork stops setting the pace of the retrofit.
The problem at programme scale
The connection admin becomes the bottleneck.
Retrofit programmes run to deadlines and funding conditions. Every property still needs its own DNO application, and a home getting a heat pump, solar and a battery has historically meant separate paperwork for each technology, filed one property at a time.
Multiply that across a scheme of hundreds of homes, delivered by several contractors, and the connection paperwork stops being admin and starts being the thing that holds up delivery.
How CLRD fits
Built for the volume a programme actually generates.
The same platform a sole trader uses, running at the scale a retrofit scheme needs.
01
One batch, a whole street
Create one batch with a shared system configuration and a list of premises. CLRD fans it out into a standalone job per property, each with its own site, MPAN and documents, and produces the shared G98 Form A where the properties form one close geographic region.
02
Every technology on one submission
A property getting a heat pump, solar and a battery is one job, not three. CLRD works out the load and the generation, routes it against the ENA thresholds and produces the right forms, including the ENA EVCP and HP Connections Form where the job needs it.
03
The same result whoever files it
Programmes run through subcontractors and multiple installers. Routing and documents are derived from the job data and the published rules, so a submission filed by one contractor matches one filed by another.
04
Evidence at programme level
Every action attributable to a named user and account, under the regulation version in force, with checksums on every exported pack. When the scheme is audited, the DNO side is already provable.
05
An API into your own systems
Push jobs straight from the scheme management or job system you already run, and read status back out. If your programme runs on its own platform, CLRD sits behind it rather than beside it, and nobody re-keys a property list twice.
06
CSV import, or embedded in your platform
Bring a property list in from a spreadsheet or a housing stock export, with a preview and analysis of the file before a single record is created. For scheme operators and portal builders, embedded and white labelled options are scoped case by case as part of an Enterprise agreement.
Where CLRD sits
Alongside your delivery, not in front of it.
Your team handles the assessment, the design and the coordination. CLRD picks up at the point a measure needs a connection application, routes it, produces the pack, submits it and holds the evidence. It runs behind the programme rather than asking anyone to change how they already work.
Tell us the shape of your programme.
Bring the volume, the technologies and the contractor structure, and we'll map how the DNO side would run.