DC's Duplicate Image Problem: What Happens Next and the Key Decisions Ahead
City agencies and federal offices face a reckoning over how to manage thousands of redundant digital records as budget pressures mount and storage costs climb.
City agencies and federal offices face a reckoning over how to manage thousands of redundant digital records as budget pressures mount and storage costs climb.

Washington's municipal and federal agencies are sitting on a quiet crisis: duplicated digital images — permit photos, inspection records, surveillance stills, planning documents — clogging government servers at a moment when the Trump administration's cost-cutting push has put every line item under a microscope. The decision about what to delete, what to archive, and who holds the authority to make that call is now landing on the desks of city IT managers and federal records officers simultaneously.
The timing matters because it's not abstract. The Office of Personnel Management, operating from its L Street NW headquarters, has been under sustained pressure from the Department of Government Efficiency to slash overhead costs, and data storage has emerged as a visible target. At the same time, Mayor Muriel Bowser's administration is navigating federal funding uncertainty that directly affects the District's own Office of the Chief Technology Officer, which manages digital infrastructure for city agencies ranging from DDOT to the Department of Consumer and Regulatory Affairs.
Duplicate image files are a mundane but expensive problem. According to industry benchmarks frequently cited in federal IT procurement documents, redundant data typically accounts for between 30 and 40 percent of an organisation's total stored data volume. For a city the size of DC — with roughly 37,000 municipal employees spread across agencies operating out of buildings from the Wilson Building on Pennsylvania Avenue to the Department of Public Works facility on West Virginia Avenue NE in Eckington — the compounding storage costs are substantial. Commercial cloud storage for government-grade, compliant systems runs between $0.023 and $0.05 per gigabyte per month depending on the vendor contract, and duplicate images can push those bills into the tens of thousands of dollars annually for a single mid-sized agency.
The National Archives and Records Administration, headquartered in the Pennsylvania Avenue building between 7th and 9th Streets NW, sets the legal framework for what federal agencies must retain and for how long. Its Bulletin 2023-03, which updated guidance on electronic records, requires agencies to document disposal decisions — meaning that simply deleting duplicate image files isn't as simple as emptying a trash folder. An authorised records officer must sign off, and in agencies thinned out by DOGE-related workforce reductions, those officers are increasingly hard to find.
Three distinct choices are converging right now. First, agencies must decide whether to centralise duplicate-detection processes or leave it to individual departments. The DC Office of the Chief Technology Officer has piloted a deduplication review for select datasets in the NoMa corridor redevelopment project files — a program that has generated tens of thousands of inspection photographs since 2021 — but that pilot has not been scaled city-wide.
Second, records managers must determine which duplicate images carry legal evidentiary value. Anacostia neighbourhood permit files, for example, have been central to several contested zoning appeals before the DC Office of Zoning on K Street NW, and premature deletion of what looked like redundant copies has created legal exposure for other jurisdictions in similar situations.
Third, the question of who pays is unresolved. Federal agencies operating in the District — and there are more than 70 with a physical footprint inside city limits — are theoretically subject to federal records law, not DC municipal rules. That split jurisdiction creates genuine confusion when a shared server hosts both city planning images and federally generated photographs from joint projects.
The practical path forward, based on established federal IT guidance, involves three near-term steps: agencies should complete a records inventory by September 30, the end of the federal fiscal year; authorised records officers need to be formally designated in writing before any deletion proceeds; and any deduplication software deployed must be cleared through the relevant agency's cybersecurity review process first. For DC's municipal agencies, the Bowser administration has until its next budget cycle — with a fiscal year 2027 submission due in January — to decide whether centralised deduplication infrastructure gets funded as a line item or gets cut alongside other overhead in the current fiscal environment. The choice will be a telling signal about whether efficiency rhetoric translates into actual operational investment.
How does this story make you feel?
Spread the word
About this article
Published by The Daily Washington DC
Daily brief
Free, in your inbox before 7am. Weekdays.
More in News