The baseline: does a documented disaster recovery plan exist? Draft is acceptable but flagged for follow-up; no plan is a hard finding.

Named role accountable for plan maintenance and execution. Required for any meaningful test/review discipline downstream.

Scope of what the plan covers — district-wide infrastructure, specific systems, or undefined. Scope clarity is the precondition for meaningful RPO/RTO discussions (see Recovery Objectives).

Cadence and last completed review of the plan document. Reviewed plans stay aligned with the actual environment; un-reviewed plans drift into shelfware.

Cadence and last completed test of the plan. Reviewing a plan is not testing it. Never-tested plans are operational fiction until proven otherwise — companion to the Restore Verification surface.

District's own assessment of the plan's operational readiness — Initial (drafted), Defined (documented + stable), Managed (regularly exercised), Optimized (continuously improved).