In the world of ISO 22301 (Business Continuity), there is one metric that rules them all: “Percentage of Plans Reviewed Annually.”

Every year, the Business Continuity Manager chases department heads to sign off on their documents.

The emails go out: “Please review and sign your BCP by Friday.”

The department heads, drowning in work, open the PDF, scroll to the bottom without reading, and click “Approve.”

The dashboard turns green. The auditor is happy. The organization is “safe.”

This is a lie.

That “Annual Review” stamp doesn’t prove your plan is valid. It only proves your plan is compliant.

A plan that is only touched once a year is dead for the other 364 days. In a dynamic operational environment, a “dead” plan is a dangerous plan.

It is time to kill the vanity metric of “Annual Review” and replace it with the metric of reality: Days Since Last Edit (DSLE).

The Reality Gap: The Speed of Change vs. The Speed of Paper

Your plant is a living organism. It changes every single day.

• Monday: A bypass line is installed around Pump B.
• Wednesday: The IT department patches the server, changing the login protocol.
• Friday: The warehouse reorganizes the spare parts rack.

If your Business Continuity Plan (BCP) was signed off in January, and it’s now October, it is already a historical fiction.

When a crisis hits in November, your team will open the binder and look for a spare part that moved three months ago.

The gap between the “Paper Reality” (the BCP) and the “Plant Reality” is where resilience fails.

The New Metric: Days Since Last Edit (DSLE)

If you want to know if your organization is truly resilient, stop asking if the plan is approved. Ask when it was last touched.

Days Since Last Edit (DSLE) measures the time elapsed since a human being engaged with the document enough to change it.

• Low DSLE (0-30 Days): The plan is alive. The team owns it. They are likely using it for training, drills, or “Modding” it to match reality. This signals Octalysis Core Drive 4: Ownership & Possession.
• High DSLE (300+ Days): The plan is an artifact. It is likely maintained solely for compliance (Core Drive 8: Loss & Avoidance). It will not survive contact with a real disaster.

Why “Staleness” is a Leading Indicator

In safety, we talk about “Leading Indicators” (Near Misses) vs. “Lagging Indicators” (Accidents).

In resilience, Staleness is your leading indicator of failure.

If a critical recovery procedure hasn’t been edited in two years, one of two things is true:

1. Your business has remained perfectly static (unlikely).
2. Your team has disengaged from the resilience process (highly likely).

A high “Staleness Score” tells you exactly where your culture is rotting. It highlights the departments that view BCP as a “Compliance Burden” rather than an operational tool.

Actionable Advice: The Heat Map

Don’t wait for the annual audit. Gamify the freshness of your plans today.

1. Audit the Timestamps: Go into your document management system. Sort your BCP documents by “Last Modified Date.”
2. Build a Heat Map: Visualize your plant. Color-code zones based on Staleness.
   • Green: Edited < 90 Days ago.
   • Yellow: Edited < 180 Days ago.
   • Red: Edited > 365 Days ago.
3. Target the Red Zones: Don’t send a generic email. Walk to the “Red Zone” department. Ask them: “Nothing has changed in your operation in a year? Really?”
   Challenge them to find one thing in the plan that is wrong. When they find it (and they will), have them update it immediately.

Conclusion

Resilience is not a state of being; it is a rate of change.

If your operations are evolving faster than your documentation, you are creating risk every day.

Stop celebrating the “Approved” stamp. Celebrate the “Edit” timestamp.

A messy, frequently updated plan is infinitely safer than a pristine, stale one.

Next Step:

Check the “Last Modified” date on your own Department’s Disaster Recovery Plan. If it’s older than the milk in your fridge, you have work to do. Update it today.

The information in this article was partially generated by Google’s Gemini, an AI language model, and has been reviewed/edited for accuracy and relevance.