Backup For
Volunteer Fire Departments

What this covers, and what it does not

Everyday Backups backs up office and station files on Windows computers, plus phones and tablets, the rosters, training records, maintenance logs, incident report copies, and financial files that keep a department organized. It is not a dispatch, CAD, radio, paging, alerting, or 911 product, and this page gives no advice about dispatch systems. Anything about dispatch belongs with the county or agency that runs it. If your department also runs EMS, patient care reports and anything medical are outside the scope of this page as well, and we give no advice about them. What follows is about the office and station side, not the dispatch or medical side.

What a volunteer department's office actually keeps

A volunteer or combination department holds more office records than its staffing would suggest, because a station computer, an officer's laptop, and a treasurer's or secretary's machine are often the only place any of it exists. The record set below is what many stations across the rural South want to be able to put a hand on, for any member, any apparatus, or any board meeting, on short notice.

• Member rosters, contact lists, and training hours, kept in your records management software or in spreadsheets
• Copies of certifications and course completion records
• Apparatus and equipment maintenance logs, and pump and hose testing logs, as records kept by the department
• Incident and run report copies kept at the station, from your incident reporting system
• Pre-plan files and hydrant or water supply map files
• Fundraiser records and subscription or membership fee records
• Grant applications, award letters, and the documentation behind them
• Board, district, and auxiliary minutes and bylaws, as documents kept on file
• Insurance paperwork, bookkeeping, stipend records, and QuickBooks
• Station photos and scanned historical records

A gap in any one of these categories tends to surface at the worst possible time, not before. A new officer takes over the truck committee and cannot find last year's pump test sheets, a board member asks what the bylaws actually say, or a grant reviewer asks for training documentation the department thought it had, and the record that should answer the question is nowhere to be found because the computer holding it failed, or the member who kept it moved on, with no copy anywhere else. At a station run by volunteers, that is rarely a paperwork inconvenience, it is often the only copy that existed.

Where these records actually go missing

• The member who kept the records moves on. Many volunteer departments run on whoever stepped up to handle a given job, the training officer, the secretary, the grant writer. When that member retires from the department, changes jobs, or simply has less time, the files on their personal laptop or phone often do not transfer with them, and no one else knows those files existed.
• One shared station computer holds everything. The day room or chief's office computer can end up holding rosters, maintenance logs, and incident report copies going back years, with no second copy anywhere else. If that machine fails, is stolen, or will not boot, the station can lose its working record in one event.
• Ransomware reaches the station network. The same shared computer that holds training records often also holds the department's financial file and years of board minutes. A ransomware event reaching that computer, or a mapped drive attached to it, can encrypt training history and financial records in the same pass.
• Training hours and certifications live in one file with no version history. Training data is often kept in a single running file or spreadsheet, updated by whoever handles it that month. Without version history, an accidental overwrite can erase entries with nothing to recover them from.
• Board and auxiliary minutes are kept as a single scanned folder. These documents are sometimes scanned once, filed in a folder, and never touched again, which also means no one notices if the folder was never backed up at all.
• Pre-plan and hydrant map files exist on one laptop only. An officer's personal laptop may hold the only copy of a pre-plan file a crew needs, with no second copy anywhere else in the department.
• Grant and insurance documentation is scattered across members. If your station is asked to show training hours, maintenance history, or past award letters during a grant application or an insurance review, many volunteer departments find the supporting documentation is split across several members' personal devices rather than kept in one place.
• Sync gets mistaken for protection. A folder that shows a green checkmark in OneDrive, Dropbox, or Google Drive looks safe, but sync only mirrors what is currently on the device. Delete a roster file, overwrite a maintenance log, or have it encrypted by ransomware, and the synced copy follows right along, often within seconds. See cloud sync vs. backup for what each actually protects against.

The 3-2-1 backup rule applied to a volunteer department

CISA promotes the 3-2-1 rule as a simple standard for small-organization backup, and it maps directly onto how a volunteer department actually holds its records, the active training and incident files from this season, and the growing history of past grants, past minutes, and past maintenance logs behind them.

A backup standard for volunteer and combination fire departments

The items below are specific to how a department's records are actually scattered across a shared station computer, an officer's personal laptop, and whatever records management or incident reporting software a given department uses. They are the starting point before anything else in this framework matters, not a complete checklist on their own.

