How Long Does a TMP Take to Approve in Victoria?

What speeds up (or slows down) approval

Factors that help

• Scaled, readable drawings that match the posted speed environment.
• Clear pedestrian and cyclist paths (or signed detours) with ramps and protection.
• One-page summary calling out work windows, stages, and any temporary stop moves.
• Consistent symbols and device naming across TMP and TGS.

Factors that slow things down

• Ambiguous staging (no “day vs night” notes or changeover steps).
• Missing driveway/loading access details.
• Unclear tram/bus interfaces or bike lane treatments.
• Version sprawl: multiple unlabeled PDFs or late scope changes.

If your works affect footpaths or bike lanes, see our Pedestrian Management guide for ramps, barriers and wayfinding tips.

Permit sequencing that affects the clock

A practical order that avoids idle time:

1. TMP strategy finalised →
2. TGS layouts aligned to the exact windows →
3. Lodge TMP/TGS with the authority and, in parallel where allowed:
   • Road Occupancy Permit (if required)
   • Footpath closure / parking bay reservation
   • Any temporary tram/bus stop moves
4. Traffic controller resourcing and VMS bookings once key conditions are known.

Bundle interdependent items in the same cover letter so reviewers see the whole picture.

What reviewers look for (pass first time)

• Safety and sight distance: advance warning spacing, taper lengths and buffers sized to speed.
• Access: emergency routes clear; maintain driveways/loading where safe or steward them.
• People walking and riding: continuous paths or robust detours (barriers, not just cones).
• Public transport: maintain stops or clearly show temporary locations.
• Staging and monitoring: who inspects, how often, and how changes are recorded.

Submission checklist (copy-ready)

Use this to keep your first lodgement tight:

• Scaled base (e.g., 1:200 / 1:500), north arrow, legend, revision/date.
• Posted speed noted; approach distances, taper lengths and buffers sized.
• Device tally (signs, cones, barriers, lighting), plus any arrow boards/VMS.
• Pedestrian/cyclist treatment and any temporary PT arrangements.
• Driveways/loading marked; stewarding notes if access is intermittent.
• Staging (setup → maintain → changeovers → pack-down), with day/night windows.
• Monitoring frequency, photo log, and on-site contact list.
• Single-page summary of the key impacts and windows.

Common causes of delay (and quick fixes)

• Unreadable drawings → increase scale, simplify labels, keep symbols consistent.
• Vague pedestrian routes → add continuous wayfinding and physical separation.
• Missing driveway/loading plan → map them and schedule stewards at peaks.
• Late scope changes → version control, and notify the reviewer early.
• No pack-down/next-day note → include stage change instructions and “END ROADWORK” placement.

How to shorten the timeline (practical tactics)

• Pre-lodge summary: one page that answers “what changes each day or night?”
• Bundle related permits were allowed to reduce back-and-forth.
• Use repeatable layouts for repetitive utility works; lodge a series with consistent staging.
• Show PT and bike interfaces clearly avoids a whole feedback cycle.
• Add photo snippets of sight lines or tricky driveways to head off questions.

Mini case snapshots

• Inner-north utility pits: repeatable TGS across multiple addresses; clean first submission led to a single, short review cycle.
• CBD weekend crane lift: approval landed after showing temporary bus stop relocation and explicit turn bans on the plan.
• School-zone trenching: moved outside drop-off/pick-up windows; approval proceeded without extra conditions.