LEARN. PRACTICE. GROW.Concept and mechanism
An execution plan is a sequence with prerequisites, an owner, estimated duration, and evidence for each step. Mark decision points before actions that are hard to reverse. The window should include entry, change, validation, and possible recovery. Calculate the last safe recovery start from the authorized end, including validation and margin. Do not consume recovery reserve as extra execution time without a valid new decision. Calendars need dates and time zones, especially when teams in Lisbon, London, and other regions participate.
Guided application
In a batch-migration exercise, confirm file producers, queues, scheduler timing, consumers, and reconciliation. Two changes in different applications may compete for the same database or specialist. A server list does not reveal these dependencies. Before starting, confirm decision-makers, access, and recovery contacts are available. If a prerequisite fails, record the deviation and apply the entry criterion; pressure to use the window does not create missing capacity or authorization.
The window ends at 03:00. Recovery takes 40 minutes, validation 15, and margin 5: the last safe start is 02:00. A step starting at 01:55 and taking 20 minutes does not fit before that deadline.
Common pitfalls
Confusing deployment completion with window completion; ignoring shared dependencies.
Related topics: Artifacts, configuration, and recovery · Execution and impact control
An executable window reserves time to validate and recover.
Reference: Contingency Planning Guide for Federal Information Systems · DR Change Management 2026.1; independent technical curriculum