Upload a caseload
Screen up to 300 sites in one pass and see the jurisdiction-wide picture — which applications are likely to be refused, need a full EIA, or only a registration, and where hazards concentrate. Every triage is produced by the same engine as the single-site tool; the caseload output is decision support for officer triage and not a determination.
Confidentiality & data-protection notice (DPA Act 843).
Upload only applications you are the proponent for, or that you handle in your official Authority capacity.
Named-officer runs store the input file's SHA-256 hash and the resulting caseload snapshot for RTI Act 989 traceability;
anonymous pilot runs are not retained.
Personal data columns (applicant name, address, phone, national ID) are not needed for screening and,
when the strict-input mode is enabled by the Authority, are silently dropped before the engine sees them.
CSV needs a header with lat and lon (or latitude/longitude).
Optional columns: ref, title, sector, size_ha, ….
GeoJSON points and polygons are both accepted (polygons screen at their centroid).
RECENT PIPELINES
— named-officer runs are saved and shareable according to access rights
Loading…
Triage summary
Where the caseload sits
By region (Regional Director view)
By sector (Act 1080 taxonomy)
Cumulative load by district (MMDA)
Hazards across the caseload
Cumulative-impact hotspots
Groups of sites close enough that their combined effect on the same catchment / community should be assessed together, not one permit at a time.