What can a traffic count deliverable contain?

Depending on the agreed study, a deliverable can contain structured interval tables, movement matrices, classification summaries, lane-level observations, QA/QC notes and agreed summary outputs.

Can traffic data be supplied in a client template?

Data can be structured to align with an agreed project template, subject to the agreed scope and delivery requirements.

What is the difference between detailed and summary traffic data?

Detailed data may retain interval, movement, lane or classification dimensions; summary data aggregates approved dimensions for the agreed reporting view. Both can be quality reviewed.

Traffic data resource

What can a traffic count deliverable look like?

This original, web-native resource explains possible TMC, classification, lane, roundabout, parking, queue, active-travel and QA/QC structures without presenting a client workbook, project record or fixed reporting template.

Explore turning movement counts Discuss a project brief

From project input to delivery

A web-native process model showing how an agreed source can become a reviewable project output.

01
Project input
02
Manual observation
03
Structured data
04
QA/QC
05
Client format
06
Delivery

Synthetic intersection data

A movement matrix starts with a defined study structure.

A junction can have three, four, five or more arms. Approaches, lanes, movements, classes and intervals are included only where the project scope calls for them.

Illustrative intersection movement model

Approaches, arm count, lanes and movement rules are defined for the actual study; this diagram is a conceptual four-arm example only.

Synthetic TMC example — interval, approach, movement and class records
Time interval	Approach	Movement	Vehicle class	Count
08:00–08:15	North approach	Left	Light vehicle	42
08:00–08:15	North approach	Through	Commercial / OGV	12
08:00–08:15	East approach	Right	Heavy vehicle	6
08:15–08:30	South approach	Through	Bus	4

Totals may be prepared by interval, approach, movement or approved class; the detailed record structure keeps each example observation traceable.

Synthetic lane-by-lane example
Interval	Approach	Lane	Classification	Count
08:00–08:15	North approach	Lane 1	Light vehicle	31
08:00–08:15	North approach	Lane 2	Commercial / OGV	7
08:15–08:30	East approach	Lane 3	Heavy vehicle	4

Lane configuration depends on the study; three lanes are shown only to demonstrate a configurable reporting dimension.

Illustrative traffic volume by interval

Text equivalent: the synthetic example totals are 71, 85, 78 and 62 across four consecutive 15-minute intervals. The values are illustrative and do not describe observed traffic.

Synthetic vehicle-classification example
Interval	Direction	Vehicle class	Count
08:00–08:15	Northbound	Light vehicle	52
08:00–08:15	Northbound	Commercial / OGV	9
08:00–08:15	Southbound	Heavy vehicle	5
08:15–08:30	Southbound	Motorcycle	11
08:15–08:30	Northbound	Cycle	4

Class names are illustrative. The approved project specification defines the classification scheme; no single scheme is universal.

Synthetic roundabout entry/exit example
Interval	Entry	Exit	Lane	Vehicle class	Count
09:00–09:15	Entry A	Exit 2	Lane 1	Light vehicle	38
09:00–09:15	Entry B	Exit 3	Lane 2	Commercial / OGV	7
09:15–09:30	Entry C	Exit 1	Lane 1	Bus	3

Roundabout outputs use entry and exit relationships where required rather than forcing left/through/right terminology.

Synthetic parking observation example
Interval	Entries	Exits	Occupancy
09:00	6	3	41
09:30	5	7	39
10:00	4	6	37

Measures depend on the approved parking-study objective, inventory and observation method.

Synthetic queue observation example
Time	Approach	Lane	Queue measure
08:00	North approach	Lane 1	Illustrative measure A
08:15	North approach	Lane 1	Illustrative measure B
08:30	East approach	Lane 2	Illustrative measure C

Queue output is defined only by the agreed queue methodology and reference point.

Synthetic pedestrian and cyclist example
Crossing / route	Direction	Road-user type	Interval	Count
Demo crossing A	Northbound	Pedestrian	08:00–08:15	18
Demo crossing A	Southbound	Cycle	08:00–08:15	7
Demo crossing B	Eastbound	Pedestrian	08:15–08:30	11

Vulnerable road-user observations remain logically distinct from motor-vehicle classification unless the agreed output deliberately combines them.

Synthetic QA/QC review summary
Review area	Illustrative review status	Scope note
Study completeness	Reviewed	Locations and expected study periods
Interval completeness	Reviewed	Expected interval sequence
Movement completeness	Reviewed where applicable	Approved movement set
Classification completeness	Reviewed where applicable	Approved class definitions
Consistency review	Reviewed	Unexpected zeros, duplicates or unusual patterns
Reconciliation	Applied where supported	Totals and structural relationships
Final review	Completed	Delivery structure and recorded exceptions

This is an example review structure. The approved scope determines which checks apply to a project.

Synthetic interval summary example
Time	Vehicle class A	Vehicle class B	Vehicle class C	Total
08:00–08:15	52	13	6	71
08:15–08:30	61	16	8	85
08:30–08:45	57	14	7	78
08:45–09:00	46	11	5	62

A clear QA/QC path

1Source video / data
2Counting / observation
3Structured interval data
4First review
5Structural validation
6Consistency / outlier review
7Correction where required
8Final QA/QC
9Deliverable

The agreed scope determines which completeness, reconciliation, consistency and manual-review checks are appropriate.