01 / 08 · The AI picks the clauses
It starts by choosing what matters for this site
PlanningAI reads the application and suggests the clauses that apply. Here it picks 22 of the 142 clauses in the LEP. 20 are suggested by the AI and 12 match what the SoEE already addresses.
02 / 08 · You adjust the list
See every clause. Add or remove any of them
Show all clauses, search and tick or untick. Search “bush” and it finds Bush rock removal already suggested and Public bushland left out. Continue when the list is right.
03 / 08 · One clause at a time
Then it assesses each clause individually
Every selected clause gets assessed individually yet all simultaneously, creating significant efficiencies versus doing them one by one manually. The same process occurs for all LEP, DCP and SEPP clauses with the human only needing to review uncertain clauses.
04 / 08 · The finding
When it can’t be sure, it says so
The application doesn’t show whether bush rock is affected, so the finding is Uncertain instead of a guess. PlanningAI is deliberately conservative and the comment names exactly what’s missing.
05 / 08 · The source
Check the instrument, word for word
Every finding is cited. Open the full clause to read the exact text of the instrument it relies on.
06 / 08 · AI Assisted Edit
Close the gap in plain English
Give the AI the information it’s missing or tell it how you assess the clause, just like you would with an AI chatbot.
07 / 08 · The result
Redrafted and re-determined
The comment is rewritten against the new evidence and the status moves from Uncertain to Compliant. This is the app’s real output for that instruction.
08 / 08 · Your call
Nothing changes until you approve it
Accept the edit, try again or revert. Save & Continue moves to the next clause.