Two decisions must refer to the same proposal
Synthetic amendment A-210 r1 adds two setup tasks to confirmed O-210. Operations approves r1, but the customer requests r2 with three tasks. The internal r1 approval does not approve r2, and the customer’s request is not confirmation of an internally feasible plan. Keep O-210’s original baseline active until both decisions support the same revision. The fixture describes operational confirmation, not a contractual signature procedure.
| Revision | Operations decision | Customer decision | Effective work baseline |
|---|---|---|---|
| Original O-210 | Confirmed | Confirmed | Remains active |
| A-210 r1; +2 tasks | Feasible | Requested different scope | Not effective |
| A-210 r2; +3 tasks | Pending review | Requested; not confirmed plan | Not effective |
Confirm one aligned amendment revision
- Record amendment revision
- Check operational feasibility
- Capture customer confirmation
- Activate aligned revised baseline
Any substantive scope revision reopens the affected decisions; do not combine approvals from different revisions.
Operations approves r2 but the customer has only requested it. Is r2 effective?
Show the worked answer
Not yet under this fixture. Obtain customer confirmation of the feasible r2 plan before activating it.
Use the decisions actually required by the agreed order process. Do not add a redundant customer step when an existing explicit action already confirms the same plan.