Resources

Resources for buyers comparing pavement investigation software.

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.

Guide 1: if the problem starts on site

Start with the tool that improves the first record, because weak field capture usually creates the later reporting delay.

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.

Guide 2: if the field record exists but reporting is slow

Start with the office-side tool when the delay is calculation, checking, formatting, or repeated report assembly.

What to look for

  • Spreadsheet churn after the field team has finished.
  • Repeated manual work to prepare client-ready outputs.
  • Good field records, but a slow reporting stage.

Guide 3: if the real problem is the handoff

Treat the handoff as its own workflow problem when the same data is being touched twice between site and office.

What to look for

  • The same job information entered once on site and again in the office.
  • Missing context when the report writer receives the record.
  • Different people handling field capture and final output with no clean continuation.

Proof routes

These are the fastest ways to judge whether the workflow is credible for your team.

Downloads

Review live download paths

Use the licensing and downloads page to review the current Android and Windows routes already exposed by the public site.