DCP testing explained
What a DCP test is, what information is recorded, and why digital capture helps the reporting workflow.
Resources
Resources for DCP testing, road core logging, and pavement investigation reporting.
Use these short guides when you need a direct technical answer, a clearer buying comparison, or a better understanding of where the workflow delay begins.
Each page is written for practical use in UK pavement investigation work and links back to the relevant Experior product pages.
Direct answer: The Experior resource section explains what DCP tests and road core logs are used for, what should be recorded, how digital field capture affects reporting, and where specialist software can reduce site-to-office delays. It is intended as a practical reference rather than a marketing library.
Resource library
These pages are organised around the search topics buyers and engineers most often ask about.
What is a DCP test used for in pavement investigation?
A short, direct explanation of how Dynamic Cone Penetrometer testing is used in pavement investigations.
CBR from DCP: what engineers need to know
How DCP data may be used to estimate in-situ strength using recognised correlations, and why context matters.
DCP software vs spreadsheets
A fair comparison of spreadsheet workflows and specialist DCP software for recording and reporting.
Road core logging best practice
What should be captured during road core logging, including location, depth, layer details, and photographs.
Digital field data capture for pavement investigations
Why structured site data capture helps with traceability, handoff, and reducing report turnaround time.
Questions engineers keep asking
Public technical discussions tend to revolve around a small number of practical questions.
How is a DCP test recorded and interpreted?
People ask what is recorded at each blow, how the result is interpreted, and how it turns into a usable pavement assessment.
How reliable is CBR from DCP?
Engineers repeatedly ask which correlation to use, when the result should be treated cautiously, and how field conditions affect the number.
How do I stop losing time between site and report?
Beyond the test itself, many discussions are really about scattered notes, photos, and retyping before the final report can go out.
Where manual pavement investigation workflows usually break down
- The field record is captured on paper and rebuilt later in the office.
- Blow-by-blow or depth-by-depth detail is rounded, simplified, or copied into a spreadsheet after the event.
- Photos, locations, and notes are stored separately from the main test or core record.
- The report writer receives an incomplete job pack and has to reconstruct the investigation.
What specialist workflow tools can improve
- DCP Data helps capture the first DCP record in a structured format on site.
- DCPAnalyser gives the office a clearer route into calculation and repeatable reporting.
- CoreDATA and RCoreAnalyser help keep road core descriptions, references, and photographs tied to the same job.
- The comparison guides explain where specialist software helps more than a spreadsheet-based process.
Link the guide to the right tool
- DCP Data is the Android field app for DCP test recording.
- DCPAnalyser is the Windows tool for DCP analysis and reporting.
- CoreDATA and RCoreAnalyser cover road core logging and office reporting.
Use the guides to narrow the bottleneck
If the main issue is field recording, start with DCP Data or CoreDATA. If the field record already exists but the office is slow, start with DCPAnalyser or RCoreAnalyser.