SurveyMarkup
Worked example
Public beta · documentation

How to use SurveyMarkup safely

A practical guide to the public beta tools, what advisory and unverified results mean, why a registered surveyor must sign off, and how to try everything with synthetic sample files — no real client data needed.

Get the sample filesTry the QA demo
Public beta guide

Use it safely

Advisory
Informational hint
Needs review
Look more closely
Unverified
Not confirmed to a standard
Surveyor sign-off
Required before deliverables
Start here

Five steps to try the public beta safely. Every result stays advisory and unverified.

  1. 1
    Try a synthetic sample

    Download a fictional .rpt / .csv / evidence file — no real client data needed.

  2. 2
    Read advisory labels

    Findings are labelled ADVISORY / NEEDS REVIEW / UNVERIFIED — never final.

  3. 3
    Review findings

    Step through OK / WARN / FAIL / REF / CHECK findings with the evidence beside each one.

  4. 4
    Export review summary

    Export an advisory review summary — a working file, not a survey deliverable.

  5. 5
    Discuss the workflow

    Request a short interview without sharing a client file.

Try a synthetic sampleRequest a workflow interview
Choose your task

Pick the tool that matches what you want to explore. During the synthetic public beta, use the bundled fictional examples only. Every output is advisory and unverified.

I have a survey reduction reportRead it and surface the lines worth reviewing first.Open Report ReaderI have a marked-up PDFLink evidence to findings and see what still needs review.Open PDF MarkupI have coded lineworkRun advisory data-quality checks before export.Open Map LineworkI just want to try itRun the engine on a fixed synthetic sample — no upload, no account.Open the QA demo

Not sure? Start with the documentation or the supported files register. Every tool stays advisory and unverified — not for survey deliverables; registered surveyor confirmation required.

On this page

1. Public beta overview

Advisory and unverified — not a survey deliverable.

SurveyMarkup is in public beta. Everything it produces is advisory — it is a checking aid, not a survey deliverable. Every professional decision remains with the registered surveyor.

Use the tools to speed up review, but a registered Australian surveyor must confirm any result before it is relied on.

Open the QA demo

2. How to use the QA demo

Findings are advisory only; a registered surveyor must confirm them.

The QA demo runs SurveyMarkup's deterministic checks on a fixed synthetic survey sample — no upload and no account needed.

Edit the fictional project/survey metadata, run the deterministic checks, and read the advisory findings. AI features are off in the current public beta.

Run the QA demo

3. How to use Map Linework

Coordinate outputs remain unverified; checks are advisory.

Map Linework runs advisory data-quality checks on coded geometry — MGA zone validity, CRS/datum, missing codes, open polygons, duplicate/zero-length geometry, closure, RL jumps, pole height, prism constant, GNSS quality and resection geometry.

It produces an export-readiness checklist. "Blocks export" means a data-integrity problem, not a legal judgement; exported CSV/GeoJSON must still be reviewed.

Open Map Linework

4. How to use Report Reader

Parsed values are advisory; your original file is never modified.

Report Reader demonstrates plain-text .rpt and .txt structures, labelled metadata, warning/error/misclosure/residual lines and a parse-confidence score.

Use the built-in synthetic sample during the public beta. Real customer-file intake and local file controls remain closed.

Open Report Reader

5. How to use the PDF Markup evidence workflow

Exports are advisory working files for registered-surveyor review.

PDF Markup links evidence/markup items to QA findings and shows an evidence summary: linked, unlinked, needs-review and missing items, plus measurement review and reviewer notes.

Real-file intake is closed during the public beta; the public demo runs on a synthetic evidence set. Exports are advisory working files for registered-surveyor review.

Open PDF Markup

6. Supported files

During the synthetic public beta, use the bundled fictional examples only.

The supported-files register lists what SurveyMarkup can import, review and export today, what remains gated, and what is not supported (for example, OCR for scanned PDFs or professional decision-making).

Use it as the authoritative file reference, not as a promise of downstream compatibility.

View supported files

7. Advisory results and human review

Every professional decision remains with the registered surveyor.

Every result is labelled. ADVISORY means an informational hint. NEEDS REVIEW means a reviewer should look more closely. UNVERIFIED means a tolerance/measurement result has not been confirmed against the applicable standard.

