Government Workflow Automation

Development applications: automating intake and completeness checks

Last checked 2026-11-13

Short answer: Automation helps most before assessment starts. An AI worker can read a lodged development application against the council's own checklist, flag missing or inconsistent documents, draft a request for further information, and track benchmark dates. In NSW an application is reviewed for completeness before lodgement and can be rejected within 14 days, only for reasons in section 39 of the regulation. That rejection decision stays with an officer.

Incomplete applications are one of the most common causes of delay in development assessment. Much of the checking is mechanical. This page covers where software can do that checking, and where the planner takes over.

On this page

What the rules say about intake (NSW example)

Rules differ between states, so check your own planning legislation. NSW gives a clear example of how intake is structured:

Some projects also need Commonwealth approval. Under the EPBC Act, a proponent must "submit a referral if your project could impact any matters protected", and Commonwealth and state approvals are separate. A council intake check can flag when an application mentions matters that may need a referral, so the officer can ask the question early.

What an AI worker can check at intake

The council's lodgement checklist is the rulebook. The AI compares what was lodged against it, then reports to the intake officer:

The output is a short completeness summary with each gap linked to the checklist item it fails. From that, the AI drafts a request for further information in Word for the officer to edit. The officer decides whether the gap is a ground for rejection, a request for information, or acceptable.

An AI check is a second pair of eyes against your checklist, not a legal test. Section 39 grounds and your own local requirements should be written into the checklist the AI uses, and reviewed by the planning team.

Tracking assessment after lodgement

Once accepted, an application moves through stages: allocation, notification, referrals, requests for information, assessment report and determination. A register in Excel or a SharePoint list can hold every application's stage, officer, key dates and next action. An AI worker can keep that register current from the mailbox and documents. It can count days against your benchmarks and send a morning summary in Teams of applications approaching a benchmark or waiting on a referral.

It can also draft routine correspondence: acknowledgements, referral cover letters, reminders to applicants who have not answered a request for information, and notification letters for the officer to approve. Nothing is sent without approval. The Everything says it asks before anything important goes out. For council correspondence, treat every outgoing letter as important.

What stays with a person

The AI prepares and tracks. The planner and the delegate decide.

Other states and US permitting

Every Australian state has its own planning legislation, portal and timeframes. The pattern is the same: a checklist, a completeness step, a clock, a determination. Build the AI's checklist from your own state's requirements, not NSW's.

US local governments handle zoning and building permits under state and local law, with no single national rule. The same intake approach applies. Federal projects can also trigger NEPA, which requires federal agencies to assess "major federal actions significantly affecting the environment" through an Environmental Assessment or an Environmental Impact Statement. Permit renewals and inspections are covered on the permits and licences page. Before using any AI tool on applicant information, see what to check before you start.

Questions people ask

Can an AI reject an incomplete development application?

No. It can identify gaps against your checklist and draft the request for information or rejection notice, but the decision to reject, and the reasons, belong to the council officer. In NSW, rejection is limited to the section 39 grounds and must happen within 14 days of lodgement.

Is the NSW 40-day figure a legal deadline?

The NSW councils' development assessment guide describes 40 days for standard applications and 25 days for fast-track applications as benchmarks. The guide notes they are not the statutory deemed-refusal period.

Does this work with the NSW Planning Portal?

The Planning Portal is not on The Everything's published integrations list. Councils that receive portal documents into a mailbox or SharePoint library can have the AI work from those copies. Anything else is a question for the vendor.

What does the AI need to run completeness checks?

Your lodgement checklist for each application type, access to where lodged documents arrive, and a register to record results. The checklist should be written and reviewed by your planning team.

Will it flag possible EPBC referrals?

It can flag applications that mention matters your checklist identifies as possible triggers, so an officer can consider it. Whether a referral is needed is a judgement for the proponent and the Commonwealth, not the AI.

An AI worker inside Microsoft 365

The Everything runs inside Microsoft 365 and Teams. It prepares, checks, tracks and drafts, and it asks before anything important goes out. There is a 14-day free trial with no credit card. After that it costs $400 AUD/month + GST per organisation, with unlimited team members. Do your own security, privacy and records assessment before using it for government work.

See how The Everything works