Permit condition register
Every condition of the planning permit as a tracked item: status, owner, responsible authority, evidence and notes — reviewable by the whole team instead of living in one person’s head.
Every condition. Every authority. Tracked to Statement of Compliance.
A planning permit is not an approval to build — it is a list of conditions, each owned by a council or referral authority, each blocking something downstream. Engis turns that list into a live, dependency-aware register your whole team works from, and tracks it through to Statement of Compliance.
What is development approvals software?
Development approvals software tracks the approvals a land development project must secure between planning permit and compliance close-out: permit conditions, referral-authority consents, engineering plan approvals, and ultimately the Statement of Compliance that lets lots title. It answers, at any moment, which conditions are open, who owns them, what evidence has been submitted, and what is blocking the next phase.
Most teams run this on a marked-up copy of the permit and a spreadsheet. That works until the permit has sixty conditions across five authorities, the project spans years, and the person who knew the history moves on. Approvals software exists to make the approval state a queryable system of record rather than institutional memory.
Approvals fragment across authorities, portals and inboxes.
Conditions are issued by the council but discharged through referral authorities — water, power, drainage, roads — each with its own portal, correspondence trail and response times. Engineering approvals run in parallel with their own submissions and amendments. Nobody sees the whole board, so the surprises surface late: a condition everyone assumed was closed, a referral response nobody chased, a compliance item discovered the week the Statement of Compliance application goes in.
- Permit conditions re-read from the PDF every time status is needed
- Referral responses buried in authority portals and email
- Engineering approval submissions tracked in a spreadsheet
- No visibility of which open condition blocks which phase
- Statement of Compliance prep as a last-minute evidence hunt
- History lost when the project manager changes
What Engis tracks
The approvals workflow is a first-class part of the Engis project record — not a bolt-on register.
AI condition extraction
Engis reads planning permit and SPEAR documentation and extracts the conditions into the register automatically, so a sixty-condition permit becomes a working register in minutes, not an afternoon of retyping.
Dependency-aware tracking
Conditions link to the approvals and delivery phases they block. When a referral consent is outstanding, you can see exactly what it holds up — and the programme reflects it.
Authority coordination
A structured record of every council and referral authority on the project: submissions made, responses received, what is outstanding and with whom. The chase list writes itself.
Statement of Compliance line of sight
The delivery phase model runs through to Statement of Compliance as an explicit milestone, so compliance close-out is tracked from day one rather than assembled in a panic at the end.
Document register and transmittals
Approval submissions, authority correspondence and evidence live in a controlled document register with numbering and transmittals — linked to the conditions and approvals they support.
Council-grade workflows
Engis includes a module built for the authority side itself — applications, referrals, engineering approvals, inspections and asset handover — because the fastest approvals happen when both sides of the counter work from structured records.
Spatial context
Zoning, overlays, flood extents and authority assets from live Australian data services sit on the map inside the same workspace, so the constraint behind a condition is visible next to the condition itself.
Audit trail
Actions on the record are logged. When an authority asks what was submitted and when, the answer is a lookup, not an archaeology project.
Who uses it
Development managers
One live answer to "what is still open and what does it block" across every project in the portfolio.
Consulting engineers
Engineering approval submissions, amendments and referral coordination tracked alongside the design phases they belong to.
Councils
Structured application, referral and permit workflows on the authority side — the same record discipline, from the other side of the counter.
Utility and referral authorities
Visibility of the developments touching your assets and the consents you are responsible for issuing.
Why a spreadsheet stops working
Spreadsheets track items; approvals are a network
A condition is not a row — it has an owner, an authority, evidence, and things it blocks. The value is in the relationships, and relationships are what spreadsheets silently lose.
Approvals are part of delivery, not adjacent to it
In Engis the condition register, the programme, the commercial position and the documents are one record. An open referral consent is visible from the phase it delays and the claim it affects — no reconciliation between systems.
Built on Australian process
Planning permits, referral authorities, engineering approvals, Statement of Compliance — the vocabulary and workflow are Australian subdivision delivery, not a generic “compliance checklist” template stretched to fit.
Frequently asked questions
What does development approvals software do?
It turns the approval obligations of a development project — planning permit conditions, referral-authority consents, engineering approvals and Statement of Compliance requirements — into a live, tracked register with owners, status, evidence and dependencies, replacing the marked-up permit PDF and spreadsheet most teams rely on.
Can Engis extract conditions from a planning permit automatically?
Yes. Engis uses AI extraction to read planning permit and SPEAR documentation and build the condition register automatically, which you then review and manage as a normal part of the project record.
Does Engis track Statement of Compliance?
Yes. The delivery phase model runs through to Statement of Compliance as an explicit milestone, and the condition and approval registers give you a continuous view of what remains outstanding on the path to it.
Is this only for Victorian projects?
The workflow — permit conditions, referral authorities, engineering approvals, compliance close-out — is common across Australian jurisdictions, and Engis’s spatial layers already draw from authority services in multiple states. Some AI extraction is tuned to Victorian documentation such as SPEAR, and coverage keeps expanding.
How do I get access?
Access is provisioned per firm. Request a three-day sandbox preview on synthetic data, book a demo, or contact the team.
Put the permit down. Open the register.
See a sixty-condition approvals board tracked live — request sandbox access or book a 20-minute demo.
Australian Hosted · Australian Data Residency