%20(1).png)
When a Client Keeps Changing Requirements: Business English Idioms and Phrases for Work
- 3 days ago
- 7 min read
Updated: 9 hours ago
In this article:
A Business English idiom for changing requirements
A client changing requirements is one of those problems that does not always look serious at first. The project still seems to be moving, people are still doing their work, and on the surface, everything looks more or less under control. Then you start to realize that the work in front of you is no longer the same as the work everyone agreed on earlier.
That is when things usually start getting messy. Tasks have to be revisited, and it becomes harder to give a clear update on where the project stands. In this article, you’ll learn natural Business English phrases you can use when a client keeps changing requirements.
For more useful phrases for problems, delays, and difficult situations at work, see our full guide to Business English for problems at work.
ADVERTISEMENT
Client Changing Requirements: Workplace Scenario Quiz
App Launch
Your team is finishing an app for a client.
At first, they ask for a few bug fixes before release. You do that.
Then they want changes to the design.
A few days later, they ask to add a new payment option too.
But your team is still expected to release it this week.
You say:
They keep moving the _____. Every time we fix one thing, there’s something else they want.
A) goalposts
B) referees
C) red cards
D) scoreboards
Choose the phrase that best completes the sentence. Then listen to the sentence.
Using Business English Naturally at Work
Many learners understand a phrase when they read it. The harder part is using it naturally in a real conversation at work.
That’s what you practice in Pro Vocabulary Lab.
Inside the program, you’ll work with:
realistic workplace situations
short dialogues based on real work conversations
speaking practice with natural Business English
Business English Idiom: When a Client Keeps Changing Requirements
The idiom in the quiz is:
move the goalposts
idiom
to keep changing requirements after work has already started
The client keeps moving the goalposts. We’ve already updated the design twice.
Every time we finish one change, they ask for something else. They’re really moving the goalposts.
We agreed on the scope last week, but now they want extra features too. They’re moving the goalposts.
It’s hard to stay on schedule when the client keeps moving the goalposts.
First, they wanted bug fixes. Now they want a new payment option as well. They keep moving the goalposts.
That's right! The correct answer is A) goalposts.
ADVERTISEMENT
More Business English Phrases for Changing Requirements
When requirements keep changing, move the goalposts is a useful phrase, but it is not the only one we can use at work. Here are some more natural Business English expressions for talking about scope changes, added requests, and projects that keep getting more difficult to manage.
The scope has changed.
(standard professional English, common in project meetings and client discussions)
= The project now includes different or extra work than what was originally agreed.
The scope has changed, so we’ll need more time to finish it.
We were almost done, but then the scope changed.
Since the scope has changed, we need to confirm what’s still included.
I thought we were only updating the homepage, but the scope has changed.
The scope has changed quite a bit since the first meeting.
If the scope has changed, we should talk about the budget too.
This was supposed to be a small update, but the scope has clearly changed.
The scope changed halfway through the project, and that caused delays.
ADVERTISEMENT
This wasn’t part of the original scope.
(standard professional English)
= This was not included in the work that was agreed at the beginning.
Adding a new payment option wasn’t part of the original scope.
I can do it, but it wasn’t part of the original scope.
This wasn’t part of the original scope. We were only asked to make a few content updates.
Redesigning the whole page wasn’t part of the original scope.
That kind of testing wasn’t part of the original scope we agreed on.
This wasn’t part of the original scope, so I don’t want to promise it without checking internally first.
We have to rework parts of the project.
(standard project language)
= We need to do some of the work again because something changed.
Because they changed the approval process again, we have to rework parts of the project.
We were ready to move forward, but now we have to rework parts of the project.
If they want all the screens updated too, we have to rework parts of the project.
Every time the requirements change this late, we have to rework parts of the project.
We only planned for small fixes, so reworking parts of the project will push everything back.
We’ve already done the first round, and now we have to rework parts of the project.
If they want us to change the layout, we have to rework parts of the project.
ADVERTISEMENT
We’ll need to revisit the timeline.
(more formal, common in project meetings)
= We need to look at the project schedule again.
With these new changes, we’ll need to revisit the timeline.
If the client wants another round of edits, we may need to revisit the timeline.
Now that the scope has changed, we’ll need to revisit the timeline.
I know this is a priority, but we probably need to revisit the timeline.
If approval doesn’t come through today, we’ll have to revisit the timeline.
We can do that, but we’d need to revisit the timeline first.
If the content is still changing, we might need to revisit the timeline.
At this point, we need to revisit the timeline because the current schedule isn’t realistic anymore.
This is starting to affect the timeline.
(more formal, more common in meetings than in everyday speech)
= This is beginning to change the project schedule.
At first, this didn’t seem like a big issue, but it’s starting to affect the timeline.
We’ve managed the smaller changes so far, but this is starting to affect the timeline now.
If we keep adding things at this stage, it’s going to affect the timeline.
I know each change looks small, but together they’ll affect the timeline.
We can make that change, but it’ll probably affect the timeline.
If this needs another round of review, that’s likely to affect the timeline.
I’m not saying we can’t do it. I’m just saying it may affect the timeline.
Once we add testing for a second model, that’s definitely going to affect the timeline.
We’ve worked around the smaller changes so far, but this is affecting the timeline more than we expected.
At this point, the repeated revisions are very likely to affect the timeline.
This goes beyond what we originally agreed on.
(formal)
= This includes more than we first agreed to do.
I’m happy to discuss it, but adding materials for the sales team goes beyond what we originally agreed on.
A second workshop wasn’t in the plan, so that goes beyond what we originally agreed on.
Supporting three regional versions from the start goes beyond what we originally agreed on.
Including manager training as part of this would go beyond what we originally agreed on.
If the rollout now needs to cover both teams, that goes beyond what we originally agreed on.
Post-launch support for another month goes beyond what we originally agreed on.
Covering internal documentation as well goes beyond what we originally agreed on.
If we’re also expected to brief their partners, that goes beyond what we originally agreed on.
ADVERTISEMENT
This is turning into a bigger project than we expected/ thought.
(natural spoken business English)
= It is becoming more complicated than we thought at first.
We only planned a few updates, but this is turning into a bigger project than we expected.
At first, it looked like a quick fix. Now it’s turning into a bigger project than we thought.
Once we started looking into the problem, it became clear that this is turning into a bigger project than we expected.
We can still do it, but it’s turning into a bigger project than we expected.
With all these extra requests, this is turning into a bigger project than we thought.
I thought we were just making a small change, but this is turning into a bigger project than we expected.
If they want more changes after this, it’s really turning into a bigger project than we expected.
You Might Also Like: Business English Phrases for Meetings: Reframe the Conversation
Practice Business English Phrases for When a Client Keeps Changing Requirements
Read the scenario. What would you say in this situation? Say your answer out loud.
New Packaging
You’re working on new packaging for a food brand.
At first, the brand manager asks for a few label changes. You do it. Then she asks for a new box design, new photos, and extra versions for different stores.
The launch date stays the same.
Say that you can do it, but there is now more work involved, so you need to look at the plan again before confirming the date.
Your Turn
What would you say?
Say your answer out loud.
Try using: We will need to revisit the timeline.
Check Your Answer in Pro Vocabulary Lab
Inside Pro Vocabulary Lab, you can listen to a natural audio version of the answer, read the transcript, and practice more workplace situations like this one.
Practice Real Workplace English Inside Pro Vocabulary Lab
workplace scenarios based on real job conversations
short dialogues and model answers
speaking practice with natural Business English
more situations focused on problems, delays, and clear workplace updates
Erin West is a Business English coach, writer, and founder of RealBusinessEnglish.com. She creates practical lessons and quizzes based on real workplace English.
Comments