Management Review & Continuous Improvement

This domain measures whether anyone reviews the program — and whether reviewing it changes anything. Both parts.

At 5 points it is the lightest domain in the REALTIMEais 70B READINESS SCORE, and that is deliberate. It is also the one most facilities skip entirely, which makes it the cheapest points in the whole framework. Here is the paradox: it is often the first thing an auditor asks about, because the answer reveals in one question whether the program is alive or on paper. Everything else takes sampling to figure out. This one takes a sentence.

The standard makes it a required element, not a nice habit. Section 4.2.4.2 of NFPA 70B (2026), item nine: a program review and revision process that considers failures and findings for continuous improvement. The review is supposed to eat the program’s own history and produce changes. Beyond the internal review cycle, the standard requires the program itself to be audited on a defined interval not exceeding five years. Review is the heartbeat; the audit is the physical. So the smallest domain carries the biggest tell. When the program has a working review loop, every other domain slowly gets better on its own. When it doesn’t, every other domain slowly rots — including the ones you fixed last year.

Five criteria — the shortest list on the board — each scored and weighted on its own:

1. The program is formally reviewed on a defined interval. Formally: an agenda, attendees, a date. Hallway consensus is not a review.
2. The review considers failure history and near-misses. A failure teaches you what already went wrong; a near-miss teaches the same lesson at a fraction of the price.
3. Review outcomes generate documented changes. Reviews produce revisions — to an interval, a procedure, a scope — or they produced minutes.
4. Metrics are defined and tracked: on-time completion rate, open corrective actions, overdue items — a handful of numbers the review actually looks at, trend over trend.
5. Resources are evaluated against program requirements. Can the program as written be executed with the people and budget it has? A program funded for half its own requirements is a finding waiting for its date.

What good looks like is refreshingly ordinary: an annual review with an agenda, attendees, and outputs. It looks at what failed, what nearly failed, whether intervals are being met, and whether the program has the resources to execute. And it produces changes — a revised interval, a new equipment class added to scope, a budget request with data behind it. One meeting a year, honestly run. That is the whole domain, and the highest ratio of points-to-effort anywhere in the framework — which is why it stings to see it scored zero as often as it is.

What this domain is worth

Five percent of the score, and worth more than that. The cost of the gap: drift — last year’s fixes quietly rot because nothing checks on them, so you pay for the same improvement twice. Resources never matched to scope, so the program is funded for half of itself and fails on schedule. And budget requests with no data behind them, which get cut first every time. The return: the review is where the ROI of every other domain actually gets captured — findings move intervals, and intervals move dollars. A budget request with trend data behind it survives the meeting. And five points for one honestly run meeting is the best points-per-hour anywhere on the board. One meeting a year, honestly run, is the highest-return hour in the program.

The test for the entire domain fits on one line: a review that produces no changes isn’t a review. It’s a meeting. A facility showed me five consecutive years of annual program review minutes — same agenda, same attendees, and almost word-for-word the same conclusion: “program operating satisfactorily, no changes recommended.” In those same five years the plant had added a production line, lost two electricians it never replaced, deferred three shutdowns, and had a bus fault that took down half the facility for a day. The program had absorbed all of that, and the review had noticed none of it. Those minutes weren’t evidence of oversight. They were evidence of its absence, signed and dated annually. The auditor read them the same way I did, in about ninety seconds. If your review has never once changed an interval, a procedure, or a budget line, it isn’t reviewing anything. It’s renewing a subscription.

Three questions to ask your program this month:

• When did we last formally review the EPM program — and what changed as a result? The second half is the score.
• What metrics do we track — and does anyone look at them? A dashboard nobody opens is a screensaver.
• Does our failure history feed back into our intervals? The last three failures — did any of them move a schedule?

Send one to your maintenance lead today. That closes the eight-domain series — and Management Review is the domain that keeps the other seven honest. The full REALTIMEais 70B READINESS SCORE assessment is free at REALTIMEais.com/readiness, scored in REALTIMEais, The Electrical Intelligence System™ — where the compliance dashboards make the review agenda write itself.

LinkedIn teaser

Five years of annual program review minutes. Same agenda. Same attendees. Same conclusion, almost word for word: “Program operating satisfactorily. No changes recommended.”

In those same five years: a new production line, two electricians lost and never replaced, three shutdowns deferred, and a bus fault that took down half the plant for a day.

The program absorbed all of it. The review noticed none of it.

Those minutes weren’t evidence of oversight. They were evidence of its absence — signed and dated annually. The auditor read them in about ninety seconds.

A review that produces no changes isn’t a review. It’s a meeting.

NFPA 70B 4.2.4.2(9) requires a review process that considers failures and findings — and produces changes.

The money: the review is where the ROI of every other domain gets captured — findings move intervals, intervals move dollars, and a budget request with trend data behind it survives the meeting. Without it, last year’s fixes quietly rot and you pay for them twice. One meeting a year, honestly run, is the highest-return hour in the program.

Part 8, the last in the REALTIMEais 70B READINESS SCORE series: Management Review & Continuous Improvement — 5% of your score, the cheapest points on the board, and the first thing an auditor asks about.

One question for today: when did we last review the program — and what changed because of it?

Free assessment: REALTIMEais.com/readiness — The Electrical Intelligence System™

#NFPA70B #ContinuousImprovement #ElectricalMaintenance #REALTIMEais