Route 1
Record DCP data on site
Choose the DCP field app if the first record is still paper-based or inconsistent between operators.
Go to DCP DataProducts
Use this page to separate three jobs quickly: recording DCP on site, reporting DCP in the office, and logging and reporting road cores across the full field-to-office handoff.
This is a decision page, not a product catalogue. Start with the job that is slow, then move to the matching product page, proof route, or download path.
When the field record is captured properly, the office can often start reporting before the site team is back in the office on data-connected tablets because the files can be uploaded into the customer's own cloud storage or transmitted into their own system rather than waiting for notes to be retyped.
Each route below points to a single main topic and the next proof step.
Route 1
Choose the DCP field app if the first record is still paper-based or inconsistent between operators.
Go to DCP DataRoute 2
Choose the desktop reporting tool if the field record exists but the office output is still too manual.
Go to DCPAnalyserRoute 3
Choose the paired core workflow if the site record and office report both need tightening up.
Go to CoreDATA / RCoreAnalyserUse this matrix when the main question is not what the software is called, but which part of the workflow is actually slowing the job down.
| Workflow question | Best-fit product | Why that route fits | Proof to review next |
|---|---|---|---|
| Do you need to capture DCP data on site? | DCP Data | The bottleneck starts with the first record, so the field app is the right place to tighten the workflow. | Field screenshots |
| Do you already have the DCP record but need better reporting? | DCPAnalyser | The field record exists, but the office still needs a cleaner route into calculation, checking, and client-ready output. | Report outputs |
| Do you need to log road cores digitally on site? | CoreDATA | The site record is the weak point, so the priority is cleaner logging, photographs, descriptions, and structured transfer to the office. | CoreDATA screenshots |
| Is the real problem the road core handoff between site and office? | CoreDATA / RCoreAnalyser | If both stages are involved, the paired workflow is the best fit because the same structured record can move into office-side reporting. | Workflow and output route |
| Do you need sample output before deciding? | DCPAnalyser or CoreDATA / RCoreAnalyser | When the buying decision depends on the final report rather than the capture step, review office-side proof first. | Sample DCP outputSample core output |
| Are you not yet sure where the bottleneck sits? | Start with the product split, then contact Experior | The safest route is to separate field capture, office reporting, and mixed workflows before choosing software. | Quick product routesAsk which tool fits |
| Do you need a complete road core workflow rather than one isolated tool? | CoreDATA / RCoreAnalyser | This route fits when site logging, images, descriptions, and final reporting all need to stay connected across the same job. | See the full workflow |
| Do you need just one DCP workflow step, not both? | DCP Data or DCPAnalyser | Choose the field app if the delay starts on site, or the desktop tool if the delay starts once the record reaches the office. | DCP field routeDCP office route |
Each summary explains where the product sits in the workflow and what proof route to use next.
DCP data capture app for recording Dynamic Cone Penetrometer tests on site.
DCP reporting software for office calculation and client-ready output.
Road core logging software and road core reporting software in one structured workflow.
The licensing and downloads page gathers the public software download routes and the contact path for licence questions in one place.