Copyright © 2026 Everyday Backups · everydaybackups.com · Secure cloud backup for small business & personal files
An independent propane dealer, LP gas distributor, heating oil company, or small bulk plant runs on a customer and tank file, not a mailing list. Every account ties back to a specific tank, its serial number, its size, whether the company or the customer owns it, and where it sits on a piece of property the dealer does not own. Layered on top of that tank record is a delivery history, a keep-fill or will-call designation, a degree-day usage pattern that drives when the truck goes back, and, for many dealers, a prepaid gallon balance the customer has already paid toward and not yet burned. Across rural Alabama, Georgia, Mississippi, Louisiana, and the Florida panhandle, that file is often what a dispatcher, a driver, and a bookkeeper all pull from before a single truck leaves the yard on a cold morning. Lose it in the middle of a heating season, whether to a cracked laptop screen, a dead office drive, or a ransomware note on the dispatch computer, and the tanks themselves do not move. What is gone is the map of which tanks belong to the company, which customers are on keep-fill and which call in, what each one has already prepaid toward, and when a system was last checked. A route built up over years of local relationships can be hard to run cleanly again without it.
Two different things, and you pick either one. The 2-minute self-check is a short set of questions you answer yourself, covering how your tank file, delivery tickets, and prepay records are currently protected. The free 15-minute Backup Risk Check is a review our team runs with you, by phone or screen share, going through where your customer and tank file, your delivery system, and your accounting records actually live, and what would happen to them if the dispatch computer stopped working in the middle of a delivery season.
Everyday Backups provides automatic, encrypted, off-site backup for Windows computers, with version history and restore support. It runs on Windows, iPhone, iPad, and Android, and paid plans start from $5.99/mo.
A propane or fuel delivery dealer does not run out of memory over a route of any size. It runs on a customer and tank file that is, in effect, a map of company-owned or company-leased steel sitting in other people's back yards, cross-referenced against who has prepaid for gallons they have not yet burned and when each system was last checked. Across rural Alabama, Georgia, Mississippi, Louisiana, the Florida panhandle, and the wider Gulf South, the list below is the record set many working dealers want to be able to put a hand on for any customer, any tank, or any delivery, on short notice.
A gap in any one of these categories tends to surface at the worst possible time, not before. A new dispatcher cannot tell whether a customer is on keep-fill or waiting on a will-call order. A customer calls asking why they were billed for a delivery when they thought they had prepaid gallons left, and the dealer's own balance record for that account is gone. A driver pulls up to an address with no gate code or dog warning on file. None of that is a paperwork inconvenience in a business where this file is often the practical way a dealer keeps track of which tanks sitting on other people's property actually belong to the company, and what each customer has already paid toward.
CISA promotes the 3-2-1 rule as a simple standard for small-business backup, and it maps directly onto how a propane or fuel delivery dealer actually holds its records: this week's active delivery tickets and prepay adjustments, and the growing archive of tank leases, service agreements, and account history built up behind them.
Your working copy is whatever sits on the dispatch computer or the bulk plant office machine today: this week's deliveries, current prepay balances, and the accumulated tank file and leases for every account on the books. A second copy on a local external drive or a second machine protects against one device failing. A third copy, off-site in encrypted cloud storage, protects the tank file and account archive, which is difficult to rebuild from memory once a season is underway, from a single event at the office or the plant taking out both of the first two copies at once.
A propane or fuel delivery dealer's tank file and account records grow with every customer and rarely get deleted outright, so relying on two drives of the same type in the same office just means both copies age and can fail together. CISA guidance calls for two genuinely different storage types, for example a local drive for quick access to the current delivery schedule and a separate cloud destination for the accumulating tank and account archive, so one kind of hardware failure cannot take out both at once.
Off-site matters more for a tank and customer file than for almost any other record category this business holds, because rebuilding an accurate map of which tanks belong to the company, and what each customer has already prepaid, is not something memory can do. Cloud backup satisfies the off-site requirement when the data goes to a separate data center rather than an external drive kept in the same office, and it is the copy that survives a fire, theft, or a flooded plant yard taking out the working files and the local backup together.
CISA recommends keeping at least one backup copy that is not continuously connected to the network. For this trade that matters most for the tank and account archive, since years of lease, service, and prepay records sitting on a mapped network drive at the office are exposed to the same ransomware sweep as this week's active delivery tickets. A cloud-based backup that is not directly mounted on your local network is far less likely to be reached and encrypted alongside the records it is meant to protect.
The items below are specific to how a propane or fuel delivery dealer's records are actually scattered across a dispatch office, a bulk plant, and whatever delivery or route software a given dealer uses. They are the starting point before anything else in this framework matters, not a complete checklist on their own.
For a broader self-assessment of your current backup posture, see the small-business backup checklist.
It helps to picture the actual day, rather than the abstract loss. The dispatch computer will not turn on, or it comes up with a ransom note instead of the route. The tanks themselves are exactly where they were left, sitting in customer yards across the county, full or low as they were before the computer failed. What is gone is the file that says which of those tanks belong to the company, which customers are on keep-fill and due for a delivery based on the last cold stretch, and what each one has already prepaid toward this season. A customer calls asking why a delivery has not shown up when they thought they were on keep-fill. Another is certain they have gallons left on a budget plan and the dealer's own balance record cannot confirm or dispute it. A driver heads to an address with no note about the gate code or the dog in the yard. None of the tanks are damaged. None of the propane already delivered has disappeared. What is gone is the dealer's own record of who owns what, who owes what, and who is due for a delivery, because that record lived on one computer, and rebuilding it from memory and a stack of paper tickets takes time a cold week does not have.
It is worth being precise about what a working backup does and does not do here. A recoverable copy of the tank file, the lease, and the delivery tickets means those records still exist and can be pulled back up. It does not make a lease, a service agreement, or a delivery ticket valid, enforceable, or sufficient proof that a system check, a delivery, or a repair was performed, and it does not decide what a customer, a landlord, or a regulator would accept as an answer. Those are questions between the parties involved, not for a backup product. What a backup changes is whether the record needed to even start that conversation is still there to look at, instead of gone along with everything else on one computer.
Two systems generate most of the records behind a propane or fuel delivery dealer: whatever delivery or route software the dispatcher uses day to day, and QuickBooks or a similar accounting platform. Knowing exactly what each one's backup covers, and where the gap is, matters because tank leases, service agreements, and tag photos often live partly outside either system.
Your delivery or route software typically holds the day-by-day delivery entries, keep-fill routing, and running prepay balances tied to your own setup and whatever it was built to track. It often does not hold scanned or signed tank leases and service agreements, tank installation records, gas check and system test notes, or tank tag photos saved to a phone or a shared folder. Being able to open the software is not a backup of any of it, it is access to a working tool, which is a different thing from a copy you control. If your delivery tracking lives in a hosted or online tool, the current entries may survive a failed office computer; what often does not survive is everything saved around it on that machine, such as scanned leases, tag photos, and your own notes, and you still depend on continued access to that tool to see your own records.
Cloud sync is a related but separate trap. A synced folder that mirrors the dispatch computer looks protected, but sync only mirrors what is currently there; delete a file or have it encrypted by ransomware, and the synced copy follows along. See cloud sync vs. backup for what each actually protects against.
A propane or fuel delivery dealer's QuickBooks company file tends to carry customer deposits, credit terms, prepay and budget plan balances, driver payroll, and a full season's worth of transactions in a single file that grows steadily and rarely gets deleted. Intuit's own documentation recommends a backup copy stored in a location separate from the original, and specifically notes that backing up to the same machine only is not adequate protection.
A common mistake at small propane and fuel delivery dealers is a built-in backup feature writing to a different folder on the same drive as the original, which does not protect against a drive failure. For a closer look at QuickBooks-specific backup steps, see QuickBooks backup for small businesses.
CISA and the FTC both flag small businesses as ransomware targets precisely because they tend to have thinner IT defenses than larger companies while still holding records worth extorting over. A propane or fuel delivery dealer fits that pattern with one added twist: what is at risk is not just one day's paperwork, it can be the dealer's own working map of which tanks belong to the company and what every customer has already prepaid. A dispatch computer running the tank and customer file is also exposed to the ordinary wear of a plant office, dust, heat, and the occasional power hiccup, on top of whatever risk a network connection brings.
For this trade specifically, the sharpest risk is the tank file and the prepay balances together. A ransomware event that reaches the office computer and any mapped network share holding leases, service agreements, and account history can encrypt all of it in one pass, at the same time it encrypts this week's active delivery tickets. Unlike a single delivery, which a driver's paper ticket might help confirm, the accumulated account-by-account tank and balance record built up over years is usually not held in complete form anywhere outside the dealer's own records.
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 office computer. For a fuller walkthrough, see ransomware restore readiness.
Backup is a recovery tool, not a security or privacy control, and it is worth saying plainly: encrypting and backing up the tank file, leases, and prepay records protects your ability to get them back if they are lost, corrupted, or ransomed, but it does not make the records secure, it does not make them private, and it does not stop anyone from misusing what is inside them. It also does not make a lease, a service agreement, or a check record any more valid, enforceable, or accurate than it already was. A tested backup shortens a bad week; it does not replace a dealer's separate security practices or its own diligence on fuel handling and customer agreements, and it is not offered here as a substitute for either.
A few other pages on this site cover businesses that sit near a propane or fuel delivery dealer but are not the same thing, and it is worth being explicit about the boundary so you land on the right one.
If your operation also runs broader freight or hauling beyond your own bobtails and transports, our page on trucking and small freight carrier backup may also be relevant. If your business spans more than one of these descriptions, more than one page may apply, but the tank and customer file described above is what this page is built around.
Our field-service page covers HVAC, plumbing, and electrical contractors who run work orders and service history against equipment a customer already owns at a fixed address. A propane or fuel delivery dealer's core record is different in kind: a customer and tank file that ties each account to a specific tank the dealer often owns or leases, sitting on a property the dealer does not own, tracked alongside a prepaid gallon balance and a keep-fill or will-call delivery pattern. A work order describes a job. A tank record describes a leased asset, a fuel balance, and a recurring delivery schedule all at once. The dispatching overlaps; the record set underneath it does not.
A convenience store or gas station sells fuel over the counter or through a pump to whoever pulls in, settled at the point of sale with records that center on register totals, fuel inventory at the site, and point-of-sale data. A propane or fuel delivery dealer sells metered product delivered by truck from its own bulk plant to tanks it often owns or leases at customer addresses, on a schedule driven by usage history rather than walk-in traffic, with prepaid balances that can span months. One business tracks a site. This one tracks a route and a thousand tanks scattered across other people's property.
A trucking or freight operation moves goods it does not own between a shipper and a receiver, and its core records are dispatch, load, and settlement paperwork for freight that changes hands at pickup and delivery. A propane or fuel delivery dealer's trucks deliver a product the dealer produced or purchased into its own bulk plant, into tanks the dealer frequently owns or leases and monitors over time, tied to a customer account with a running prepaid balance. The freight business tracks a load moving once between two parties. This business tracks a tank that sits in the same yard for years and a balance that carries forward delivery after delivery.
No. Sync keeps a folder looking identical across every device connected to it, so a deletion, an overwrite, or a ransomware encryption event on one device shows up in the synced copy just as fast, often within seconds. Backup keeps point-in-time versions you can reach back to from before the damage happened. For a tank file built account by account, delivery by delivery, that cannot be re-driven to recreate a missing entry, that version history is what actually protects you. See our comparison of cloud sync vs. backup for the full explanation.
Two different clocks apply here. Day-to-day version history exists to undo a recent mistake or a recent ransomware event, so it needs to reach back far enough that you can still return to a copy from before the problem started. Separately, many propane and fuel delivery dealers choose to keep tank leases, delivery tickets, and prepay records for a customer relationship, a budget-plan cycle, or longer for their own business reasons. How long any particular record needs to be retained is a business decision, and in some cases a legal one, for your own advisors; this page addresses only whether the records you decide to keep can actually be recovered.
Treat it as something to look at that day, not at the next slow week. Common causes each point to a different fix: a dispatch laptop was powered down overnight and never connected during the scheduled backup window, a file was open in another program, a drive filled up, or a login or network issue blocked the upload. A failure that sits unresolved for a few weeks in the middle of a busy heating season means there is no real coverage during exactly the stretch when the most deliveries, tickets, and prepay adjustments are being logged. Alerting on failure, rather than discovering it later, is the baseline fix.
No. Everyday Backups is a backup and recovery service, not a compliance, certification, or regulatory product. It makes no claim about satisfying any fuel handling, gas check, leak check, relight, or system test recordkeeping requirement, any driver qualification or training requirement, any meter calibration or weights and measures requirement, or any record-retention obligation that may apply to your operation. A copy of a gas check record, a driver credential, or a calibration certificate that you already keep is a file like any other file to this service; whether keeping it, and for how long, satisfies any requirement is a question for your own advisors or the relevant regulatory body, not for this page or this service.
No. Everyday Backups makes no claim that a backed-up tank lease, customer service agreement, delivery ticket, or gas check, leak check, relight, or system test record is valid, enforceable, or sufficient proof of what was checked, delivered, or performed, and no claim about what a customer, a landlord, or a regulator would accept as an answer. A recoverable copy of a document means the document still exists and can be produced; whether its terms hold up, or whether it establishes that a procedure was carried out correctly, is a legal, safety, or business question for the parties involved and your own advisors, not something a backup service determines.
No. Fuel handling and delivery procedures, leak checks, relights, system tests, odorization, tank siting, driver qualification, DOT, PHMSA, OSHA, and state fire marshal requirements, weights and measures rules, environmental questions, and the tax or insurance treatment of your business are matters for your own attorney, safety professional, regulatory contact, tax preparer, or insurance agent. Everyday Backups gives no advice on any of it. It only helps you keep a recoverable copy of the tank file, contracts, tickets, and records you already produce in the course of that work.
It installs on Windows machines, whether that is the dispatch computer running the tank and customer file, an office computer at the bulk plant that holds leases and delivery records, or a second machine used for accounting, watches for failed or overdue backup jobs and alerts when one happens, keeps version history so a file can be pulled from an earlier point in time, encrypts data in transit and at rest, and sends the copy to off-site cloud storage rather than local media that could be lost in the same event as the originals. It is meant to be set up once and then run quietly in the background through the busiest weeks of a heating season. Each Windows machine that touches the tank file or the delivery records needs its own coverage.
Everyday Backups is a backup and recovery service, not legal, safety, regulatory, tax, or insurance advice. It gives no propane, LP gas, fuel handling, leak check, relight, system test, odorization, tank siting, driver qualification, DOT, PHMSA, OSHA, state fire marshal, hazmat, meter calibration, or weights and measures advice, and no tax or insurance advice. It does not by itself satisfy, and makes no claim of satisfying, any fuel handling recordkeeping, reporting, or record-retention requirement, or any driver training, certification, or meter calibration requirement. It makes no claim that a backed-up tank lease, customer service agreement, delivery ticket, or gas check, leak check, relight, or system test record is valid, enforceable, or sufficient proof of what was checked, delivered, or performed. A backup is a data recovery tool, not a data security or privacy product, and backing up a record does not make that record secure, private, or compliant with any rule. No compatibility with any specific delivery, route, or accounting software is guaranteed or implied; verify backup scope and file coverage with your own review. References to CISA, FTC, and Intuit documentation are for informational context only and do not constitute endorsement by those organizations. Consult qualified legal, safety, regulatory, tax, and insurance professionals for requirements specific to your operation.
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