How changes are handled during a project

Product work reveals information. A user flow may need another state, an integration may behave differently than documented, or the business may make a new decision. We record the change and explain its effect before the work is added.

A request can replace lower value work, move to a later release, extend the current scope, or be declined. We present the relevant options with timing, cost, risk, and product impact so the decision remains yours.

If delivered behaviour does not match the agreed acceptance criteria, correcting it is part of the work. Scope control should never be used to relabel a defect as a new feature.