Approve a change and apply its authorized effects once
Retain exact proposal revisions and distinct technical, contract, budget and schedule decisions before finalizing local or external effects.
Current Revision 3 Reviewed Oct 26, 2026
On this page
Before you beginCurrent capability and authorityClearly labeled synthetic exampleInputs and terminologyProcedureVerify the resultWhat happens nextTroubleshootingBefore you begin#
- Cost/change access and the distinct approval capability for each required decision.
- A published workflow version, affected records and exact evidence versions.
Current capability and authority#
Retain exact proposal revisions and distinct technical, contract, budget and schedule decisions before finalizing local or external effects.
Clearly labeled synthetic example#
Synthetic CHG-014 proposes an 80,000 commitment increase and zero budget increase. A technical acceptance alone changes neither amount; final commercial authorization reclassifies the included 80,000 exposure once.
Inputs and terminology#
| Term | Meaning |
|---|---|
| Technical decision | Acceptance of a configuration or engineering basis; it is not contract or budget authorization. |
| Finalization | A separately validated transaction that applies approved effects or records a pending external application. |
| Unknown external outcome | An unconfirmed provider result that requires reconciliation before retry or confirmation. |
Procedure#
Prepare the proposal
Open Changes and New change. Select the published workflow and exact commitment/configuration revision; enter proposed contract and budget effects separately.
Assess schedule and evidence
Record assumptions, affected equipment/milestones and exact documents. Mark unresolved schedule consequences as assessment required rather than inventing an impact.
Submit the exact revision
Review and save the draft, complete assessment and submit. Material edits create a new revision; prior decisions cannot authorize new terms.
Record independent decisions
Each designated reviewer records only the decision supported by their explicit capability and workflow version. Review conditions and required evidence.
Finalize and reconcile
Finalize only after every required current decision and condition is satisfied. Inspect the applied effect or pending/unknown external status. Retry an uncertain request using its retained identity; do not create a duplicate proposal to recover a timeout.
Preserve corrections
Use an authorized amendment or reversal with reason and linked original effects. Retain the prior approvals and original baseline.
Verify the result#
A single approved revision has one durable effect identity, retained decisions and coherent classification of pending exposure.
What happens next#
Engineering acceptance alone leaves commercial commitments and approved budget unchanged.
Finalizing an 80,000 included change moves it from pending exposure into the commitment once; it does not increase the management forecast twice.