Traffic video planning resource
Traffic Video Processing Brief Template: Scope, Classes, Intervals and Outputs
A planning framework for turning a project question and supplied footage into an agreed observation brief before processing begins.
The structures and examples below are original and synthetic. They are not client forms, project records, legal advice, a promise of suitability or a substitute for a project-specific agreement.
Why a written brief matters
Describe the decision before describing the files.
A traffic video processing brief makes the requested observation visible before anyone starts a count. It connects the engineering question to the footage, locations, rules, outputs and review path. This is distinct from the recording standard: that resource checks whether footage is usable and handed over clearly; this page sets the analysis scope to be applied after a source is reviewed.
Five-part brief template
Use only the sections the study requires.
01
Decision and scope
State the decision the data will support, study type, locations, local timezone, observation dates and required periods.
02
Source and coverage
List every camera/view, file range, start/end time, known gap, visibility constraint and any synchronisation requirement.
03
Observation rules
Define count lines, approaches, movements, lanes, active-travel areas, vehicle classes, intervals and exception treatment.
04
Outputs and review
Agree required tables, summary level, template/column labels, QA/QC checks, exception record and delivery contact.
05
Secure handover
Confirm approved transfer method, authorised access, file index, retention instructions and receipt check.
Synthetic example: scope and movement rules
Set the observation unit, not just the location name.
A scope table reduces ambiguity where a team needs movement-level data. This illustrative example does not represent a real junction, footage file or count result.
| Field | Illustrative entry | Clarification required before processing |
|---|---|---|
| Study objective | Understand turning demand in defined peak periods | Which decision will use the data? |
| Observation unit | Approach, movement and 15-minute interval | Which movements and lanes are included? |
| Road users | Project-defined vehicles, pedestrians and cyclists | What class dictionary and crossing rules apply? |
| Time basis | Local timezone stated in the approved brief | Are clocks aligned across all relevant views? |
Synthetic example: class schedule and interval output
Agree labels, intervals and outputs together.
| Class | Scope note | If unclear |
|---|---|---|
| Passenger vehicle | Apply approved visible characteristics. | Use approved exception rule. |
| Commercial / heavy | Use the project dictionary; do not substitute a generic national scheme. | Escalate where the evidence is insufficient. |
| Pedestrian / cyclist | Count only the agreed crossing or observation boundary. | Record coverage limitation. |
| Interval | Dimension | Required field |
|---|---|---|
| 08:00–08:15 | Movement | Approved movement label |
| 08:00–08:15 | Class | Approved class label or exception |
| 08:00–08:15 | QA note | Coverage or review status where required |
Exceptions, QA/QC and handover
Write down what could affect interpretation.
Synthetic exception record
Condition: illustrative reflection obscures one class cue during a stated period. Action: use the approved rule, flag the condition and retain the note with the affected output. The example contains no client, project, date, location or video reference.
Brief-to-delivery QA/QC
- ✓ Check source coverage against the stated scope.
- ✓ Confirm labels, intervals and output columns match the approved brief.
- ✓ Reconcile review notes, exceptions and final file identity.
- ✓ Confirm agreed handover recipient and secure-transfer process.
Use this to start a scoped conversation
The public form is for the brief, not source footage.
Share the study objective, locations, observation periods, required movements or classes and expected output. If the scope is suitable, approved secure transfer and project-specific data-handling arrangements can then be confirmed separately.
Frequently asked questions
Before you send a brief.
Is this a downloadable client form?
No. It is a public planning reference. A project team should agree its own secure brief, access route and file-transfer arrangements with the appointed provider.
Can one template be used for every traffic video study?
No. A link count, turning-movement count, classification study or active-travel study needs different observation boundaries and rules. Use the sections that match the approved scope.
Should large video files be sent with the brief?
No. The public form is for a project brief, not large or sensitive files. Agree a secure-transfer process after the scope is understood.