WA BUILDING PERMIT APPLICATION REVIEW PLATFORM

Better BA1 submissions.Faster council reviews.

Council reviewers see a relevant evidence preview and the exact source reference for every configured requirement, then verify the source and record their own outcome. Improved applicant submission quality is a later, separately approved stage.

PlanScout locates and previews the evidence. The reviewer completes every check and retains every professional and statutory decision.

Discuss a historical backtest View the BA1 reviewer demo

Initial pathway: certified BA1 applications for Class 1a dwellings and associated Class 10 structures. Reviewer workspace first; applicant-facing use is a later, separate decision.

DURING COUNCIL REVIEW

Complete every check more efficiently

See every configured requirement with a relevant evidence preview, source document, page or sheet reference and exception status. Open the source, complete the check and record the human outcome.

Review requirements and cited evidenceSelect a row
Requirement	Evidence preview	Source	Human status
Property address	10 Banksia Way…	BA1 · page 1	Awaiting review
BA3 drawing reference	Revision C	BA3 · page 2	Awaiting review
Uploaded drawing revision	Revision D	Plans · cover sheet	Awaiting review

Evidence located. Reviewer confirmation required.

BEFORE LODGEMENT

Improve submission quality — a later stage

Catch missing evidence, BA1 and BA3 mismatches, conflicting details and outdated drawing revisions before they create avoidable rework.

Applicant-facing use is enabled only after a council approves the reviewer workflow, data controls and operating model. It is a later, separate decision and forms no part of the historical backtest.

Improve the BA1 pack before lodgement

Missing mandatory evidence
BA1 and BA3 detail mismatch
Conflicting property information
Outdated drawing revision

How pack quality is improved

Better-quality application pack smoother, fully evidenced council review

BA1 intakeBA3 consistencyDrawing revisionsMandatory evidenceLocal checklistSource-linked review

ONE PLATFORM. TWO ROLE-SPECIFIC WORKSPACES.

Complete council review. Improved applicant submissions later.

A council engagement begins with the reviewer workspace using completed historical applications. Applicant-facing use is enabled only after the workflow, data controls and operating model are approved.

REVIEWER WORKSPACE

Work through every configured requirement

Building surveyors and permit officers see a relevant evidence preview, the exact source document and location, any comparison values and the current exception status. The reviewer opens the source, completes the check and records the human outcome.

review the full configured requirement catalogue
view evidence previews
open the cited source document
check page, sheet, section and revision
confirm sufficient or insufficient evidence
escalate matters requiring professional judgement
record notes and an auditable outcome
prepare reviewer-approved suggested communication

Explore the reviewer workspace

APPLICANT WORKSPACE — LATER STAGE

Improve the pack before lodgement

Where a council later enables applicant-facing use, applicants, builders and agents would receive immediate, plain-English feedback on missing evidence, inconsistent details and revision issues before lodging through the local government’s existing channel.

upload or prepare the application pack
review missing or inconsistent evidence
understand the source of each issue
route corrections to the relevant party
replace corrected documents
prepare a better-quality pack before lodgement

Explore the applicant workspace (later stage)

The same application pack is presented differently according to the user’s role, permissions and responsibilities.

Incomplete and incorrect applications create avoidable delay.

A 2019 WA Auditor General audit of selected local government entities found materially longer permit processing where further information was required, with most reviewed information requests relating to incomplete or incorrect applications.

External sector evidence only. This is not a PlanScout performance claim.

WA Auditor General, 2019

CONTROLLED PUBLIC-SECTOR DEPLOYMENT

Role-specific, source-linked and auditable by design.

PlanScout is designed to separate applicant and reviewer experiences, preserve source references and record human outcomes. Access, data location, retention, model-provider boundaries and operational security controls are documented and agreed before genuine application data is processed.

Separate applicant and reviewer workspaces

Source-linked human review history

No automated statutory action

Council-agreed controls before live use

Review the assurance approach

EVIDENCE-LED HUMAN REVIEW

See the evidence. Verify the source. Record the decision.

For each configured requirement, PlanScout surfaces a relevant evidence preview and identifies the source document, page, sheet or section. The reviewer verifies that evidence against the underlying source and records whether the requirement has been satisfied.

Relevant evidence surfaced

Text excerpt or highlighted form field
Extracted value with surrounding context
Drawing crop or title-block crop
Plan-sheet callout or page thumbnail

The preview helps the reviewer understand why the requirement was surfaced.