SurveyMarkup labels the scope and limits of each result. A registered surveyor must review the source evidence before any professional reliance.

8. Why registered surveyor sign-off is required

Surveyor review and sign-off stay manual.

SurveyMarkup does not determine whether a survey satisfies regulatory or cadastral requirements, and it never sets a result as surveyor-confirmed on its own.

A registered/licensed surveyor must review and sign off before any deliverable, lodgement, or legal/cadastral decision. This boundary is intentional and is not bypassed in the beta.

9. AI explanation safety

AI features are off in the current public beta.

AI features are off during the synthetic public beta. Deterministic checks and their stated limits remain the launch workflow.

If explanatory AI is introduced later, it will remain separate from numeric results and professional decisions.

10. Data privacy — do not upload confidential files during beta

Use the bundled fictional examples only; source files stay unchanged.

Please do not upload confidential or real client data during the public beta. Use the synthetic sample files below to try every tool safely.

Where parsing happens in your browser (Report Reader), your file is read locally; in all cases your original file is preserved and never modified.

Data handling notes

11. Future registered-surveyor sign-off workflow

Design preview only — it never confirms a rule or a survey.

We are designing a workflow to track a registered surveyor's review — status, reviewer details, the rule source/version/effective date, unresolved items, evidence and comments. Why sign-off is required: SurveyMarkup is a checking aid and cannot make the professional call.

What the current beta does: it shows advisory, unverified findings only. What the future workflow may support: structured review tracking and an audit trail. What stays manual: a registered surveyor's professional judgement and the sign-off itself.

It is a design preview only — it tracks workflow status, never confirms a rule, and never sets surveyor_confirmed=true. Registered-surveyor sign-off stays manual.

See the workflow design preview

12. CRS, datum and geoid plausibility (GDA2020 / AUSGeoid / AHD)

Plausibility metadata only — not coordinate authority. Registered surveyor confirmation required.

SurveyMarkup previews Australian coordinate context — the GDA2020 and GDA94 datums, MGA zones 49–56, the AUSGeoid2020 and AUSGeoid09 geoid models, and AHD/RL heights — and flags pairings that look inconsistent (for example a datum and geoid model that are not conventionally used together).

These are advisory metadata-plausibility checks, not coordinate authority. SurveyMarkup leaves coordinates, datums, zones and heights unchanged. A flagged mismatch is a prompt to look more closely, never a professional determination.

Because the checks read declared metadata, a value can be present and self-consistent while still being the wrong choice for the actual data. Every result stays UNVERIFIED, and a registered surveyor must confirm the correct datum, zone and geoid model against the project brief and applicable standards before reliance.

See how the advisory checks work

13. Free field tools

Free advisory working aids — advisory and unverified, never survey deliverables.

The /tools section hosts eight free advisory calculators and validators — COGO (bearing, distance and area), grid ↔ ground (combined scale factor), traverse misclose, level loop closure, a point file validator, a coordinate and datum converter, a deliverable checklist generator and a datum/metadata quick-check. Every tool shows the full working for each calculation so each step can be re-checked.

Where a published guideline applies, results only ever read “within guideline” or “exceeds guideline — review”, and guideline values are read from the published advisory rule packs. Every result is advisory and unverified — not a survey deliverable — and a registered surveyor must confirm it independently before reliance.

Open the field tools
Show your working · advisory only

How the advisory checks work.

Every major check explains what it inspects, the formula or heuristic it uses, the default threshold and where that threshold comes from, and its false-positive / false-negative limits. Thresholds are triage defaults that need registered-surveyor review — nothing here is a pass/fail conclusion, and every result stays advisory and unverified.

