Back to Workflows
Workflow

Client Scope Change

Manages requests to modify the scope of an active client engagement, including impact assessment and formal approval.

Trigger: Client or project team identifies a need to change the project scope
Total: 3-10 business days
5 stages

Workflow Stages

1

Change Request Submission

Document the proposed scope change with clear description of what is being added, modified, or removed.

Inputs

  • Change request from client or team
  • Current scope of work document
  • Change request template

Outputs

  • Formal change request document
  • Change request logged in system
  • Impact assessment initiated
Project Manager
1-2 hours
2

Impact Assessment

Analyze the change request impact on timeline, budget, resources, and deliverables.

Inputs

  • Change request document
  • Current project plan
  • Resource allocation data

Outputs

  • Impact assessment report
  • Revised timeline estimate
  • Cost impact analysis
Project Manager
2-3 days

Decision Points

  • Does the change require additional budget?
  • Does the change affect the project critical path?
3

Internal Approval

Review the impact assessment internally and decide whether to proceed with the client approval process.

Inputs

  • Impact assessment report
  • Profit margin analysis
  • Resource availability

Outputs

  • Internal approval decision
  • Revised proposal for client
  • Risk mitigation recommendations
Service Delivery Manager
1-2 days

Decision Points

  • Is the change feasible and commercially viable?
4

Client Approval

Present the scope change impact and revised terms to the client for their formal approval.

Inputs

  • Revised proposal
  • Impact summary for client
  • Updated contract terms if needed

Outputs

  • Client approval or rejection
  • Signed change order
  • Updated contract amendment if applicable
Account Executive
2-5 days

Decision Points

  • Does the client accept the revised terms?
5

Implementation and Plan Update

Incorporate the approved change into the project plan and communicate updates to all stakeholders.

Inputs

  • Signed change order
  • Current project plan
  • Stakeholder communication list

Outputs

  • Updated project plan
  • Revised milestone schedule
  • Stakeholder notifications sent
Project Manager
1-2 days

Frequently Asked Questions

Who can submit a scope change request?

Either the client or any member of the project team can submit a scope change request. All requests go through the same assessment and approval process.

How are scope changes tracked over the life of a project?

All scope changes are logged in a change register that provides a complete audit trail of every modification, its impact, and approval status.

What happens if a scope change is rejected?

The requestor is informed of the rejection reason. Alternative approaches may be proposed to address the underlying need without a formal scope change.

Ready to implement this workflow in your business?

Our team can implement this workflow into your business operations with custom tools and training.