1. Overview
Jumptech’s integration with the Energy Networks Association (ENA) Connect Direct portal allows you to seamlessly submit, track, and manage Distribution Network Operator (DNO) applications for Low Carbon Technologies (LCT), such as EV chargers, solar PV, battery storage, and heat pumps, directly within the platform.
This guide details the complete application lifecycle: how to process new applications, track their progress, handle communications, and modify submitted applications using the integrated amendment workflow.
2. How to Process Applications (Step-by-Step)
Processing a DNO application involves preparing your site data, uploading mandatory hardware documentation, and submitting the request to the ENA Connect Direct portal.
Step 1: Navigate to the DNO Application Tab
For every applicable project, a dedicated DNO Application tab is available.
Open the relevant project and select the DNO Application tab.
The initial status of any new application will always display as Not Sent.
Step 2: Complete the Application Form
While the application is in the Not Sent stage, the form is fully open and editable. Complete all required fields accurately:
Core Identification Data: Input the MPAN, MPRN, Customer Address, and Main Address. Double-check these entries carefully; they serve as unique network identifiers and lock permanently once submitted.
Add Equipment and Site Specs: Use the form configuration controls (Add / Remove / Duplicate / Enter Manually) to accurately declare the specific technologies being installed.
Upload Cutout Images: Click the Cutout image edit pencil to upload and crop necessary photographs of the property’s physical fuse cutout. Ensure these photos are clear and legible to prevent the system from flagging your application for manual engineering reviews.
Step 3: Submit to the DNO
Once the form is thoroughly filled out, click Submit Application. The platform packages your data and transmits it securely to the ENA Connect Direct portal.
Step 4: Track the Application Status
After submission, the platform continuously tracks the lifecycle of the file. You will see the application transition through various real-time statuses, including:
Not Sent: The draft stage before submission.
Submitted: Safely received by the system and awaiting automated or manual validation.
Submitted (Escalated to DNO): Passed directly to a local DNO engineer for complex scenarios, such as looped utility supplies or fuse upgrade requests.
In Review: Actively being assessed by utility administrators.
Approved / Auto-Approved: Granted permission to proceed with the asset installation.
Failed / Rejected: Returned by the network due to data discrepancies, invalid imagery, or grid capacity limits.
3. Managing System Communication & Project Views
Tracking DNO Comments
Reviewer feedback is embedded within the application record to ensure a clear audit history:
Visibility: DNO comments are visible across almost every phase of the lifecycle, except when an application is in a Not Sent status or when an application has been redacted.
Functionality: Historical comments are strictly read-only. The availability of the comment input box is automatically controlled by the system based on the application's current processing state.
Secure Project Switching
When navigating between separate installations in Jumptech, switching projects triggers a clean data load accompanied by a loading spinner on the DNO tab. This ensures you always view the correct, isolated data for the active project, eliminating any latency risks or cached data leaks from previously viewed records. The application data remains completely synchronised with the DNO network.
4. Modifying Existing Submissions (The Amendment Process)
If the DNO returns, rejects, or asks for changes to your application, you can edit it directly. Instead of cluttering your dashboard with confusing duplicate copies, you make your updates right on the original submission. This keeps your entire project history neat, tidy, and all in one place.
The Default Read-Only State
To prevent accidental changes to submitted records, any application requiring changes is Read-Only by default. Form fields, configuration actions (Add / Remove / Duplicate / Enter Manually), and standard submission controls remain hidden until an explicit amendment session is initiated.
Step-by-Step Amendment Workflow
[ Eligible Application State ] ➔ Click "Amend" ➔ Form Unlocks ➔ Modify Permitted Fields ➔ Click "Submit Amendment"
Step 1: Verify Amendment Eligibility
The system automatically evaluates whether an application can be updated. An Amend button will appear on the application tab only if the DNO has flagged that specific submission as amendable, and the application sits in one of the following Connect Direct statuses:
Auto-Approvedor(Re) Auto-ApprovedDNO ApprovedorDNO Approved with LimitFailed,Failed - Too Large, orFailed - Invalid Cut-Out ImageImage Scan FailedFurther Information RequiredCommissioning Submitted
Step 2: Open the Session
Click Amend. An informational banner will immediately display at the top of your screen:
"You are amending a submitted application. Click Submit Amendment to send your changes to the DNO."
This action unlocks the editable sections of the form and reveals the Cutout image edit pencil.
Step 3: Modify Allowed Fields
Correct the elements called out by the DNO reviewers. Take note of the platform's structural constraints:
| Editable Amendment Fields | Strictly Locked Fields (Always Read-Only) |
|---|---|
• Basic Technical Specifications • Core Application Details • Cutout Infrastructure Images | • Core IDs: MPAN & MPRN • Locations: Customer & Main Address • Post-Install: Commissioning Details & Supporting Files |
Step 4: Finalise Your Changes
Two dedicated controls govern the end of your editing session:
Submit Amendment: Opens a confirmation modal. Once confirmed, the updated package goes back to the DNO, the application status reverts to Submitted while under review, and an audit log reading "DNO Application Amended" is written to the project timeline.
Cancel Amendment: Discards all session modifications instantly, returning the application to its locked, read-only state.
⚠️ Important Tab Behaviour: Navigating away from the DNO tab to another area of the platform while actively editing will silently cancel your amendment. Always submit or manually cancel your session before changing tabs.
5. Advanced Scenarios & Data Exceptions
Handling Amendment Failures
If the DNO rejects your submitted corrections, a notification banner appears at the top of the tab:
"The last amendment attempt failed: [Category supplied by DNO]"
This error layout is purely informational. Review the reason provided; you can click Amend again to fix the issue, or click Start New Application to wipe the slate clean.
Non-Amendable Applications
If a rejected application does not meet the DNO’s criteria for adjustments, the Amend option will remain hidden. In these circumstances, your path forward is to click Start New Application (which aligns the button label with the internal submission modal copy) to establish an entirely fresh profile.
Redacted and Archived Applications (GDPR Requirements)
When an application's personal data is scrubbed or removed by the DNO, typically due to GDPR guidelines or corporate retention limits, the system updates dynamically:
A notification banner states: "The DNO has archived this application. No further amendments can be made."
The Amend tool is permanently disabled, the form is locked, and automatic system polling ceases.
Allowed Paths: Historical DNO Comments remain visible for review, and you can click Start New Application to process a clean, replacement file.
6. General Support & Troubleshooting FAQ
Q: Why are the form options and input boxes completely hidden on my rejected application?
A: Submitted and rejected applications stay read-only by default to preserve historical records. To make updates, look for and click the Amend button to enter editing mode, or select Start New Application to begin a fresh submission.
Q: Why can't I find the "Amend" button on a rejected application?
A: The DNO evaluates applications individually to verify if they can be modified. If the DNO passes a non-amendable flag or if the application status falls outside permitted guidelines, the button is hidden. You must click Start New Application instead.
Q: What happened to the traditional "Resubmit" option?
A: The traditional "Resubmit" loop has been replaced entirely by the integrated Amend ➔ Submit Amendment workflow to ensure changes tie directly back to the original application ID in the DNO database without generating duplicate clones. This keeps the data fully optimised.
Q: I am inside active Amendment mode, but the MPAN, MPRN, and address fields are still greyed out. Why?
A: These fields define the core structural location of the utility link. The DNO does not permit identity corrections on an existing folder. If a typo occurred on an ID or address during the original submission, cancel your amendment session and click Start New Application.
Q: Why did the DNO comments stop working after an application was archived?
A: Comments remain available on almost all application states except for files that were left as Not Sent prior to archiving or data scrubbing.
Q: What does the "Archived by DNO" banner mean?
A: This indicates that the DNO has scrubbed the data payload, usually due to GDPR or corporate data expiration rules. Because the record is archived, amendments are closed. Use Start New Application to establish a fresh submission link.
Q: When I switch projects, I occasionally see data details from the previous project for a split second. Is this normal?
A: The system deploys a structural loading spinner to overwrite local browser cache memory during project changes. If extreme local connection latency causes old data elements to briefly ghost on your screen, simply refresh your web browser page to force a clean visual sync.
Tracking Existing Applications
You will see a filter on the ‘Projects’ page called "DNO Application Status". This allows you to identify the status of each request. To use this:
- Select the DNO Application Status" filter dropdown
- Select one of the statuses to filter e.g. Not Sent or Submitted
Video - How to
Problem solving
| Issue | Cause |
| I cannot submit the DNO application? | The system has built in logic to validate the form contents before submission. For example, if you had set the property supply as single phase and set the device preference as 3 phase, one of these answers cannot be correct,, so the system will stop the submission until this has been rectified! |
| What are the statuses? | We currently have the following:
|
| What if the device is not on the list? | We have allowed a manual device addition. If you need to do this click on ‘Enter Device Manually’ and fill in the information requested |
| Can we make the DNO action only show at a certain stage in the flow? | We would advise to have this active from the beginning of the flow but this can be configured if required |
| How do I submit a Notification only? | Since the Connect Direct portal was launched, the ENA are no longer accepting notifications. An application per project is required. |
| Can I re-submit an application? | Yes, if your application is either in the Submitted or Rejected status. |
| If I need to speak to the ENA is there a reference number? | Yes, it will be shown in the application tab. Use this with any direct communications and it will speed up the process. |
Comments
0 comments
Article is closed for comments.