Backup For
City Halls & Local Government Offices

The files a city hall or municipal office cannot afford to lose

A small municipal office's real work product is not glamorous, it is files: minutes, ordinances, account histories, permit records, and spreadsheets, most of them living on a small number of Windows PCs shared by the clerk, the utility billing desk, the permit or zoning desk, and the mayor's or manager's office. The categories below are the ones a working city hall should be able to recover from a specific date when the situation calls for it.

• City clerk records, including correspondence, official filings, notary and oath records, and the day-to-day record-keeping that runs through the clerk's office and touches nearly every other department at some point.
• Council and meeting minutes, agendas, and packets, covering both the working drafts prepared before a meeting and the final approved record afterward, along with any supporting attachments and exhibits that were part of the packet.
• Ordinances and resolutions, including the working files used to draft, amend, and codify them over time, and any redline or comparison versions kept during the review process.
• Utility billing records: water and sewer accounts, meter-reading data, customer account history, payment history, and delinquency and shutoff records that the billing desk relies on every single day to answer a resident's question at the counter.
• Permit files, code-enforcement files, and planning and zoning records, including applications, inspection notes, photographs, correspondence with property owners, and case history that may be referenced years after a case closes.
• Business license records issued and renewed through the office, including application files and renewal history.
• Accounting, budget files, purchase orders, and payroll, the financial backbone of the municipality's day-to-day operations, along with bank reconciliation files and vendor payment history.
• Scanned documents, deeds and easements, maps, and contracts with vendors, many of which exist only as a single scanned copy on a shared drive with no second copy anywhere else.
• Grant files and reporting documents tied to state or federal funding the municipality has received or applied for, including the supporting documentation that a reporting cycle may require on short notice.

A gap in any one of these categories becomes a real problem in a specific moment: when a resident disputes a water bill and no one can pull up the meter-reading history, when a permit file cannot be located during a property dispute, or when last month's council packet is needed and the only copy was on a PC that will not turn on.

Where backup gaps hide in a small municipal office

• One shared PC, or a handful of them, with no separate off-site copy. A town of a few thousand residents often runs its entire office on two, three, or four Windows computers. If those machines are the only place the data lives, there is no backup, there is one copy.
• Backup assumed to be "handled" but never confirmed. In an office with no dedicated IT staff, backup responsibility can drift between whoever set it up years ago and whoever happens to still be employed. No one currently on staff may actually know whether it is running.
• Cloud sync mistaken for backup. A folder that syncs to OneDrive or a similar service will faithfully sync a deletion, an overwrite, or a ransomware encryption event to the synced copy as well. Sync keeps files available across devices; it does not, by itself, give you an independent, restorable copy from before something went wrong.
• Utility billing exports saved only to the billing desk's own PC. Meter-reading data, account history, and delinquency records exported from utility billing software often land in a local folder that no one has thought to add to a backup routine.
• Scanned deeds, easements, maps, and vendor contracts with a single copy. These are often scanned once, filed in a folder, and never touched again, which also means no one notices if the folder was never backed up.
• No one has tested a restore. A backup job that reports success confirms data was copied somewhere, not that a specific file can actually be found and opened when it is needed.
• Backup media kept in the same building. An external drive stored in the same office it is meant to protect offers no protection against a fire, a burst pipe, or theft that affects the whole building at once.
• Only one person knows where the files live. In an office of a few people, the clerk, the treasurer, or the office manager who set up the current system may be the only one who knows where backup data goes and how to start a restore.
• Turnover taking backup knowledge with it. Small municipal offices see real staff turnover, an elected clerk's term ends, a treasurer retires, a part-time employee moves on, and the person who configured or last checked the backup may leave without documenting what they knew. The backup itself may keep running, or it may have quietly stopped, and no one currently in the building can say which.
• Old PCs kept in service past their reasonable lifespan. A tight budget often means computers stay in service years longer than a private business might keep them, which raises the odds of a hardware failure happening before a replacement is budgeted, making an independent, off-site copy more important, not less.

See the deeper write-up on ransomware restore readiness for what recovery looks like after files are encrypted.

Understanding the 3-2-1 backup rule for a city hall

The 3-2-1 rule is a straightforward framework promoted by CISA and widely used in small-business and small-office backup guidance. Applied to a small municipal office, here is what it looks like in practice.

A backup standard for city halls and local government offices

The checklist below reflects CISA small-business backup principles and FTC small-business cybersecurity guidance, applied to the file environment of a small municipal office. This is a starting framework for backup decisions, not legal, records-retention, or compliance advice.

• Map every machine in the office. List every Windows computer in the building: the clerk's desk, the utility billing desk, the permit or zoning desk, and the mayor's or manager's office. For each machine, identify what data lives there and is not copied anywhere else. That list is your minimum backup scope.
• Include utility billing exports explicitly in backup scope. Locate the folder where meter-reading data, account history, and delinquency or shutoff records are exported or saved on a Windows machine, and confirm it is included in your backup configuration.
• Add scanned documents, deeds, easements, and maps to backup scope. These files are frequently scattered across a scanning folder or a shared drive. Locate every folder that holds them and confirm each one is covered.
• Retain at least 30 days of version history. CISA guidance notes that ransomware and accidental deletions are often not discovered for days or weeks after the event. Thirty days of version history gives a meaningful window to recover a clean copy from before a bad change.
• Encrypt backup data in transit and at rest. Office files can include resident account details and staff payroll records. Backup data should be encrypted before it leaves the office network and should remain encrypted in storage.
• Monitor backup jobs and receive failure alerts. A backup that fails silently leaves the office with no current coverage and no warning. Monitoring that alerts on a failed or missed backup job is a baseline requirement, especially in an office with no dedicated IT staff to check manually.
• Test restores on a regular schedule. CISA explicitly recommends periodic restore testing. A quarterly spot-restore, pulling a council packet, a utility billing export, and a scanned deed from different dates and confirming each opens correctly, is a practical cadence for a small office.
• Document who handles recovery. Someone in the office should be able to answer, without searching: what is backed up, where the backup data goes, and how to start a restore. A short written note, kept somewhere other than the machine being backed up, turns a stressful recovery into a manageable one.

