How do you respond to a proposal in an English meeting?
There are four moves: accept ("That sounds like a good plan."), accept on a condition ("That could work, as long as …"), hold back ("Could we come back to this once we have the figures?") or decline. When you decline, a direct "That is not a good idea." sounds blunt in a meeting; the sequence reservation, reason, alternative works better: "I'm not sure that would work for us, because … What if we … instead?"
- Accept: "That sounds like a good plan." / "I'm happy to go with that." — on a condition: "That could work, as long as …" / "In principle I agree, but …"
- Hold back: "Could we come back to this once we have the figures?" / "I'd need to check with my team first."
- Decline: reservation + reason + alternative — "I'm not sure that would work for us, because … What if we … instead?"
B2 · Meetings · 10 minResponding to proposals, taught brick by brick.
A structured lesson for B2 learners. Hear a polite no with a counter-proposal, meet the four ways to respond to a proposal from a tutor — accept, accept on a condition, hold back, decline with an alternative — then practise them in interactive drills before the closing quiz. The whole arc takes about ten minutes and nothing requires a signup.
- CEFR levelB2 · Upper intermediate
- Time to completeAbout 10 minutes
- SkillsSpeaking, Business English, Listening, Vocabulary
- Bricks10 blocks
01 / 06
What this is about: a proposal on the table
In many meetings there comes a point where someone makes a concrete proposal: a new supplier, a later launch date, an extra person on the team, a rollout in two phases. From that point on, the meeting is no longer collecting ideas. A decision is due, and the room is waiting for your response. That moment is what this lesson is about. How to put forward a proposal of your own is covered in the Making Suggestions lesson, and how to agree or disagree with an opinion in Agreeing and Disagreeing. Here the proposal is already on the table, and you have four moves. You can accept it as it stands. You can accept it on a condition. You can hold back because something is still missing. Or you can decline it and bring an alternative into play. The four moves have one thing in common: they tell the room what happens next. After a clear yes, someone can get started. After a yes on a condition, the room knows what still needs to be settled. After a "not yet", it is clear what the room is waiting for, and after a no with a counter-proposal, the discussion has a new direction. Responding this way makes you sound polite and decisive at the same time, and that combination is what makes a response useful in a meeting.
02 / 06
Accepting: a clear yes
If you like a proposal, it is fine to say so clearly. A clear yes needs no decoration: "That sounds like a good plan.", "I'm happy to go with that.", "That works for us." or, more casually, "Let's go with that." "That works for me" speaks for you personally, "That works for us" for your team or department, so be clear about whether you are agreeing for yourself or for your team. It helps to attach a next step to the yes, because then the agreement turns straight into work: "That sounds like a good plan. Shall I let the supplier know?" or "I'm happy to go with that — I can update the project plan by Friday." That way the chair does not have to ask who is taking care of it. Be careful with too much hedging, though. A sentence like "I think maybe that could perhaps work" leaves the room unsure whether you agree or have doubts. If you agree, say so plainly. If you have doubts, name them openly — that is what the second move, the yes on a condition, is for. A plain yes is not impolite, by the way: it saves the room time and shows that you genuinely support the proposal.
03 / 06
Accepting on a condition: as long as, provided that, in principle
Often your answer is a yes that depends on something. In that case, name the condition outright instead of just hinting at it. A neutral version is "That could work, as long as we keep the March launch date." Slightly more formal is "I'm happy to go with that, provided that Finance approves the budget." More formal still, for example in a negotiation or a formal email, is "We could agree to that on condition that the supplier guarantees the delivery dates." Another option is "In principle I agree, but …": you say yes to the idea and immediately put the missing point on the table — "In principle I agree, but we'd need a second supplier as a backup." Watch the tense with these conjunctions. When the condition refers to the future, the verb after as long as, provided that and on condition that normally stays in the present simple, even though the event still lies ahead: "as long as the supplier delivers by May", "provided that Finance approves the budget". One practical point as well: name one or two concrete conditions that can be checked. A yes with five conditions can easily sound like a hidden no, and a vague condition such as "as long as everything goes well" helps nobody. A good condition is one you can tick off later: the budget is approved, the date is fixed, the supplier has confirmed.
04 / 06
Holding back: "not yet" as a real answer
Sometimes you cannot decide yet, because figures are missing, because your team needs a say, or because the proposal has come too fast. In that case "not yet" is a full answer, provided that the room learns what you are waiting for. The basic form is "Could we come back to this once we have the figures?" "Once" means "as soon as" here and ties the delay to a clear point in time. If you need to consult someone first, say "I'd need to check with my team first." Watch the preposition: "check with" for people and departments — "check with my team", "check with Legal". German "bei meinem Team nachfragen" easily leads to "check by" or "check at", and neither works here. Other options are "Before we decide, could we see the cost breakdown?" and "Can we put this on the agenda for next week's meeting?" What matters is that your "not yet" stays concrete. Say what is missing and, if possible, when you will get back to the room: "Let me look at the figures, and I'll come back to you by Thursday." A vague "Let me think about it" with no time attached gives the room no next step and can come across as a hidden no. And if you already know that you want to decline, holding back achieves little: the question simply returns at the next meeting. In that case the fourth move is more honest.
05 / 06
Declining with a counter-proposal: reservation, reason, alternative
A no is perfectly legitimate in a meeting; what matters is how it lands. A useful sequence has three steps. First, signal a reservation: "I'm not sure that would work for us" or "I have some concerns about the timeline". The room now knows a no is coming, but the door has not slammed. Then give one concrete reason, most simply with "because": "because the budget for this year is fixed", "because the team is fully booked until June", "because switching suppliers mid-project adds risk". One clear reason usually persuades more than a long list. Finally, put an alternative on the table; "What if we … instead?" is made for this: "What if we start with one region instead?", "What if we keep the current supplier until the contract ends?" After "What if we", the base form of the verb is the usual choice. The past form — "What if we started with one region?" — is also possible and sounds a little more tentative. For more ways to phrase the counter-proposal, see the Making Suggestions lesson. The counter-proposal does not have to be perfect. It shows that you care about the shared goal even if you do not like the route, and it gives the person who made the proposal something to respond to. That turns a no into a fresh start for the discussion.
06 / 06
The German trap: word-for-word refusals
When you turn down a proposal in English, a direct translation is tempting: "Das ist keine gute Idee" becomes "That is not a good idea.", "Das macht keinen Sinn" becomes "That makes no sense.", and "Nein, das funktioniert nicht" becomes "No, that doesn't work." These sentences are grammatically correct English. In an English business meeting, though, they sound blunt, because they deliver a verdict with no reservation, no reason and no alternative. The person who made the proposal can easily hear a judgement on their work rather than on the plan, and the discussion stalls. The fix is not more complicated vocabulary but the sequence from this lesson. "That is not a good idea." becomes "I'm not sure that would work for us, because the budget is fixed. What if we start with one region instead?" If the logic really is unclear to you, "That makes no sense." becomes a question: "I'm not sure I follow. Could you walk us through the numbers?" And "No, that doesn't work." becomes "I'm not sure that would work for us, because the team is fully booked until June." Direct sentences do have their place, for example in a quick exchange between colleagues who know each other well. But when a proposal is on the table in a meeting, reservation, reason and alternative are the safer choice. A good test before you speak: after your sentence, does the room know how things can move on? If not, the reason or the alternative is usually what is missing.