How It Works

How Checkmarkup
Works

Upload your survey files. Checkmarkup analyses your data, highlights issues, and helps you deliver accurate results — with confidence.

Step 1

Upload Files

Drag and drop .fld, .rpt, .txt or PDF reduction files. Up to 50 MB.

  • Multiple files per project
  • Encoding detected automatically
  • Originals are never modified
Step 2

Analyse Data

The QA engine parses station setups, observations and feature codes.

  • Preserves original line numbers
  • Reconstructs F1/F2 pairs
  • Detects common 12d / Trimble shapes
Step 3

Review Findings

Open the dashboard for filterable issues and click-through detail.

  • Color-coded severity
  • Suggested next action
  • Status workflow (open → resolved)
Step 4

Export QA Report

Generate a standalone HTML QA report ready to share.

  • Three sections: office / field / re-observe
  • Grouped by station setup
  • Disclaimer baked in
From raw file to reliable QA report
  1. Raw Survey Files
  2. Upload & Parse
  3. Detect Issues
  4. Export QA Report

What Happens Behind the Scenes

Each module is independent so we can add new rules and parsers without breaking what already works.

Parsing Engine

Pluggable parsers per file type — each one feeds the same rule engine.

Issue Detection Rules

Independent rule modules with thresholds, severity and fix categories.

Markup Viewer

Highlights anchored to original line numbers — never to bytes that can shift.

Report Generation

HTML first, PDF later. JSON output for downstream automation.

Why Teams Love This Process

Fast review

Hundreds of warning lines reduced to ranked findings.

Better traceability

Every issue references the exact source line.

Safe automation

No raw data is ever overwritten by the assistant.

Ready to See Checkmarkup in Action?

Free during early access. Bring your own .fld / .rpt files.