Canberra's Duplicate Image Problem: What Happens Next and the Key Decisions Ahead

Canberra's public sector has a digital housekeeping problem. Across ACT government agencies, the Australian National University, and several Commonwealth departments headquartered in the city, duplicate images buried in content management systems are inflating storage costs, slowing website performance, and — in some cases — causing outdated or incorrect visuals to resurface in public-facing publications. The question now is who moves first, and how.

The issue has sharpened in recent months as agencies complete post-pandemic digital audits and confront the real price of deferred maintenance. Storage is not free. Cloud hosting for large government image repositories can run into tens of thousands of dollars annually, and duplicates — sometimes numbering in the hundreds of thousands across a single large agency's archive — contribute directly to that bill. The practical pressure to act is real, even if the urgency rarely makes it above the level of a branch manager's inbox.

What's Actually at Stake Locally

At the ACT government's Access Canberra service centres, including the busy Dickson shopfront on Cowper Street and the Tuggeranong outlet near Anketell Street, staff regularly pull images from a centralised digital asset library to update community-facing materials. When duplicates exist — the same photo stored under six slightly different filenames — frontline staff have no reliable way to know which version is current. That creates a quiet but persistent risk: outdated headshots of ministers who have since left office, aerial shots of suburbs like Gungahlin that predate recent development, or accessibility images that no longer meet updated WCAG 2.2 standards introduced in late 2024.

The University of Canberra, based in Bruce, flagged a similar operational issue in its web governance review last year. Managing a library of tens of thousands of assets across faculties and student services units means duplicate detection is largely manual — a task that falls to web coordinators already stretched across multiple responsibilities. ANU's digital experience team on Acton Peninsula has taken a more structured approach, piloting automated deduplication tools within its content management environment, but rollout across all 14 colleges is still pending a final budget allocation.

The ACT's whole-of-government Digital Strategy, which runs through to 2030, nominates data quality as a tier-one priority. Duplicate asset management sits squarely within that frame, yet specific program funding for image library remediation has not been publicly announced as of July 2026.

The Decisions That Will Define the Next Six Months

Three choices will largely determine whether Canberra's institutions get ahead of this or keep patching it. First, procurement: agencies need to decide whether to integrate deduplication capability into existing platforms like Squiz or Drupal, or procure standalone digital asset management software. Licensing costs for mid-tier DAM platforms typically start around $30,000 per year for a government-scale deployment — a figure that requires a formal business case in most ACT agencies before the next budget cycle closes in late 2026.

Second, governance: someone has to own the problem. Without a named asset steward — a specific role rather than a shared responsibility — remediation work stalls. The ACT Digital Strategy assigns data stewardship obligations to agencies individually, which means no central authority is currently mandating action on this specific issue.

Third, standards: the ACT government's ServiceNow-based service portal and the Access Canberra website both pull from separate image repositories. Unifying naming conventions and metadata schemas before running deduplication tools is unglamorous work that typically takes three to six months for an organisation of even moderate complexity. Skipping it means duplicates return within a year.

For public servants in Barton and Phillip who manage communications teams, the practical advice from digital archivists is consistent: start with a read-only audit before touching anything. Map what exists, establish which assets are live in production, and only then run automated similarity detection. Deleting first and asking questions later — a common instinct when facing a bloated image folder — risks pulling visuals that are still embedded in published pages across dozens of agency microsites. The audit is the unglamorous work. It is also the only part that cannot be skipped.