Copyright © 2026 Everyday Backups · everydaybackups.com · Secure cloud backup for small business & personal files
In water and fire damage restoration, the documentation is the invoice. A carrier does not pay against a memory of what a technician saw; it pays against dated moisture readings, timestamped photos, and equipment logs recorded inside a building that, by the time anyone questions the file, has already been dried, rebuilt, and reoccupied. There is no going back to re-shoot that evidence. If the job file is gone, the site cannot recreate it, and an unpaid balance is what is left. This work is also emergency work, captured hour by hour on a technician's phone or tablet in the field and dumped to one office computer at the end of the day, in a business where the same storm that generates the call volume can just as easily take out that office.
Everyday Backups provides managed, encrypted cloud backup for Windows computers, with monitoring, restore support, and regular backup health reporting. Paid plans from $5.99/mo.
A water, fire, smoke, or storm damage job produces a dense, time-stamped file over the course of days or weeks, built while the loss is still an active site: readings, photos, and records that only exist because someone captured them while the water was still standing, the smoke odor was still present, or the equipment was still running. Once the structure is dry, rebuilt, and handed back to the owner, that evidence cannot be regenerated. The list below is what a working restoration file should be able to produce, for one specific loss, on demand.
Every one of those items is dated and site-specific. A drying log from a loss three months ago cannot be rewritten from memory, and a thermal image or before-photo cannot be reshot once the drywall is back up and the tenant has moved back in. If the file that supports payment on a job disappears before the carrier releases funds, or before a dispute over scope is resolved, the work already performed has no documentation behind it, and the balance owed on that job becomes the loss.
A restoration job file is not a construction record built for the property owner who hired you, and it is not a completed-roof record built to show a homeowner what was installed. It is a file built for a third party, the carrier or program administrator who reviews and pays against it, and that reviewer was never on site. The readings, the photo timestamps, and the equipment logs are what stand in for their own eyes. That is what makes the file the actual basis of payment rather than just a record you keep for your own reference.
It is also captured under time pressure that most job files are not. A drying log is only useful if the readings were taken on the schedule the job required, not reconstructed afterward. A before-photo only has value if it was taken before demolition or extraction began, not after. Because that capture window closes permanently once the work moves forward, a restoration job file has no do-over the way a delayed invoice or a missing measurement report on a different kind of job might.
These are the moments a backup gap turns from a theoretical risk into a real one. Each has a different trigger, but the outcome is the same when no independent, off-site backup exists.
A hard drive failure on the machine that receives field data from every open loss means no access to drying logs, no way to confirm which readings were already taken, and no visibility into which jobs still need a certificate of satisfaction. During a period when call volume is already at its highest, this is also when the business can least afford to be rebuilding job files instead of running crews.
A restoration company's busiest days are triggered by severe weather, and the office running that business sits in the same geography as the losses it is responding to. Wind, flooding, or a power outage that reaches the office building at the same time it reaches the customer base can put local machines and local drives at risk at exactly the moment job volume, and the documentation load that comes with it, is highest.
A phone or tablet used to record a moisture reading, a thermal image, or a mid-drying photo set is dropped, damaged, or lost before the data is transferred to the office. That specific monitoring visit's readings and photos cannot be recreated once the job has moved past that point in the drying process. Backing up the office folder those files land in, and keeping the transfer routine tight, is what closes this gap.
CISA and the FTC both identify small businesses as ransomware targets. Ransomware typically encrypts every file it can reach on the local machine and any connected network shares, and a cloud sync folder replicates the encrypted versions almost immediately. A backup that is not continuously connected to the network is the copy most likely to survive with usable job files intact.
A question about a specific loss can surface long after the crew has moved on and the site has been reoccupied. If the drying log, the photo set, or the signed work authorization for that job exists only on a machine that has since failed, or a folder that was never backed up, there is no way to reproduce documentation for a site that no longer shows any sign of the original damage. Backup here means being able to recover your own operational records; it does not change how any claim is evaluated or paid.
A drying-log spreadsheet gets overwritten with the wrong day's readings, or a job folder gets deleted during a routine cleanup between busy stretches. Cloud sync propagates the mistake immediately. A backup with version history lets you recover the file as it existed before the error, from a point in time before the change happened.
The 3-2-1 rule is a framework promoted by CISA and used widely in small-business backup guidance. Applied to a restoration company's job files, here is what it means in practice.
The working copy on the office PC counts as one. A second copy might sit on an external drive or a secondary workstation. A third copy, off-site in encrypted cloud storage, protects against a local event affecting the first two at the same time. A company running its entire job-file record through one office machine is one hardware failure away from losing every open loss's documentation at once.
Two drives in the same machine, or a RAID array in the same office, are not meaningfully redundant against a building-level event. CISA guidance calls for at least two distinct storage types, for example a local drive plus a separate cloud destination, as independent layers of protection.
Off-site means physically separated from your office, in a way that a storm, fire, or theft affecting the building cannot reach both the primary data and the backup at the same time. Cloud backup to a separate data center satisfies this. An external drive sitting in the same room does not.
CISA recommends keeping at least one backup copy that is not continuously connected to the network, since ransomware increasingly targets connected backup destinations along with production files. A cloud backup that is not directly mounted on the local network is the version most likely to survive a ransomware event with usable job files intact.
The checklist below reflects CISA small-business backup principles and FTC small-business cybersecurity guidance, applied to the way a restoration company's documentation is actually produced and stored. This is a starting framework for backup decisions, not legal, regulatory, or claims-handling advice.
If your company also handles roof replacement alongside restoration work, see backup for roofing contractors, which covers the measurement, estimate, and completed-roof records specific to a re-roof rather than the hour-by-hour mitigation documentation this page focuses on. If your work also includes general contracting or rebuild scope for the property owner, see backup for contractors and construction companies, built around records for the owner who hired you rather than a file built for a third-party payer. For preparing your files ahead of the storms that generate this work in the first place, see hurricane season business file backup. For a broader self-assessment of your current backup posture, see the small-business backup checklist.
Your estimating software and your moisture-documentation software store job data in different ways depending on the product: some write files locally to your Windows machine, others operate primarily through a vendor-hosted account with data on the vendor's servers. The questions to answer for your own backup are where each system stores its records on your machines, whether those locations are included in your backup scope, and whether any of the data is saved locally at all or only reachable through a login.
If your software is mainly cloud-hosted, the local backup question shifts to what you save on your own machines from that system: exported readings, downloaded photo sets, PDF authorizations, and estimate documents. Those locally stored files remain your responsibility to back up independently. A vendor's copy of your data on their servers, or a carrier portal you upload documentation to, is not a substitute for your own backup of what lives on your machines, and access or retention terms on either can change.
Some platforms allow scheduled exports to a local folder. If yours does, setting that up and including the export folder in your backup scope is a practical way to make sure readings and photo sets are covered alongside your other business files. Check your specific software's own documentation, since export behavior varies by product.
Job costing, subcontractor payments, payroll, and carrier receivables for a restoration company commonly run through QuickBooks. The company file is frequently stored on a single office desktop with no second copy anywhere else. Intuit's own documentation recommends keeping backup copies of QuickBooks data in a separate location from the original and specifically notes that backing up only to the same machine is not adequate protection against hardware failure.
Common oversights include the company file living on one machine with no independent copy, an automatic backup feature writing to a different folder on the same drive as the original, and exported reports treated as complete backups when they only capture a snapshot rather than the full file. For detailed QuickBooks backup steps, Intuit's own documentation is the authoritative source.
Many small restoration companies run OneDrive, Dropbox, or a similar sync service on their office machines and assume it protects their job files. The distinction matters most in the moments a real recovery is needed.
Cloud sync mirrors the current state of a file. When a drying log is overwritten, or a photo folder is deleted, or ransomware encrypts a set of job files, that change replicates to the cloud copy, usually within seconds. At that point both the local copy and the synced copy reflect the damage, and the sync service has preserved nothing useful for recovery.
Backup keeps point-in-time copies with version history, so a job file can be restored as it existed at a specific date and time before the deletion, the overwrite, or the ransomware event. Microsoft's own OneDrive documentation describes version history and Personal Vault features, but these are limited by plan and duration and are not designed as a replacement for an independent backup with a defined retention window and active monitoring.
The FTC and CISA both publish guidance noting that small businesses, including small contracting operations, are targets of ransomware campaigns, in part because they often run with less IT infrastructure than larger organizations while still holding financial records and customer data that create pressure to pay a ransom rather than lose the files.
For a restoration company, the factors that raise the stakes include job documentation for multiple open losses concentrated on one or two Windows machines, QuickBooks accounting covering years of job costing and payroll on the same network, and typically no dedicated IT staff checking backup health on a regular basis.
CISA's #StopRansomware guidance identifies offline and encrypted backup copies as the primary technical recovery mechanism once ransomware has encrypted production files. A backup connected to the same network as the infected machines, or a sync folder replicating changes in real time, may itself be encrypted before the attack is even noticed. A backup that is not continuously mounted on the local network is the copy most likely to survive with usable job files intact. A tested backup does not eliminate downtime during a ransomware incident, but it is the difference between a difficult week of recovery and losing job files, financial records, and correspondence with no path back.
No. Backup only affects whether your own records still exist; it has no bearing on how any claim is reviewed, evaluated, or paid, and Everyday Backups does not provide insurance, estimating, appraisal, or claims-handling advice of any kind. What backup changes is whether the drying log, the photo set, and the correspondence for a specific job are still recoverable if the machine or device holding them fails, is lost, or is affected by a ransomware incident.
No. Everyday Backups is a general file-backup service, not a compliance or records-standards tool. It does not satisfy, and does not claim to satisfy, any industry documentation standard, any carrier program or audit requirement, any state water-restoration, mold-remediation, or general-contractor licensing rule, any EPA lead-safe-work recordkeeping obligation, or any other record-retention requirement that may apply to your business. Your company keeps its own regulatory, licensing, and recordkeeping obligations regardless of what backup service is used.
Yes. Even when a moisture-documentation app is mainly cloud-hosted, your business still saves files locally to Windows machines: exported readings, downloaded photo sets, signed work authorizations, estimate documents, and QuickBooks accounting files. Those locally stored files are not backed up by the app vendor. A vendor storing your data on their servers is also not the same as you having an independent backup you control and can restore from on your own timeline.
The most common discovery moments are a hard drive failure on the office PC during a high-volume stretch, a lost or damaged phone that held a monitoring visit's readings and photos with no second copy, a ransomware incident encrypting multiple machines at once, and a carrier or adjuster request for a specific job's documentation months after the site has been reoccupied. Each surfaces a gap that was invisible while the business was running normally.
No. Cloud sync mirrors the current state of a file: if it is deleted, overwritten, or encrypted by ransomware, that change replicates to the sync destination almost immediately. Backup keeps point-in-time versions so a file can be restored as it existed before the damage. Microsoft's OneDrive documentation describes version history, but it is limited by plan and duration and is not a substitute for a managed backup with a defined retention window.
CISA guidance recommends retaining enough history to recover from incidents that are not discovered right away, since ransomware and accidental deletions are often noticed days or weeks later. Thirty days of version history is a practical minimum. Some restoration companies choose longer retention for job files that could be referenced by a carrier or adjuster well after the work is complete.
Treat a failure as something to check right away rather than at a weekly review. Common causes include the machine being off during the scheduled window, a file locked by an open application, low disk space, or a network or credential issue. If failures go unnoticed for an extended period, current jobs have no coverage, and a hardware failure or ransomware event during that window has no recovery path. Alerts on failed or missed backups are the baseline way to avoid discovering a gap only when you need to restore.
Everyday Backups installs on Windows machines, monitors backup job health, sends alerts when a backup fails or goes overdue, keeps version history so you can recover files from a prior point in time, encrypts data in transit and at rest, and stores backups off-site in cloud infrastructure rather than local media that could be affected by the same event as your primary machines. It runs automatically in the background once configured, with monitoring and health reporting so you know it is working without checking manually. Companies with more than one Windows machine, for example an office PC and a secondary estimating workstation, need coverage on each one.
Whether you want to check your current situation yourself first or talk it through with someone who can give you a second set of eyes, there is a starting point that fits.
The 2-minute self-check at everydaybackups.com/a/backup-risk-check.html asks a short set of questions about your current setup and tells you where the gaps are. No signup required. It takes about two minutes and gives you a clear picture of where you stand right now.
If you would rather talk through your specific setup, our team offers a free 15-minute Backup Risk Check. We look at what you have, identify the gaps, and give you honest guidance on what to fix first, whether or not you use Everyday Backups to do it. Schedule at app.everydaybackups.com/contact or call us at 850-980-3691.
Everyday Backups is a general file-backup service, not a legal, regulatory, records-compliance, or claims-handling tool. It does not by itself satisfy any industry documentation standard, carrier program or audit requirement, state water-restoration, mold-remediation, or general-contractor licensing rule, EPA lead-safe-work recordkeeping obligation, record-retention requirement, consumer-protection, privacy, or other legal or regulatory obligation applicable to a water, fire, smoke, or storm damage restoration contractor. Backup is a recovery mechanism for your own operational files and is not a substitute for your own insurance, claims, adjusting, or licensing processes, and does not affect whether or how any claim is reviewed or paid. Your company keeps its own regulatory, licensing, and recordkeeping obligations regardless of what backup service is used. References to drying logs, moisture readings, moisture maps, thermal images, photo sets, psychrometric and equipment records, category and class determination notes, work authorizations, estimates, adjuster and carrier correspondence, containment and disposal records, subcontractor invoices, technician certification file copies, and payroll and accounting records refer only to ordinary operational files saved to Windows machines and are not claims that Everyday Backups satisfies any regulatory, licensing, safety, or industry-standard obligation, nor does Everyday Backups provide insurance, estimating, appraisal, adjusting, mold, indoor-air-quality, health, biohazard, or job-site-safety advice of any kind. No compatibility with any specific estimating, moisture-documentation, claims, CRM, accounting, or other application is guaranteed or implied; verify backup scope and file coverage with your own IT review. Mention of software categories such as estimating software, moisture-documentation software, or carrier portals is for illustrative purposes only and does not constitute endorsement of or claimed compatibility with any specific vendor or product. References to CISA, FTC, Intuit, and Microsoft documentation are for informational context only and do not constitute endorsement by those organizations. Consult qualified legal, tax, insurance, and industry-specific advisors for requirements specific to your business.
Everyday Backups runs on Windows, iPhone, iPad, and Android. Set it once; it backs up automatically, encrypted, off-site. Paid plans from $5.99/mo.
Prefer to talk to a person? Call 850-980-3691
Want a second set of eyes? Schedule your free 15-minute Backup Risk Check with our team
Copyright © 2026 Everyday Backups · everydaybackups.com · Secure cloud backup for small business & personal files