How this advisory check worksMGA zone plausibility (49–56)
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Reads the project's stated MGA zone and checks it is one of the Australian MGA zones 49–56.
Formula / logic
Integer range test: the zone number must satisfy 49 ≤ zone ≤ 56. A value outside the range is flagged; a missing value is reported as advisory, not failed.
Threshold
MGA zones 49–56 (default plausibility band)
Threshold source
The 49–56 range reflects mainland Australian MGA zones. It is a plausibility band only — it does not confirm the data was actually captured or computed in that zone. Confirm the correct zone against the project brief and office standards.
False positive
A correct project that legitimately uses an off-band or local grid would be flagged even though it is fine for its purpose.
False negative
A plausible-but-wrong zone (e.g. zone 55 typed instead of 56) passes the range test while still being the wrong zone for the data.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — plausibility band only; confirm the applied zone against applicable survey requirements and office standards.
How this advisory check worksCRS / datum present
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Checks that both a coordinate reference system and a datum are stated on the project metadata.
Formula / logic
Presence test: CRS and datum strings must both be non-empty. Missing values are reported as advisory so they are not silently assumed.
Threshold
Both CRS and datum must be declared
Threshold source
There is no numeric threshold — this is a metadata-completeness prompt. It checks that a value is declared, never that the declared value is correct.
False positive
Data that carries its CRS/datum elsewhere (e.g. a sidecar file) is flagged because the field on this metadata is blank.
False negative
A declared but incorrect CRS/datum string passes the presence test while still being wrong.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — completeness prompt only; the declared CRS/datum still needs registered-surveyor confirmation.
How this advisory check worksGDA / AUSGeoid pairing
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Looks at the declared datum (GDA2020 / GDA94) and the declared geoid model (e.g. AUSGeoid2020) and flags pairings that look inconsistent.
Formula / logic
String-pairing heuristic: GDA2020 is conventionally paired with AUSGeoid2020; other combinations are surfaced as advisory for a human to confirm. It is a naming-consistency hint, not a transformation check.
Threshold
GDA2020 ↔ AUSGeoid2020 (conventional pairing)
Threshold source
The expected pairings are conventions, not a computation. SurveyMarkup only compares declared datum/geoid names. Confirm the correct datum, geoid model and any transformation for the job.
False positive
A deliberate, valid mixed-epoch workflow is flagged as inconsistent when it is intentional.
False negative
A self-consistent pair of names can still be the wrong choice for the actual coordinates, and that passes silently.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — naming-consistency hint only; no transformation is computed. Confirm against applicable standards.
How this advisory check worksDuplicate point detection
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Finds pairs of points whose horizontal positions sit on top of each other within a small tolerance.
Formula / logic
Planar distance: for each pair, d = √((ΔE)² + (ΔN)²). If d ≤ the duplicate tolerance the pair is reported as coincident.
Threshold
0.005 m (default; needs review)
Threshold source
Default duplicate tolerance is 0.005 m (5 mm). It is a triage default chosen for synthetic demo data, not an office or regulatory value — it needs registered-surveyor review against your capture method.
False positive
Two genuinely distinct features captured very close together (e.g. stacked utilities) are reported as duplicates.
False negative
Near-duplicates just beyond 5 mm — common with GNSS scatter — are not flagged.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — 0.005 m is a default triage tolerance; confirm the appropriate value for the survey.
How this advisory check worksZero-length geometry
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Flags line/polygon segments whose start and end points are effectively the same position.
Formula / logic
Segment length L = √((ΔE)² + (ΔN)²); a segment with L at or below the duplicate tolerance is treated as zero-length.
Threshold
0.005 m (default; needs review)
Threshold source
Uses the same 0.005 m default as duplicate detection. It is a data-integrity heuristic, not a survey measurement, and needs review.
False positive
Deliberate degenerate markers (a point modelled as a 1-vertex string) are flagged.
False negative
A very short but non-zero erroneous segment above the tolerance is not caught.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — shares the duplicate tolerance default; confirm for the dataset.
How this advisory check worksOpen polygon
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
For strings marked as polygons (should-close), checks whether the last vertex returns to the first.
Formula / logic
Gap = distance from the last vertex back to the first. If the gap exceeds the open-polygon tolerance the ring is reported as not closed.
Threshold
0.05 m (default; needs review)
Threshold source
Default open tolerance is 0.05 m. It is a drafting/topology default for triage, not a survey closure standard, and needs registered-surveyor review.
False positive
An intentionally open boundary modelled as a polygon is flagged.
False negative
A ring closed within 0.05 m but with the wrong intermediate shape still passes the closure gap test.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — 0.05 m is a triage default; confirm against drafting/office standards.
How this advisory check worksClosure / misclose vector
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Estimates the misclose of a closed string by comparing the computed return position with the start.
Formula / logic
Misclose magnitude = √((ΣΔE)² + (ΣΔN)²) around the ring. Values between the advisory and open thresholds are surfaced as advisory; this is a magnitude only, not a least-squares adjustment.
Threshold
advisory 0.005 m / open 0.05 m (defaults; need review)
Threshold source
Advisory closure default is 0.005 m and the open limit is 0.05 m. These are demo triage bands, not a proportional misclose standard (e.g. 1:n) and not an adjustment — they must be reviewed.
False positive
A long traverse with an acceptable proportional misclose can exceed a fixed 5 mm band and be flagged.
False negative
A short ring with a small absolute misclose can pass while still being poor proportionally.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — fixed-distance triage bands only; no adjustment is performed. Confirm proportional/closure requirements with a registered surveyor.
How this advisory check worksRL jump
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Looks for large vertical steps in reduced level (RL) between consecutive related points.
Formula / logic
ΔRL = |RL₂ − RL₁| between sequential points on a string; a step above the RL-jump tolerance is reported as advisory.
Threshold
1.0 m (default; needs review)
Threshold source
Default RL-jump tolerance is 1.0 m. It is a generic triage value with no terrain context — steep ground or kerb/structure detail can legitimately exceed it — so it needs review.
False positive
Genuine vertical features (retaining walls, batters, kerbs) trip the jump test.
False negative
A wrong RL within 1.0 m of its neighbour is not flagged.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — 1.0 m is a context-free default; confirm for the terrain and feature type.
How this advisory check worksPole height
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Sanity-checks the recorded pole/target height against a plausible maximum.
Formula / logic
Range test: pole height must not exceed the maximum pole tolerance; an over-range value is reported as advisory.
Threshold
4.0 m max (default; needs review)
Threshold source
Default maximum is 4.0 m. It is a typical-equipment plausibility ceiling, not a calibrated limit, and should be confirmed against the actual equipment used.
False positive
An unusual but valid tall-pole or offset setup is flagged.
False negative
A mistyped-but-plausible height (e.g. 2.0 m instead of 2.5 m) passes the range test.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — 4.0 m is an equipment plausibility ceiling; confirm against the gear used.
How this advisory check worksPrism constant
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Compares the prism constant used against the expected prism constant for the job.
Formula / logic
Difference test: |used − expected| compared against the prism tolerance; a mismatch beyond tolerance is reported as advisory.
Threshold
0.001 m (default; needs review)
Threshold source
Default tolerance is 0.001 m (1 mm). Sign conventions and expected values vary by manufacturer and office practice — confirm the correct expected constant and sign convention.
False positive
A different but correctly handled prism/offset convention is flagged as a mismatch.
False negative
A wrong constant within 1 mm of the expected value passes.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — sign conventions vary; confirm the expected constant with a registered surveyor.
How this advisory check worksGNSS quality / PDOP
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Surfaces GNSS quality indicators such as PDOP and reported horizontal/vertical sigmas against plausible ceilings.
Formula / logic
Threshold tests: PDOP ≤ max, σH ≤ limit, σV ≤ limit. Values beyond the ceilings are reported as advisory. SurveyMarkup does not recompute the GNSS solution.
Threshold
PDOP 4.0 / σH 0.03 m / σV 0.05 m (defaults; need review)
Threshold source
Defaults are PDOP ≤ 4.0, σH ≤ 0.03 m, σV ≤ 0.05 m. These are generic triage ceilings, not a network/RTK acceptance standard — confirm against your positioning method and office standards.
False positive
A valid solution under difficult sky conditions can exceed a generic ceiling and be flagged.
False negative
Good-looking DOP/sigma values do not establish a correct fixed solution; a bad fix within the ceilings passes.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — generic ceilings only; confirm acceptance criteria for the positioning method.
How this advisory check worksResection geometry / danger circle
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Checks that a resection used enough reference points with adequate angular spread (a danger-circle proxy).
Formula / logic
Counts reference points and inspects minimum angular separation. Below the minimum point count or minimum separation, the geometry is surfaced as advisory/weak.
Threshold
≥ 3 points, ≥ 30° separation (defaults; need review)
Threshold source
Defaults are at least 3 points and at least 30° minimum separation. These are simplified proxies for resection strength, not a full danger-circle or variance analysis — they need review.
False positive
A strong real-world setup with tight-but-adequate geometry can be flagged by the simplified proxy.
False negative
A configuration that meets the count/spread proxy can still sit near the danger circle in reality.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — simplified geometry proxy only; confirm resection strength with a registered surveyor.
How this advisory check worksReport Reader parse-confidence
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Reports how much of a plain-text survey report SurveyMarkup could confidently recognise and label.
Formula / logic
Heuristic score from the proportion of recognised, labelled lines/blocks versus unrecognised text. A low score is reported as a partial parse, prompting manual review of the original.
Threshold
Heuristic 0–100% recognised (not a correctness score)
Threshold source
The confidence score is a parsing heuristic, not a measure of survey correctness. A high score means 'well recognised', never 'correct'. No professional threshold is asserted.
False positive
A neatly formatted report can score high while containing values that are wrong.
False negative
An unusual vendor format can score low even though its contents are correct.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — recognition heuristic only; always review the original report.
How this advisory check worksF1 / F2 observation classification
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Attempts to label face-left / face-right (F1/F2) observation lines parsed from a report.
Formula / logic
Pattern-matching on common report layouts to tag observations as F1 or F2. It is a labelling aid; it does not compute or check the observations themselves.
Threshold
Pattern-based F1/F2 labelling (heuristic)
Threshold source
No numeric threshold — this is a text-classification heuristic that varies by vendor format and needs human confirmation.
False positive
An unusual layout can cause an observation to be mis-tagged F1/F2.
False negative
Observations in an unrecognised layout may be left unclassified.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — labelling heuristic only; confirm face conventions against the source report.
How this advisory check worksUnparsed vendor blocks
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Marks regions of a report that SurveyMarkup could not confidently recognise so they are not silently dropped.
Formula / logic
Any contiguous text not matched to a known label is retained and surfaced as an 'unparsed' block for the reviewer.
Threshold
All unrecognised text retained (transparency)
Threshold source
No threshold — unparsed blocks are shown for transparency. Their presence does not imply a problem, and their absence does not imply correctness.
False positive
Harmless vendor preamble can appear as an unparsed block and look like a gap.
False negative
Recognised-but-misread text is not surfaced as unparsed even though it may be wrong.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — transparency aid only; review unparsed blocks in the original report.
How this advisory check worksPDF evidence state (linked / unlinked / needs-review / missing)
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Summarises how evidence/markup items relate to QA findings: linked, unlinked, needs-review, or missing.
Formula / logic
Set bookkeeping: each evidence item is mapped to a finding (linked), left unmapped (unlinked), flagged for a human (needs-review), or expected-but-absent (missing). It is workflow tracking, not a measurement.
Threshold
Linkage states only (no measurement)
Threshold source
No numeric threshold. States describe linkage only; 'linked' means an item was associated with a finding, never that the finding is resolved or that the survey is acceptable.
False positive
An item marked needs-review may already be fine; the state is a prompt, not a defect.
False negative
An item shown as linked can still be linked to the wrong finding.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — workflow bookkeeping only; a registered surveyor confirms the evidence.
How this advisory check worksAI explanation safety
Advisory and unverified — registered surveyor confirmation required. Not for survey deliverables.
What it checks
Describes how AI text is produced and bounded while keeping it separate from reviewer confirmation.
Formula / logic
AI explanations are generated from the engine's own output, shown unchanged. Numeric and boundary guards stay on; the AI does not invent numbers, change tolerance results, or set any confirmation flag.
Threshold
Explanatory text only (can be wrong)
Threshold source
No threshold. AI text is explanatory only, can be wrong, and is rate-limited/capped. It cannot set a finding or surveyor-confirmation state.
False positive
AI wording can over-state confidence in plain language even when the underlying finding is advisory.
False negative
AI text can omit a caveat that matters; always read the engine finding and the original data.
Confirmation
Registered surveyor confirmation required — this result stays unverified.
Provenance
Provenance note — AI text is an explanation aid only; reviewer confirmation stays separate.

