A control loop rather than a step in the chain, which is why it produces no state token. It requires a baseline and it revises one; it does not create a state that a later stage gates on.
Absorbed changes are recorded as such. A change absorbed without record is indistinguishable from an estimate that was wrong, and the two have different lessons.
Boundary
Trigger (in)
A request or an event that moves the engagement off its baseline.
Output (out)
An approved, rejected or absorbed change, and a rebaselined plan where approved.
Requires
plan-baselined
Produces
none
Floor: can this run itself
Position
review
Manual because
control
Basis
A change is raised by a person and approved by another. Four eyes on anything that moves the baseline.
Confirmed by
nobody named
Behaviour: what runs it
Systems
Change control, Planning and baseline
Data
Dataset
Authoritative source
Also in
State
Owner
Change request
Change control
settled
Engagement Lead
Engagement plan
Planning and baseline
settled
Engagement Lead
Deliverable
Planning and baseline
S, Y, S, -, D, M, S, -, W, O, R, K
settled
Engagement Lead
Rules: what is decided here
ID
Rule
State
Enforced by
Basis
Owner
RUL-45
Change against a baseline is recorded before work proceeds
defined
Change control
Gate in change control.
Engagement Lead
RUL-46
Absorbed changes are recorded as absorbed
defined
Change control
Distinguishes a decision from an estimating error.
Engagement Lead
RUL-47
Scope increases above a threshold need client sign-off