Business English · Session 08

Push Back Politely

Disagree with a request or plan without creating tension.

Session 082026-08-02Intermediate4 min
1.0x

Ready. Select a line to jump into the conversation.

Add word

Save this expression

Hello everyone. In today's lesson, we'll practice three phrases for pushing back politely at work.

Pushing back is not the same as being negative. It means raising a concern before a decision becomes a problem.

The goal is to sound thoughtful, calm, and useful, not defensive or difficult.

Our first expression is, "I see your point, but I have a concern."

Use this when you want to acknowledge someone's idea before introducing a different view.

It is softer than starting with "I disagree," because it shows that you listened first.

Example one: "I see your point, but I have a concern about the launch timing."

Example two: "I see your point, but I have a concern about how this will affect support."

Example three: "I see your point, but I have a concern about the amount of manual work involved."

Example four: "I see your point, but I have a concern about whether the data is strong enough."

This phrase is useful because it keeps the conversation open.

You are not shutting the idea down. You are asking the team to look at one risk more carefully.

Our second expression is, "Can we revisit the timeline before we commit?"

Use this when the plan may be good, but the deadline feels too aggressive.

"Revisit" sounds professional because it means review again, not reject.

Example one: "Can we revisit the timeline before we commit to Friday?"

Example two: "Can we revisit the timeline before we tell the client this is final?"

Example three: "Can we revisit the timeline before engineering starts planning around it?"

Example four: "Can we revisit the timeline before we add this to the public roadmap?"

This phrase is useful when a deadline is moving faster than the information behind it.

It gives the team a chance to slow down without making anyone feel blamed.

Our third expression is, "I want to flag a potential risk here."

Use this when you need to point out a risk before it becomes expensive or embarrassing.

"Flag" means to bring something to people's attention.

Example one: "I want to flag a potential risk here: we may not have enough testing time."

Example two: "I want to flag a potential risk here before we lock the scope."

Example three: "I want to flag a potential risk here around customer expectations."

Example four: "I want to flag a potential risk here because the approval path is still unclear."

This phrase sounds responsible because it focuses on the work, not on personal disagreement.

It is especially useful in meetings when everyone is moving quickly and no one has named the downside yet.

So today we practiced three phrases: "I see your point, but I have a concern," "Can we revisit the timeline before we commit," and "I want to flag a potential risk here."

A natural meeting sentence could be: "I see your point, but I want to flag a potential risk here."

Or: "Can we revisit the timeline before we commit? I want to make sure the plan is realistic."

I hope today's script helps your pushback sound calm, professional, and useful.

Good pushback protects the work and the relationship at the same time.

Use these phrases when something feels risky, rushed, or not fully thought through.

That is it for today's Work English lesson. Try one of these when you need to disagree without creating tension.

Key Expressions

I see your point, but I have a concernA respectful way to acknowledge someone's view before raising a concern.

Balanced and diplomatic; it shows listening before disagreement.

  • Disagreeing in meetings
  • Raising concerns
  • Protecting a project plan
I see your point, but I have a concern about the launch timing.I see your point, but I have a concern about how this will affect support.I see your point, but I have a concern about the amount of manual work involved.I see your point, but I have a concern about whether the data is strong enough.
Can we revisit the timeline before we commitA professional way to ask the team to review a deadline before agreeing to it.

Calm and practical; it questions the plan without rejecting it.

  • Discussing aggressive timelines
  • Preventing rushed commitments
  • Reviewing launch plans
Can we revisit the timeline before we commit to Friday?Can we revisit the timeline before we tell the client this is final?Can we revisit the timeline before engineering starts planning around it?Can we revisit the timeline before we add this to the public roadmap?
I want to flag a potential risk hereA useful phrase for bringing attention to a possible issue early.

Responsible and neutral; it focuses on risk, not personal disagreement.

  • Naming project risks
  • Slowing down a rushed decision
  • Protecting quality or customer expectations
I want to flag a potential risk here: we may not have enough testing time.I want to flag a potential risk here before we lock the scope.I want to flag a potential risk here around customer expectations.I want to flag a potential risk here because the approval path is still unclear.