These explainers describe data-quality triage only. They do not make a survey or coordinate decision and do not replace registered-surveyor judgement. A registered surveyor must validate every threshold and confirm every finding before reliance.

Synthetic data

Download synthetic sample files.

Try every tool without uploading real client data. Each file is fictional, carries the PUBLIC BETA — ADVISORY ONLY note, and produces advisory, unverified output only.

Synthetic sample files
README
PUBLIC BETA — ADVISORY ONLY. Not for survey deliverables. These files are synthetic — use them to try the tools without uploading real or confidential client data. Every result is advisory and unverified; a registered surveyor must confirm it.
  • .rptReport Reader — synthetic .rpt
    Download
    Demonstrates
    A full plain-text reduction report with instrument, station, misclosures, residual and control points.
    May trigger
    Missing face observation, unclear setup method, high residual (UNVERIFIED), pole-height (ADVISORY) and parse-confidence warnings.
    Next step
    Review the parsed metadata and advisory panels, then export the HTML summary. Every professional decision remains with the registered surveyor.
  • .txtReport Reader — synthetic .txt
    Download
    Demonstrates
    A simpler plain-text report with a single caution line and a clean error count.
    May trigger
    One advisory warning line; low overall warning count.
    Next step
    Compare the extracted summary lines against the original; treat all output as advisory.
  • .csvMap Linework — synthetic .csv
    Download
    Demonstrates
    Coded survey points (KERB, BLDG) with fictional MGA-style coordinates.
    May trigger
    Missing feature code, a near-duplicate point and an open polygon for the data-quality checks to flag.
    Next step
    Run the field-data QA checks and review the export-readiness checklist before any export.
  • .geojsonMap Linework — synthetic .geojson
    Download
    Demonstrates
    The same synthetic linework as GeoJSON features, carrying the advisory note.
    May trigger
    CRS / coordinate correctness must be confirmed by a surveyor before downstream use.
    Next step
    Inspect the geometry in your GIS, but confirm CRS and coordinates before relying on it.
  • .jsonPDF Markup — synthetic evidence set
    Download
    Demonstrates
    Four evidence items: one linked, one unlinked, one needs-review and one missing, with a measurement and reviewer notes.
    May trigger
    NEEDS REVIEW (missing + needs-review), ADVISORY (unlinked) and UNVERIFIED (measurement) advisories.
    Next step
    Review linked vs unlinked evidence and the missing-evidence advisories, then export the evidence summary.
