UPS Runtime Checklist: The Battery That Buys You Ten Minutes You Did Not Schedule

The quick version: the power cut that hurts a small business is almost never the long one — that's a closure, and everyone knows how to react. It's the two-minute flicker that lands in the middle of a payment batch, a stock count, or a database write, and leaves the business rebooting a half-dead file server with a customer's card machine blinking. A UPS is cheap insurance against exactly that: enough battery to ride through the flicker, or to shut things down cleanly when the power doesn't come back. This page gives the four-question sizing check, the quarterly battery test that catches the dead cell before the storm does, and the shutdown order that protects the database instead of the monitor.

What a UPS actually buys

Strip the marketing: a UPS does two jobs, and only two. Ride-through — a flicker or brownout shorter than the battery never reaches your equipment at all. Graceful exit — if the power stays out, the battery buys you minutes to shut down in the right order instead of yanking the disk out from under the database. It does not buy a workday; a desktop drawing 150 W drains a mid-size UPS in ten to twenty minutes, and anything with a laser printer attached does worse. Businesses that expect runtime from a UPS bought the wrong product: for hours of runtime you want a generator or a battery power station; for minutes of clean shutdown, a UPS.

The four-question sizing check (once, ten minutes)

1. What plugs in? Only what must survive: the router/modem, the switch, the file server or NAS, the point-of-sale machine, and one workstation. Not monitors (they can reboot), not printers, not the kettle — every socket you protect divides the battery thinner.
2. What does it draw? Add the wattage (nameplate is fine; a plug-in power meter is better). A typical small-office protected set — router, switch, NAS, one desktop — draws 80–150 W. A POS terminal with a card reader adds 30–50 W.
3. How long to ride through? At 100 W draw, a 600 VA/360 W unit holds roughly five to eight minutes; a 1500 VA/900 W unit holds twenty-plus. Match runtime to the shutdown you need, plus margin — not to the outage you fear.
4. How long to shut down clean? Time it once: NAS gracefully powering off, 3–5 minutes; database flush, 2–5; everything else, seconds. If your runtime is four times your shutdown time, you're sized. If it isn't, buy a bigger battery or protect fewer sockets.

The quarterly battery test (ten minutes, four readings)

UPS batteries die quietly — sealed lead-acid cells lose capacity from heat and age, and the unit's own self-test lies about it. Every quarter, run four readings and write them down:

• Runtime at load. Pull the wall plug under real load and time how long the equipment holds. Compare to the same reading a year ago; capacity that has fallen by a third is a battery on borrowed time.
• Alarm check. The unit should beep on the transfer and again on low battery. A UPS that never alarms is a UPS nobody would notice failing.
• Self-test result. Run the unit's own battery test after the pull-the-plug one — the internal test is a claim, the wall-pull is evidence.
• Date on the battery. Sealed lead-acid lasts 3–5 years at room temperature, less on a warm shelf. Past four years, price a replacement — for many units the cell swaps in ten minutes with a screwdriver.

Log the four readings next to your other quarterly checks; a runtime column that shrinks across quarters is the early warning no dashboard provides.

The shutdown order (protect the database, not the monitor)

When the lights stay out and the battery is draining, order matters. Equipment tolerates a hard cut in reverse order of damage:

1. Databases and point-of-sale first. Close the POS session, stop the accounting package, flush and stop the database service. These are the only machines that corrupt when the power dies mid-write.
2. File servers and NAS second. Trigger the graceful shutdown; the NAS rebuilds its array the polite way only if you let it stop politely.
3. Workstations third. Save, close, shut down. Two minutes, and the half-written document survives.
4. Network gear last. Router and switch stay up until everything behind them is down — they carry the shutdown commands and the cloud backups.

If the UPS speaks USB to the NAS or server, configure it once to do this automatically — a scripted shutdown beats a sprint across the shop, and it works at 2 am when nobody is in the building.

Worked example: the bakery's flicker

A bakery ran its till and card machine off one power strip with everything else — ovens included. A summer brownout cut power for ninety seconds during the Saturday stock count; the till rebooted mid-batch, the card machine lost its terminal key, and the morning took forty minutes to reconcile by hand. The oven, being a dumb resistive heater, never noticed.

The fix cost one afternoon: a 900 W UPS under the counter carrying the till, the card machine, and the network gear. The quarterly test times the runtime (nineteen minutes at their load), and the UPS's USB cable tells the till to close the batch and shut down cleanly if the outage passes six minutes. The next flicker — six months later — was a non-event: the till blinked, the count continued, nobody looked up.

The four traps

• Runtime theatre. A big UPS whose sockets carry monitors and a printer — the battery spent on things that don't care about power while the database rode bare.
• The never-tested battery. The unit passed its 2019 purchase test and has been a paperweight since 2022. The wall-pull test is the only one that counts.
• The daisy-chained strip. A surge strip feeding a UPS (or a UPS feeding a strip) trips protections against each other; wall socket to UPS to equipment, nothing between.
• The shutdown that needs a human. A runtime plan that assumes someone is standing next to the server when the lights go out — configure the automatic shutdown once and let the cable do the sprinting.

From the HIVE80lab kit

Every page ships with a kit block — the paid tools behind the free advice:

• The First 30 Minutes — free incident quick-start checklist
• Ops Starter Kit — incident response for small teams — $14
• Ops Starter Kit Vol. 2 — advanced incident response & communications & $27
• Ops Mega Bundle — all 5 kits in one download — $49

Related: the power failure IT checklist covers the morning after — what to check when the power returns and the machines come up in the wrong order; the backup restore drill checklist is the safety net for the outage that outlasts every battery; the annual leave coverage checklist is the same principle for people — plan the transfer before the absence, not during it; and the seasonal peak readiness checklist is when the flicker risk is highest, because summer heat and winter storms are the two seasons that kill power and batteries alike.the generator transfer checklist is the next rung up the power ladder — the monthly transfer test that proves the transfer switch, not just the engine;