Original source identified

Source document
Page or sheet
Section or field
Drawing revision and comparison source where relevant

The reviewer can open the original document or full drawing sheet for verification.

Reviewer completes the check

Confirmed sufficient
Confirmed insufficient
Not applicable
Escalated or resolved

PlanScout records the reviewer’s outcome but does not make the professional or statutory decision.

Evidence previews accelerate navigation and verification. They do not replace review of the underlying source document or the reviewer’s professional judgement.

REQUIREMENT-BY-REQUIREMENT EVIDENCE PREVIEW

Review every configured requirement with its evidence preview and source.

PlanScout maps the council-confirmed BA1 requirement set to relevant evidence previews across the forms, certificates, drawings and supporting documents in the application pack.

Reviewers see the PlanScout evidence status, preview, exact source reference and separate human review status for every configured requirement.

Evidence preview → exact source reference → reviewer verification → human outcome

Synthetic evidence map

PSW-DEMO-0001 · 10 Banksia Way

Select a row to preview evidence

Configured requirement	PlanScout evidence status	Evidence preview and source	Human review status
Application property addressREQ-001 · View linked finding	Potential supporting evidence located	10 Banksia Way… · BA1 · page 1	Awaiting review
Certificate of design complianceREQ-007 · View linked finding	Potential supporting evidence located	Certificate present · BA3 · page 1	Awaiting review
Insurance property addressREQ-013 · View linked finding	Possible mismatch	12 Banksia Way… · HII · page 1	Awaiting review
Certificate drawing referenceREQ-011 · View linked finding	Possible mismatch	Revision C · BA3 · page 2	Awaiting review

PlanScout shows where relevant evidence appears. The reviewer opens the cited source, completes each check and records the human outcome.

Evidence mapping workflow

Requirement → evidence → source → status → reviewer outcome

Synthetic application pack

FormsCertificatesDrawingsSupporting evidence

Configured requirements

Statewide prescribed and statutory-form requirements, cross-document consistency checks, and the participating local government’s configured intake and workflow checks.

Requirement

Configured check and rule source

Evidence

Relevant value or document located

Source

Document and page cited

Status

Potential evidence located or exception surfaced

Reviewer outcome

Authorised reviewer records the decision

1Requirement selected

2Candidate evidence linked

3Page referenced

4Exception separated

5Human outcome recorded

Potential supporting evidence and exceptions appear in one workspace.Every result remains linked to its source document and page.The permit authority retains professional and statutory judgement.

PlanScout shows where relevant evidence appears. The reviewer opens the source, completes each check and records the human outcome.

View the BA1 reviewer demo

Initial product scope

Focused first on certified residential building permit application packs.

The initial pathway is deliberately narrow: BA1 — Application for Building Permit – Certified for Class 1a dwellings and associated Class 10 structures. The participating local government confirms its terminology, intake checklist, local workflow checks and applicable rule sources during configuration.

What PlanScout checks

Expected document set
BA1 and BA3 field consistency
Property, applicant and builder details
Drawing and certificate revisions
Mandatory supporting evidence
Local government intake-checklist items

Statutory and professional boundaries

Does not approve or refuse building permit applications
Does not replace a registered building surveyor
Does not determine structural adequacy
Does not determine complete National Construction Code compliance
Does not determine planning merit
Does not determine whether development approval is required
Does not replace the permit authority

PlanScout may locate and present evidence associated with these matters, but it does not make the underlying professional or statutory determination.

PlanScout’s initial pathway concerns certified building permit application packs. It may identify evidence of a prior planning approval or an unresolved prerequisite, but it does not determine the planning pathway or assess planning merit.

Statewide framework, local configuration

One WA building-permit framework, configured to each local government.

BA forms, building classifications and core statutory pathways are standard across Western Australia. Local governments may use different portal labels, application checklists, local prerequisites and operational workflows. PlanScout maps these variations to a versioned statewide model without requiring every local government to use the same terminology.

One Western Australian statutory framework, configured to each local government’s terminology, checklist and workflow.

Standard statutory pathway

Retain canonical BA form codes, building classifications and statewide requirement sources.

Local terminology mapping

Display the participating local government’s preferred service names and applicant-facing terminology.

Local checklist configuration

Map local intake requirements and supporting-document expectations to the canonical pathway.

Versioned rule sources

Record the source, jurisdiction, effective dates, version and local applicability of each configured check.

