01
Start from the request, not a blank page
Upload the client request form. The system reads and checks it, catching typos, wrong field types and missing sections before they cost you.
Faster TMP authoring · NZGTTM-native
Prepare traffic management plans faster
Cleaner plans, fewer declines. Enter it once, not four times. Drafted in minutes. Approved by your team.
Book a demoThe problem
Authoring a TMP is slow, repetitive and unforgiving.
A designer re-keys the same site details across four documents, formats a risk assessment by hand, and hopes nothing was missed before it reaches the RCA. One empty field or one inconsistency means a decline — and significant rework time. Under NZGTTM, plans are now risk-based, which is right for safety but puts more thinking and more documentation on the people writing them.
Too much time on paperwork
The diagram and risk assessment is the skilled part. Everything around it is manual.
Rework is expensive
Declines cost days, and the reason rarely gets shared.
The stakes are real
A missed hazard isn’t admin — it’s risk.
How it works
From client request to RCA-ready — with a human in control the whole way.
02 In development
Site research, gathered and made design-ready
A Chrome extension pulls traffic flows, bus routes, education facilities and road details from the sites your designers already use. It all collates against the job, with no re-keying. Then you get a clear, digestible brief, so you start drawing with the full picture.
03
Design in your own tools
Build the TMD in the diagram tools you already use. Keep what you know. Upload your TMDs and GTMPs, and the system reads them alongside the site data.
04 In development
A full risk assessment, built to the framework
Your site data and diagrams are assessed together against NZGTTM and WorkSafe requirements, and the risk assessment is drafted to that framework — not a generic template you have to rewrite.
05
Review, approve, and package RCA-ready
Everything populates a purpose-built editor with live preview, and the source behind every value. Approve section by section. A final check confirms every field, then exports a clean, RCA-ready pack.
Why TrafficSense
Built for the realities of traffic management.
Enter it once, not four times
The same details used to be re-keyed across every document. Now they’re captured once and kept in sync — so designers stop copy-pasting and focus on the work only they can do.
Qualified humans always in control
The drafting is done for you; the decisions stay yours. Per-section approval and a final check before anything is submitted.
Auditable by design
Every value shows its sources — the request, the diagram, LINZ, NZTA counts, past projects. No black box.
It learns, so your team gets better
Every RCA decline becomes shared knowledge, not one person’s memory.
Pricing
Simple, per-plan pricing.
Start with a pilot, then pay for the plans you author — no rip-and-replace, no lock-in. We’re finalising pricing during early access, so you’ll get clear numbers before you commit.
Pilot
Free
2-month pilot
Run a pilot on real plans, alongside your current workflow.
- Full NZGTTM drafting
- Review + approve editor
- Complete audit trail
Recommended
Team
Per plan
confirmed during your pilot
For teams authoring TMPs day to day. Pay for what you author.
- Everything in Pilot
- Company templates + form profiles
- User management
- Priority support
Enterprise
Custom
volume & scale
For larger teams and RCAs with tighter requirements.
- Volume pricing
- SSO + admin controls
- Full audit trail — data provenance and user-activity loggingIn development
- Onboarding + training
- Priority SLA
Resources
Worth a read.
- What a compliant TMP must include under NZGTTM (the checklist) Under NZGTTM a TMP is four documents built on a site-specific risk assessment. Here is what each part must include — the checklist to work through before you submit.
- Why traffic management plans get declined, and how to prevent it Most TMP declines come down to a handful of avoidable gaps. Here are the patterns RCAs see most often, and how to close them before you submit.
- TTM acronym decoder: TMP, TMD, STMS, CAR and more A plain-English decoder for New Zealand's temporary traffic management acronyms — TMP, TMD, STMS, CAR, WAP and more — with the CoPTTM-to-NZGTTM changes flagged.
FAQ
Questions worth asking.
Does it replace your existing diagram authoring tool?
No — it works alongside the tools you already use, like RapidPlan, handling everything before and after the diagram: capture, drafting, structured review, compliance QA, and the audit trail.
How do I know it isn’t just making things up?
Every value shows where it came from — the request form, your drawing, the public road record, a rule, or your own input. It reads your drawing rather than guessing at it: anything it can only infer is flagged for your review, never filled in silently. And anything it can’t identify becomes a question for you to answer, not an invented blank. Drafting happens last, against confirmed facts only — so there’s nothing left for it to make up.
Which framework is TrafficSense built on?
NZGTTM. It and the Australian state frameworks share one parent — the Austroads Guide to Temporary Traffic Management — so TrafficSense is built on that risk-based foundation, not a single market’s rulebook.
Will it get things wrong?
Sometimes, yes — any drafting tool can, and we would rather say so plainly than pretend otherwise. That is exactly why nothing goes out on its own. TrafficSense drafts and checks; a qualified person on your team reviews, edits and approves every plan before it is submitted to an RCA. The judgement stays where it has always been.
Three things make that review fast rather than a second job. It is built for temporary traffic management and works to NZGTTM and WorkSafe requirements — not a general-purpose chatbot guessing at your industry. Every value shows where it came from, so you are checking a source rather than taking a claim on trust, and anything that cannot be verified is flagged rather than guessed. And before export, a final check runs across every field against the same rules the road controlling authority applies, so gaps surface on your screen instead of in a decline.
That holds on complex plans as much as simple ones: the harder the job, the more there is to check, and the more useful it is to have every value traceable. You stay accountable for the plan, so you stay in control of it.
Do we lose control?
No. Every output is reviewable, editable, and auditable. Nothing is submitted automatically — a person always lodges. The hybrid safety model is non-negotiable: the drafting is automated, the sign-off never is.
What about our data?
Your data, your quality, your control. Information is used to draft and check your plans — not to train models for anyone else. Our product Privacy Policy covers how data is handled once you’re an authorised user of the Service.
How do we start?
Run a pilot alongside your current workflow and measure the difference — no rip-and-replace. Tell us a bit about your team and we’ll get you set up.
Ready to submit cleaner plans, faster?
Get early access and a direct line to the team building it.
Book a demo