Feature Release update – September 2025

What are the latest NFWV features?

Spring’s sprung and over winter we’ve been huddled down working on new FWV features and enhancing old ones.

New Reporting Panel, including the Transport Disruption Assessment Report

New Forward Works Viewer dashboard layout and create report button

If you click on your Dashboard you’ll notice it’s been rejigged – there’s a new ‘create report’ button, and a section for saved reports. We’re working on users being able to run different reports from this section – for example you’ll soon be able to run a report of all projects published in the FWV for your organisation. For now though, the Transport Disruption Assessment report lives here. Primarily aimed at users who work in the network coordination space, it enables you to search for projects by address or area and generate a list of projects which intersect with the specified Transport Disruption layers. Developed in conjunction with Auckland Transport, the Works Coordination team at AT will be using this report to help analyse the risk of projects on their network, and we envisage it being useful to anyone in the works coordination/network management space beyond the Auckland region when we have more datasets loaded.  

The report has the same functionality as a watchlist – it’ll self-populate with projects that are published to the FWV within the boundary/address that you’ve set in the report criteria. You can mark projects as ‘read’ and ‘unread’ in the report, and soon, you’ll be able to turn on email notifications for new projects in the report.  To make the report function as a watchlist, you’ll need to save the report – then it’ll be added to your ‘My Saved Reports’ section of the Dashboard.

Over time this report will be improved to include additional datasets – so you’ll be able to run a report on all projects intersecting with specific layers of your choosing, rather than a pre-set group.

New transport disruption assessment report panel

Location search improvements

New search improvements - a pin when you search by address, and a boundary when you search by area, on the map

We’ve introduced a pin/boundary for when you are performing a location based search.  If you use project search and search by an address, you’ll get a pin at the address location surrounded by a 250m perimeter.  If you search by an area (like a suburb or city), the area will be highlighted in a pink outline, to make it easier to see the boundary that you’re searching in. This also works for the map location search.  

Changes to transport impacts

We have changed the layout of transport impacts slightly – the live lane category has now changed to ‘carriageway’ and you no longer need to tick a box for the impacts to appear.

Changes to the traffic impacts layout

Improved project ingest

The automated project data ingest has been improved. You can read more about the new ingest process here – but essentially now we are able to remove projects from the FWV if they’re not included in your dataset (if they’ve been included in your dataset previously).

Improved project creation workflow

We have improved the project creation workflow and re-labelled the ‘next’ and ‘back’ buttons to reflect the next possible action. We have also added a ‘step 1 of x’ counter at the top of the workflow so you know which section you’re in.

Changes to the project creation workflow and better navigation between panels

Coming Soon

Improvements to the TDA

We will shortly be loading in bus route and bus stop data for the whole country, which means that everyone will be able to see if their project intersects with a bus route or a bus stop, no matter where you’re based.

As part of this work, we’ll also show which bus stop or bus route(s) your project is clashing with.

Improved Stage workflow

We have noticed that more and more users are creating projects with stages, but the workflow is a bit cumbersome so we’ve made some improvements. Now when you create a multistage project, once you’ve clicked save after project creation, the project will open up on the stage page – giving you confirmation that the first stage has created, and making it easier to add subsequent stages.

We will also be changing the way stages are displayed on the stage tab.  Stages which have passed their end date will turn grey and move to the bottom of the page, whilst stages which remain in progress and planned will remain white and at the top of the list.  

‘First published’ date field

We’ve had a few requests for this so we’re pleased to say we’re introducing it – now you’ll be able to see the date that a project was first published to the Forward Works Viewer, as well as when it was last updated. As we have only introduced the history module recently, there will be projects which we aren’t able to give a publish date on, but any projects since 17th July onwards will have a ‘first published’ date on them.  Over time we will look to improve this by including a ‘last edited’ and a ‘last published’ date field so that users can be more confident in the data quality.