content

Client Engagement Team Site

A six-page intranet site for coordinating a single client engagement, with a fictional onboarding review showing how to align scope, delivery, roles, decisions, and reusable prompts.

Request pricing See it in MangoApps

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: Management consulting · Professional services · Business process advisory

9:41

Sites

Overview

Client Engagement Team Site is a six-page intranet starter for coordinating one client engagement. Its fictional example follows a four-week review of Northstar Group’s employee onboarding service. An overview page points contributors to the outcome and boundary, working sequence, role ownership, and decision example; dedicated pages provide the detail, and a resource page gathers authored prompts for scope discussions, meeting preparation, and decision notes.

Use the site when a delivery lead, engagement consultant, and specialists need a shared reference for what the work covers, how evidence moves toward discussion, and how to handle requests that may change the boundary. The sample sequence moves from aligning the review question to gathering inputs, synthesizing observations, and discussing findings. The decision example distinguishes an agreed direction from an open question and shows how to make the effect on work visible. These are static examples, not a live schedule, project tracker, client document search, or approval workflow.

Before use, replace the fictional client and onboarding details with confirmed engagement information, including actual scope, contributors, outputs, and timing. Keep observations separate from interpretation and recommendations, and do not treat an adjacent request as approved work. This site is not a contract, statement of work, delivery plan for every engagement, or substitute for the authoritative records and approvals your organization requires. For a small task with no meaningful handoffs or scope questions, a shorter working note may be easier to maintain.

Standards & compliance context

Treat the fictional Northstar review, boundary, roles, and decision as sample content, not as evidence of a real client agreement or approved work.
Confirm the actual engagement scope, decision authority, and required records through your organization’s applicable contract and governance processes; this template does not establish them.
For any audience-restricted page, check that access is configured by the site owner and that the page remains usable with keyboard navigation and assistive technology in line with WCAG 2.1 AA.

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

Engagement overview

Coordinate the Northstar service-readiness review
A shared starting point for the consultants, delivery lead, and specialists working on one engagement. This fictional example follows a four-week review of Northstar Group’s employee onboarding service. Use the pages here to align on the review boundary, sequence, ownership, and decisions.
The engagement at a glance
Start with the outcome, then open the page that holds the working detail. Outcome and boundary Describe the current onboarding journey, identify observed friction points, and present prioritized findings for discussion. Redesign and implementation are not included by default. Working sequence Align on the review question, gather agreed inputs, synthesize observations, then discuss findings. Role ownership The delivery lead coordinates the plan and decision record; contributors bring subject expertise and evidence. Direction and rationale Record the question, context, chosen direction, rationale, and affected work so contributors can follow the same picture.
Section Divider
How the work fits together One engagement, one shared picture
Connect the question to the next handoff
A practical coordination pattern for the fictional review. Keep the review question visible The review asks how employees currently move through onboarding, where handoffs occur, and what evidence supports the team’s observations. Use the agreed review question to focus interviews and document review. Record observations separately from recommendations. Check proposed work against the stated scope. Move new requests into a decision discussion If a contributor hears a request to redesign a separate system, capture the request and context rather than silently adding work to the review. Note what was requested and where it arose. Bring the boundary question to the engagement discussion. Reflect an agreed change in the scope and delivery references.
Open a working reference
Each destination gives the detail for one part of the engagement. Team responsibilities See who coordinates each work product and handoff. Reusable resources Use authored prompts for scope discussions and decision notes.

Engagement scope

