By the Numbers: Perth's Duplicate Image Problem Is Costing Councils and Developers More Than They Realise

Perth's property and infrastructure pipeline is generating document volumes that city planners have not seen before, and buried inside that paper trail is a growing administrative headache: duplicate images lodged with development applications, title records and infrastructure tenders are inflating storage costs, slowing approval workflows and, in some cases, triggering compliance reviews that delay projects by weeks.

The problem has sharpened over the past 18 months as Metronet construction contracts, AUKUS-related works near HMAS Stirling at Garden Island, and a state government housing push across the Ellenbrook and Alkimos corridors have collectively pushed the volume of digitally lodged planning documents to levels the system was not designed to handle at scale.

What the Numbers Actually Show

Western Australia's Department of Planning, Lands and Heritage manages the state's primary Development Assessment Panel portal. Industry compliance consultants working across the Perth CBD and inner suburbs have observed that large mixed-use development files — particularly those tied to transit-oriented projects near stations on the Yanchep Rail Extension — routinely contain image assets duplicated between three and seven times across a single application package. Each full-resolution site photograph or architectural render can run between 15 megabytes and 40 megabytes. A mid-sized apartment proposal in Scarborough or Mount Claremont, which might include 80 to 120 such images, can therefore arrive carrying anywhere from 3.6 gigabytes to well over 10 gigabytes of redundant data.

Storage costs for government-grade cloud infrastructure in Australia have been tracking at roughly $0.023 per gigabyte per month on enterprise contracts, according to publicly available AWS and Azure pricing schedules current as of June 2026. That sounds trivial per file. Multiply it across thousands of active applications at any given time in a city where the Urban Development Institute of Australia's WA chapter reported more than 24,000 lots in the pipeline as of late 2025, and the cumulative overhead becomes material.

Local government authorities feel this differently. The City of Stirling, which covers some of Perth's most active medium-density renewal precincts from Scarborough through to Osborne Park, processes hundreds of development applications per year. Each duplicate image set that passes through its ePlanning portal requires manual or automated deduplication before archiving, or it sits on record inflating the authority's own storage and audit burden indefinitely.

Why Perth's Conditions Make This Worse

Three converging pressures specific to Western Australia have amplified what elsewhere might be a manageable nuisance. First, the state's Indian Ocean Strategy and associated defence construction activity around Rockingham and the Henderson Maritime Precinct have introduced a class of applicants — defence contractors and federal agencies — that operate under separate documentation standards and often lodge identical image sets across multiple regulatory portals simultaneously. Second, Perth's housing demand, driven partly by interstate and international migration into growth corridors in the city's north, means planning departments are processing applications faster than their data hygiene protocols can keep pace. Third, the WA State Budget surplus, which the Cook government reported at $3.3 billion in the 2025-26 mid-year review, has funded rapid capability uplift in Metronet — but the document management infrastructure supporting that uplift has lagged the construction timeline.

Curtin University's Spatial Sciences department, based in Bentley, has been studying cadastral data integrity across metropolitan Perth and has published work noting that image redundancy in geospatial datasets compounds when multiple agencies — local government, state planning, Landgate and infrastructure delivery bodies — each maintain their own record copies without a deduplication handshake between systems.

For developers and their consultants, the practical advice is straightforward: audit image libraries before lodgement, strip metadata duplicates, and compress files to the minimum resolution specified in each authority's lodgement checklist. For the City of Perth and surrounding councils, the medium-term answer likely involves a shared deduplication layer integrated into the state's OneStop planning portal — a project that has been discussed at the WA Local Government Association level but has not yet attracted dedicated funding in the 2026-27 budget cycle, which lands in September.

Until then, the duplicate images keep stacking up — and so does the cost of ignoring them.