What this guide does
This guide explains what standalone networks are and when to use them as internal “sandbox” networks.
This guide shows how to create standalone networks from scratch or by duplicating existing networks.
This guide also explains how standalone networks are edited and how they can later be converted to publicly visible networks.
Prerequisites
NHVR Portal (NHVR Go) account with Road Manager access.
Access to Network Management in NHVR Go.
The network or area of responsibility you want to model in a standalone (non-public) network.
Date of last review
Date of last review: [02 03 2026]
Step-by-step instructions
1. Open the NHVR Portal (NHVR Go) and log in using your Road Manager account.
2. Go to Access Management and open the Network Management tools (Vehicle Networks).
3. To create a standalone network from scratch:
a) From the main menu, choose Standalone Network.
b) Search the list of available standalone networks to check that a suitable one does not already exist.
c) If required, choose the option to create a new standalone network.
d) Enter a name for the new network and confirm. A new standalone network space is created, usually with a blank map.
4. To create a standalone network by duplicating an existing network:
a) Use the filters to find the network you want to duplicate and click the Vehicle Network Name hyperlink to open it.
b) Use the Duplicate function for the network.
c) A new network is created as an exact replica (including roads, conditions, restrictions and infrastructure points) in standalone status and is not visible to operators.
5. After the standalone network is created, open it in Network Management.
6. Use the normal Network Update Request tools to edit the standalone network:
a) Use the automatically created draft Network Update Request (NUR), or create a new NUR for the standalone network.
b) Add, remove or adjust road segments, conditions and infrastructure points as required.
7. For duplicated standalone networks, be aware that when you submit a Network Update Request, the changes are automatically published to that standalone network because it is not yet public facing.
8. When you are ready for the standalone network to be used publicly, work with the NHVR (for example via the Access Policy team) so the standalone network can be associated with the correct access instrument and vehicle configurations and converted to a Pre-Approved Network, Permit Scheme or Gazette network.
Tips and common issues
Standalone networks are not visible to operators and are intended as temporary or internal sandboxes.
Duplicated networks are always created as standalone networks until they are associated with an access instrument and vehicle configurations.
Draft or submitted NURs on the original network are not copied to a duplicated standalone network; you must recreate any required changes.
Use clear naming for standalone networks so your organisation can easily distinguish test or internal networks from public-facing ones.
Where to get help
Check your organisation’s internal process for requesting new or converted networks.
Contact the NHVR Network Management or Access Policy support team for help converting standalone networks to public networks.