Payaca now shows the DNO's own reasons on a 'works required' connection application, so installers know whether they're waiting on paperwork or a network upgrade.
Jamie Duncan
Two statuses on a connection application look similar and mean completely different things. "Further information required" is a paperwork problem: the DNO wants a detail you already have, and a quick response clears it. "DNO works required" is a network problem: the DNO has decided their equipment needs upgrading before your system can connect, and there is nothing you can email your way out of.
Mixing the two up costs installers real time. A customer told "the DNO needs more information" expects an update within days. A customer who actually needs to hear "the network on your street needs reinforcing" is due a very different conversation, and the earlier that conversation happens, the less it costs you in goodwill.
Every G98 or G99 application you submit through Payaca goes to your Distribution Network Operator through ENA Connect, and comes back with a status that tells you where it sits in the DNO's process. Most of those statuses describe an administrative step: awaiting assessment, under assessment, approved. "DNO works required" is different. It means the DNO has looked at your application and decided their own infrastructure, not your paperwork, is the blocker. The local substation or feeder does not currently have capacity for what you are asking to connect, and something on their side has to change before it will.
That is a fundamentally different kind of wait. A "Further information required" status usually clears in the time it takes you to reply with the missing detail. Network reinforcement is physical work on infrastructure the DNO owns and schedules on their own timeline, often queued behind other reinforcement projects in the same area. It is not something a quick phone call speeds up.
Until recently, a "works required" status told you that something was blocking the connection without telling you what. You were left calling the DNO to find out, or waiting for the next status change and hoping it explained itself.
Payaca now stores and displays the DNO's own stated reasons for a "works required" status directly on the connection application page. When ENA Connect returns this status, whatever the DNO has written about what's needed comes with it, so you can read the actual blocker rather than inferring one. Payaca keeps polling for updates in the background the whole time the application sits in this status, so the moment the DNO moves it on, you see the change without logging into a separate portal to check.
Tracking connection applications at scale?
Payaca tracks every G98 and G99 application in the project it belongs to, from submission through commissioning, with statuses and DNO reasons visible alongside the rest of the job. See how it works.
Read the reasons before you pick up the phone. The DNO's stated reason is often specific enough to answer the customer's question on its own. If it names a capacity constraint on the local network, you already have what you need to explain the delay honestly.
Have the harder conversation early. A customer who signed a proposal expecting a six-week install date needs to hear, as soon as you know it, that this job is now waiting on the DNO's own infrastructure rather than a document review. That is a worse conversation to have than "the paperwork's nearly done," but it is a much worse one to have late.
Automate the alert so nobody has to remember to check. If you already wire up automations on DNO status changes, add a condition for this specific status: email the customer, raise a task for the account manager, or tag the project so every job currently waiting on network works shows up in one filtered view instead of buried across your pipeline.
Don't resubmit. Unlike a rejected application, "works required" is not something a corrected resubmission fixes. The application stays where it is while the DNO progresses the works on their side; resubmitting only adds a duplicate for someone to untangle later.
The jobs that get held up by network capacity are the ones where the gap between "DNO said something" and "installer told the customer something true" matters most. Payaca surfacing the actual reason, in the same place you already track the rest of the job, closes that gap by however many days it used to take to notice and chase.
See how Payaca helps clean tech installers save time and grow their business.
Book a demo
Payaca automations now fire the moment a document is signed, and task templates carry a default assignee and deadline. How UK installers chain signatures, stage moves and pre-assigned tasks into one workflow.
When a full-export G99 connection would be refused or need reinforcement, an export limitation scheme (ENA EREC G100) keeps the job alive. Here is how it works and how to track it across a busy install schedule.
Payaca automations now fire on DNO application status changes and on every change proposal event, not just acceptance. How UK installers wire up the two mid-job waits that stall installs: grid applications and scope changes.