Copyright © 2026 Everyday Backups · everydaybackups.com · Secure cloud backup for small business & personal files
A solar installation company runs on a paper trail that starts with a signed contract and does not end until a utility grants permission to operate. In between: a site survey and roof measurements, a shade analysis and production model built during the proposal, a system design and layout drawing, a permit and plan set submitted to the local authority, an interconnection application packet and the utility correspondence that follows it, inspection and commissioning photos taken on the roof, equipment serial numbers and warranty registrations for every panel, inverter, and battery installed, and the financing paperwork the customer signed to pay for it. Most of that record lives as files on one or two Windows computers in the office, plus whatever a site technician has captured on a phone or tablet before it makes it back to the folder for that job. The honest question every solar installer needs to answer is whether that project folder could actually be reproduced, not just re-typed, on the day a computer fails, a technician's tablet is lost, or ransomware locks the network down mid-project.
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 solar or battery storage installer builds a distinct project file for every job, one that a general contractor, a roofer, or a field-service dispatcher does not carry in quite the same form. The categories below are the operational files that project record needs to hold, ones a regulator, a utility, a financing company, or an equipment manufacturer may expect to see again long after the crew has moved on to the next job.
A gap in any of these categories becomes a real problem at a specific, predictable moment: when a utility asks for a resubmitted interconnection packet, when an inspector wants to see a commissioning photo of a label that has since been covered over, or when a customer's battery fails under warranty three years later and the installer cannot produce the serial number and registration that prove the unit is covered.
Solar installation overlaps with other trades on the surface, a crew on a roof, a signed contract, a Windows office computer, but the actual work and the records it produces are different enough that this page is written specifically for solar and battery storage installers rather than adapted from a neighboring trade.
Distinct from roofing contractors. A roofing contractor's core record is a measurement report, a damage assessment, and insurance-claim documentation built around the condition of the roof itself. A solar installer's core record is an energy-system design, an interconnection application, and a commissioning package built around a system that has to be approved by a utility before it can be turned on. Roof measurement and insurance-claim work is genuinely not what a solar job produces, even when the crew is standing on the same roof a roofer would be.
Distinct from field-service contractors. HVAC, plumbing, and electrical field-service businesses run on recurring maintenance dispatch: a customer calls, a technician is scheduled, a service ticket is closed, and the cycle repeats for the same equipment for years. A solar installation is project-based. Each job runs once, start to finish, from a signed contract through permitting, interconnection, inspection, and commissioning to permission to operate, and then the crew is on to the next address. The record-keeping problem here is not recurring dispatch history, it is keeping one long project file intact from start to finish without losing a document a third party is waiting on.
Distinct from general contractors and construction companies. A general contractor's project file centers on the building itself: framing, structural changes, trade coordination, and a building permit tied to construction code. Solar installation is a specialty energy trade layered onto an existing structure. The permit is for an energy system, not a building, the inspection checks system installation and labeling rather than construction quality broadly, and the paperwork that follows the job, the interconnection packet and the utility's own review, has no equivalent in a general construction project.
A solar job is not finished when the panels go up. It is finished when a utility grants permission to operate, and everything between the signed contract and that final approval is a paper trail with a regulator and a utility on the other end of it.
Once a customer signs, a solar installer typically produces a site survey, a system design, and a permit set that goes to the local authority having jurisdiction for review and approval. In parallel, an interconnection application goes to the utility, often with its own set of forms, technical attachments, and a review queue that runs on the utility's own timeline rather than the installer's. Both processes generate correspondence: requests for additional information, revision requirements, approval letters, and confirmation numbers that the installer needs to track and, in many cases, produce again if asked. None of that paperwork is optional to a project file. It is the record that lets an installer show it followed the process it says it followed.
After the physical installation, the project moves into inspection and commissioning. An inspector checks the completed system, and the installer typically documents equipment labeling, wiring, and site condition with photos taken at that specific visit. Those commissioning photos, and the equipment serial numbers recorded during installation, are captured on a roof or at an electrical panel on one specific day. If the project folder holding that documentation is lost mid-job, the installer is not just re-typing a document from memory. It has to reproduce evidence a third party, the permitting authority, the utility, or the financing provider, is actively waiting on, and a photo of a serial number sticker on a panel that has since been covered by a racking clamp or an inspection sticker cannot be recaptured without sending a crew back out to the site.
The paper trail does not end at permission to operate, either. Equipment serial numbers and the manufacturer warranty registration confirmations filed at the time of install are what a warranty claim years later actually depends on. A customer calling about a failed inverter or a degraded battery five years after installation is depending on the installer being able to produce the serial number, the install date, and the registration confirmation for that specific unit. If that project folder was never backed up and the office computer that held it failed at some point in the intervening years, the installer may have no way to support a warranty claim it is contractually or practically expected to help with.
The situations below are the practical moments when a backup matters, or a backup gap becomes a crisis. Each one has a different trigger, but they share a common outcome when no independent off-site backup exists.
A failed hard drive on the main office computer during an active project means no access to the current permit set, no way to confirm what was submitted to the utility, and no visibility into which equipment was ordered for which address. If the machine also held the interconnection correspondence, the gap compounds at the exact moment a resubmission or a status check is needed.
CISA and the FTC both identify small businesses as ransomware targets. When ransomware runs, it typically encrypts all accessible files on the local machine and any network shares mounted at the time, and a cloud sync folder replicates the encrypted versions within seconds. A backup that is not continuously connected to your network is the copy that survives with usable data intact, which matters most when a permit or interconnection deadline does not move just because the office network is down.
A technician's phone or tablet gets left at a job site, dropped, or lost between visits, and it held the only set of inspection and commissioning photos from that day. Without a backup that captures those photos once they reach the office, or a habit of prompt transfer off the device, that specific commissioning record is gone, and a return truck roll to recapture it may not even be possible once the site has moved on.
A customer calls about a failed inverter or a degraded battery three or five years after installation, and the manufacturer wants the serial number and the original registration confirmation before it will process a claim. If that project's records lived only on a computer that was replaced or failed in the meantime, and no backup preserved the file, the installer has no way to produce the documentation the warranty claim depends on.
A utility interconnection review comes back with a request for additional information or a correction, sometimes months after the original submission. If the original application packet, design files, or supporting documents cannot be located quickly, the project stalls in the queue while the office reconstructs what it already built once.
When the person who managed proposals, permitting, or interconnection submissions departs, they often take with them the organizational logic of where files for each project are stored. Permit sets saved outside the main project folder, correspondence kept in a personal inbox, and serial number logs saved to a personal desktop may never transfer to whoever takes over. A backup that captures everything on the machine, regardless of folder structure, preserves what is there even when the departing person's organization approach is not obvious to anyone else.
The 3-2-1 rule is a straightforward framework promoted by CISA and widely used in small-business backup guidance. For a solar installation company, here is what it looks like applied to the files that actually matter.
Your working copy on the office PC or project coordinator's laptop counts as one. A second copy might be a local external drive or a secondary workstation. A third copy, off-site in encrypted cloud storage, is the copy that protects a project's permit set, interconnection packet, and commissioning record against a local disaster affecting both of the first two copies at the same time.
Keeping backups only on the same type of storage, such as two internal drives in the same office machine, does not provide meaningful redundancy against hardware failure. CISA guidance calls for at least two different storage types, for example a local drive and a separate cloud destination, as distinct and independent layers of protection.
Off-site means physically separated from the office where the working files live. Cloud backup satisfies this requirement when the data is sent to a separate data center rather than just an external drive in the same room. The off-site copy is the one that matters most in the scenarios where everything at one location is affected: fire, flood, theft, or a ransomware attack that hits every connected device.
CISA specifically recommends maintaining at least one backup copy that is not continuously connected to the network. Ransomware attacks target connected backup systems as part of the same encryption sweep that hits production files. A cloud-based backup that is not directly mounted on your local network is the copy most likely to come through a ransomware event with your permit, interconnection, and equipment records still usable.
The checklist below reflects CISA small-business backup principles and FTC small-business cybersecurity guidance, applied to the file environment of a working solar installer. This is a starting framework for backup decisions, not legal, regulatory, engineering, or code advice. Everyday Backups also backs up Windows machines for businesses in construction and specialty trades, handling project files, contracts, and accounting the same way described on this page.
For a broader self-assessment of your current backup posture, see the small-business backup checklist. If your work is roof measurement, damage assessment, and insurance-claim documentation rather than energy-system design and interconnection, see backup for roofing contractors instead. If your business runs on recurring maintenance dispatch rather than project-based installs, see backup for field-service contractors. If your work spans general building and construction beyond the solar system itself, see backup for contractors and construction companies. For a closer look at recovering specifically from a ransomware incident, see ransomware restore readiness.
Two categories of software generate the bulk of a solar installer's critical operational data: solar design and proposal software, and the accounting system. Understanding what your backup does and does not cover for each is essential before you assume you are protected.
Solar design and proposal software, a category of tools used to build site surveys, shade analyses, production models, system designs, and customer proposals, stores its data in different ways depending on the product. Some generate a report or design file you download and save locally as a PDF or image. Others operate as web-based platforms where the primary record of a project's design lives on the vendor's servers rather than your machines. Named here only as a description of the software category, with no endorsement or compatibility claim for any specific product, the key questions to answer for your backup configuration are: where does the software store or export its data on your Windows machine, are those files included in your backup scope, and are they saved locally at all, or only accessible through a vendor login.
If your design or proposal software is cloud-based with data primarily on the vendor's servers, the local backup question shifts to what you save locally from that system: exported design PDFs, shade analysis reports, proposal documents sent to customers, and any other files written to Windows machines in your office. Those locally stored files remain your responsibility to back up independently. The vendor's copy of your data in their cloud does not substitute for your own backup of what lives on your machines, and vendor data retention policies can change.
Some platforms allow you to configure automatic export paths or scheduled report downloads that write to a specific local folder. If your software has this capability, setting up an export to a known folder path and including that folder in your backup scope is a practical way to ensure design and proposal files are covered alongside your other business files. Verify this with your specific software's own documentation, as behavior varies across platforms.
Many solar and battery storage installers use QuickBooks for job costing, equipment purchase tracking, subcontractor and crew payments, and revenue recognition as projects reach milestones such as permission to operate. QuickBooks company files (.QBW) can grow large, are frequently stored on a single office desktop, and are the source of truth for the business's complete financial history across every project. Intuit's own documentation recommends maintaining backup copies of QuickBooks data files 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 QuickBooks backup oversights at solar installation companies include the company file stored on one machine with no second copy anywhere, the Intuit automatic backup feature saving to a different folder on the same drive as the original, and portable company files (.QBM) treated as complete backups when they are actually compressed snapshots that may not include all supporting files. A complete backup for a solar installer covers the company file itself, the backup copy that QuickBooks may write to its own backup folder, and any exported job-costing or equipment-purchase reports the business saves separately.
For a detailed look at QuickBooks backup practices, see QuickBooks backup for small businesses. Intuit's documentation, referenced there, is the authoritative source for QuickBooks-specific backup configuration steps.
The FTC and CISA both publish guidance specifically noting that small businesses, including specialty trade contractors, are targets of ransomware campaigns. The reason is practical: smaller businesses often have less IT infrastructure than large organizations, making them easier to compromise, while still holding customer financing information and years of project records that create pressure to pay a ransom rather than lose that history.
For a solar installation company, the factors that make ransomware particularly consequential include active project files, permit sets, and interconnection correspondence concentrated on a small number of Windows machines, QuickBooks accounting covering years of job-costing and equipment-purchase history stored locally, commissioning photos and serial number logs with no off-site copy, and typically no dedicated IT staff checking backup health on a daily basis.
CISA's #StopRansomware guidance identifies offline and encrypted backup copies as the primary technical recovery mechanism when ransomware has encrypted production files. A backup connected to the same network as the infected machines, or a sync folder that replicates changes in real time, may itself be encrypted before the attack is detected. A backup that is not continuously mounted on your local network is the copy most likely to survive a ransomware event with usable project data intact.
Ransomware recovery is not only a technology question. Even with a solid backup in place, a ransomware incident typically means some period of disruption while systems are cleaned and data is restored, and an active project mid-permit or mid-interconnection does not pause for that disruption. What a tested backup changes is whether there is a path back to the project files at all, rather than starting a permit set, an interconnection packet, or a serial number log over from nothing. For a closer look at preparing for that scenario specifically, see ransomware restore readiness.
No. The roofing contractor page covers roof measurement, damage assessment, and insurance-claim documentation, records built around the condition of the roof itself. This page covers solar and battery storage installation: energy-system design, interconnection applications, utility correspondence, and commissioning records, records built around a system that a utility has to approve before it can operate. A solar crew may work on the same roof a roofer would, but the paperwork the two businesses generate is fundamentally different.
No. The field-service page covers recurring maintenance dispatch for HVAC, plumbing, and electrical contractors: a customer calls, a technician is scheduled, a ticket is closed, and the cycle repeats for the same equipment for years. Solar installation is project-based. Each job runs once, from a signed contract through permitting, interconnection, inspection, and commissioning to permission to operate, and the records this page focuses on reflect that permit-to-PTO lifecycle rather than recurring service history.
No. The contractor and construction page covers general building work: framing, structural changes, trade coordination, and building permits tied to construction code. Solar installation is a specialty energy trade. The permit is for an energy system rather than a building, and the interconnection packet submitted to a utility, along with the utility's own review and correspondence, has no equivalent in a general construction project.
Not independently. Solar design and proposal software, named here only as a description of the software category and not as an endorsement or compatibility claim for any specific product, holds a copy of your project's design and proposal data under its own systems, which is not the same as a backup you control on your own timeline. Any design file, shade analysis report, or proposal exported or saved to a Windows machine in your office needs to be in your own backup like any other file on that computer.
Not on its own. A sync tool mirrors the current state of a folder, so a deletion, an overwrite, or a ransomware encryption event propagates to the synced copy too, often within seconds. Backup keeps earlier versions on purpose, which is what lets you recover a permit set or an interconnection packet as it existed before the damage rather than after it. See cloud sync vs. backup for a full comparison.
Yes, when the QuickBooks company file location is included in your backup scope. QuickBooks company files are frequently kept on a single office computer with no second copy, and Intuit's own documentation notes that backing up only to the same machine is not adequate protection. See our QuickBooks backup guide for how to confirm your file is properly covered.
No. Everyday Backups makes no claim about interconnection requirements, permitting procedure, electrical code, NEC compliance, electrical licensing, utility compliance, solar production, energy savings, payback periods, tax credits, incentives, rebates, or system performance or warranty validity. A backup is a data recovery tool, not a compliance program, an engineering review, or legal, tax, or electrical advice. The installer and its own licensed electricians, engineers, and legal counsel keep their own regulatory and code obligations regardless of what backup service is used.
Everyday Backups installs on Windows machines, backs up chosen files automatically on a schedule, encrypts data in transit and at rest, keeps version history so you can recover a prior copy, monitors for failed or missed jobs, and stores backups off-site rather than on local media that could be damaged in the same event as your primary computer. Paid plans start at $5.99/mo, with monthly reporting so you know coverage is working without checking it by hand. Take the free 2-minute self-check to see where your current setup stands, or review the small-business backup checklist for a broader assessment. For a closer look with our team, schedule a free 15-minute Backup Risk Check.
Whether you want to check your current situation on your own 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 and device backup service for Windows computers, not solar, electrical, tax, incentive, engineering, or code advice, and not legal, regulatory, or compliance advice. A backup is a data recovery tool; it is not a security product and it does not protect customer personal information or financing paperwork from unauthorized access, breach, or misuse. It makes no claim about solar system production, energy savings, payback periods, tax credits, incentives, rebates, interconnection requirements, permitting procedure, electrical code, NEC compliance, electrical licensing, utility compliance, or system performance or warranty validity, and it does not by itself satisfy any contractor-licensing, permitting, interconnection, record-retention, consumer-protection, or other legal or regulatory requirement applicable to a solar or battery storage installation business. References to site surveys, shade analyses and production models, system designs, permit and plan sets, interconnection packets, utility correspondence, inspection and commissioning photos, equipment serial numbers, warranty registrations, customer contracts, and financing paperwork refer only to ordinary operational files saved to Windows machines and are not claims that Everyday Backups satisfies any regulatory recordkeeping, licensing, engineering, or code obligation. No compatibility with any specific solar design, proposal, CRM, or accounting platform is guaranteed or implied; verify backup scope and file coverage with your own IT review. Mention of software categories such as solar design and proposal software or solar CRM is illustrative only and is not an endorsement or a compatibility claim for any specific product. References to CISA, FTC, and Intuit documentation are for informational context only and do not constitute endorsement by those organizations. The installer and its own licensed electricians, engineers, and legal counsel keep their own regulatory, code, permitting, and recordkeeping obligations regardless of what backup service is used. Consult qualified legal, tax, engineering, and licensing 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