From job data to routed DNO paperwork, SLD, and submission record.

CLRD captures the system details once, resolves the correct DNO route, and produces the documents required for submission — formatted, versioned, and audit-defensible.

INPUT

System details captured

Enter the job details once — site, system, equipment, export limit, and installer information. CLRD handles the ENA reference data automatically.

Site details
System specification
Export limit
ROUTING

Submission pathway resolved

CLRD resolves the submission pathway across G98, G99, Fast Track, and G100-supported submissions, applying the correct ENA reference data from the selected equipment.

G98 / G99 / Fast Track
G100 where required
ENA reference applied
OUTPUT

DNO-ready documents produced

CLRD produces the DNO-ready document pack — forms, SLD, declarations, and submission record — versioned, structured, and ready to send.

Versioned document pack
SLD included
Audit trail captured
Four steps to create a job.

Job creation is a short, guided sequence. You enter the data once — CLRD applies the reference data, resolves the route, and builds the documents from there.

Step 01

Client

Choose the client the job belongs to, or add a new one. Everything filed under the job ties back to them.

Existing or new
Step 02

Site

Enter the installation site — address, MPAN, and supply details. This anchors the DNO and network references.

Address · MPAN
Step 03

System details

Specify the system — inverter, panels, storage, and export limit. CLRD pulls the matching ENA reference data automatically.

Equipment · export limit
Step 04

Confirm

Review the resolved submission route and create the job. From there CLRD drives the full lifecycle.

Route resolved
CLRD Job Lifecycle

Once created, a job moves through a controlled set of states — in two phases. Pre-install secures DNO approval before any work begins; post-install captures the as-built record after the system is fitted.

Pre-install

Inputs are locked and the route is set, the pre-install pack is generated, and the application is submitted to the DNO for approval — before anyone is on site.

Post-install

On the install date the as-built details are confirmed, the post-install pack is generated and submitted, and the job is completed against the DNO record.

CLRD job lifecycle diagram: a job is created from client, site and system details, validated pre-install, its document pack generated and submitted to the DNO; once approved and installed, the post-install pack is generated, submitted, and the job completes. Exception states cover blocked, cancelled, and failed jobs.
The full CLRD job lifecycle — from creation through pre-install approval and post-install completion, including exception states.
What CLRD produces.

Every job produces a complete, submission-ready document pack — built from the same structured record, so the paperwork and the audit trail never drift apart.

Routed DNO application

The correct G98, G99, Fast Track, or G100 form for the resolved route, pre-filled from the job record.

Single Line Diagram (SLD)

A schematic generated from the system you specified — no separate drawing step.

Declarations & supporting documents

Installer declarations and the supporting paperwork the submission needs, compiled into one pack.

Versioned submission record

Every document version-stamped and locked at generation, retained as a defensible audit trail.

See it on your own jobs.

Book a walkthrough, or review the plans built around your monthly job volume.