Free property checks

Check any Australian address — free, instant, no account

Zone, overlays, verified lot boundary, easements and design wind region, straight from government services. One pass, one screen, downloadable as a PDF.

Free, no account, not metered. Runs the full site brief — zone, overlays, verified lot boundary, easements and design wind — and gives you the PDF.

Pick your check

Free here, billed per report elsewhere

Typical per-address pricing elsewhere in the Australian property-data market, against what the Draftly site brief includes.
CheckProperty-data platformsDraftly site brief
Flood report $39–$69 Free
Bushfire pre-screen $39–$69 Free
Planning PDF around $9 Free
Geotechnical desktop study around $119 Free
State heritage certificate $63.04 Free

Source: Draftly's public comparison audit, last updated 2026-08-12 — the same figures shown at /compare/. Figures are point-in-time and describe the property-data category generally, not any one named vendor; verify current pricing with the vendor. A state heritage certificate fee is set by the state heritage body.

How Draftly compares

DimensionDraftlyCanibuildBuildertrend / CoConstructArchistarProperty-data platformsClearCalcsCouncil & state portals
Address-to-answer speedType an address → a useful answer, with nothing in between.45144.51.51
Planning data reliabilityHow much of the planning answer is real government data vs inference.4414.5415
Visual UXMap, drag-and-drop, live feedback — how it feels to use.453.5433.51
Drafting & exportDrawings, DXF/PDF sets, documents a council or certifier accepts.4.521.5112.51
Engineering defensibilityStructural calculations, member schedules, AS/NZS-referenced outputs.421114.51
Commercial readinessPricing clarity, payments, onboarding, market maturity.3.53.54.543.53.5—
Partner / trade ecosystemPartner programs, integrations, API access, white-label.4.533.52.5221
Running the buildSchedule of works, trade dispatch, purchase orders, and what the homeowner can see.31.54.5111—
What you get before payingHow much of a usable answer arrives without a subscription, a per-report fee, or a sales call.511.51.52.523

Scores are calibrated for ONE job: the address-to-permit-to-built workflow for Australian backyard structures and small residential builds — for trades, builders and homeowners. They are not a verdict on general construction software. A tool can score low here and be excellent at what it is actually built for. Pergolas and decks are Draftly’s validated launch offer; the other structure types available in Draftly (carports, sheds, fences, retaining walls, granny flats and more) are in Beta.

Scored 1–5. “—” means the dimension does not apply to that product. Last updated 2026-08-12. See the full comparison · Report an error.

Where Draftly is weak

This table is an audit, not a brochure. These are our own limitations, published because a comparison that only flatters us is worth nothing.

  • Planning zones come live from government APIs in 5 states/territories (VIC, NSW, QLD metro councils, TAS, ACT). SA is answered from a shipped snapshot of the PlanSA zones layer (~3 m simplified), not a live call, because SA has no public point-query service — the brief says so on the result rather than showing a fetch time that would imply otherwise. WA/NT and full per-state overlay completeness are still gaps; uncovered lookups fall back to guided manual entry, never a fabricated answer
  • Hazard depth is thinner than the dedicated property-data platforms. Heritage is queried in all six wired jurisdictions and acid sulfate soils across the NSW councils that publish them; bushfire and flood are wired where a government service exposes them. Noise, school catchment and soil hazards outside NSW are not aggregated nationally
  • AI is used only for extracting details from documents you upload and for the help assistant — never for planning data (address research is a pure government-API lookup)
  • Draftly Works is new. The schedule, gates, orders and claims are built and tested, but no build has yet been run end to end on it by a customer
  • Purchase orders and progress claims exist as tested engines with database rules behind them, and neither has a screen in the app yet. Xero sync is not connected either — so a purchase order will be a record in Draftly until both land
  • A stage completion asks for a photo and a readiness checklist. The gate is enforced; the photo file itself is not stored yet, so the evidence is a prompt rather than a record
  • The dependency cascade — recalculating downstream dates when a stage runs late, and naming which trades are affected — is built and tested, but the schedule screen still shows the baseline plan. It does not yet move dates on you
  • Billing handles the happy path: new subscriptions, upgrades and cancellations. A failed card or a refund is not yet reflected automatically in the product — those are handled by hand in Stripe today
  • Commercial maturity lower than the volume-builder platforms — live payments and a subscriptions interface shipped 2026-08-04, but still pre-public-launch
  • Mobile UX still being polished (Section-3 site-design rework in progress)

Read more