Helping councils, surveyors and developers record better road name information.
From 3 August 2026, responsible naming authorities will need to provide road name origin information in SPEAR when registering new road names in plans of subdivision.
This information helps explain where a road name came from, why it was chosen, and how it connects to the local area.
Recording this information will help:
Terminology note
Different systems use different terms. SPEAR uses 'responsible authority', while the naming rules use 'naming authority'.
On this page and in the downloadable resources, 'responsible naming authority' means the authorised SPEAR user responsible for submitting plans of subdivision and recording road name origin information.
SPEAR is Victoria’s online system for processing planning permits and subdivision applications.
When a new road is created through a plan of subdivision, responsible naming authorities will be prompted to enter road name origin information in SPEAR.
This includes:
The technical change will be made in SPEAR after close of business on Friday 31 July 2026. The requirement will apply from 3 August 2026.
Road names are part of Victoria’s cultural record. They can recognise local history, Aboriginal language and culture, native plants and animals, community service, local events, and people who have contributed to a place.
Recording the origin of road names helps make sure this information is not lost over time.
It also helps naming authorities, surveyors and developers show that new road names comply with the naming rules.
The responsible naming authority enters the information into SPEAR.
In most cases, the information should be collected before the road name reaches the SPEAR street address allocation stage.
Depending on local processes, the information may be provided by:
Responsible naming authorities should have a process in place to collect road name origin information from developers or surveyors before new road names are entered in SPEAR.
Templates are available on this page to help collect the information early.
For each new road name, users need to provide information about the origin of the name.
The theme explains the broad category of the name.
Examples include:
Where you’re using a theme for multiple roads, the theme needs a link to place where the subdivision is being built.
In these cases, each road name origin statement will need:
If the road is named after a person, more information is required.
This helps identify commemorative names and supports better reporting on who is being recognised in place naming.
If the road is named after a person, SPEAR will ask for gender information where known.
This supports reporting on gender equality in commemorative naming.
The history should briefly explain:
The history does not need to be long. A short, clear explanation is usually enough.
A good road name history answers three simple questions:
What does the name refer to?
Is it a person, plant, animal, local feature, event, Aboriginal language word, theme or something else?
Why was this name chosen?
What makes the name meaningful, appropriate or significant?
How does the name connect to the place?
What is the local connection?
A good history should be:
It should avoid vague statements such as ‘local history’, ‘native plant’ or ‘named by developer’ without further explanation.
Avoid subjective explanations about the feeling a name is intended to evoke, unless the origin and local connection are clearly explained.
The examples below show the difference between incomplete, non-compliant and compliant road name histories.
These are examples only. Always make sure the road name complies with the naming rules and any local council requirements.
| Incomplete | Compliant |
|---|---|
Named after Mary Smith. or Named after Mary Smith, a former local resident. | Named after Mary Smith, a long-term local resident who volunteered with the town’s maternal health service for more than 30 years. Mary lived near the subdivision area and is remembered for her contribution to community health and local families. |
Named after previous landowner. or Named after John Brown, who previously owned land in the area. | Named after John Brown, who farmed this land from 1948 to 1982 and contributed to the establishment of the local agricultural society. The road is located within the former Brown family property. |
War veteran. or Named after Thomas Lee, a local World War II veteran. | Named after Thomas Lee, a local resident who served in World War II and later worked with the local RSL to support returned service members. Thomas lived in the area for more than 40 years. |
Incomplete | Compliant |
|---|---|
Aboriginal word. or Aboriginal word meaning water. | The name comes from an Aboriginal language word meaning water. It was selected in consultation with the relevant Traditional Owner group because of the road’s location near a local waterway. |
Traditional name. or Named using an Aboriginal language word. | The name uses an Aboriginal language word provided through the appropriate Traditional Owner engagement process. The word relates to local plants found in the area and supports recognition of Aboriginal language and culture. |
First Nations theme. or Aboriginal name connected to Country. | The name was selected following advice from the relevant Traditional Owner group. It reflects a place-based language theme connected to the local landscape. |
Note: Aboriginal language names must be developed through the appropriate Traditional Owner and Registered Aboriginal Party engagement and approval processes.
Incomplete | Compliant |
|---|---|
Native plant theme. or Named after banksia plants found in Victoria. | Named after the Silver Banksia, a native plant recorded in nearby reserves. The name forms part of a local flora theme used throughout the subdivision. |
Flower name. or Named after wattles. | Named after Golden Wattle, a native plant common in the surrounding landscape and used as part of the estate’s native flora naming theme. |
Tree theme. or Named after eucalyptus trees. | Named after River Red Gum, a tree species found along local waterways and used as part of a road naming theme reflecting the area’s natural environment. |
Incomplete | Compliant |
|---|---|
Bird name. or Named after a native bird. | Named after the Eastern Rosella, a native bird commonly observed in the local area. The name forms part of a native bird theme for the subdivision. |
Animal theme. or Named after wallabies. | Named after the Swamp Wallaby, a native animal known to occur in nearby bushland reserves. The theme reflects local fauna found around the development area. |
Local wildlife. or Named after frogs in the area. | Named after the Growling Grass Frog, a species associated with wetland environments in the region. The name supports the subdivision’s wetland and local fauna theme. |
Avoid road name histories that are too vague.
| Avoid | Why it is not enough |
|---|---|
Named after a local person. | It does not identify the person or explain their local contribution. |
Native plant. | It does not identify the plant or explain the local connection. |
Developer theme. | It does not explain why the theme is appropriate for the area. |
Historical name. | It does not say what the history is. |
Named after family member. | Personal preference is not enough. The name must comply with the naming rules and have a connection to place. |
Other. | 'Other' should only be used when no other theme applies. The history still needs to explain the origin of the name. |
Our templates can help councils, surveyors and developers collect road name origin information before it is entered into SPEAR.
Use this template for all new road names.
For a complete list of accepted road types, check Appendix A of the naming rules.
| Field | Information to provide |
|---|---|
Proposed road name | |
Road type | Street, Road, Lane, Court, Avenue, etc. |
Subdivision or estate name | |
Responsible naming authority | |
Developer or applicant | |
Surveyor | |
Road name theme | Commemorative, Aboriginal, flora, fauna, Anzac, other |
Is the road named after a person? | Yes / No |
If yes, who is the person? | |
Is the person living? | Yes / No / Unknown |
Gender, if known | Woman / Man / Self-described / Multiple people / Unknown |
History behind the name | |
Connection to the local area | |
Source of information | Historical society, council record, Traditional Owner advice, local history source, community nomination etc. |
Has the name been checked in VICNAMES? | Yes / No |
Has the road type been checked? | Yes / No |
Notes |
Use this structure if you are not sure where to start.
Named after [person, place, plant, animal, event or theme], which/who [brief explanation]. The connection to the local area is [local connection].
'Named after Mary Smith, a long-term local resident who volunteered with the town’s maternal health service for more than 30 years. The road is located near the former community health centre where Mary volunteered.'
Use this when a road is named after a person, group or event.
| Question | Response |
|---|---|
Who or what is being commemorated? | |
What did they contribute? | |
What is their connection to the local area? | |
Is the person living? | |
If the person is living, have you sought an exemption from the Registrar of Geographic Names? Note: If the Registrar’s decision is not to grant an exemption, the name cannot be used. | |
Have you sought or attained family consent? | |
What sources support this information? | |
Suggested SPEAR history text |
Named after [full name], who [contribution or significance]. Their connection to the local area is [local connection].
Use this when proposing an Aboriginal language name.
| Question | Response |
|---|---|
What is the proposed name? | |
What language does it come from? | |
What does it mean? | |
Which Traditional Owner group has been consulted? | |
Which Registered Aboriginal Party (RAP) has been consulted? | |
What advice or approval has been received? By whom? | |
What is the connection to place? | |
Suggested SPEAR history text |
The name comes from [language] and means [meaning]. It was selected following consultation with [Traditional Owner group] and [Registered Aboriginal Party] because [connection to place].
Use this when a road is named after a plant or animal.
| Question | Response |
|---|---|
What species is being recognised? | |
Is it found locally? | |
What is the local connection? | |
Is this part of a broader naming theme? | |
Suggested SPEAR history text |
Named after [species], a native [plant/animal] found in [local area or nearby feature]. The name forms part of a [flora/fauna] theme reflecting the local environment.
Use this when a road is part of a broader theme.
| Question | Response |
|---|---|
What is the theme? | |
Why was this theme chosen? | |
How does the theme connect to the local area? | |
Does each road name still have its own explanation? | |
Suggested SPEAR history text |
This road forms part of a [theme] naming theme. The theme was selected because [connection to local area].
A quick overview of the new SPEAR road name origin requirements, who they apply to and why the information is being collected.
Best for: councils, surveyors, developers and anyone needing a short summary.
Step-by-step guidance for responsible naming authorities on when and how to enter road name origin information in SPEAR.
Best for: council officers and responsible naming authority users entering information in SPEAR.
You can view a complete process map on Process Manager if you prefer a visual version.
A simple form for collecting road name origin information before it is entered in SPEAR.
Best for: single road names or small subdivisions.
A spreadsheet for collecting road name origin information for multiple roads.
Best for: growth areas, staged subdivisions or developments with many new road names.
A template to help councils create or improve a local name bank.
Best for: responsible naming authorities, growth councils and councils working with developers on future subdivisions.
| Put Her Name On It | Use Put Her Name On It’s name bank starter toolkit for practical guidance on creating a diverse and representative name bank. It includes research sources, nomination processes and community engagement ideas. |
|---|---|
| Finding Her Research Hub | If you need specialist historical research support, Finding Her Research Hub services can help identify suitable commemorative candidates and develop evidence-based name banks that reflect local history and diverse community contributions. |
For questions about SPEAR access, system issues or technical support, contact the SPEAR Service Desk.
Phone: (03) 9194 0612
Email: spear.info@transport.vic.gov.au
For questions about naming rules, road name origins, commemorative names, Aboriginal language names or road naming requirements, contact Geographic Names Victoria.
Phone: (03) 8572 7991
Email: geo.names@transport.vic.gov.au
Page last updated: 30/07/26