Push back and reject both describe resistance, but they leave the conversation in very different states. Reject closes or denies a request outright, more than most negotiations actually call for. Push back resists while keeping discussion or negotiation open.
The test: is the door open or closed?
The question to ask is whether the speaker is ending the discussion or resisting while still engaging. A vendor scenario tests exactly this distinction: a vendor proposes a mid-contract price increase, and the team wants to keep negotiating, not end the relationship.
"We push back on the vendor's proposed price increase and are requesting a call to discuss alternatives."
That fits the scenario -- the team is resisting the number while staying at the table.
"We reject the vendor's proposed price increase."
That closes the proposal more than the situation calls for. It reads as a final answer, not an opening move in a negotiation.
If the vendor's terms were actually unacceptable and the relationship wasn't worth preserving, "we reject the proposed price increase" would become the accurate wording -- reject isn't wrong in general, it's wrong for a situation where the door is meant to stay open.
The common mistake: reaching for reject too early
The mistake is reaching for "reject" when the goal is renegotiation -- it closes the proposal further than the scenario calls for and can prematurely end a relationship or deal meant to stay open. The reverse mistake also happens: using "push back" when a firm, final denial is genuinely needed leaves the door open to pressure that should have been shut down.
Want to learn "Push Back" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →A quick check before choosing: if you would be willing to keep discussing the number after saying the sentence, use "push back." If the sentence should end the discussion entirely, "reject" is the accurate word.
Reject sits alongside refuse and decline
Reject is one of three words -- alongside refuse and decline -- that all close a request more firmly than push back does, each with a slightly different flavor. Reject tends to read as the most neutral and procedural of the three: a proposal, an application, or an offer gets "rejected" without much emotional coloring, the way a filter rejects an input that doesn't meet a spec.
That neutrality is exactly why "reject" can feel jarring in a negotiation you intend to continue. It sounds like an evaluation has been completed and failed, rather than like an opening position in an ongoing back-and-forth. Push back, by contrast, sounds like a move within the negotiation -- which is precisely the frame most vendor and client conversations need until someone has genuinely decided to walk away.
Choosing correctly between the two also protects the relationship in a second, subtler way: once you've told a vendor you "reject" their proposal, reopening the conversation later can feel like backtracking. Starting instead with "we push back on" leaves you room to escalate to a firmer word later if the negotiation doesn't move, without having spent your strongest word too early.
Practice scenarios
Practice using push back in situations like:
- resisting a vendor's price increase while signaling you still want to negotiate
- choosing between 'push back' and 'reject' for a term that genuinely needs to be shut down
- rewriting a negotiation email that closed a door you meant to keep open
Useful practice phrases:
- "We push back on... and are requesting a call to discuss alternatives."
- "We reject..."
- "That's not a rejection -- it's pushback with room to keep talking."