Case Studies /

The roadworking management software that keeps Kiwis moving.

HTML/CSS logo Ember logo Leaflet logo Node logo Postgres logo
View of a road construction site from above showing a road cone, sand bags, and the myWorksites logo

MyWorksites aims to realise efficiencies in managing and coordinating roadworks, while also minimising disruption for road users.

The system handles the entire life cycle of roading projects including:

  • Early collaboration: avoiding potential clashes between projects and discovering opportunities to work smarter.
  • Permitting of roadworks under the Utilities Access Act.
  • Processing and acceptance of Traffic Management Plans defined by the Code of Practice for Temporary Traffic Management.
  • Coordination and mitigation of the cumulative impacts of roadworks.
  • Detour route management.
  • Situational awareness of planned events for real time operations.
  • Notifications for affected parties such as public transport operators, parking services, traffic light controllers and emergency services.
  • Public notification of roadworks via an API, informing services such as Google maps and
  • Auditing and quality control of roadworks.
  • Warranty of road repairs.
  • Remote access for system users, allowing on-site updates and real time project information to be communicated.


MyWorksites really began in 2011 in post-quake Christchurch. On a flight from Auckland to Christchurch, Robyn Gardner (then of Christchurch City Council) quite literally sketched out her idea on the back of a napkin.

TMP for Christchurch, as it was then called, was a system designed to process the Traffic Management Plans being submitted as part of the post-quake rebuild effort. The volume of TMPs had increased tenfold, almost overnight, and the existing paper-based systems at Christchurch City Council couldn’t cope as the repair effort got under way.

Additionally, NZTA and CCC needed a way to help the public navigate a city now dominated by daily road changes due roadworks and associated disruption. The key to the original system’s success, was that it made the planned works of every company or organisation more transparent. This led to widespread collaboration in the industry and has been credited as one of the key tools that helped keep Christchurch moving post-quake - but don’t just take our word for it.

Skip forward a few years, and MyWorksites was born in early 2016. Auckland Motorways Alliance partnered with Media Suite to rebuild the tool, with the vision that it would become a nationwide service.

In 2017, Auckland Transport, representing the largest council in the Southern Hemisphere, added the management of its 7500 kilometres of roads to MyWorksites. A permitting and billing system was then added to the application.

In 2018, the country’s second largest council joined the fold. Christchurch City Council transitioned from TMP for Christchurch, and Media Suite added a range of features including planning maps and global permitting.

MyWorksites screenshot shown on a tablet device

Seeing the future

While MyWorksites provides an essential set of tools for everyone working on New Zealand roads, it also serves a higher purpose, providing a real time picture of a city’s roads and public spaces. This data can be used to minimise traffic congestion, plan for events that significantly impact the city’s traffic movement, and allow contractors across company and sector lines to collaborate before they dig.

By sharing information, contractors could work together to reduce spend and minimise disruption. Using MyWorksites, expected roadworks (maintenance, planned works etc) could be scheduled years in advance. A clear picture of future works would assist councils to allocate budgets in long term plans, collaborate on larger works, and anticipate traffic impacts.

Illustration of Jonathan Prince

Technically speaking

A lot of useful functionality in this application is provided through maps. The foundation for our mapping is the Leaflet framework. We build on this using custom UI components to provide a tailored experience in order to meet the varying needs of each use-case. We couple this with some clever geospatial wrangling on the backend, with our good friend PostGIS taking care of the heavy lifting. We also use information and tools from the OpenStreetMaps project for detailed information on road specifications and routing.

Our backend is built around a NodeJS server and PostgreSQL/GIS database. Alongside the main application server are several smaller services set up to handle PDF generation, street routing and a mail queue. We run all backend services inside Docker containers, running as a cluster on the Amazon Container Service.

Jonathan Prince, Technical Lead