Create a launch scope change protocol
Assess late launch requests against customer commitments, dependencies and readiness before changing the approved release scope.

Describe the requested change precisely
Record the current approved scope, the proposed addition or removal, the requester and the decision deadline. Link to the affected launch asset, workflow or customer commitment. A request to “improve the launch” is too broad to assess; identify the exact behavior or deliverable that would change.
Separate a correction required for accuracy or safety from an optional enhancement. A broken registration flow may need immediate attention, while an additional campaign channel can be evaluated against the remaining capacity. The distinction helps the launch owner make an explicit tradeoff.
Map the consequences before approving
Ask each affected owner to identify work, approvals and tests that must be repeated. A revised product claim can affect the landing page, sales presentation, announcement and support guidance. Include those dependencies in the estimate instead of considering only the first edit.
State what would be displaced if the change is accepted. Preserve the original launch objective and any commitments already made. When evidence is incomplete, record the uncertainty and the person who can resolve it rather than treating an optimistic estimate as a confirmed plan.
Use a decision record with clear options
The launch owner should choose among accepting the change, reducing another part of the scope, deferring the request or moving the launch milestone. Name the authorized approver and capture the reason, affected deliverables, owners and revised acceptance criteria.
Illustrative case: a team requests a new audience segment shortly before launch. The decision record explains that the segment needs separate messaging and routing validation. The owner may retain the approved audience for this release and schedule a later test, rather than quietly expanding the campaign without preparation.
Release the revised plan and verify it
Update the single launch plan, mark superseded assets and notify the people whose work changes. Confirm that the release checklist, customer-facing materials and internal briefing all describe the same scope. A decision recorded in a meeting is not enough if execution still follows an older file.
Before closing the change, verify the affected customer journey and obtain the required approvals. At the retrospective, review late requests by cause: missing discovery, unclear ownership, external changes or avoidable delay. Use that evidence to improve planning without creating an inflexible process that blocks necessary corrections.