Controlled power event

Prove the shutdown path once, before an outage makes it urgent.

Use the exact critical load and reserve that matter, record one observed power event, then keep a compact proof record that can be repeated after a material change.

Power-event record

Turn an outage assumption into one controlled event you can repeat.

Record the intended load, continuity window, observed battery time, and the event checks that prove storage or services stopped and restarted as expected.

View assumptions and sources →

The values below are editable planning baselines. Change the few inputs you know; open Advanced assumptions only when they change your decision.

Required event window——

Observed runtime margin——

Event checks completed——

Verification state——

Event evidence

Check only what the controlled event actually demonstrated.

Keep the steps and outcomes with the equipment path. The local record excludes credentials, host names, and private notes.

The device received the power-event signalThe host, NAS, or shutdown integration detected the outage as intended.Services and storage stopped in the intended orderConfirm the stop sequence completed before energy was exhausted.The path restarted without an unexpected recovery conditionCheck the equipment and expected services after normal input power returns.The event steps and missing dependencies were recordedKeep a short repeatable procedure beside the continuity equipment path.

Next verification gap

—

Power-event record

Keep one proof record close to the system.

Copy, share, or save the tested load, runtime result, and completed checks so the same event can be rerun after a change.

Next decision

Return to continuity plan Review shutdown reserve

Plan tools

Keep this useful version close, shareable, and easy to revisit.

Reset inputs