Volume 18, Chapter 4
Power, Generators, and Utility Continuity
Definition
An unannounced grid outage hit MANIAC MINDZ in the middle of a rush order. The generator started, ran for four minutes, and stopped. Nobody had checked its fuel in weeks. Production stopped for the rest of the afternoon, and a promised same-day delivery slipped by a full day.
is keeping the business running, or failing in a controlled way and recovering fast, when the grid, water, or another basic utility stops without warning. In most markets, an outage isn't a rare disaster, it's a routine operating condition.
Why did a generator that was sitting right there, ready to help, do nothing? Because a backup that hasn't been checked isn't actually a backup, it's just equipment that happens to still be in the building. Readiness has to be verified regularly, the same way Chapter 2 treats any other equipment, or it quietly stops being ready without anyone knowing.
Treat backup power like any other equipment: inspected regularly, logged consistently, and never assumed to be ready just because it worked last time. A generator with no fuel is not a backup, it's a decoration.
Matching Power Sources to What Actually Needs Them
| Power Source | Typical Role | What It Should Cover First |
|---|---|---|
| Grid power | Primary source | Everything, when available |
| Generator | Planned backup during longer outages | Machines mid-production, refrigeration, security systems |
| Inverter / battery backup | Instant, silent bridge during the switch-over | POS and computer systems, so an in-progress sale or record isn't lost mid-entry |
Not everything deserves power at the same priority. A generator with barely enough capacity should protect machines-in-progress and security first, a phone charger can wait.
The Generator Log
A generator is exactly the kind of asset Chapter 2's inspection tiers already apply to: a quick daily fuel check, a weekly run-test, and scheduled servicing, logged every time, using the Generator & Power Log.
| Check | Frequency |
|---|---|
| Fuel level | Daily |
| Test run (even briefly) | Weekly |
| Oil change / full service | Per manufacturer schedule |
The Outage Response Procedure
| Step | Action |
|---|---|
| 1. Confirm it's an outage, not a local fault | Check with a neighbor or the utility's outage line |
| 2. Switch to backup per the written order in Section 2 | Don't improvise the priority list mid-crisis |
| 3. Protect in-progress work | Save/close open records before backup power runs low |
| 4. Log the outage | Duration, cause if known, cost impact, feeds Volume 23's mistake log if it's a repeat pattern |
Example Story: The Generator That Had No Fuel
Here's the full version of the four-minutes-then-stopped story from the start of this chapter.
An unannounced grid outage at MANIAC MINDZ during a rush order revealed the generator hadn't been checked in weeks. It started, ran for four minutes, and stopped: out of fuel, with no backup plan beyond it. Production stopped for the rest of the afternoon, and a promised same-day delivery slipped by a full day.
The business didn't need a bigger generator. It needed the habit of checking the one it already owned. A simple daily fuel check, logged every morning during Chapter 1's opening routine, ended the problem for good.
Across Industries
What backup power needs to protect first depends on what actually stops the business when it's lost.
| Business | A Utility Continuity Practice |
|---|---|
| Golden Crust Bakery | Backup power prioritized to ovens mid-bake, not the shop lights |
| Rapid Auto Works | Diagnostic equipment on an inverter, so an outage doesn't corrupt a reading mid-test |
| Precision Print & Press | A print job mid-run protected first, a half-finished job often can't simply resume where it left off |
Common Mistakes
This is the exact assumption that failed in the example story. Readiness has to be checked, not assumed.
Forces someone to improvise what gets power first during an actual outage, under pressure.
A recurring pattern (same time of day, same season) stays invisible without a record. This is exactly Volume 23's argument for logging consistently.
Quiz Yourself
Practice Exercise
Check your generator's fuel level and last service date right now. Start logging it daily using the Generator & Power Log, and write down your backup power priority order before the next outage, not during it.
Quick Summary
Quick Summary
- Treat backup power like any other equipment: inspected regularly, logged consistently, never assumed ready.
- Set a written priority order for what gets backup power first, machines-in-progress and data systems before convenience items.
- Log every outage; a repeating pattern is only visible once it's recorded.
- Volume 18 complete. Next, Volume 19: Project Management covers managing big, one-off jobs.