Service summary
Level crossing surveys record agreed road-user and crossing activity in a rail environment.
When it is used
Use them for safety, access, rail planning and operational context.
Methodology
Define the crossing boundary, road-user modes, crossing events, time periods and any train-related context before observation.
Inputs and source requirements
Provide a location plan, dates, periods, defined observations, any classifications and required output files.
Movements and classifications
Movement, direction, lane and classification rules are agreed only where they are relevant to this study.
Time intervals
Set the reporting interval and any peak or operating windows before collection or processing.
Typical deliverables
Agreed data tables, location and methodology notes, defined assumptions and quality-review information.
Quality control
Check coverage, definitions, interval structure and delivery format against the approved brief.
Limitations
The result describes the defined observed scope and period; it should not be used to make claims beyond the available evidence.
Privacy and security
Sensitive files, video and identifiers are exchanged only through approved project workflows.
Frequently asked questions
Can train events be included?
Yes, if the brief defines the event and the footage shows it clearly.
Does it assess rail safety by itself?
No. It is an observation record, not a complete safety assessment.