Event scope
Define what the event involves: expected attendance, setup and pack-out times, road closures, parking areas, pedestrian flows, loading zones, emergency access and any alcohol or entertainment that changes crowd behaviour.
Your TMPDesignerEvent traffic planning should start early because closures, pedestrians, parking, emergency access, resident impacts and RCA timelines often need more detail than organisers expect.

The key points, split into simple blocks so the page is useful without feeling like a wall of text.
Define what the event involves: expected attendance, setup and pack-out times, road closures, parking areas, pedestrian flows, loading zones, emergency access and any alcohol or entertainment that changes crowd behaviour.
Plan for how people arrive, move around and leave. Crowd behaviour affects crossing points, marshalling, signage and emergency access. Large or alcohol-licensed events usually need more detailed planning.
Event closures need the same detour, access, emergency and stakeholder thinking as worksite closures, plus timing that fits setup, the event itself and breakdown. Late submissions are a common reason event permits are delayed.
The relevant council, RCA or network owner reviews the submission. Our role is to help make the information clearer, more complete and easier to respond to.
Send the work location, scope, dates, site plans or markups, methodology, hours of work, access needs, photos if available, and any RCA comments already received.
Yes. Your TMP Designer focuses on the planning, documentation and drawing support around the job. If your project also needs on-road setup, equipment or training, we can keep the TMP, CAR/WAP and drawing information aligned while those field services are arranged with the right provider.
Send plans, photos, dates or RCA comments and get practical next steps for TMP design, CAR support, amendments or overflow planning.