Scope Change Approval: Control Extra Work Before the Team Starts

By Paul Foster

Extra work often begins with a reasonable request: “While you are here, can you also take care of this?” Trouble starts when the request bypasses review. The crew may lack time, materials or authority; the customer may assume it is included; the office may learn about it only after completion.

A scope-change process gives the team a respectful way to capture the request, review its effect and obtain the right approval before work begins.

Make the original scope easy to find

The current approved proposal, work order or service plan should identify what the team agreed to deliver. Field staff need access to the relevant version and a way to flag a mismatch. If nobody can tell which version controls, pause and resolve that first.

Teach the difference between clarification and change. Confirming where an included task occurs may clarify scope. Adding rooms, quantities, visits, materials or timing can change it. When uncertain, route the question rather than improvising a commitment.

Capture the request in plain facts

Record who requested the change, when, what they asked for, the affected location or service, and any stated timing. Avoid rewriting the request as an approved instruction. Label it “requested” until the designated reviewer decides.

Do not place sensitive customer information in casual team messages. Use the working job record and notify the reviewer with the job identifier.

Review operational and commercial impact

The reviewer checks whether the request is feasible, who must perform it, what materials or access are needed, whether the schedule changes, and whether another approval is required. The appropriate commercial owner determines price or agreement effects under the business’s normal process.

This review is a recommendation, not a universal contract rule. Each company should align the workflow with its actual agreements, insurance, safety practices and authorization levels. Unusual legal or contractual questions need qualified review.

A fictional ClearPath Grounds example

ClearPath Grounds is fictional. During a scheduled cleanup, a tenant asks the crew to remove debris from an adjacent storage area that is not listed in the work order. The crew lead documents the affected area through the company-approved process, with any required customer permission, records the request and explains that the office must review additions.

The project manager checks access, disposal needs and available time. The authorized customer contact approves the documented change through the company’s normal method. The manager issues a revised work instruction, and the crew acknowledges it before starting. If approval had not arrived, the crew would have finished the original scope and left the requested area unchanged.

Use an authorization matrix

Write who may approve common changes and what must be escalated. The matrix might distinguish no-cost scheduling adjustments, changes within an existing allowance, additions requiring a revised quote, and requests the business will not accept.

Automation can route requests and collect acknowledgments. It should not infer approval from silence, a casual message or a status change made by someone without authority.

Stop rules for extra work

Stop when the request is outside the approved scope.
Do not begin when the requester’s authority is uncertain.
Escalate safety, access, legal or insurance concerns.
Do not rely on verbal approval when company policy requires another form.
Pause if the change affects other scheduled commitments.
Do not backdate approval after work merely to make the record look complete.

Emergency conditions may need a separate procedure. Define that procedure in advance, including who can authorize protective actions and how the facts are documented.

Close the loop with operations and billing

Once approved, update the controlled scope or issue a linked change record. Notify the service lead, scheduling and billing owners that need the information. Require acknowledgment from the person doing the work. Preserve the request, review, approval and final instruction.

If declined, record the reason at an appropriate level and confirm that the original scope remains active. A declined change should not leave the crew guessing.

Metric: extra work started before approval

Track extra work started before approval: count reviewed scope-change cases in which work began before the required authorization timestamp. Define which changes require approval and use the start evidence available in your process. Review every occurrence rather than using a favorable percentage to dismiss a control failure.

This metric measures adherence to the approval process. It does not establish whether a charge is legally collectible or a customer relationship is healthy.

Reusable scope-change checklist

Make the current approved scope accessible.
Record the request as requested, not approved.
Check feasibility, schedule and required authority.
Use the correct approval method.
Issue a controlled instruction or revised version.
Obtain operational acknowledgment.
Update billing and scheduling records.
Record declines and preserve the original scope.

When a customer request changes an open proposal, return it to the estimate follow-up process before treating it as approved work.

Use the Business Systems Scorecard to spot approval gaps. If extra work regularly arrives through informal channels, request a free 30-minute FSF Systems Review.

Prepared with AI assistance and reviewed for publication. ClearPath Grounds is fictional; the example is not a client result. This is process guidance, not legal advice.