Designed change
The proposed change process would connect new instructions to reviewed tasks, responsibilities and billing assumptions.
Illustrative scenario combining common practice needs. Software shown is a suggested stack.
Catch the change while it is small
The design would give staff a simple way to flag work that falls outside the current plan. The responsible lawyer would assess the instructions, identify the effect on scope and decide what needs to be discussed with the client. The proposed process would preserve that decision in the matter.
Update the work behind the decision
Once the appropriate instructions and approvals are in place, the team would revise tasks, dependencies and the relevant billing assumptions. Existing work would be checked for duplication or superseded instructions. A later review could then distinguish an agreed change from work that simply accumulated around the original plan.
The practical lesson
A scope decision becomes useful when it changes the work people are expected to perform.