Business Continuity Planning for West Texas Offices
Ask most small business owners in West Texas what happens if the office goes dark tomorrow, and you will get an honest shrug. Maybe a spring storm knocks out power in Lubbock. Maybe hail takes out the roof over the server closet in Amarillo, a dust storm cuts visibility so staff cannot safely drive in from Levelland or Brownfield, or ransomware locks every computer in a Midland-Odessa office overnight. The cause changes. The question stays the same: how does the business keep serving customers while things get fixed?
That is what a business continuity plan answers. It is not a binder for the shelf. It is a short, practical set of decisions made ahead of time, so nobody is guessing under pressure.
Business continuity vs. disaster recovery vs. backups
These terms get mixed up, so it helps to separate them:
Business continuity is the whole-business plan: how you keep taking calls, serving customers, paying people and meeting obligations during a disruption.
IT disaster recovery is the technology piece inside it: how you restore computers, applications, internet and data. Ready.gov says the IT disaster recovery plan should be developed together with the business continuity plan, and that IT recovery priorities should match the business priorities.
Backups are one ingredient of recovery. They matter a lot, but a backup alone does not tell anyone where to work, who calls customers or which system comes back first.
If you have already worked on backups, good. We cover how to prove they restore in How to Know Your Backups Will Actually Restore. This post is about the bigger plan around them.
Step 1: Figure out what actually has to keep running
Ready.gov recommends starting with a business impact analysis, which predicts the consequences of a disruption and gathers what you need to build recovery strategies. In plain terms, sit down with the people who run each part of the business and ask:
What do you do every day that customers or the business depend on?
If you could not do it for an hour, a day or a week, what would happen?
What do you need to do it: people, software, data, phones, internet, equipment, paperwork?
Ready.gov points out that timing matters. A short power outage is a minor inconvenience for most businesses, but one lasting hours can cause real losses. A CPA firm in March, a gin office in harvest season and a clinic on a full patient day all feel the same outage very differently.
When you are done, rank your functions. The ones with the biggest operational and financial impact get restored first. That ranked list is the heart of the plan.
Step 2: Set two simple targets for each critical system
For each important function, agree on two numbers. Ready.gov and NIST both use these terms:
Recovery time objective (RTO): how long that function can be down before the damage becomes unacceptable.
Recovery point objective (RPO): how much recent data you can afford to lose. If your RPO for the accounting system is one business day, backups need to run at least that often.
Ready.gov notes that the recovery time for each IT resource should match the recovery time objective of the business function that depends on it. In other words, do not promise the front desk it will be back in two hours if restoring its server takes two days. Now is the time to find that gap, not during an outage.
Step 3: Plan for the disruptions West Texas actually sees
Ready.gov lists common disruption scenarios worth considering, including physical damage to a building, restricted access to a site, utility outages such as power, and damage to or loss of IT, voice and data communications. Here is how those tend to look out here.
Severe weather and building damage. Hail and high winds can damage roofs, windows and rooftop equipment. Ask what happens if the room with your server, firewall or phone system takes water. Keep critical equipment off the floor and away from roof leaks where you can, and know where you would work if the building were closed for a week.
Dust storms and travel. The National Weather Service notes that dust storms are most common in the Southwest, can arrive suddenly and can drastically reduce visibility. If staff cannot safely drive in, can they work from home with secure access to the systems they need? Test that before you need it.
Power outages. Ready.gov notes that power outages can disrupt communications and close businesses, and recommends unplugging electronics because power can return with surges. A battery backup (UPS) on servers and network gear buys time to shut down cleanly. For longer outages, decide what must run on a generator and what can wait.
Internet loss. Many rural South Plains offices rely on a single connection. If your phones, cloud apps and card processing all ride on it, one cut line stops everything. A second connection from a different provider, or a cellular backup for the firewall, is often the most useful continuity upgrade a small office can make.
Cyberattacks. CISA's #StopRansomware Guide recommends knowing which systems are most critical so you can set restoration priorities, keeping offline, encrypted backups, and keeping a hard copy and offline version of your incident response plan. That last point matters: if ransomware locks your network, a plan stored only on that network is gone too.
Cloud outages. Even cloud services go down sometimes. We walk through that scenario in How to Keep Your Business Running When Microsoft 365 Goes Down.
Step 4: Write down who does what
Ready.gov's business continuity planning process includes organizing a team and defining tasks. For a small office, that can fit on a page or two:
Who declares an emergency and decides when to switch to the backup plan
Who calls whom: a contact list for staff, your IT provider, internet carrier, insurance agent, key vendors and landlord, with personal cell numbers
How you reach customers: a short message for your phone greeting, website and social pages
Where people work if the office is unusable
Which systems come back first, in the order from Step 1
Where key information lives: account numbers, license keys, network diagrams and vendor contacts, kept somewhere that does not depend on the office being up
Keep a printed copy and a copy somewhere outside your network. CISA makes the same recommendation for incident response plans.
Step 5: Test it, then keep it current
A plan nobody has practiced tends to fall apart at the first surprise. Ready.gov includes testing as the final step of its planning process, and NIST SP 800-34 covers testing, training and exercises as part of keeping contingency plans useful.
You do not need a big production. A one-hour tabletop exercise works well: gather your managers, describe a scenario ("hail damaged the roof overnight and the server room has water" or "every computer shows a ransom note Monday morning") and walk through the plan step by step. Note where people get stuck. CISA offers free Tabletop Exercise Packages with ready-made scenarios, including natural disasters and ransomware, that small businesses can adapt.
Review the plan at least once a year, and any time you move offices, change key software, switch internet providers or lose a key employee.
How Double Technologies helps
Double Technologies helps businesses in Lubbock, Amarillo, Abilene, Midland-Odessa and across the South Plains build continuity plans that fit how they actually work. That includes ranking critical systems, setting realistic recovery targets, setting up backup and disaster recovery, planning for backup internet and power, and running tabletop exercises with your team. Our team brings 30 years of combined experience, and we can work remotely or come to you. Our hours are Monday through Friday, 8 AM to 7 PM, and Saturday, 9 AM to 5 PM Central.
If you are not sure how your business would keep running through a storm, outage or cyberattack, call Double Technologies at (806) 319-8521 or contact us to set up a planning session.
Sources for further reading: Ready.gov, Business Continuity Planning; Ready.gov, Business Impact Analysis; Ready.gov, IT Disaster Recovery Plan; Ready.gov, Power Outages; National Weather Service, Dust Storms and Haboobs; NIST SP 800-34 Rev. 1, Contingency Planning Guide; CISA, #StopRansomware Guide; CISA, Tabletop Exercise Packages.




Comments