What the review covers
The example engagement is a four-week review of the current employee onboarding journey. Intended outcome: describe the current journey, identify observed friction points, and present prioritized findings for discussion with the engagement team. In scope: mapping current onboarding steps from accepted offer through the first month; reviewing agreed process materials; and discussing observations with people identified for the review. Not included by default: redesigning or configuring a separate client system, implementing recommendations, or evaluating unrelated employee services. A new request is a question to discuss, not an automatic change to the work.
Scope at a glance
Illustrative boundaries for this fictional review. Work area Included Not included by default Current journey Document onboarding steps and handoffs Redesign a separate client system Evidence Review agreed materials and discuss observed steps Claim findings beyond gathered evidence Output Present prioritized observations for discussion Implement recommendations
A boundary example
Keep observations tied to the agreed review; route adjacent requests to a discussion. Included: document the current onboarding steps A conversation reveals that a new starter waits for account access after an existing onboarding step. The team records where the handoff occurs, what evidence supports the observation, and which part of the current journey it affects. Tie the observation to the current process. Record missing evidence as a question, not a conclusion. Include the supported observation in the review findings. Discuss separately: redesign a client system A participant asks the team to redesign a separate client system. That request may merit discussion, but documenting the current onboarding journey does not include redesign by default. Capture what was requested and why it arose. Bring the boundary question to the engagement decision discussion. Do not promise added work before the appropriate discussion.
Continue with the related work
Use these pages when a boundary question affects delivery or direction. Delivery approach See the sample sequence for gathering and discussing evidence. Engagement decisions See how the example boundary question is recorded and explained.

Delivery approach

How the review moves from question to discussion
A sample four-week sequence for coordinating the work, not a live schedule or a guarantee. Align on the review question and scope boundary. Gather agreed process materials and observations, synthesize what the evidence supports, then discuss findings and open questions with the engagement team. Keep observations, interpretations, and recommendations distinct. When a new request falls outside the stated review, record its context and bring it to the decision discussion instead of silently expanding the work.
A four-week example sequence
Timing illustrates how this fictional review might be organized; actual engagement dates and dependencies determine the working plan. Align the review question Agree the intended outcome, review boundary, relevant contributors, and inputs for the example review. Week 1 Gather agreed inputs Review identified process materials and collect observations relevant to the current onboarding journey. Week 2 Synthesize observations Group evidence by journey stage, note gaps, and distinguish observations from interpretations or recommendations. Week 3 Discuss findings and open questions Present prioritized observations, explain their evidence, and record boundary or direction questions for follow-up. Week 4
Worked coordination example
Keep the review useful without treating an adjacent request as approved work. An interview surfaces a system-redesign request During a discussion about onboarding, a participant asks the team to redesign a separate client system. The delivery lead records the request and its context; the consultant distinguishes it from the current-process observation; the team discusses whether it belongs in a separate engagement conversation. Do not silently add redesign tasks to the review sequence. Keep the current onboarding observation in the evidence set. Record the direction and any effect on scope or plan.
Coordinate the next detail
Move from sequence to the shared ownership and decision references. Engagement scope Check the review boundary before adding work. Team responsibilities See which role coordinates each part of the example. Engagement decisions See what context and rationale to capture.

Team responsibilities

Who coordinates what
Role descriptions are illustrative for the fictional Northstar review. The delivery lead coordinates the engagement plan, keeps the shared decision record legible, and brings boundary questions to the engagement discussion. The engagement consultant connects the review question to evidence and communicates findings. A specialist contributes focused subject expertise and helps distinguish what evidence supports from what remains uncertain. These roles work together; role ownership does not imply that one person makes every client or commercial decision. The decision page shows how this example records direction and rationale.
Role responsibilities
A clear coordinating role makes handoffs visible while keeping expertise and decisions with the appropriate contributors. Delivery lead Coordinates the working plan and shared decision record. Brings scope questions and dependencies into the team discussion. Keep the current sequence and key dependencies visible. Record the question, direction, rationale, and affected work. Reflect agreed direction in the scope and delivery references. Engagement consultant Connects the review question to interviews, process materials, and the findings discussion. Tie observations to the relevant journey step and evidence. Separate observation from interpretation or recommendation. Bring evidence gaps and new requests to the engagement discussion. Specialist Contributes focused expertise to help interpret observations and identify additional context that may be needed. Explain evidence limits within the specialist area. Flag assumptions that could affect an interpretation. Share relevant input with the consultant and delivery lead.
Example work products and handoffs
The coordinating role is distinct from contributors who provide evidence or expertise. Work product Coordinates Input or handoff Review question and scope summary Delivery lead Consultant and specialist align on evidence needs Current-journey observations Engagement consultant Specialist helps interpret relevant evidence Decision record Contributors provide context and rationale Findings discussion Delivery lead coordinates the plan and open questions
Related coordination references
Delivery approach Follow the sample sequence and evidence handoffs. Engagement decisions Review the completed example and decision context.

