Scope Change Conversation
A practical page for preparing a client conversation when a request may exceed an agreed service commitment. Separate the documented scope from the new need, compare options, and record the decision route without promising approval.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: IT services and managed support · Consulting and professional services · Business process outsourcing
Overview
Scope Change Conversation is a procedure page for preparing an evidence-based discussion when a client request may go beyond an agreed service commitment. Its fictional Northstar Support example starts with a clear contrast: the existing commitment is one weekly service summary, while the client asks for daily summaries during a four-week launch. The page keeps that example illustrative and makes clear that the request does not establish what the agreement covers or authorize a change.
The page guides the reader through the work needed before and during the conversation: locate the governing agreement or approved scope record, capture the request in the client’s words, clarify its timing and purpose, assess effort and dependencies, compare options, and identify the engagement’s actual decision owner. A worked example demonstrates a decision record with the request, options, rationale, status, responsible roles, next step, and sample dialogue. Role-based handoffs distinguish coordination by the account lead from evidence gathering by the delivery lead and authorization by the designated decision owner.
Use this template when cadence, effort, timing, or deliverables may differ from the documented commitment and the team needs a structured discussion. Do not use it as a contract, formal change order, approval workflow, or replacement for the engagement’s required change-control process. It is also not a reason to promise a requested option before feasibility and authorization are confirmed. Replace or clearly retain the fictional scenario, then align role descriptions and records with the actual engagement arrangements.
Standards & compliance context
- Check the governing agreement and approved scope record; this page does not replace contractual change-control terms or legal advice.
- Confirm the designated decision owner and any required authorization evidence through the engagement’s applicable arrangements before treating a proposed change as agreed.
- Keep the record factual, attributable to the relevant roles, and limited to information needed to explain the request, assessment, decision, and next action.
- Use clear headings and readable text, and check the published page for WCAG 2.1 AA accessibility, including keyboard access and sufficient contrast.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Prepare the scope conversation
Use the fictional scenario to distinguish a possible scope change from a request that still needs assessment.
-
Fictional example: Northstar Support has agreed to send a weekly service summary. During a four-week launch, the client asks for a daily summary. Use this example to separate the existing commitment from the new need, compare options, and identify the proper decision route. It illustrates work coordination—not customer policy or approval.
Start with what was agreed
Verify the documented commitment and capture the client’s need before comparing solutions.
-
Keep the commitment, request, and evidence distinct. Original commitment: In the Northstar Support example, the agreement includes one weekly service summary. New need: During a four-week launch, the client asks for a daily summary. The request could involve additional effort, a different reporting rhythm, or a temporary priority; the request alone does not establish what the agreement covers. Check the governing agreement and any relevant approved scope record before discussing options. Capture the request in the client’s words, when it is needed, how long it applies, who will use the summary, and what decision or action it supports. Ask the engagement’s designated decision owner to clarify any ambiguity in the commitment.
Compare options without promising an outcome
Make likely benefits and tradeoffs visible while leaving feasibility and authorization to the actual engagement process.
-
Northstar options are illustrative. Assess feasibility and impact for the actual engagement. Keep the weekly summary Retains the stated example cadence May not provide the launch-period visibility the client is seeking Discuss a time-limited daily summary Could address the short-term need if capacity and authorization permit Requires effort and priority assessment; other planned work may be affected Clarify the need before changing cadence May reveal a narrower update or decision point that meets the need The client needs to explain which information is urgent and when it will be used
Prepare and hold the discussion
Move from evidence gathering to a client conversation and a clear decision handoff.
-
Bring the evidence, clarify the need, and agree the real decision route. Gather the commitment and request Locate the relevant agreement or approved scope record. Note the existing cadence, the exact request, its requested start and end, and known effort or delivery dependencies. Clarify what the client needs Ask what decision or action the daily summary would support, which information is time-sensitive, and whether the need applies throughout all four launch weeks. Do not assume the requested format is the only solution. Present options and impacts Separate what is within the known commitment from what needs assessment or authorization. Describe capacity, timing, dependencies, and tradeoffs using evidence-based estimates—not promises. Confirm who decides and what happens next Identify the authorized decision owner from the engagement’s governing arrangements. Record the decision or unresolved question, rationale, responsible role, and next action. A discussion by itself is not approval.
Worked example: decision record
See how to document an unresolved request, rationale, roles, next step, and careful sample dialogue.
-
Fictional Northstar Support example, dated 14 May 2026. Request: Daily service summaries during the four-week launch, instead of the agreed weekly summary. Options considered: Keep the weekly cadence; assess a time-limited daily cadence; or clarify whether a narrower update would meet the need. Rationale: The client wants more frequent visibility during launch, while preparing daily summaries could draw capacity from other planned delivery work. First clarify which information supports a specific decision, then assess effort against current engagement priorities. Decision status: No change is approved in this example. The designated engagement decision owner must determine authorization under the applicable arrangements. Responsible roles and next step: The account lead coordinates the follow-up discussion; the delivery lead assembles commitment and effort evidence; the designated engagement decision owner resolves the authorization question. Record the actual decision date and rationale if a decision is made. Sample dialogue: “We can see why daily visibility would help during launch. Our current commitment is a weekly summary. Could you tell us which decision the daily update needs to support? We’ll assess the options and tradeoffs, then confirm the decision route and owner before treating any change as agreed.”
Role-based handoffs
Keep evidence gathering, client coordination, and authorization responsibilities distinct.
-
Assembles agreed-scope evidence and assesses delivery effort, dependencies, and capacity. Delivery lead Coordinates the client conversation, captures the request and need, and communicates the agreed next step. Account lead Resolves authorization and confirms whether a proposed change can be agreed under the engagement’s governing arrangements. Designated engagement decision owner
How to use this template
- Replace or clearly retain the Northstar example, and confirm the actual engagement roles and decision route before sharing the page.
- Locate the governing agreement and approved scope record, then capture the existing commitment and the client’s request separately.
- Ask what decision or action the requested change supports, when it is needed, how long it applies, and which information is time-sensitive.
- Assess feasible options with the delivery lead, documenting effort, capacity, timing, dependencies, and impacts on planned work.
- Discuss the options without implying approval, and confirm the authorized decision owner and any unresolved questions.
- Record the decision status, rationale, responsible role, and next action, then update the record when the decision or request changes.
Best practices
- Quote the existing cadence from the governing agreement or approved scope record rather than relying on recollection.
- Record the client’s request in their words, including requested start, end, and intended use.
- Ask which decision the requested information will support before treating the proposed format as the only solution.
- Describe effort, capacity, timing, and dependencies as assessed evidence, not guaranteed outcomes.
- Label each option with both its potential benefit and its tradeoff so the client can compare them.
- Keep discussion status separate from authorization status, and state plainly when no change has been approved.
- Assign each follow-up to a responsible role and record the next action so an open decision does not disappear.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should we use this scope change conversation template?
Use it when a client request may alter the cadence, effort, timing, or deliverables in an existing service commitment. It helps distinguish what the agreement says from what the client now needs. The Northstar example uses a request for daily rather than weekly service summaries during a four-week launch.
Does a request automatically mean the agreed scope has changed?
No. The example explicitly treats the request as something to assess, not as an approved change. Check the governing agreement and relevant approved scope record, then follow the engagement’s actual authorization route. A discussion or written record alone does not establish approval.
Who should prepare and run the discussion?
The page assigns practical roles rather than naming individuals. The delivery lead assembles commitment and effort evidence, the account lead coordinates the client conversation, and the designated engagement decision owner resolves authorization. Confirm those roles against the engagement’s governing arrangements before use.
How often should the conversation or decision record be updated?
The template does not prescribe a recurring review cadence. Update the record when a new request, decision, or material change in timing or impact needs documenting. If the request remains unresolved, capture the next action and responsible role so follow-up does not rely on memory.
Does this template satisfy a legal or contract change-control requirement?
No. It is a work-coordination aid, not a substitute for the governing agreement, required change-control process, or legal advice. Use the applicable engagement arrangements to identify who can authorize a change and what formal records are required.
What is a common mistake this template helps prevent?
A frequent pitfall is treating the requested solution as the only way to address the client’s need. The page prompts the team to ask what decision the new information supports, clarify which details are time-sensitive, and compare alternatives. It also warns against implying approval before the authorized owner decides.
What should we customize before using the page?
Replace the fictional Northstar Support scenario with an example appropriate to the audience, or clearly retain it as an illustration. Confirm the actual source of scope evidence, role names, authorization route, and record-keeping expectations. Keep any client-specific commitments accurate and avoid presenting illustrative options as promises.
Does the template connect to contracts, project tools, or approval workflows?
The supplied page is static content; it does not specify contract, project-management, or approval integrations. Users must locate the relevant agreement and approved scope record through their existing processes. Do not describe the page as submitting or approving a change.
How is this different from handling the request ad hoc?
An ad-hoc conversation can blur the original commitment, the client’s need, and a possible solution. This page separates those elements, makes tradeoffs visible, and names the roles involved in the handoff. It also leaves a sample decision record that shows how to document an unresolved authorization question.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Scope Change Conversation ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
