Feature · DNO aware routing

The fastest route for the job. Never the engineer's queue.

CLRD knows every DNO's criteria. It sends a job through the portal only when it will pass, so it isn't stuck in a second queue waiting for an engineer.

First job free. No card to start.

What it is

The quickest route to the DNO, for every job

CLRD knows how every DNO takes applications: its own criteria, its own inboxes, its own fast tracks, and whether a job can go through the portal. From that it gives every job the quickest route it qualifies for, and sends it there.

Why it matters

The portal approves automatically only when every check passes. A job that fails one isn't turned away. It's passed to a DNO engineer and waits in a second queue behind everyone else's, and a quick approval becomes a long wait. CLRD runs those checks first. A job that will pass goes through the portal, one that won't goes straight to the connections team, so it starts in the right queue and never sits in the wrong one.

For jobs that clear first time, at every DNO.

  • Each DNO's own requirements held per operator: inboxes by standard, procedure and phase, their own forms, and their notes on the job.
  • The DNO's portal used only where the job meets every check it runs, on UK Power Networks today.
  • Size and phase limits checked before anything is sent, so a job is never filed where it will fail.
  • Operator fast tracks built for: SSEN's loop impedance form, UK Power Networks' loop impedance statement, SPEN's site boundary map.
  • Networks that take applications only through their own portal are flagged, with the pack ready to send there.
  • Every reply lands on the job thread, whichever way the application went.
Send to DNO
CLRD confirming submission with the 'Send these documents to the DNO' dialogCLRD confirming submission with the 'Send these documents to the DNO' dialogEnlarge

In practice

What changes on the next job.

No second queue

A job that wouldn't clear the portal's checks goes straight to the connections team, not to the back of an engineer's queue.

The quickest route it qualifies for

The fastest procedure the job meets, and the DNO's own fast track where it offers one.

One button, whichever DNO

Send to DNO works the same way everywhere. CLRD works out where it goes.

Before & after

With CLRD vs. without.

Workflow
CLRD
Manual / Spreadsheet
Portal or inbox
Decided from the job, before it's sent
Try the portal and see
Each DNO's own requirements
Held per operator, applied automatically
Remembered, or dug out of the DNO's guidance
Operator fast tracks
Evidence built where the DNO offers one
Known only if you've used one there
A job that fails an automatic check
Never sent to the portal, filed with the connections team
Waits in an engineer's queue

See dno aware routing on your own jobs.

Run one of your own installs through it free. Or book twenty minutes and we'll do it with you.

First job free. No card to start.