Practice vocabulary for setting expectations with clients: scope of work, change requests, escalating issues, and managing project boundaries professionally.
0 / 5 completed
1 / 5
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 / 5
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 / 5
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 / 5
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 / 5
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.