Record a client scope change without losing the original brief

How to approach: Record a client scope change without losing the original brief

A scope change should be recorded as a version, not a rewrite. Keep the original brief and add the new request, the impact, and the approval. A rewrite hides why the team is doing different work than the contract describes. A control that depends on memory is not yet a control. The capacity plan should use productive hours, not scheduled hours. The offshore team should record the local time for both locations.

Start the note with the specific field that changed. Then record the old value, the new value, and the date. The note should be short enough to read in a review. If the source is unclear, route the question instead of guessing. The shift report should show the export time and the system. The onboarding plan should end with a written readiness decision.

Record the original and the new request

Link the original brief and quote the relevant scope. Write the new request in the client's words. A paraphrase can change the meaning of the request. A short note with four fields is easier to use than a long narrative. The change note should keep the original brief visible. The team lead should review the missed handoffs weekly.

Record who made the request and the date. A request from an unauthorized contact should be routed before the work changes. The note should show the authority check. Keep the evidence with the record rather than in a separate log. The access review should name the role and the permission level. The capacity plan should use productive hours, not scheduled hours.

Assess the impact

Record the impact on time, cost, and the current queue. A change that looks small may displace other work. The impact should be visible to the account owner. Separate what was observed from what was assumed. The access review should name the role and the permission level. The capacity plan should use productive hours, not scheduled hours.

Name the tasks that will stop or move because of the change. A scope change without a trade-off is usually an unapproved expansion. The account owner should decide what gives. Separate what was observed from what was assumed. The offshore team should record the local time for both locations. The access review should name the role and the permission level.

See how a specialist offshore team can support a controlled scope and evidence trail.

Get the approval

Record who approved the change and the date. A change that affects the contract or the fee should have the same approval as the original agreement. The approver should see the impact. Ask whether a new reviewer could act on the record without a conversation. The quality sample should link the finding to the source update. The client owner should see the trade-off before the scope changes.

If the approval is pending, mark the work as on hold. Do not start the new scope on a verbal request. The record should show the hold and the owner. Keep the boundary visible in the place where the work is assigned. The status vocabulary should be short enough to remember. The quality sample should link the finding to the source update.

Update the team and the brief

Send the change note to the team before the next shift. Update the brief and the task system. A change that is recorded but not communicated will be missed. Test the rule on one real handoff before applying it to both shifts. The capacity plan should use productive hours, not scheduled hours. The onboarding plan should end with a written readiness decision.

Confirm that the team understands the new scope. A short read-back is enough. The confirmation should be recorded with the change. Name the owner in the same line as the action. The onboarding plan should end with a written readiness decision. The review should leave one owner and one date.

U.S. Small Business Administration provides public guidance relevant to testing this workflow.

Review the change for patterns

Review the scope changes monthly. Look for repeated requests that should be part of the standard service. A pattern may point to a pricing or packaging problem. Test the rule on one real handoff before applying it to both shifts. The quality sample should link the finding to the source update. A handoff that cannot be confirmed is not yet complete.

Share the pattern with the account owner. The goal is a clearer scope, not more change notes. A stable scope is easier to deliver and easier to review. Name the owner in the same line as the action. The quality sample should link the finding to the source update. The access review should name the role and the permission level.