• Map every device that touches department records, not just the station computer. On most volunteer departments that includes the shared station computer, an officer's personal laptop or phone, and sometimes a treasurer's or secretary's machine. List each one and ask what leaves that device and goes nowhere else. That list is your backup scope, not a guess.
• Locate your records management and incident reporting software's actual export path, not just its screen. Whatever records management software or incident reporting system your department uses holds data tied to its own setup. Find whatever export or save function it offers, save those files to a folder on a Windows machine, and confirm your backup configuration actually reaches that folder. Being able to open the software is not the same as having a copy you control.
• Add pre-plan files, hydrant and water supply maps, and grant documentation as named backup targets, not an afterthought. These records are usually saved separately from your records management software, often in a shared folder or on an officer's personal device. Because a pre-plan file or years of training documentation cannot always be reconstructed from memory the same way twice, this is one of the file categories that can be difficult to replace.

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

When the member who kept the records moves on

It helps to picture the actual meeting night, rather than the abstract loss. A new truck committee chair asks where last year's pump and hose test sheets are, or a grant application is due and the department needs training hours and maintenance history going back several seasons. The station is still there, the apparatus bay is still set up exactly where it was left. What is sometimes gone, at many volunteer departments, is the file that answers the question, because the member who kept it retired from the department, moved away, or simply stepped back, and the files lived on their own laptop or phone rather than anywhere the department controls.

It is worth being precise about what a working backup does and does not do here. A recoverable copy of training records, maintenance logs, or grant documentation means those records still exist and can be pulled back up on a new machine, under whichever member picks up the job next. It does not decide what a grant reviewer will accept, what an insurer will ask for, or how a disputed training hour should be resolved, that remains your department's own judgment, guided by your own officers and board. Many volunteer departments find that simply having the file at all, once the person who kept it has moved on, is the harder problem, and that is the problem a tested backup addresses.

What your records management software, incident reporting system, and QuickBooks backups do and do not cover

Two kinds of software generate most of the records behind a volunteer department, whatever records management software and incident reporting system a department uses to track rosters, training, and run reports, and whatever accounting software or QuickBooks handles the books and stipend records. Knowing exactly what each one's backup covers, and where the gap is, matters because board minutes, pre-plan files, and grant documentation often live partly outside either system.

Cybersecurity guidance and restore readiness for a volunteer department

CISA and the FTC both publish guidance noting that small organizations, including small volunteer organizations, are targets of ransomware. A volunteer department's station fits that pattern with one added detail, what is at risk is not just one season's training records, it can be the department's only surviving record of every member's certifications and every apparatus maintenance history, often kept on whichever computer or laptop a busy volunteer happened to use. CISA's #StopRansomware guidance points to offline and encrypted backup copies as the main technical way to recover once ransomware has already encrypted production files. A backup drive that stays mapped to the network, or a sync folder that mirrors changes as they happen, can be swept up in the same attack as everything else. A cloud backup that is not sitting on your local network as a mounted drive is much less likely to be touched by whatever just encrypted the station's computer. For a fuller walkthrough, see ransomware restore readiness, and for a plain way to confirm your own setup actually works, see how to test your backup restore.

Backup is a recovery tool, not a security, privacy, or compliance control, and it is worth saying plainly, encrypting and backing up rosters, training records, and incident report copies protects your department's ability to get them back if they are lost, corrupted, or ransomed, but it does not make those records secure, it does not make them private, and it does not make them compliant with any rule. It does not satisfy any fire service standard, any insurance or public protection rating, any incident reporting or state reporting requirement, any workplace safety requirement, any HIPAA or patient care report requirement, any grant requirement, any records retention rule, or any cybersecurity requirement that may apply to your department, and it gives no legal or regulatory advice of any kind. A tested backup shortens a bad week, it does not replace your department's own cybersecurity practices or its own diligence on recordkeeping obligations, and it is not offered here as a substitute for either.

A department that loses a member's personal laptop also loses whatever photos that member had of the station and its history. Keeping station photos and scanned historical records backed up from phones and tablets, not just the shared station computer, is worth the same attention as any other record category here. See phone photo backup and what happens when the person who kept the files moves on for the same pattern seen from other kinds of organizations.

How this differs from the adjacent pages we publish

A few other pages on this site cover offices that sit near a volunteer fire department but are not the same thing, and it is worth being explicit about the boundary so you land on the right one.

• Not backup for city halls and local government offices. That page covers a paid municipal office with full time staff, the broad record set a town hall or city hall keeps day to day. This page covers a volunteer run station whose records follow whoever on the roster stepped up to keep them. Where a department is itself a city or county department, both pages apply.
• Not backup for fire protection and fire sprinkler inspection companies. That page covers a private, for profit trade, companies that inspect and test sprinkler systems, alarms, and extinguishers in other people's buildings. This page covers a fire department itself, with its own apparatus, training, incident, and board records rather than a client inspection history.

If your organization spans more than one of these descriptions, such as a department that is also a city department, more than one page may apply, but the rosters, training records, maintenance logs, and board documents described above are what this page is built around.