Engagement decisions

Make the direction and its effect easy to follow
A useful decision record explains the question, context, chosen direction, rationale, and affected work. Record a decision when the team has chosen a direction that affects the engagement’s scope, sequence, or interpretation. Include enough context for a contributor who missed the discussion to understand what was considered and why. Keep unresolved questions distinct from chosen directions. If a decision changes the work, reflect its effect in the scope and delivery references so the team works from the same picture.
Completed example: keep the review focused
Fictional scope clarification for the Northstar onboarding review. Decision detail Recorded example Question Does a request to redesign a separate client system belong in this review? Context The request arose during a discussion of the current onboarding journey. Direction Keep this review focused on documenting the current onboarding journey; discuss system redesign separately. Rationale The stated review boundary covers the current journey and findings, not redesign or implementation of a separate system. Effect on work Continue documenting relevant onboarding observations. Do not add redesign tasks to this review sequence.
Decision or open question?
Use wording that makes the state of the discussion observable. A decision has a chosen direction The example identifies a selected boundary and explains why it fits the stated review. A reader can tell what work continues and what is separate. State the direction in a sentence that can guide the next work step. Tie the rationale to the engagement context. Describe which scope or delivery details are affected. An open question still needs discussion If the team has not agreed whether a new request changes the engagement, record it as unresolved and identify the appropriate team discussion. Write the question without implying approval. Capture the context and evidence available so far. After direction is agreed, update the decision record and affected references.
Follow the decision through
Engagement scope Compare the direction with the stated review boundary. Delivery approach See how the direction affects the example sequence. Team responsibilities Clarify who coordinates and contributes to the record.

Reusable resources

Working references for the next engagement conversation
Use these authored examples to make scope discussions, meeting preparation, and decision notes more specific. Keep each prompt tied to the engagement in front of you. Distinguish confirmed context from questions still under discussion; these examples are working references, not client-approved documents or a connected document search.
Reusable engagement prompts
Each card contains usable prompts and links to the related detail page. Scope conversation prompts What outcome is this engagement working toward? Which current process or service is included? What output is expected? Which adjacent request is not included by default? What discussion would clarify a boundary? Scope prompts See the scope example Meeting preparation checklist Write down the question to resolve, relevant scope detail, evidence or context already available, roles whose input is needed, and work that may change depending on the direction. Meeting preparation See the delivery sequence Decision-note structure Capture five parts: question; context; chosen direction or open status; rationale; and effect on scope, sequence, or interpretation. The Northstar example shows a completed scope clarification. Decision notes Read the completed example
Choose the reference that fits the work
Use a prompt where it helps the team coordinate. When the boundary is unclear Use the scope prompts to distinguish the stated review from an adjacent request, then bring unresolved direction to the engagement discussion. Name the intended outcome. Describe the request in relation to the stated boundary. Separate a question from an agreed direction. When the team needs a shared record Use the decision-note structure to capture context and rationale, then make the effect on scope or sequence visible to contributors. Record the question and relevant context. State what is decided and what remains open. Reflect the direction in the affected reference.

How to use this template