For a broader self-assessment of your office's current backup posture, see the small-business backup checklist.

Utility billing and municipal accounting software: what backup actually covers

Two categories of software generate most of a small city hall's day-to-day records: utility billing software and municipal accounting or ERP software. Understanding what your backup does and does not cover for each is essential before assuming the office is protected.

Permit, code-enforcement, and clerk or agenda-management software

Beyond billing and accounting, two more categories of office software carry records a small municipality cannot easily recreate: the system used for permits and code enforcement, and the system used to manage council agendas and minutes.

Budget and staffing realities for a small office

A town hall serving a few thousand residents does not have the budget or the staff of a large city's IT department, and a practical backup approach has to work within that reality rather than assume it away.

The clerk, the utility billing desk, and the mayor's or manager's office are often the entire administrative staff, and each person already has a full workload without backup administration added on top. That makes two things especially important: backup that runs automatically once it is configured, without someone having to remember to start it, and monitoring that surfaces a problem on its own rather than requiring someone to go check. A system that depends on a staff member remembering to run a manual backup, or reviewing logs on a regular schedule, tends to work well for a few months and then quietly stop being checked once other priorities take over.

Cost matters too. A small office weighing backup options is often comparing a modest monthly cost against the time and disruption of trying to reconstruct utility billing history or a permit file from scratch, or against the cost of an IT consultant brought in only after something has already gone wrong. A backup service priced for a small business, rather than an enterprise IT budget, is generally a better fit for an office this size than a solution built around a full-time IT department that does not exist here.

Procurement can also be a real hurdle for a small municipality, where any new recurring expense may need to clear a purchase-order process or a council vote before it can be adopted. A backup service with a simple, published, per-device monthly price is easier to bring through that process than a custom enterprise IT quote with variable line items. Getting a straightforward answer to "what would this cost us" before committing staff time to evaluate it further is worth doing early.

Ransomware and the small municipal office

The FTC and CISA both publish guidance noting that small offices, including small government offices, are targets of ransomware. Ransomware has been a real and repeatedly documented problem for local government offices, as reflected generically in CISA's #StopRansomware guidance and FTC small-business cyber guidance. The point of raising it here is narrow and practical: what matters most once files are encrypted is whether you can restore them, not whether backup prevents the attack in the first place.

For a small city hall, the factors that make this worth planning for are familiar: clerk records, utility billing data, and permit files concentrated on a small number of Windows machines, usually no dedicated IT staff monitoring backup health day to day, and a small team that cannot absorb an extended outage of the utility billing desk or the permit counter. A backup connected to the same network as an infected machine, or a cloud sync folder that mirrors changes in real time, can itself be encrypted before anyone notices. CISA's guidance points to offline and encrypted backup copies as the primary technical recovery mechanism once production files are encrypted, backup is about recovery, not prevention.

It is worth being precise about what this page is and is not saying. It does not claim that any particular city, town, or agency has been the victim of a ransomware attack, does not cite a dollar figure or a percentage tied to any incident, and does not name a specific case. The generic point, that ransomware has repeatedly affected local government offices and that restore readiness matters as a result, comes from CISA and FTC small-business and small-office guidance, not from any incident described on this page.

If the utility billing desk cannot issue a bill, or the permit counter cannot pull up an open case, the practical cost to residents and the office starts accumulating immediately, independent of whatever caused the outage. Being able to restore clerk records, billing data, and permit files from a recent, clean backup is what turns a multi-day office closure into a same-day recovery.

For a deeper walkthrough of what restore readiness actually looks like, see ransomware restore readiness.

How a city hall differs from a housing authority

Everyday Backups also works with public-sector offices on the housing side, and the two are genuinely different environments even though both run on Windows PCs with a small staff.

A housing authority's core records center on tenant files, HUD and Section 8 documentation, and inspection history tied to a specific federal housing program. A city hall or general municipal office is broader: the clerk's office, the council, utility billing, permits, code enforcement, and licensing, none of which involve HUD housing programs or tenant files at all. The backup priorities differ accordingly. A city hall's most time-sensitive records are usually utility billing account history and permit or code-enforcement case files, where a gap creates an immediate service problem for a resident or a business at the counter. See backup for housing authorities for the HUD and tenant-file side of public-sector backup.

If your office happens to run both a general municipal function and a separate housing program, the practical answer is the same either way: map every Windows machine and every folder that holds records not duplicated elsewhere, and make sure each one is included in backup scope, regardless of which department it belongs to. The underlying backup standard, off-site, encrypted, monitored, tested, does not change based on which department's files are involved; only the specific files being protected do.