Portfolio dashboards
Every active project rolled up into one live view — phases, status, budgets and risk — so the portfolio position is a screen, not a compilation exercise.
A developer’s delivery truth usually lives in other people’s systems: the consultant’s report cycle, the council’s portal, the permit PDF, the accounts package. Engis puts the portfolio itself — phases, conditions, approvals, spend, risk, spatial context — into one live operating system that answers to you.
Engis is development delivery software: the system of record for the years between planning permit and Statement of Compliance. For a developer or development manager, that means every active project structured into its real phases — permit, functional layout, detailed design, tender, construction, compliance — with the conditions, approvals, budgets, documents and risks of each phase tracked as live records rather than report attachments.
The portfolio view sits on top. Instead of reconstructing status from a stack of monthly consultant reports, the answer to “where is every project, and what is blocking it” is a dashboard you open — built from the same records the delivery work runs on.
Most development portfolios are managed on a lag. Consultants report monthly, councils respond on their own clock, and the internal tracker is a spreadsheet someone updates before the board meeting. The information exists — but it is scattered, stale by the time it is compiled, and owned by everyone except the developer. The result is a familiar pattern: surprises surface at the report cycle, not when they happen.
One environment, structured around the phases an Australian development project actually moves through — with the portfolio rolled up on top.
Every active project rolled up into one live view — phases, status, budgets and risk — so the portfolio position is a screen, not a compilation exercise.
Projects structured around real delivery phases with budgets and schedule, including a dependency-aware programme with finish-to-start, start-to-start and lag logic.
Every planning permit condition tracked with status, owner and responsible authority. AI extraction reads the permit documentation and builds the register for you.
A structured record of the councils, water authorities and referral bodies on each project — what has been submitted, what is outstanding, and which open item blocks which phase.
Phase budgets with progress claims, variations and invoicing tracked against them — the commercial state of the project alongside its delivery state.
A controlled document register with numbering, transmittals, RFIs and submittals — the delivery paper trail attached to the project record it belongs to.
Live parcels, zoning, overlays, flood extents and utility assets from Australian authority data services on the project map — site constraints visible in the same workspace as the conditions they trigger.
A delivery-focused risk register alongside the projects it concerns, so risk review is part of running the portfolio rather than a standalone ritual.
Drop a contract, fee proposal or program and interrogate it. Engis reads AS 2124 and AS 4000 style contracts and extracts key terms into the record.
Your projects are delivered by consultants, approved by councils and serviced by utilities. Engis is built for that whole network — which is exactly what makes the developer’s view work.
Portfolio-level visibility of phases, approvals, spend and risk across every active project — current, not month-old.
The working record of each project: conditions, authority submissions, programme, documents and budget in one workspace.
Civil engineering consultancies run their delivery and commercial workflows in Engis too — same vocabulary, same record discipline.
Engis includes workflows built for the authority side — applications, referrals, engineering approvals — because faster approvals help every seat at the table.
Feasibility platforms model the acquisition and stop. Construction platforms start when the contractor mobilises. The years in between — approvals, design, authority coordination, compliance — are where programmes are won or lost, and that is the ground Engis owns.
Dashboards built on stale inputs just redecorate the lag. Engis dashboards are live because they sit on the same records the delivery work actually runs on — conditions, approvals, claims, documents.
Planning permits, referral authorities, Statement of Compliance, GST-aware claims — the vocabulary is Australian development delivery, not a generic project template stretched to fit.
Currency and independence. A monthly report is a snapshot compiled from systems you cannot see. Engis makes the underlying record — permit conditions, authority submissions, programme, budgets, documents — the shared working surface, so the portfolio position is live and queryable at any moment, not reconstructed at each report cycle.
No. Engis is provisioned per firm, and a developer’s own team can run its projects — conditions, approvals, budgets, documents, spatial context — as a complete system of record. That said, Engis is also built for consultancies, councils and authorities, so the network can converge on the same record discipline over time.
No. Feasibility software answers the acquisition question — yield, funding, margin — and ends at the purchase decision. Engis begins where feasibility ends: it runs the delivery of the project you now own, from permit through to Statement of Compliance. It includes site feasibility context, but delivery is its centre of gravity.
In Australia. Engis runs on Australian-region infrastructure with per-firm data isolation enforced at the database level, verified by automated tests on every release.
Access is provisioned per firm. Request a three-day sandbox preview on realistic synthetic data, book a demo, or contact the team directly.
Request a sandbox preview on synthetic data, or book a 20-minute demo walking through a live delivery programme.
Australian Hosted · Australian Data Residency