Clone the site and replace the Northstar onboarding scenario with confirmed information about the engagement’s outcome, boundary, contributors, and expected outputs.
Review the scope page with the appropriate engagement participants, making included work, exclusions, and unresolved boundary questions explicit.
Adapt the illustrative four-week sequence to actual dates, dependencies, evidence sources, and discussion points, then assign coordination and contribution roles using the responsibilities page.
As work proceeds, record observations with their supporting context and keep them distinct from interpretations, recommendations, and unanswered questions.
When a request or direction affects scope or delivery, capture the question, context, chosen direction or open status, rationale, and affected work on the decisions page.
After an agreed change, update the relevant scope and delivery references, check that navigation still leads to the current information, and remove sample details that no longer apply.

Best practices

Keep the intended review outcome and exclusions visible on the scope page so contributors can check new requests before treating them as work.
Tie each observation to the journey step and evidence that supports it, and label evidence gaps as questions rather than conclusions.
Use the sample sequence as a planning prompt, then replace its weeks with actual timing and dependencies instead of presenting it as a committed schedule.
Name one coordinating role for maintaining the plan and decision record while making clear that contributors supply expertise and evidence.
Mark a decision as open until the team has chosen a direction, and avoid wording that implies approval where none exists.
When direction changes, update the scope and delivery references together so linked pages do not tell contributors different stories.
Use the reusable prompts as conversation aids, not as client-approved documents or a substitute for the engagement’s authoritative records.
Check page headings, link destinations, keyboard access, and contrast against WCAG 2.1 AA when configuring the site for its intended audience.

What this template typically catches

Issues teams running this template most often surface in practice:

A new request is silently added to the work instead of being captured as a boundary question for discussion.

An observation is written as a conclusion or recommendation even though its supporting evidence is missing or incomplete.

The sample four-week sequence is mistaken for a committed schedule despite actual dependencies or dates being different.

Contributors cannot tell who coordinates the plan, decision record, or findings discussion.

An unresolved question is worded like an agreed direction, leading readers to assume work has been approved.

A decision changes scope, but the scope or delivery page is not updated to reflect the direction.

The same engagement detail is copied across pages and becomes inconsistent as the work changes.

Sample Northstar content remains in the site after customization, confusing contributors about the real client or review.

Common use cases

Consulting delivery lead coordinating a review

Use the overview, responsibilities, and delivery pages to give contributors a shared view of the review sequence and handoffs. Keep the decision record current when scope questions affect the plan.

Employee-experience consultant reviewing onboarding

Adapt the fictional onboarding scope to document a client’s current journey, agreed process materials, and observed friction points. Preserve the distinction between evidence-backed observations and proposed redesign.

Specialist joining a cross-functional engagement

Use the role and scope references to see where focused expertise is needed and what the review does not include by default. Add relevant evidence or assumptions to the team discussion rather than treating expertise as approval authority.

Professional-services team handling an adjacent request

When a discussion surfaces work outside the engagement boundary, capture the request and context and route it to the decision discussion. Update the shared references only after direction is agreed.

Frequently asked questions

What kind of engagement is this template designed for?

It is a coordination site for one client engagement, illustrated with a fictional four-week review of an employee onboarding service. Its pages connect the engagement outcome and boundary to delivery steps, role ownership, decision records, and working prompts. Adapt the example to a different project by replacing its sample subject matter and aligning each page to the agreed work.

Does the sample four-week plan set a required delivery cadence?

No. The four-week sequence is illustrative, not a live schedule or a guarantee. Use it as a way to organize alignment, input gathering, synthesis, and discussion, then replace the timing with the actual engagement dates and dependencies. Update the delivery reference when the working plan changes.

Who should maintain and use the site?

The example assigns coordination of the plan and shared decision record to a delivery lead. The engagement consultant connects the review question to evidence and findings, while a specialist contributes focused expertise. Contributors use the scope and decision references to understand the boundary and the effect of agreed directions.

Does this template establish a contract, compliance process, or client approval?

No. The sample pages explain an illustrative engagement boundary and working approach; they do not replace a statement of work, client approval, legal review, or applicable organizational requirements. Confirm actual scope and authority through the appropriate engagement process. The template does not claim that its fictional examples have been approved or reviewed.

How should the team handle a request that falls outside the stated scope?