Design preview · advisory only

Registered-surveyor review workflow (design preview).

A preview of the future sign-off workflow. It tracks workflow status only — it never confirms a rule, never sets surveyor_confirmed=true, and never creates a survey deliverable.

Design preview only — this workflow does not confirm any survey rule, does not set surveyor_confirmed=true, and does not create a survey deliverable.

Final statutory and professional assessment requires a registered Australian surveyor. Engine results are checking aids only. Every deliverable, lodgement, legal/cadastral decision and sign-off remains with a registered/licensed surveyor.

1 · Review workflow status
Awaiting registered surveyordesign preview
  1. Not started
  2. Draft review
  3. Awaiting registered surveyor
  4. Comments received
  5. Changes required
  6. Future confirmation placeholder
  7. Blocked — unverified
2 · Required registered surveyor details
Reviewer name
(unassigned — design preview)
Reviewer role
Registered surveyor (to be assigned)
Registration no.
—
Jurisdiction
NSW (demo reference)

Placeholder fields — no surveyor is assigned in this preview.

3 · Rule source / version / effective date
Rule source document
Jurisdiction surveying regulation (demo reference)
Source version
demo-v0
Effective date
—
Reviewed at
—
4 · Unresolved items
  • Loop 5 closure 0.045 m — review against the applicable tolerance (unverified).
  • Face observations not detected — needs review.
