Strata plan field verification software
Before a strata plan is lodged, or when a lot boundary is questioned, a surveyor walks the building and checks the plan against the structure: lot boundaries against walls, floors and ceilings, car spaces and storage cages against their lots, and areas against what was built. Each discrepancy has to be identified by lot and level. SurveyThanks treats every lot as a stored row, so findings attach to the right lot and the report lists them by lot.
Built for surveyors running teams of roughly 3–50 inspectors.
Sample Strata plan report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Strata plan report
Verification schedule — Level 2
- Building
- Fictional Residences, 15 Sample Lane
- Inspection date
- 25 August 2026
- Plan checked
- Draft strata plan, revision C
| Lot | Finding | Status |
|---|---|---|
| Lot 7 (apartment 201) | Walls and balcony as shown | Status: Agrees |
| Lot 8 (apartment 202) | Study wall built 400 mm into corridor | Status: Differs |
| Lot 7 car space (basement B1) | Line marking matches plan | Status: Agrees |
| Storage cage S12 | Built but not shown on plan | Status: Amend plan |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the strata plan report where your template puts it.
Per lot
- Lot number and apartment or unit
- Level
- Boundaries checked (walls, floor, ceiling, balcony)
- Agrees with plan (yes / no)
- Photo with comment
Part lots
- Car spaces
- Storage cages
- Linked principal lot
Common property
- Encroachments found
- Areas not inspected
Standards the report works to
- NSW ActStrata Schemes Development Act 2015 (NSW)
- Sets what a NSW strata plan must show and how building structure defines the boundaries of a lot.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the strata plan report gets built
Capture it once, offline
Your firm builds the strata plan field verification form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your marks, stations and monitoring points
Enter marks, stations and monitoring points once, as a register. Every one of your observations, rounds and movement readings then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The strata plan report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a strata plan report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The movement summary reports 4 mm at PM3; the round’s readings put it at 11 mm.
Checks a surveying framework usually carries
- Control, datum and epoch are stated for every deliverable
- Quoted tolerances match the project specification being reported against
- Every mark named in the text exists in the register
- Assumptions and sources of error are recorded rather than assumed
Questions
- Can a car space be linked to the lot it belongs to?
- Yes. Car spaces and cages are rows that reference their principal lot, so the report can show each lot with everything that belongs to it.
- Can we re-check the same building after rectification?
- Yes. The lots are already in the register, so a follow-up inspection records new findings against the same lots and the report shows what changed.
- Can the developer receive the findings before the full report?
- Findings are captured on site and the report can be rendered as soon as the crew is back in coverage, so a short discrepancy schedule can go out the same day.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other surveying work we cover
- Construction set-out recordsSet-out verification report
- Contour and detail surveysDetail survey report
- Deformation monitoring roundsMovement monitoring report
- GPR survey recordsGPR survey report
- Laser scan site capturesPoint cloud delivery report
- Mine survey pickupsMine survey report
- Utility locating recordsLocate mark-up report
- Volumetric drone surveysVolume report
Other disciplines
Rebuild your strata plan report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.