Capture what was requested and the context in which it arose, then bring the boundary question to the engagement discussion. Do not silently add the work or describe it as approved. Once direction is agreed, record the rationale and reflect the effect in the scope and delivery references.

What should we customize before sharing the site?

Replace the Northstar onboarding scenario with confirmed details for the engagement, including its intended outcome, included work, exclusions, contributors, and actual sequence. Review the worked decision example and prompts so they do not imply a direction that your team has not agreed. Check every page and navigation label for relevance before inviting contributors.

Does the site connect to project tools or client document systems?

No live project, calendar, or document-search connection is configured in the example. The reusable resources are authored prompts that link to pages within this site, not a connected repository or client-approved document set. Add only destinations and integrations your site environment actually supports.

How is this different from coordinating an engagement in ad-hoc notes?

The six-page structure gives scope, delivery, responsibilities, decisions, and prompts distinct homes linked from an overview and navigation menu. A completed fictional decision example shows how context, direction, rationale, and work impact fit together. Ad-hoc notes can scatter those details or leave contributors unsure which reference reflects the current direction.

Related templates

Sites

Leaving the Company Well

Leaving the Company Well is a practical departure guide for handing off active work, preparing co...

Sites

Learning Transfer After a Course

A one-page guide for learners and managers to test one course idea in everyday work. Choose a sma...

Sites

Open-Source Software Use

The Open-Source Software Use page shows developers and technical buyers what to record before add...

Sites

Using AI at Work

Using AI at Work is a three-page intranet learning site with a fictional worked example, prompt c...

Sites

Financial Forecast Assumptions

A reference page for documenting forecast drivers, evidence, scenario values, dependencies, and a...

Forms

Employee Onboarding Form

Employee Onboarding Form for collecting new hire details, tax references, direct deposit, emergen...

Inspections

Abandoned Channel Hygiene Audit

Abandoned Channel Hygiene Audit template for reviewing inactive, orphaned, and duplicate communic...

Sop

New Employee Onboarding Checklist

New Employee Onboarding Checklist template for standardizing pre-boarding, first-day orientation,...

Go deeper on the topic

Related concepts

Digital Workplace vs Modern Intranet

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 Client Engagement Team Site ready.

Request pricing

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.

6 pages Engagement overview Engagement scope Delivery approach Team responsibilities Engagement decisions Reusable resources

