CONNECTED. PROTECTED. READY FOR WHAT’S NEXT.
After a Power Outage: An Anonymous Business Recovery Story
Getting equipment back online is only part of recovery. This anonymous HVAC example shows why staff access, a known support contact and a clear restart check matter.
The call during the outage
During a February 2026 power outage lasting approximately a day, an HVAC service business ran into problems with its QuickBooks server. The client contacted its dedicated IT MGMT representative directly when the normal support-ticket route was unavailable.
The representative already knew the setup and monitored network activity for the return of connectivity. The client’s name, precise location and exact incident timetable are omitted to protect its privacy.
Power returned. Then we checked the work.
Within seven minutes of power returning, IT MGMT confirmed that operations were back up, including checking each office user’s connectivity. The goal was to verify that people could actually work, rather than stop at seeing equipment come online.
The seven-minute figure describes this particular recovery, reported by IT MGMT. It starts when power returned; it is not the duration of the blackout or a promise for another incident.
A stronger backup-power plan
After the incident, we upgraded the network and server battery-backup arrangement from approximately 12 hours to an estimated 24-hour runtime. The estimate was based on APC guidance and the equipment’s power requirements.
The UPS communicates battery status through the server, keeping our team informed about remaining runtime so we can update the office during an outage. Actual battery runtime varies with load, battery condition and circumstances; 24 hours is an estimate, not a guaranteed result.
What changed afterward
As of September 2026, Adam Gross reports that this client has had no further QuickBooks server issues since the engagement. That is an owner-reported observation, not an independently audited result or proof that backup power was the only possible cause.
The business remains anonymous. No client quote, location or financial outcome is implied.
Apply the lesson: build a restart checklist
You do not need to run an HVAC company to use the lesson. For your own office, agree these checks with the person responsible for IT before an interruption:
- Write down a fallback contact. Keep an approved support number somewhere staff can reach if the usual portal or office network is unavailable.
- Name the work that must restart. List the applications, shared files and communications staff need, along with their owners and any outside vendors.
- Agree who checks access. Choose someone to confirm a normal work task from a staff device. A server responding does not establish that every person can work.
- Record what remains unavailable. Separate restored access from unresolved application or vendor problems, and give the team a next update time.
- Review the weak point afterward. Decide whether backup power, contact information or recovery documentation needs attention.
This is a planning checklist, not an instruction to switch power equipment or a record of additional work performed for the anonymous client. A UPS runtime estimate and a data-backup recovery test answer different questions; discuss both when defining your recovery plan.
Questions worth asking about your own setup
- Can staff contact support when the normal ticketing route is unavailable?
- Which equipment needs backup power, and is its runtime estimate based on the actual load?
- Who receives low-battery information and keeps the business informed?
- Does the recovery check include staff access to the applications they need?
LET’S BUILD WHAT’S NEXT
Your next chapter
starts with a conversation.
Tell us where you are. Let’s talk about where you want to go.
