Grid zone: 55 · E 501 842.310 · source context retainedAFTER PROCESSING · BEFORE PROFESSIONAL SIGN-OFF
Review before you sign off.
An independent, working review desk for completed survey files — designed, built and tested end to end by one surveyor who also writes the software. Every tool on this site is live and functional; this is the working portfolio.
The site runs on fictional example data only and real client files are not accepted. Every calculator works directly in your browser — nothing you type is uploaded.
Report Reader trace
Declared zone and coordinate context need review.
The attention item keeps line 3348 attached; it does not decide the intended project zone.
Confirm the intended zone against project control and surveyor instructions before downstream export.
Findings point back to available evidence
Examined and excluded material stays visible
Original working files remain unchanged
Your registered surveyor retains sign-off
Useful working checks, open to everyone.
Each tool runs in your browser, shows its method and comes from the same registry as its working route. No entered working values are uploaded by these eight utilities.
COGO Calculator — Bearing, Distance & Area
Join, radiate and polygon area from grid coordinates, with the full working shown for every step — including the grid-vs-ground area note. Free advisory working aid.
Grid ↔ Ground Converter — Combined Scale Factor
Point and line scale factor, height factor and combined scale factor for MGA2020 — convert grid and ground distances both ways with the full working shown.
Traverse Misclose Checker
Linear and angular misclose, relative precision and an advisory Bowditch comparison. Tolerance guidelines are read from loaded advisory rule packs, never hardcoded.
Level Loop Closure Checker
Loop misclose against a project-selected C√K guideline grouping, with advisory distribution and the full working shown; no survey order or jurisdiction is inferred.
Point File Validator
Advisory duplicate-id, coincident-point, easting/northing-order and zone-extent checks with browser-local parsing and a bundled fictional example.
Coordinate & Datum Converter — MGA2020
Geographic ↔ MGA2020 grid with zone, point scale factor and grid convergence shown, explicit GDA94 lineage and method selection, and a copyable method statement for every result.
Deliverable Checklist Generator
A printable, per-state checklist of questions to ask before a survey package leaves the office. Advisory prompts only — it never decides anything for you.
Datum & Metadata Quick-Check
Paste header blocks from project files to compare datum, zone, geoid and epoch declarations in one consistency table. Advisory — confirm against the source files.
See the wider system behind the calculators.
Public product images and demonstrations use fictional data. Signed-in workflows, demos and prototypes are labelled separately in the evidence-backed catalogue.
Synthetic previewProject Review Pack
A project-backed review workspace that keeps files, coverage, source-linked attention items and reviewer decisions together.
- Account access is invitation-only.
- Findings are advisory and never replace professional review or sign-off.
Synthetic previewSource-linked Report Reader
Reads supported report text, keeps attention items tied to source lines and exposes what was not examined.
- The public preview uses fictional survey data.
- A registered surveyor must decide whether any item matters to the job.
Synthetic previewPDF Viewport Pin Prototype
Experiments with saved advisory pins over the first visible PDF viewport without changing the source document.
- This is viewport pinning, not page-anchored document markup; native PDF scrolling or zoom can move the document beneath a pin.
- The public preview is fictional. The experimental signed-in route is not exposed as an operational project tool.
The evidence is spread across the completed job.
The final office pass often means reconstructing what happened across reports, plans and reviewer notes before deciding what deserves attention.
Report and reduction text
Warnings, misclose lines, metadata and observations can be separated by hundreds of lines.
Plan and file context
PDF, point and linework evidence often lives in a different view from the review note.
Reviewer handoff
What was examined, dismissed or left open can depend on email, memory or an informal checklist.
One Review Pack. Four clear steps.
Report Reader leads the workflow. Supporting evidence, honest coverage and reviewer decisions stay connected in one handoff.
Start with the source report
Report Reader organises supported RPT and TXT content and keeps each finding tied to its source line.
Add supporting evidence
Fictional PDF and map examples add page, coordinate and linework context without a customer-file upload.
Review coverage and findings
See what was examined, what was skipped and which items still require professional judgement.
Return one review summary
Record reviewer notes and hand back a source-linked advisory summary. Original files stay unchanged.
CORE INSTRUMENT · REPORT READER
Advisory read only. Confirm against booked observations.
Start from the source, not a dashboard score.
Report Reader is the working public instrument. It reads supported RPT and TXT content in the browser and keeps attention items tied to their source lines.
The evidence, explanation and reviewer state travel together.
Show what ran—and what did not.
A useful review begins with the file manifest and exclusions. Unsupported or partial material should never disappear behind a confident-looking result.
The agreed working-file set
Readable sections and records
Unsupported, skipped or partial material
Open decisions and professional judgement
Start with the fictional workflow.
The contact form goes straight to the inbox behind this site. Conversations use the fictional example; no client file is ever requested.
Read security and handlingBuilt by Tim Albash.
Brisbane-based survey technician with a civil-engineering background and field and office experience across high-rise set-out, construction, cadastral, subdivision and detail survey work.
Roles and projectsYour surveyor decides.
- Make statutory decisions for survey work
- Replace registered surveyor judgement
- Determine cadastral boundaries
- Alter source files
One surveyor, one codebase.
SurveyMarkup is designed, built, tested and operated by Tim Albash — a surveyor who works across the full stack: field workflow, geometry and QA logic, the API behind it, the browser tools in front of it, and the deployment it runs on.
This site is the working demonstration. If you are reviewing a potential team member or collaborator, the evidence is the product itself.
Get in touchSurvey workflow and QA rules on one side; FastAPI, PostgreSQL, Redis, Next.js, Docker and automated browser testing on the other.
Thousands of automated backend and browser tests, encrypted backups and rehearsed deployments stand behind what you see.
Operated by Tim Albash, sole trader, ABN 50 427 523 590 — the same identity published on the legal pages.
Fictional example data, advisory-only wording and visible limits are deliberate — the same care applies to real work.
Start with the fictional worked example.
See the source-linked Review Pack without an account or upload. The tools, the tests behind them and the trail they leave are the point of this site.