RoadScope
Join us at Breakbulk AmericasSept 22–23, 2026Houston, TX · Booth M01
Back to Documentation

Pre-Report Data Gaps Check

Before any report generates, RoadScope audits your POIs for missing measurements and classifications — fix the gaps or proceed with a disclosure.

6 min read

What the Check Does

When you click Generate Report for any report type, RoadScope first audits the survey's field data ("Checking data…"). If everything a professional deliverable needs is present, generation starts immediately. If not, an amber Data completeness check card pauses generation and tells you exactly what is missing — for example "3 of 42 POIs have gaps".

What Gets Audited

Each POI is checked for the data its category is expected to carry:

  • **Bridges & viaducts** — a height and/or weight measurement
  • **Overhead obstacles, signage, structures** — a height measurement
  • **Roads, paths, and work zones** — a width measurement
  • **Most operational categories** — an association with a route (a POI on no route cannot appear in a route report)
  • **Curfew POIs** — a structured schedule (days and/or start–end times); free-text-only curfews are flagged because they cannot feed calendar analysis

    • Unclassified POI types and missing route positions (chainage) are also reported. Reference categories like photos and staging notes are exempt.

    Fix or Proceed — Your Call

    The card lists the gap groups (informational in blue, warnings in amber, up to 8 shown with a "+N more" line) and offers two buttons: Go Back & Fix Data or Proceed Anyway. The check never blocks you — but if you proceed, the generated report includes a "Data Gaps — Field Data Completeness" section disclosing the gaps, so the deliverable is honest about what was not measured. When the survey is clean, that section is omitted entirely.

    Relationship to the AI Report Studio Gate

    The AI Report Studio's pre-publish checklist runs the same completeness audit as one of its checks, and treats missing measurements more strictly: a failed check there must be resolved or explicitly overridden with a logged justification.