Practice vocabulary for setting expectations with clients: scope of work, change requests, escalating issues, and managing project boundaries professionally.
0 / 22 completed
1 / 22
A client asks you to add a new feature that wasn't in the original agreement. What is the correct professional term for this situation?
The correct term is 'change request.' You might say: 'That sounds like a great addition — I'll put together a change request with the updated timeline and cost.'
2 / 22
Which phrase best communicates that a client's new request falls outside the agreed project boundaries?
'Out of scope' is the professional term. Example: 'Adding a mobile version would be out of scope for the current engagement — I'd be happy to discuss a separate phase for that.'
3 / 22
A client expects their project delivered in 2 weeks but you estimate 5 weeks. Which phrase best describes your initial conversation?
This is called 'setting expectations.' Early, honest communication about timelines prevents later conflicts. You might say: 'I want to set expectations upfront — based on the requirements, I estimate this will take 4–5 weeks.'
4 / 22
The project is significantly delayed due to unclear requirements from the client. What should you do professionally?
You should escalate the issue. Example: 'I want to flag that the delayed feedback on the design mockups has pushed our timeline back by approximately one week. I'll need to revise the estimate accordingly.'
5 / 22
How would you professionally tell a client that their new request will require more time and money?
'I'll need to revise the estimate' is the professional phrasing. It's factual, non-accusatory, and frames additional cost as a natural consequence of the expanded scope.
6 / 22
During a sprint review with your client, they excitedly propose integrating a third-party library to drastically improve the performance of their user profile page. You've been focused on delivering core functionality as outlined in the initial specification. Which phrase best reflects your need to carefully evaluate this request?
<code>Scope Creep</code>
This situation exemplifies 'scope creep,' where the project requirements expand beyond their original definition. Simply accepting the request without assessment can lead to significant delays and budget overruns. The correct response acknowledges the client's suggestion while emphasizing the need for a structured evaluation of its impact on the existing scope and timeline, preventing uncontrolled expansion.
7 / 22
You're reviewing a PR with your client, Sarah from Acme Corp. She's requesting a custom dashboard displaying real-time server metrics – something not initially discussed or planned for in the project scope. Which phrase best communicates your need to discuss the implications of this change before proceeding?
Sarah's request introduces scope creep – an uncontrolled expansion of project requirements. Option 1 is overly casual and doesn't address the potential impact. Option 2 correctly acknowledges the change while proposing a discussion to assess its consequences, aligning with professional communication. Options 3 and 4 are inappropriate responses that avoid acknowledging the deviation from the original plan.
8 / 22
During a sprint review with your client, David from Beta Solutions, he excitedly suggests adding a new 'gamification' feature to the user interface – points, badges, leaderboards – to increase engagement. This wasn't part of the original product roadmap or discussed in detail. Which phrase best expresses your cautious approach while still being collaborative?
The correct answer, "Let's immediately implement this; it'll be fantastic for user retention!", reflects a lack of critical evaluation and immediate commitment to scope creep. The other options demonstrate more professional communication – acknowledging the suggestion while requesting further discussion about its implications (time, resources, impact). This is crucial in managing client expectations and maintaining project control.
9 / 22
During a sprint review with your client, they excitedly propose integrating a third-party library to drastically improve the performance of their user profile page. You've been focused on delivering core functionality as outlined in the initial specification. Which phrase best reflects your need to carefully evaluate this request?
<code>Scope Creep</code>
This situation exemplifies 'scope creep,' where the project requirements expand beyond their original definition. Simply accepting the request without assessment can lead to significant delays and budget overruns. The correct response acknowledges the client's suggestion while emphasizing the need for a structured evaluation of its impact on the existing scope and timeline, preventing uncontrolled expansion.
10 / 22
You're reviewing a PR with your client, Sarah from Acme Corp. She's requesting a custom dashboard displaying real-time server metrics – something not initially discussed or planned for in the project scope. Which phrase best communicates your need to discuss the implications of this change before proceeding?
Sarah's request introduces scope creep – an uncontrolled expansion of project requirements. Option 1 is overly casual and doesn't address the potential impact. Option 2 correctly acknowledges the change while proposing a discussion to assess its consequences, aligning with professional communication. Options 3 and 4 are inappropriate responses that avoid acknowledging the deviation from the original plan.
11 / 22
During a sprint review with your client, David from Beta Solutions, he excitedly suggests adding a new 'gamification' feature to the user interface – points, badges, leaderboards – to increase engagement. This wasn't part of the original product roadmap or discussed in detail. Which phrase best expresses your cautious approach while still being collaborative?
The correct answer, "Let's immediately implement this; it'll be fantastic for user retention!", reflects a lack of critical evaluation and immediate commitment to scope creep. The other options demonstrate more professional communication – acknowledging the suggestion while requesting further discussion about its implications (time, resources, impact). This is crucial in managing client expectations and maintaining project control.
12 / 22
During a sprint review with your client, they excitedly propose integrating a third-party library to drastically improve the performance of their user profile page. You've been focused on delivering core functionality as outlined in the initial specification. Which phrase best reflects your need to carefully evaluate this request?
<code>Scope Creep</code>
This situation exemplifies 'scope creep,' where the project requirements expand beyond their original definition. Simply accepting the request without assessment can lead to significant delays and budget overruns. The correct response acknowledges the client's suggestion while emphasizing the need for a structured evaluation of its impact on the existing scope and timeline, preventing uncontrolled expansion.
13 / 22
You're reviewing a PR with your client, Sarah from Acme Corp. She's requesting a custom dashboard displaying real-time server metrics – something not initially discussed or planned for in the project scope. Which phrase best communicates your need to discuss the implications of this change before proceeding?
Sarah's request introduces scope creep – an uncontrolled expansion of project requirements. Option 1 is overly casual and doesn't address the potential impact. Option 2 correctly acknowledges the change while proposing a discussion to assess its consequences, aligning with professional communication. Options 3 and 4 are inappropriate responses that avoid acknowledging the deviation from the original plan.
14 / 22
During a sprint review with your client, David from Beta Solutions, he excitedly suggests adding a new 'gamification' feature to the user interface – points, badges, leaderboards – to increase engagement. This wasn't part of the original product roadmap or discussed in detail. Which phrase best expresses your cautious approach while still being collaborative?
The correct answer, "Let's immediately implement this; it'll be fantastic for user retention!", reflects a lack of critical evaluation and immediate commitment to scope creep. The other options demonstrate more professional communication – acknowledging the suggestion while requesting further discussion about its implications (time, resources, impact). This is crucial in managing client expectations and maintaining project control.
15 / 22
During a sprint review with your client, they excitedly propose integrating a third-party library to drastically improve the performance of their user profile page. You've been focused on delivering core functionality as outlined in the initial specification. Which phrase best reflects your need to carefully evaluate this request?
<code>Scope Creep</code>
This situation exemplifies 'scope creep,' where the project requirements expand beyond their original definition. Simply accepting the request without assessment can lead to significant delays and budget overruns. The correct response acknowledges the client's suggestion while emphasizing the need for a structured evaluation of its impact on the existing scope and timeline, preventing uncontrolled expansion.
16 / 22
You're reviewing a PR with your client, Sarah from Acme Corp. She's requesting a custom dashboard displaying real-time server metrics – something not initially discussed or planned for in the project scope. Which phrase best communicates your need to discuss the implications of this change before proceeding?
Sarah's request introduces scope creep – an uncontrolled expansion of project requirements. Option 1 is overly casual and doesn't address the potential impact. Option 2 correctly acknowledges the change while proposing a discussion to assess its consequences, aligning with professional communication. Options 3 and 4 are inappropriate responses that avoid acknowledging the deviation from the original plan.
17 / 22
During a sprint review with your client, David from Beta Solutions, he excitedly suggests adding a new 'gamification' feature to the user interface – points, badges, leaderboards – to increase engagement. This wasn't part of the original product roadmap or discussed in detail. Which phrase best expresses your cautious approach while still being collaborative?
The correct answer, "Let's immediately implement this; it'll be fantastic for user retention!", reflects a lack of critical evaluation and immediate commitment to scope creep. The other options demonstrate more professional communication – acknowledging the suggestion while requesting further discussion about its implications (time, resources, impact). This is crucial in managing client expectations and maintaining project control.
18 / 22
You're discussing the upcoming release with Mark from GlobalTech. He asks, 'Can we add a feature to automatically send users a daily digest email summarizing their recent activity?' This wasn't in the original requirements document. Which phrase best communicates your concerns while remaining professional?
The correct answer emphasizes the impact on timeline and budget, acknowledging the request but politely pushing back against scope creep. Options A and D are overly enthusiastic and don't address the potential consequences. Option C is passive and doesn't clearly state the issue.
19 / 22
During a Slack conversation with client support, Alex from Stellar Solutions mentions, 'Our users are complaining about slow page loads. Can you investigate and optimize the database queries?' What is the most appropriate response to acknowledge his concern and initiate action?
This response demonstrates proactive problem-solving by creating a ticket and outlining the initial steps. It's crucial to acknowledge the issue and show you're taking ownership. Options A is reactive and doesn't initiate action; B is too vague; C simply delegates without detail.
20 / 22
You've been tasked with writing a PR description for a change that improves the API response time for a key endpoint. The client, Lisa from Nova Systems, is reviewing it. Which phrase would best convey the technical improvement to a non-technical stakeholder?
Option 1 provides a clear and concise explanation of the technical change – caching – in terms that a non-technical user can understand. The other options are too detailed and use jargon without context. It's important to translate technical improvements into understandable benefits.
21 / 22
During a standup meeting with your client, Chris from Horizon Dynamics asks: 'Could you integrate support for two-factor authentication (2FA) to enhance security?' You've been focused on delivering the core user login functionality. What's the best way to respond?
This response politely declines the request by explaining why it's outside the current scope and suggesting a discussion about priorities. This avoids over-promising and setting unrealistic expectations – crucial for client management.
22 / 22
Sarah from Zenith Solutions asks during a code review: 'Can you explain the reasoning behind this complex algorithm? I'm not sure it's the most efficient solution.' What is the most professional and constructive response to offer?
The correct answer acknowledges her concern while providing a rational explanation for the choice – highlighting trade-offs demonstrates understanding and openness to discussion. It avoids dismissing her feedback and invites further exploration of the technical decision.
What does the "Client Communication Vocabulary" exercise cover?
Practice vocabulary for setting expectations with clients: scope of work, change requests, escalating issues, and managing project boundaries professionally.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Client Communication Vocabulary"?
This exercise has 22 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Freelance Client exercises?
Browse the full Freelance Client hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.