Engagement overview Coordinate the Northstar service-readiness review A shared starting point for the consultants, delivery lead, and specialists working on one engagement. This fictional example follows a four-week review of Northstar Group’s employee onboarding service. Use the pages here to align on the review boundary, sequence, ownership, and decisions. The engagement at a glance Start with the outcome, then open the page that holds the working detail. Outcome and boundary Describe the current onboarding journey, identify observed friction points, and present prioritized findings for discussion. Redesign and implementation are not included by default. Working sequence Align on the review question, gather agreed inputs, synthesize observations, then discuss findings. Role ownership The delivery lead coordinates the plan and decision record; contributors bring subject expertise and evidence. Direction and rationale Record the question, context, chosen direction, rationale, and affected work so contributors can follow the same picture. Section Divider How the work fits together One engagement, one shared picture Connect the question to the next handoff A practical coordination pattern for the fictional review. Keep the review question visible The review asks how employees currently move through onboarding, where handoffs occur, and what evidence supports the team’s observations. Use the agreed review question to focus interviews and document review. Record observations separately from recommendations. Check proposed work against the stated scope. Move new requests into a decision discussion If a contributor hears a request to redesign a separate system, capture the request and context rather than silently adding work to the review. Note what was requested and where it arose. Bring the boundary question to the engagement discussion. Reflect an agreed change in the scope and delivery references. Open a working reference Each destination gives the detail for one part of the engagement. Team responsibilities See who coordinates each work product and handoff. Reusable resources Use authored prompts for scope discussions and decision notes. Engagement scope What the review covers The example engagement is a four-week review of the current employee onboarding journey. Intended outcome: describe the current journey, identify observed friction points, and present prioritized findings for discussion with the engagement team. In scope: mapping current onboarding steps from accepted offer through the first month; reviewing agreed process materials; and discussing observations with people identified for the review. Not included by default: redesigning or configuring a separate client system, implementing recommendations, or evaluating unrelated employee services. A new request is a question to discuss, not an automatic change to the work. Scope at a glance Illustrative boundaries for this fictional review. Work area Included Not included by default Current journey Document onboarding steps and handoffs Redesign a separate client system Evidence Review agreed materials and discuss observed steps Claim findings beyond gathered evidence Output Present prioritized observations for discussion Implement recommendations A boundary example Keep observations tied to the agreed review; route adjacent requests to a discussion. Included: document the current onboarding steps A conversation reveals that a new starter waits for account access after an existing onboarding step. The team records where the handoff occurs, what evidence supports the observation, and which part of the current journey it affects. Tie the observation to the current process. Record missing evidence as a question, not a conclusion. Include the supported observation in the review findings. Discuss separately: redesign a client system A participant asks the team to redesign a separate client system. That request may merit discussion, but documenting the current onboarding journey does not include redesign by default. Capture what was requested and why it arose. Bring the boundary question to the engagement decision discussion. Do not promise added work before the appropriate discussion. Continue with the related work Use these pages when a boundary question affects delivery or direction. Delivery approach See the sample sequence for gathering and discussing evidence. Engagement decisions See how the example boundary question is recorded and explained. Delivery approach How the review moves from question to discussion A sample four-week sequence for coordinating the work, not a live schedule or a guarantee. Align on the review question and scope boundary. Gather agreed process materials and observations, synthesize what the evidence supports, then discuss findings and open questions with the engagement team. Keep observations, interpretations, and recommendations distinct. When a new request falls outside the stated review, record its context and bring it to the decision discussion instead of silently expanding the work. A four-week example sequence Timing illustrates how this fictional review might be organized; actual engagement dates and dependencies determine the working plan. Align the review question Agree the intended outcome, review boundary, relevant contributors, and inputs for the example review. Week 1 Gather agreed inputs Review identified process materials and collect observations relevant to the current onboarding journey. Week 2 Synthesize observations Group evidence by journey stage, note gaps, and distinguish observations from interpretations or recommendations. Week 3 Discuss findings and open questions Present prioritized observations, explain their evidence, and record boundary or direction questions for follow-up. Week 4 Worked coordination example Keep the review useful without treating an adjacent request as approved work. An interview surfaces a system-redesign request During a discussion about onboarding, a participant asks the team to redesign a separate client system. The delivery lead records the request and its context; the consultant distinguishes it from the current-process observation; the team discusses whether it belongs in a separate engagement conversation. Do not silently add redesign tasks to the review sequence. Keep the current onboarding observation in the evidence set. Record the direction and any effect on scope or plan. Coordinate the next detail Move from sequence to the shared ownership and decision references. Engagement scope Check the review boundary before adding work. Team responsibilities See which role coordinates each part of the example. Engagement decisions See what context and rationale to capture. Team responsibilities Who coordinates what Role descriptions are illustrative for the fictional Northstar review. The delivery lead coordinates the engagement plan, keeps the shared decision record legible, and brings boundary questions to the engagement discussion. The engagement consultant connects the review question to evidence and communicates findings. A specialist contributes focused subject expertise and helps distinguish what evidence supports from what remains uncertain. These roles work together; role ownership does not imply that one person makes every client or commercial decision. The decision page shows how this example records direction and rationale. Role responsibilities A clear coordinating role makes handoffs visible while keeping expertise and decisions with the appropriate contributors. Delivery lead Coordinates the working plan and shared decision record. Brings scope questions and dependencies into the team discussion. Keep the current sequence and key dependencies visible. Record the question, direction, rationale, and affected work. Reflect agreed direction in the scope and delivery references. Engagement consultant Connects the review question to interviews, process materials, and the findings discussion. Tie observations to the relevant journey step and evidence. Separate observation from interpretation or recommendation. Bring evidence gaps and new requests to the engagement discussion. Specialist Contributes focused expertise to help interpret observations and identify additional context that may be needed. Explain evidence limits within the specialist area. Flag assumptions that could affect an interpretation. Share relevant input with the consultant and delivery lead. Example work products and handoffs The coordinating role is distinct from contributors who provide evidence or expertise. Work product Coordinates Input or handoff Review question and scope summary Delivery lead Consultant and specialist align on evidence needs Current-journey observations Engagement consultant Specialist helps interpret relevant evidence Decision record Contributors provide context and rationale Findings discussion Delivery lead coordinates the plan and open questions Related coordination references Delivery approach Follow the sample sequence and evidence handoffs. Engagement decisions Review the completed example and decision context. Engagement decisions Make the direction and its effect easy to follow A useful decision record explains the question, context, chosen direction, rationale, and affected work. Record a decision when the team has chosen a direction that affects the engagement’s scope, sequence, or interpretation. Include enough context for a contributor who missed the discussion to understand what was considered and why. Keep unresolved questions distinct from chosen directions. If a decision changes the work, reflect its effect in the scope and delivery references so the team works from the same picture. Completed example: keep the review focused Fictional scope clarification for the Northstar onboarding review. Decision detail Recorded example Question Does a request to redesign a separate client system belong in this review? Context The request arose during a discussion of the current onboarding journey. Direction Keep this review focused on documenting the current onboarding journey; discuss system redesign separately. Rationale The stated review boundary covers the current journey and findings, not redesign or implementation of a separate system. Effect on work Continue documenting relevant onboarding observations. Do not add redesign tasks to this review sequence. Decision or open question? Use wording that makes the state of the discussion observable. A decision has a chosen direction The example identifies a selected boundary and explains why it fits the stated review. A reader can tell what work continues and what is separate. State the direction in a sentence that can guide the next work step. Tie the rationale to the engagement context. Describe which scope or delivery details are affected. An open question still needs discussion If the team has not agreed whether a new request changes the engagement, record it as unresolved and identify the appropriate team discussion. Write the question without implying approval. Capture the context and evidence available so far. After direction is agreed, update the decision record and affected references. Follow the decision through Engagement scope Compare the direction with the stated review boundary. Delivery approach See how the direction affects the example sequence. Team responsibilities Clarify who coordinates and contributes to the record. Reusable resources Working references for the next engagement conversation Use these authored examples to make scope discussions, meeting preparation, and decision notes more specific. Keep each prompt tied to the engagement in front of you. Distinguish confirmed context from questions still under discussion; these examples are working references, not client-approved documents or a connected document search. Reusable engagement prompts Each card contains usable prompts and links to the related detail page. Scope conversation prompts What outcome is this engagement working toward? Which current process or service is included? What output is expected? Which adjacent request is not included by default? What discussion would clarify a boundary? Scope prompts See the scope example Meeting preparation checklist Write down the question to resolve, relevant scope detail, evidence or context already available, roles whose input is needed, and work that may change depending on the direction. Meeting preparation See the delivery sequence Decision-note structure Capture five parts: question; context; chosen direction or open status; rationale; and effect on scope, sequence, or interpretation. The Northstar example shows a completed scope clarification. Decision notes Read the completed example Choose the reference that fits the work Use a prompt where it helps the team coordinate. When the boundary is unclear Use the scope prompts to distinguish the stated review from an adjacent request, then bring unresolved direction to the engagement discussion. Name the intended outcome. Describe the request in relation to the stated boundary. Separate a question from an agreed direction. When the team needs a shared record Use the decision-note structure to capture context and rationale, then make the effect on scope or sequence visible to contributors. Record the question and relevant context. State what is decided and what remains open. Reflect the direction in the affected reference.