Councils carry a development application from lodgement to final completion — assessment, referrals, conditions, engineering approval, construction oversight, defects, asset handover. Most of that lives in a records system built for correspondence, not delivery. Engis includes a module built as council-grade workflows for exactly this arc, on the same platform the developers and consultants across the counter use.
The module follows a development application through its real lifecycle: pre-application, lodgement, assessment with further-information stops, referrals, conditions, decision and issue — then onward through the civil delivery the permit unlocks: detailed design assessment and approval, pre-commencement, construction, practical completion, defect liability and final completion.
It is not a contractor tool with the logo swapped, and not a generic records system with planning terminology bolted on. The stages, the referral states, the statutory clock behaviour and the post-permit engineering milestones are modelled the way Australian subdivision assessment and development engineering actually run.
Statutory lodgement platforms carry the application; the records system carries the correspondence. But the working state — which referrals are outstanding, where the statutory clock stands, which conditions gate compliance, what the development engineer signed off, which inspections found defects, what as-constructed information has actually been handed over — tends to live in spreadsheets, shared drives and individual inboxes. When the officer changes, the state goes with them.
Available for council and authority tenants — enabled per council, with role-based access for the teams involved.
Applications tracked through their full arc — pre-application, lodgement, assessment, further information, referral, conditions, decision and issue — with a statutory clock that pauses correctly while further information is outstanding.
Referrals to internal teams and external authorities tracked as records with real states — pending, in progress, no objection, conditions, objected — so the referral board is a view, not a chase list.
Detailed design assessment and approval tracked as explicit stages after the permit, where the development engineering workload actually lives.
The post-permit sequence modelled as milestones: pre-commencement meeting, commencement, CCTV review and rectification, as-constructed submission, practical completion, defect liability walkthrough, final completion and bond return.
Scheduled inspections — pre-start, routine, hold point, practical completion, defect liability, final acceptance — with pass and fail outcomes recorded, and defects tracked through to close-out.
As-constructed drainage, road, sewer and water assets captured spatially and exportable as GeoJSON — structured data for the asset register, not a PDF to be re-digitised.
Application, referral and inspection metrics reported from the same records the work runs on — no separate reporting spreadsheet to maintain.
The conditions a council issues are the conditions delivery teams track in Engis — same vocabulary, same structure, which is what makes the counter faster in both directions.
Zoning, overlays, flood extents and authority assets from live Australian data services on the map beside each application.
Assessment stages, referral states and the statutory clock as live records — the position of any application in one lookup.
Design assessment, approvals, inspections, defects and as-constructed handover as structured workflows rather than folder conventions.
As-constructed capture arrives as spatial data ready for the asset system, not drawings to trace.
Developers and consultants run their side of the same work in Engis — conditions, submissions, documents — so both sides of the counter reference the same state.
Records systems store what happened; Engis models what happens next — which referral is outstanding, which condition gates compliance, which inspection is due. The stages and states are Australian subdivision process, not a configurable blank slate.
Most tooling stops at the permit. The engineering half — design approval, construction oversight, defects, handover — is where council effort concentrates, and it is modelled here as first-class workflow.
Engis also runs the developer and consultant side of delivery. Shared vocabulary and structured submissions mean fewer malformed applications in, and clearer expectations out.
No. SPEAR remains the statutory lodgement and certification platform in Victoria. Engis is the working system around it — the assessment, referral, engineering and delivery record. Engis AI can read planning permit and SPEAR-lodged documentation to build condition registers, but there is no live SPEAR synchronisation.
Per authority. The council workflows are enabled for council and authority tenants as part of firm onboarding, with role-based access controlling what each team sees and does.
Yes. As-constructed asset capture exports as GeoJSON for your asset and GIS systems, and reporting is built from the same application, referral and inspection records the teams work in.
In Australia. Engis runs on Australian-region infrastructure with per-tenant data isolation enforced at the database level, verified by automated tests on every release.
Contact the team for a walkthrough of the council workflows, or request sandbox access to explore on synthetic data.
Book a walkthrough of the application, referral, inspection and handover workflows — or request sandbox access.
Australian Hosted · Australian Data Residency
