Resource levelling on traffic signal projects rarely gets the attention it deserves at the programme planning stage. Most project managers focus on sequencing activities and protecting the critical path, which is correct. But the schedule that looks clean on a Gantt chart can silently demand five electricians on Tuesday and zero on Wednesday, or require two specialist signal technicians for a single morning of controller configuration. Without resource levelling, those imbalances get discovered in the field rather than on paper.
What resource levelling actually means in this context
Resource levelling is the process of adjusting activity start and finish dates within available float so that resource demand stays within what's actually available, without extending the project end date where possible. It's distinct from resource smoothing, which accepts an extended duration in exchange for a flat resource profile. For traffic signal projects, both techniques apply at different points in the programme.
The resources that most commonly need levelling on a signal deployment are licensed electricians, traffic control personnel, signal technicians, and civil crews for conduit and pit work. Each has a different supply constraint. Traffic controllers are typically available through labour hire at short notice, but they're also the most expensive to idle. Licensed electricians working on AS/NZS 3000-compliant installations are less flexible; you can't substitute an unqualified labourer for an electrical task at a signalised intersection.
Signal technicians are the scarcest resource on most projects. Controller configuration, detector tuning, and commissioning traffic signal systems each demand a narrow skill set. Spreading that work without levelling frequently creates situations where a technician is needed at two sites simultaneously because the programme treats their tasks as independent when they share a resource.
Where the peaks usually form
Resource peaks on traffic signal programmes tend to cluster at three points: the civil preparation phase, the equipment installation phase, and the testing and commissioning phase. Civil work and installation often overlap on larger projects because the programme tries to compress duration by starting installation at completed sites while civil work continues elsewhere. That's a legitimate strategy, but it doubles the crew types on site and frequently exhausts your electricians before commissioning begins.
The commissioning phase is where under-levelled programmes break down most visibly. If installation finishes across multiple intersections within a few days of each other, every commissioning activity queues up at once. A single senior technician can't test conflict monitoring, validate timing plans, confirm signal aspect output, and verify detector loops across four intersections in a week without something being rushed or postponed.
Staggered installation completion dates, built deliberately into the programme, are the most effective buffer. That stagger is only possible if float in non-critical installation activities is identified early and used deliberately. This is exactly the kind of schedule analysis covered in detail when looking at traffic signal project scheduling and float management. Float that isn't mapped to resource demand is float that gets consumed accidentally.
Practical steps for levelling a signal project programme
The steps below apply to projects involving between 4 and 20 intersections, which covers the majority of Australian council and state authority signal upgrades.
- Build a resource-loaded schedule from the start. Each activity should carry a resource type and quantity before any levelling is attempted. A schedule with no resource assignments can't be levelled; it can only be guessed at.
- Identify your binding constraint early. On most projects, signal technician availability is the binding constraint. Build the programme around that constraint first, then layer other resources on top.
- Use float in civil and trenching work to absorb peaks. Civil activities typically carry more float than electrical or commissioning tasks. Shifting a pit excavation by two days rarely affects the critical path but can reduce the crew size needed on a given day from five to three.
After the initial levelling pass, run a resource histogram for each crew type across the full programme duration. Any day where demand exceeds your contracted supply is a risk. Address it before the programme is baselined, not after the subcontract has been signed.
The interaction between resource levelling and subcontractor onboarding
Resource levelling decisions directly affect how subcontracts should be structured. A levelled programme with predictable crew size requirements is far easier to quote accurately than a programme with sharp peaks. Subcontractors pricing against an un-levelled programme will either pad their rates to cover standby risk or underprice and then claim variations when actual demand spikes. Neither outcome serves the project.
Getting subcontractors engaged early enough to validate resource assumptions is one of the key steps in subcontractor onboarding on traffic signal projects. A subcontractor who has reviewed the resource-loaded programme before signing a subcontract has no reasonable basis to claim they were unaware of the crew size required in any given week.
Where specialist subcontractors are involved (controller manufacturers providing commissioning technicians, for instance), their availability windows should be confirmed before the programme is baselined. Treating their technician availability as a fixed constraint, like a piece of equipment with a delivery date, is the correct approach. You level around them, not the other way around.
Resource levelling on fast-track and night-work programmes
Traffic signal projects with night-work requirements introduce a separate resource challenge. Night crews are a different pool from day crews. Many electricians and civil workers don't rotate between shifts on the same project, which means the effective resource capacity per day drops. A programme that assumes the same electrician can work a day shift on civil and a night shift on signal installation is both unrealistic and a fatigue risk under the model Work Health and Safety Act provisions adopted across Australian jurisdictions.
Night-work programmes need their own resource histogram, run separately from the day-work programme. Where the two programmes share personnel (the signal technician who needs to witness a night-time cutover, for example), those shared resources need to be tracked as constrained across both shifts.
Fast-track programmes that compress duration by adding parallel work streams increase resource demand without automatically increasing supply. The mathematics are straightforward: compressing a four-week installation into three weeks requires more simultaneous crew, not just earlier starts. If that additional crew isn't available in the local labour market, the compression isn't achievable. Resource levelling forces that reality check before it becomes a programme failure.
Keeping the levelled programme current
A levelled programme that isn't updated as work progresses ceases to reflect reality within a fortnight. Resource levelling isn't a one-time exercise. Each progress update should re-run the levelling check against actual resource consumption and remaining work. If an activity took longer than planned, the resource that worked on it was either idle on other tasks or over-committed, and the programme should reflect which occurred.
Tracking actual resource usage against the levelled baseline is also the data that supports variation claims if scope changes extend the programme. An un-levelled, un-tracked programme makes it almost impossible to demonstrate that a scope change caused additional resourcing costs. A levelled, tracked programme makes that demonstration straightforward.
On projects where the client authority reviews the programme monthly, submitting a resource-loaded, levelled schedule rather than a bare Gantt chart signals a level of planning rigour that most contractors don't provide. It's also the foundation on which realistic recovery plans are built if something actually goes wrong.