This guide explains how a Network Update Request can be closed and recorded as complete without being published as a normal approval. It outlines common closure reasons and what happens to the NUR after closure. Use this guide when a NUR should not proceed, has been superseded, or needs to be withdrawn and archived.

NHVR Portal account with appropriate permission to close Network Update Requests.

Access to the relevant NUR in Network Management.

Date of last review: [25 02 2026]

1. Log in to NHVR Go.

2. Open Access Management then Vehicle Networks and locate the network with the NUR you wish to close.

3. Select the relevant Network Update Request from the left panel.

4. Review the history and workflow overview to confirm that closing the NUR is appropriate (for example it has been superseded or created in error).

5. Open the workflow tools drawer and choose the option to Close or equivalent for the NUR.

6. Select the most appropriate closure reason from the available list, such as:

a) Withdrawn.

b) Duplicate case.

c) Non responsive Road Manager.

d) Other.

7. Add any comments explaining why the request is being closed, then confirm the closure.

8. The NUR will move into a closed or archived state and will remain available for audit and reference.

Use clear comments so future readers understand why the NUR was closed rather than completed.

Closing a NUR does not delete it; it remains part of the audit trail.

If you accidentally close a NUR, follow NHVR internal processes to determine whether it can be re opened or if a new NUR is required.

Consider whether duplication or cloning might be more appropriate if the intent is to move changes to another network.

Follow your organisation’s internal process for when NURs should be closed or withdrawn.

Contact NHVR Access Policy or Network Management support if you are unsure which closure reason to use.