What to look for
- Handwritten notes or loose records during DCP testing or road core logging.
- Different operators recording the same type of job in inconsistent ways.
- The office rebuilding the job before reporting can begin.
Resources
Use this page to separate site capture, office reporting, and handoff problems before you commit to a product conversation.
These short guides are written for engineers, testing contractors, technicians, and consultants who need a practical next step rather than generic marketing copy.
Start with the tool that improves the first record, because weak field capture usually creates the later reporting delay.
Use DCP Data for Dynamic Cone Penetrometer field capture or CoreDATA / RCoreAnalyser for road core logging and reporting.
Start with the office-side tool when the delay is calculation, checking, formatting, or repeated report assembly.
Use DCPAnalyser for DCP reporting or CoreDATA / RCoreAnalyser if the job is road core reporting.
Treat the handoff as its own workflow problem when the same data is being touched twice between site and office.
Use the products page to compare workflows, then use the contact page if you want to talk through the full sequence.
These are the fastest ways to judge whether the workflow is credible for your team.
Use DCP Data and CoreDATA / RCoreAnalyser to review live Google Play screenshots from the Android tools.
Use the sample DCP output route or the sample road core output route.
Use the licensing and downloads page to review the current Android and Windows routes already exposed by the public site.