Site references
Location, chainage, lane or position details, and job identifiers.
Resource
Road core logging best practice
A good road core log should capture enough information for someone in the office to understand exactly where the core came from, what the layer structure looked like, and what supporting evidence goes with that record. The aim is clarity, traceability, and a smoother reporting stage.
Direct answer: Road core logging should capture location, depth, layer description, material type, photographs, condition, and chainage or other reference information needed to tie the core back to the job. A clear road core record also helps the office prepare a more reliable report without rebuilding the investigation from separate notes.
What to capture
Core details
Recovered depth, layer depths, material type, layer description, and condition.
Supporting evidence
Photographs, reinstatement records, and anything else needed for later office review.
Why record quality matters
Road core reports are harder to prepare when the office has to reconstruct the location, the layer sequence, or the visual evidence from separate notes and image folders.
How digital logging helps
Structured logging can keep the core record, the photographs, and the supporting references together. That is the type of workflow supported by CoreDATA and RCoreAnalyser.
Frequently asked questions
What information should be recorded during road core logging?
Road core logging should capture location, depth, layer description, material type, photographs, condition, and chainage or other reference information needed to tie the core back to the job.
Why are photographs useful in road core records?
Photographs help preserve visual evidence of the core condition and layer makeup for later office review and reporting.
Why does structured logging help?
Structured logging reduces missing information and makes the office handoff more consistent.