How Canberra's Government Agencies Got Buried in Duplicate Images — and What It's Costing Them

Australian Public Service agencies operating out of the Capital Hill precinct and across Canberra's suburban office clusters are sitting on digital image libraries bloated by years of uncoordinated file management — a problem that has quietly driven up storage costs and complicated the shift to modern content management systems. The practice of duplicate image replacement, once a niche IT headache, has become a live operational issue for departments now migrating legacy systems ahead of the federal government's 2027 deadline for cloud-based infrastructure compliance.

The timing matters. The Albanese government's Digital Government Strategy, released in late 2023, set firm expectations around data hygiene and interoperability. Agencies that can't demonstrate clean, deduplicated asset libraries risk failing compliance reviews tied to the strategy's implementation phases. For Canberra's public service, which employs roughly 160,000 people across the ACT — many of them in departments with decades-old intranet and document systems — that is not a theoretical concern.

How the Duplication Problem Built Up

The roots go back to the early 2000s, when individual directorates within large departments began maintaining their own SharePoint sites, shared drives and content management systems with little coordination from central IT. An image uploaded to a Department of Finance communications team in one fiscal year might be re-uploaded — sometimes in multiple resolutions — by the same team the following year, or by a separate division entirely. By the time departments began auditing their holdings in preparation for cloud migration, some were finding tens of thousands of near-identical files stored across multiple servers.

The Australian National University's digital records research group has previously documented similar problems in large institutional settings, and the University of Canberra's Faculty of Arts and Design has grappled with managing image archives across its Kirinari Street campus as it digitised historical holdings. Neither institution is unique. The pattern repeats across any organisation that grew its digital operations incrementally, without enforcing file-naming standards or central repository rules from the outset.

One contributing factor specific to the federal government context is machinery-of-government changes. When departments are restructured — as occurred repeatedly between 2013 and 2022, when entities were merged, split and renamed across portfolios including Home Affairs and the former Department of Human Services — digital assets frequently migrated incompletely. Files duplicated during those handoffs were rarely cleaned up afterward. The Department of Finance's own resource management guidance acknowledged the challenge of legacy data in its 2022-23 portfolio budget statements, though it did not quantify the storage overhead involved.

What Agencies Are Now Doing About It

The practical work of duplicate image replacement involves running deduplication algorithms across file stores, identifying canonical versions of each image, and systematically replacing or retiring the redundant copies. For large agencies headquartered along the Northbourne Avenue corridor or in the Barton and Parkes precincts, that can mean processing libraries that have not been meaningfully audited since the Howard era.

The Digital Transformation Agency, based in Canberra, has been coordinating guidance for agencies navigating this work as part of the broader cloud uplift program. Storage costs on government cloud tenancies — typically priced per gigabyte per month — give the deduplication effort a direct budget justification beyond compliance. Even modest reductions in redundant image files across a large department can translate to measurable savings over a contract year.

For agencies still in assessment phase, the immediate priority is establishing what they actually hold. That means commissioning image audits — often handled by internal IT teams or contracted digital asset management specialists — before any replacement work begins. Agencies that skip this step and proceed directly to new content management deployments risk carrying the same duplication problem into their new environment, which defeats the purpose of the migration entirely.

Departments expecting to complete their cloud compliance assessments before the end of the 2026-27 financial year will need to have deduplication strategies signed off well before then. The window is narrower than it looks, and the administrative groundwork — policy sign-off, vendor engagement, staff training on new asset management workflows — takes longer than most project timelines initially allow.