5 · Evidence needed
  • Synthetic QA demo report
  • Synthetic PDF evidence set (ANN-001…ANN-004)
6 · Comments / exceptions
Comments
  • Design preview — no registered-surveyor review has occurred.
Exceptions
  • Tolerance set not surveyor-confirmed (stays unverified).
7 · What this workflow does NOT do
  • Does not set surveyor_confirmed=true or confirm any survey rule.
  • Keeps tolerance confirmation and every QA-engine result unchanged and UNVERIFIED.
  • Keeps every legal and regulatory acceptance decision with the responsible professional.
  • Produces an advisory review record; every survey deliverable remains the registered surveyor's responsibility.
  • A registered surveyor's professional judgement and sign-off remain entirely manual and outside this tool.
8 · Future confirmation placeholder
Confirmation disabled in design preview

A future registered-surveyor confirmation step would live here. It is intentionally inert: there is no control that sets surveyor_confirmed=true, and the audit note records that no confirmation was performed — “No confirmation performed in this design preview; surveyor_confirmed stays false.”.

Wording you will see across SurveyMarkup: advisory, needs review, unverified, registered surveyor confirmation required, and not for survey deliverables. Every professional decision remains with the registered surveyor.

Guides

Survey workflow guides

Advisory, unverified walkthroughs for common Australian survey review workflows. Every output needs registered surveyor confirmation and is not for survey deliverables.

