LEARN. PRACTICE. GROW.Define what each closure means
Accepted installation, RUN handover, supplier exit, and legacy decommissioning can have different criteria. Under the fictional rule, stabilization ends after three critical-incident-free cycles, training, and confirmed on-call contacts. Three clean cycles do not replace night-shift confirmation. A phase may close with residual actions only under authorized conditions: accepting owners, capacity, funding, and deadlines. The decision should delimit completed work and what remains tracked. Do not generalize an installation signature into authorization to delete data or shut down every old system.
Transfer capability, configuration, and obligations
Slides and attendance show training occurred. A rehearsal performed by the shift shows whether it can find the procedure, authenticate with authorized access, and recover the accepted version. Correct gaps and repeat the necessary execution. Identify who handles daily operations and who retains contractually covered correction obligations. In the 90-day correction case, handover neither extinguishes that obligation nor makes the supplier responsible for every incident. Retain contacts, coverage conditions, evidence, and timing to route the issue to the right person.
Plan commercial exit alongside technical exit
In the abstract calendar, renewal occurs on day 100 and notice must reach the supplier by 70, inclusive. Internal approval on 72 no longer satisfies that condition. Do not invent universal consequences: confirm options and exposure with procurement under the terms. The exporter may depend on a supplier whose contract ends before the planned date; a signed replacement does not automatically provide that capability. Integrate notices, export, validation, access, and coverage into the plan early. This lets the committee decide while executable alternatives remain.
Calculate the exit network without removing validation
Export takes two days. Then three-day validation and four-day consumer preparation run in parallel. One-day revocation waits for both, and one-day closure waits for revocation. With resources available for that parallelism, duration is 2+max(3,4)+1+1=8 days. Starting on 64 ends on 72. Reaching 70 would require starting by 62 or justifying an executable network change. Adding every branch gives 11 and using the short branch gives 7; both distort dependencies. No arithmetic authorizes removing required validation merely to meet a date.
Reconcile dependencies before shutdown
A traffic-free week does not necessarily cover a monthly job. In the exercise, the job still targets legacy and month-end has not occurred. Address that dependency and validate inventory under plan criteria. Include infrequent consumers, recovery procedures, monitoring, and relevant credentials. Stopping consumption and ending payments are also distinct decisions. Of 5 thousand monthly, only 2 thousand stops being paid on shutdown; 3 thousand remains committed for three months. Established savings are 6 thousand even if old technical capacity is no longer used.
Connect retention and sanitization to authorized scope
Before sanitization, owners need to confirm content, retention, permitted disposition, and required evidence. NIST800-88Rev.2 supports program governance; this lesson neither teaches commands nor certifies deletion. A certificate for A1, A2, A4 does not fully match the A1, A2, A3 list: A3 needs reconciliation and A4 clarification. Snapshots and backups outside the certificate need their own documented handling. Equal counts or dates do not prove identity, and deleting an application does not establish removal of all copies. Active retention needs appropriate authority before irreversible actions.
Guided practice: closure decision package
Build a matrix of phase, criterion, evidence, gap, owner, and decision. Fill in accepted installation, unconfirmed night shift, pending monthly job, A3 without evidence, and commercial notice planned for 72 when the limit is 70. Calculate eight network days and 6 thousand spending reduction. Then propose what may close under supplied authority and what should remain open. Include the benefit owner, baseline, and subsequent measurement date. The aim is to preserve operating autonomy and obligations without claiming outcomes not yet observed.
Synthetic exit fixture; abstract elapsed days, no real contract interpretation.
export = 2
validation = 3 # after export
consumer_preparation = 4 # after export, parallel with validation
revoke = 1 # after both branches
close = 1 # after revoke
duration = 2 + max(3, 4) + 1 + 1 # 8
start_64 -> finish_72 # misses receipt deadline70
saved_over_3_months = 3 * 2 # 6 thousand; commitment3/month remains
expected_assets = [A1, A2, A3]
certificate_assets = [A1, A2, A4]
missing = [A3]; unexpected = [A4]
snapshots_and_backups = outside_this_certificateInstallation can be accepted while decommissioning awaits the monthly job, A3 reconciliation, and authorized handling of retained snapshots.
Common pitfalls
Treating training as autonomy; using a traffic-free week as complete inventory; counting remaining commitments as savings; generalizing limited-scope certificates.
Related topics: Suppliers and acceptance · Value and closure · Governance and risk
Useful closure identifies what was accepted, who can operate, what remains owed, and which evidence supports each conclusion.
Reference: Evolving the SRE Engagement Model · PMP ECO July 2026; DR PMP 2026.7