IT CHANGE PLAN — YENRA
Guide: https://yenra.com/change-management/
Purpose: define evidence, responsibility, rollout gates, and recovery.
Use actual manufacturer/platform procedures for implementation. This form
does not supply a generic restore, migration, or rollback command.

Change ID / reason / urgency / business owner / technical owner:
Affected service, locations, devices, accounts, and dependencies:
Known working state and evidence / current version / target version:
Window / approved interruption / latest recovery decision time:
Authorizer / approval record / affected-user communications:

PREPARATION
Supported procedure and exact documentation/version:
Representative test environment / approved test data:
Configuration and data protection; tested restore evidence:
Irreversible steps and data/transaction consequences:

ACCEPTANCE CASE (repeat)
Starting state / account role / action:
Expected business and technical result:
Actual result / evidence / test time / tester:
Pass or unresolved issue / owner:

ROLLOUT GATES (repeat per group)
Group and inclusion criteria / exclusions and offline devices:
Checks and observation period covering relevant business cycles:
Stop conditions / decision owner / actual go or hold decision:

RECOVERY
Supported recovery or forward-repair route / tested duration:
Access and personnel available:
New transactions: preserve, replay, reconcile, or other approved treatment:
Continuity arrangement / communication / completion evidence:

CLOSURE
Intended versus actual configuration inventory:
Business owner acceptance / outstanding issues and dates:
Support contacts, errors, and delayed jobs reviewed:
Lessons and required follow-up:
Reference: NIST SP 800-128, linked in the guide.