Survey report QA softwareReport review · advisorySurvey linework softwareLinework review · advisoryGDA2020 / MGA review toolsAustralian CRS · advisoryDXF export for survey lineworkDXF handoff · advisoryCSV to DXF workflowCSV → DXF · advisoryPDF markup for surveyorsDrawing review · advisoryBluebeam alternativeComparison · advisorySurvey field data checkingField-data review · advisoryCommon survey field mistakesGuide · advisorySurvey QA checklistChecklist · advisory12d-friendly exportHandoff · advisorySupported survey file formatsFormats · advisoryEngineering survey workflow softwareField-to-office · advisoryCadastral survey QA advisory toolCadastral · advisory onlyCivil construction survey reviewCivil construction · advisory
Reference

Australian surveying glossary

Plain-language definitions of the Australian survey terms SurveyMarkup works with. SurveyMarkup previews and surfaces these signals for review. Coordinate authority and every professional decision remain with the registered surveyor.

GDA2020
Geocentric Datum of Australia 2020 — Australia's current national geodetic datum. SurveyMarkup surfaces a dataset's declared datum for review; coordinate authority remains a professional decision. GDA2020 / MGA review tools.
GDA94
An earlier Australian datum, largely superseded by GDA2020. Transforming between GDA94 and GDA2020 is a professional task; SurveyMarkup only previews the declared datum. GDA2020 / MGA review tools.
MGA2020 (Map Grid of Australia)
The Universal Transverse Mercator projection used with GDA2020, divided into zones. Use MGA2020 wording where the grid associated with GDA2020 matters. GDA2020 / MGA review tools.
MGA zones 49–56
The UTM zones covering the Australian mainland and islands. A dataset's zone is part of its CRS metadata that a reviewer should confirm before export. Map Linework CRS preview.
AHD (Australian Height Datum)
The national vertical datum used for heights (reduced levels) across Australia.
AUSGeoid
A geoid model relating ellipsoidal heights to AHD heights. Height transformations remain a professional responsibility.
PSM (Permanent Survey Mark)
A stable, recoverable mark with published coordinates used as survey control.
Traverse misclose
The closure error when a traverse returns to its start or to a known point. A large misclose is an advisory prompt to review the observations. Review reports in Report Reader.
F1/F2 (face left / face right)
Two instrument faces used to observe the same target; the spread between them helps detect pointing or collimation error. SurveyMarkup may flag an unusual F1/F2 spread for review. Review reports in Report Reader.
Prism constant
A fixed offset for a reflector/prism that must match the instrument setting; a wrong value shifts measured distances.
RL (Reduced Level)
A height expressed relative to a vertical datum such as AHD.
Residual
The difference between an observed value and its adjusted (best-fit) value; large residuals are worth a closer look. Review reports in Report Reader.
Sigma / standard deviation
A precision indicator reported by adjustment software. SurveyMarkup surfaces reported sigma values; it does not re-run the adjustment. Review reports in Report Reader.
Resection
Determining an instrument's position from observations to known points; weak geometry reduces reliability and is worth reviewing.
CRS (Coordinate Reference System)
The datum, projection and units a dataset uses. Confirming the CRS is essential before any CAD or GIS handoff. Map Linework CRS preview.
Reduction report (.rpt)
A plain-text output from survey computation software summarising observations, adjustments and checks. The Report Reader extracts advisory review signals from these. Open the Report Reader.
Feature code
A short code classifying a surveyed point or line (for example KERB, FENCE, TREE) so linework can be structured for drafting. Open Map Linework.
Combined scale factor
The factor relating grid distances to ground distances; mixing grid and ground without applying it introduces error.
DXF / GeoJSON / KML
Common CAD and GIS exchange formats. SurveyMarkup can export advisory working files in these formats for review — not as survey deliverables. Supported files.

Safety & scope

SurveyMarkup helps prepare and review working information. Every professional decision remains with the registered surveyor, and original data and final outputs require qualified review.

Assistance only - professional review remains required.