A portable count is only useful when it answers a live network question. Whether a council needs evidence for a speed reduction scheme, a contractor is assessing temporary traffic management, or a highways team is investigating rat-running, the objective should shape the deployment. To deploy portable traffic counters effectively, begin with the decision the data must support, rather than the equipment available on the day.
Portable, above-ground detection gives transport teams a faster route to credible traffic data without cutting the carriageway or installing inductive loops. That reduces roadworks exposure, limits disruption to road users and makes short-term monitoring practical at more locations. The benefit, however, depends on selecting the right sensing technology, position and survey parameters for the site.
Start with the survey decision
Traffic volume alone rarely tells the full story. A two-way daily total may establish whether a road is busy, but it will not show whether a junction is capacity constrained during the school run, whether HGVs are using an unsuitable route, or whether excessive approach speeds are creating a road safety concern.
Set the survey purpose before specifying the counter. For a residential speeding concern, individual vehicle speeds, direction and time-of-day profiles are likely to matter most. For a proposed active travel crossing, vehicle flows, gaps in traffic and peak-period demand may be required. For a development or network study, classification, directional movements and the relationship between traffic patterns on nearby links may be more relevant.
The length of the survey also needs thought. A seven-day count can provide a useful representative profile where conditions are normal, while a longer deployment may be needed to account for seasonal variation, school terms, local events or works on an alternative route. Avoid collecting a technically accurate sample that is operationally unrepresentative.
How to deploy portable traffic counters
The practical deployment process has three connected stages: assess the site, configure the detection zone and validate the output. Skipping any one of them can introduce errors that are difficult to identify once the counter has been removed.
Assess the physical environment
Walk the site before installation. Record the carriageway layout, number of lanes, lane widths, posted speed limit, typical vehicle behaviour and any features likely to affect detection. Parked vehicles, lay-bys, bus stops, tight bends, gradients, guardrails and roadside vegetation can all influence the field of view or create unusual trajectories.
For radar or AI video detection, identify a mounting position with a clear view of the required approach or carriageway section. A stable street lighting column, signpost or purpose-designed temporary support may be suitable, subject to the relevant asset owner permissions and safe working arrangements. The mounting height, lateral position and angle should allow the system to distinguish the intended lanes while excluding adjacent roads, footways and private accesses where possible.
The location should also reflect what the survey is intended to measure. A count immediately downstream of a signalised junction may be distorted by platooning and queuing. A counter close to a side road may capture turning traffic that does not represent through flow. In contrast, those same positions may be exactly right when the project is assessing signal operation or junction demand. There is no universally correct placement – there is only a placement that fits the question.
Select technology that suits the task
Portable radar counters are well suited to rapid volume, speed and directional monitoring, particularly where a non-intrusive installation is required. They can be deployed without disturbing the road surface and can capture vehicle movement across a defined detection area.
AI-powered video detection can add value where the survey requires more detailed classification or the separation of road users such as vehicles, cyclists and pedestrians. It is particularly useful where multimodal activity, complex movements or vulnerable road user behaviour are part of the operational issue. Video-based systems need careful consideration of sight lines, lighting conditions and privacy requirements.
Wireless traffic sensors may be appropriate for targeted monitoring where rapid placement and low-impact installation are priorities. The right choice depends on the data outputs required, the road geometry, expected traffic speeds, duration of deployment and whether the equipment must operate autonomously for an extended period.
Legacy pneumatic tube counts can still have a place in some survey programmes, but they introduce installation and maintenance considerations that above-ground radar and video solutions can avoid. Tubes can be vulnerable to damage, may affect cyclist comfort and require physical fixing across the carriageway. Where safety, speed of deployment and minimal road disruption are central requirements, non-intrusive counters offer a stronger operational case.
Configure before collecting data
A counter should not be treated as a fit-and-forget device. Configure the correct lanes, detection directions, speed thresholds, vehicle classes and recording intervals before the survey starts. For many network studies, 15-minute intervals provide the resolution needed to identify peak demand and compare traffic conditions across locations. For longer trend monitoring, hourly or daily aggregation may be sufficient, provided the underlying data remains available for review.
Check the device clock and ensure it is aligned with other survey equipment, signal logs or incident records. A time mismatch can undermine comparisons between datasets, especially where the purpose is to understand congestion at a junction or the impact of a temporary intervention.
Power and communications should be planned at the same time. Battery autonomy needs to cover the intended duration with sensible contingency for colder weather and higher data transmission demand. If remote access is available, use it to confirm device status and identify faults early rather than discovering a failed survey at collection.
Validate the deployment on site
Before leaving the location, observe live traffic and compare it with the counter output. Confirm that vehicles travelling in each relevant lane are detected, travelling direction is correct and speeds are plausible. Watch for false detections caused by vehicles in an adjacent lane, reflections from roadside objects or a detection zone that extends too far beyond the intended carriageway.
A short manual check is valuable. Count a sample of vehicles over a defined period and compare it with the recorded total. The purpose is not to create a full manual survey, but to identify obvious configuration issues while they can still be corrected. At complex sites, repeat the check at different traffic levels, particularly if queues or turning movements alter vehicle spacing.
Installation safety must remain central throughout. Site personnel should work from a safe position, apply the appropriate traffic management arrangements and avoid unnecessary carriageway access. One of the principal advantages of portable above-ground counters is that they can reduce exposure compared with road-embedded installations. That advantage is lost if the deployment method is not properly planned.
Protect data quality during the survey
Traffic data can be affected by factors outside the counter itself. Roadworks, collisions, diversions, adverse weather, school holidays and major local events can change normal traffic patterns. Keep a site log that records these conditions, along with installation time, equipment settings, any site visits and removal time. This gives analysts the context needed to explain unusual peaks, troughs or gaps.
Review incoming data where remote monitoring is possible. A sudden fall to zero may indicate a power, communications or configuration issue. An unexpected rise in a particular class could reflect a genuine operational change, but it may also signal that a neighbouring lane or side road has entered the detection area. Early review protects the survey programme and avoids unnecessary repeat visits.
Data cleaning should be transparent. Clearly distinguish validated observations from estimated or excluded periods, and retain the original dataset. For public-sector decision-making and scheme appraisal, confidence in the audit trail can be as important as the headline figure.
Turn counts into practical action
The strongest portable traffic counter deployments connect measured behaviour to a network response. Speed distributions can support targeted speed management or speed indication device locations. Directional flows can inform junction design, signal staging or temporary traffic management. Vehicle classification can identify inappropriate HGV use, while cyclist and pedestrian counts can strengthen the evidence base for active travel investment.
It is also worth comparing data across time rather than relying on a single total. A road carrying moderate daily traffic may still experience a severe, short peak that affects a school crossing or junction exit. Equally, a scheme may reduce average speed but leave the highest-risk speeding periods unchanged. Good analytics reveal these operational patterns and help teams prioritise interventions with measurable benefit.
For authorities and contractors managing multiple sites, a consistent deployment method makes datasets more comparable and reduces survey risk. C & T Technology supports this approach with above-ground radar, video and wireless detection solutions designed around practical installation, reliable monitoring and better road network decisions.
A portable counter should leave more than a spreadsheet behind. When the technology, site position and validation process are aligned, it provides evidence that can move a road safety concern, congestion issue or scheme proposal from assumption to informed action.