Existing workflow retained

Fit the evidence workspace around the local government’s existing lodgement, records and assessment process.

PlanScout normalises statutory meaning without forcing all local governments to use identical labels or internal processes.

One pack, five controlled stages

Prepare the evidence before the reviewer applies judgement.

Confirm the pathway and requirement layers

Confirm the certified BA1 pathway, applicable statewide requirements, local government intake checklist, workflow checks, rule sources and effective dates.

Index the application pack

Identify the BA1, BA3, drawings and supporting documents, then extract the fields required for the configured checks.

Map requirements to evidence

Show which document and page contains potentially relevant evidence for each requirement, together with the extracted value and current evidence status.

Surface exceptions

Separate potential supporting evidence from missing evidence, conflicting details, revision mismatches, matters outside automated scope and external dependencies.

Apply professional and statutory judgement

The authorised building surveyor or permit officer verifies the evidence, resolves exceptions and determines whether any formal action or communication is required.

PlanScout structures the evidence. Local government officers retain the judgement and statutory control.

Explore the full workflow

Primary product proof

Explore the evidence workspace from the reviewer’s point of view.

Review a fictional certified BA1 application through its requirement-by-requirement evidence map, inspect source-linked findings and record human outcomes. The applicant view shows how potential corrections can be explained before lodgement.

Open reviewer demonstration Open applicant demonstration

Synthetic reviewer workspace

Requirement-by-requirement evidence map

20/20

expected document types

configured requirements

potential evidence rows

permit-authority review items

external-agency dependency

Human

outcome required

Evidence preview → exact source reference → reviewer verification → human outcome

A staged adoption journey

Prove the evidence workflow on previous submissions before changing the live process.

Start with the current pathway, validate the evidence mapping on previous submissions and proceed to live shadow use only where authorised staff find the results useful.

Stage 1 · Workflow review

Map the current certified building permit intake process.

Identify the local terminology, intake checklist, recurring application-pack issues, evidence checks, systems and staff roles used for the selected pathway.

Request a workflow review

Stage 2 · Historical BA1 suitability backtest

Check the requirement and evidence mapping on completed historical applications.

Configure the applicable statewide requirements, statutory form relationships and local government intake checks before comparing PlanScout’s findings with the known historical outcome. Completed within an agreed period of up to 90 days. Data handling, retention and return arrangements are agreed in writing before any genuine council application data is provided.

original submitted pack
earlier version before correction
corrected or resubmitted version
final accepted version
previous correction or further-information outcome
checklist or requirements applicable at the time

Stage 3 · Optional live shadow use

Proceed to live shadow use only after staff review.

PlanScout can operate beside the current permit administration and building surveying process without writing to the official record or taking statutory action.

Production integration, applicant-facing use and operational deployment require separate approval.

Public-sector due diligence

Designed for controlled evaluation before live deployment.

Before any live application data is processed, PlanScout and the participating local government must agree the architecture, data flows, access controls, retention arrangements, model-provider boundaries and contractual responsibilities.

Human oversight

PlanScout findings require human review. The authorised officer retains responsibility for all statutory actions and decisions.

Evidence and audit

Findings are designed to link to the source document, page, extracted value, configured rule and reviewer outcome.

Data boundaries

Any use of genuine council application data, including a historical backtest, must be configured and contracted so that customer application documents are not used for general model training.

Controlled access

Pilot access, user roles and the treatment of applicant information must be agreed before live operation.

Retention and deletion

Retention periods, export requirements and secure deletion must be documented in the pilot agreement.

Rule governance

Each configured rule should record its source, jurisdiction, application pathway, effective dates and approval status.

Do not interpret this overview as a security certification or legal compliance statement. Final controls depend on the agreed pilot architecture and contract.

Review assurance approach

Frequently asked questions

Clear boundaries from the start.

Perth, Western Australia

Built in Perth for Western Australian workflows

A focused local government technology product.

PlanScout is developed by Propertise AI Group, a Perth-based technology company focused on reducing administrative rework in property workflows.

Founded by Paul Clark, combining software delivery, digital transformation and engineering experience.

PROVE IT ON COMPLETED BA1 SUBMISSIONS

Test the evidence workflow before changing the live process.

Compare PlanScout’s findings with completed BA1 application packs, corrected versions and known council outcomes. No production integration, applicant communication or statutory action is required for the historical backtest. Results are reported in writing, including where PlanScout performs poorly.