The ACT government's digital asset libraries contain tens of thousands of image files stored across multiple platforms, many of them duplicated two, three, or more times across different agency drives and content management systems. That's not a secret, but the scale of it — and the cost of cleaning it up — has finally pushed the issue into procurement conversations happening right now across London Circuit and Parkes Way.
The problem didn't emerge overnight. It built over roughly fifteen years, accelerating sharply after 2015 when federal and territory agencies began moving away from centralised print communications toward agency-by-agency digital publishing. Each directorate stood up its own website, its own social media operation, its own stock photo library. Without a shared taxonomy or a single digital asset management system governing the whole of government, images were downloaded, renamed, re-uploaded, and stored again — sometimes dozens of times for a single photograph of, say, the Kings Avenue Bridge or a Gungahlin development site.
The Machinery That Created the Mess
The ACT government operates through eight directorates plus a cluster of statutory bodies, each with its own communications team. The City Renewal Authority alone manages visual assets tied to projects across Northbourne Avenue and the inner north. Transport Canberra and City Services photographs light rail operations, road works, and park maintenance separately from the broader Transport Canberra corporate communications function. ANU and the University of Canberra, while not government bodies, face the same compounding problem: both institutions expanded their digital footprint aggressively after 2018, and both have acknowledged internally that asset management hygiene fell behind publishing velocity.
The federal public service brought its own layer. Agencies headquartered in Barton, Woden, and the Parliamentary Triangle each built image libraries to support ministerial communications, annual reports, and social content. When staff rotated — as they do at high rates in Canberra — image conventions rotated with them. A photographer hired by one agency would shoot a building, deliver files to a shared drive, and six months later the same building would be shot again because no one could locate the original licence or confirm the metadata.
Why It Matters in Mid-2026
Storage costs are one part of the calculation but not the biggest one. The real expense sits in licensing. Commercial stock image licences purchased by individual teams — at prices ranging from roughly $50 for a single-use web image to several hundred dollars for extended broadcast rights — have been duplicated across directorates that didn't know another team had already paid for the same asset. A 2024 whole-of-government digital review, which the ACT government commissioned through its Digital, Data and Technology Solutions function, flagged redundant licensing as a measurable line item, though the full figures have not been publicly released.
The replacement process — auditing existing libraries, deduplicating files, establishing a shared metadata standard, and migrating surviving assets into a consolidated system — has been described in tender documentation published on the ACT government's procurement portal as a multi-stage project. The first stage, covering high-use campaign imagery, was scoped to be completed before the end of the 2025-26 financial year, which ends today, July 4, 2026.
For public servants working out of offices in Civic, Dickson, or the Woden Town Centre, the practical upshot is a changed workflow. Staff who previously saved images to personal network folders will be directed to a central repository with search and licence-status functions built in. Training sessions have been scheduled across several directorates for July and August.
The broader lesson Canberra's digital teams are drawing from this episode is about governance architecture rather than technology alone. Procurement of a better image management system doesn't prevent the next sprawl if the policy settings — who can publish, what gets saved, where, and under what licence terms — aren't locked in from the start. Those policy questions are still being worked through. The cleanup is the easy part.