How to Negotiate a Small Change in Plans in Your Target Language

The four jobs: CHANGE → REASON → OPTION → CONFIRM

These are four jobs, not four mandatory sentences.

1. CHANGE: What single detail needs to move?
2. REASON: Does the other person need one useful reason?
3. OPTION: What workable alternative can they accept, reject or modify?
4. CONFIRM: What exactly is now agreed?

Example: you planned dinner for Friday at 7:00 at the same restaurant.

Possible response: “Could we make it 7:30 instead? My train gets in later than I expected. If that’s difficult, I can still do 7.”

If the other person agrees: “Great—Friday at 7:30, same restaurant.”

Notice what did not change: Friday, the restaurant, the activity and the people. Only the time moved.

First, decide what stays fixed

This is the part most phrase lists skip. Before you worry about politeness, separate the plan into stable details and the one detail you want to change.

If you change the day, time, place and activity in one breath, the other person has to rebuild the whole plan while also decoding your language. Sometimes that is genuinely necessary. But if only one thing is wrong, keep the other pieces visible.

This “one-variable” method is a practical FunFluen teaching frame, not an official linguistic rule. It fits a broader interaction skill described in the Council of Europe’s CEFR goal-oriented co-operation descriptors: learners develop from making and responding to suggestions toward explaining problems, comparing alternatives and checking mutual understanding.

Job 1: make the change visible

The request should not be hidden inside an apology maze.

Buried: “I’m really sorry, and I know we arranged this already, and I feel bad because you planned around it, but there’s something with my train and I was wondering…”

Visible: “Could we make it 7:30 instead?”

You can still be warm. The point is simply that the listener should know what decision you are asking them to make.

The British Council’s Changing a meeting time lesson models exactly this kind of concrete interaction: an existing meeting time becomes a problem, one speaker asks whether it can be moved, alternatives are considered, a brief reason is given and the updated arrangement is confirmed.

Repair common learner responses

Job 2: give the reason that helps them decide

You do not owe the other person your autobiography.

A reason is useful when it explains the constraint:

• “My train gets in at 7:10.”
• “I have another meeting until 3.”
• “I can stay for an hour, but not two.”
• “It looks like it’s going to rain, so could we meet somewhere indoors?”

You can also keep a private reason private:

• “Something has come up. Could we move it to tomorrow?”
• “I have a conflict at that time. Would 4:30 work?”

That is not evasive if the missing detail is irrelevant to the other person’s decision. A useful question is: Does this detail help them evaluate the change? If not, you probably do not need it.

Job 3: give the conversation somewhere to go

A request is easier to negotiate when the other person can accept it, reject it or modify it.

You can offer one option:

• “Could we make it Sunday morning instead?”
• “Could we meet at the café next to the station?”
• “Could we keep tomorrow but make it a one-hour session?”

Or invite theirs:

• “If 7:30 doesn’t work, what time would be easier for you?”
• “I need somewhere indoors. Is there another place you’d prefer?”

Do not machine-gun five alternatives at someone to prove you are flexible. One workable option is usually enough to start the next turn.

What if they hesitate or say no?

A rejected change is not the same as a failed relationship. It means one version of the edit does not work.

Suppose you ask: “Could we make it 7:30 instead?”

They answer: “I can’t—I need to leave by 8.”

You now have three sensible moves:

1. Keep the original: “No problem. Let’s keep 7, then.”
2. Change a different variable: “Would it help if we met somewhere closer to the station?”
3. Ask which constraint is flexible: “Got it. Is another day easier, or should we keep tonight at 7?”

What not to do: repeat the same request with more emotional pressure—“Are you sure? Please? It would really help me…”—unless new information genuinely changes the decision.

When you are not sure what their “maybe” means

Do not pretend the agreement exists.

“I think 7:30 should be fine” is not the same as “7:30 is confirmed.” You can say:

• “No problem—could you let me know once you’re sure?”
• “Should we keep 7 for now and change it only if you confirm?”

This prevents optimism from quietly turning into a fake commitment.

Recovery: “Wait—are we cancelling?”

This is where the stable details become useful.

If the listener misunderstands the size of the change, do not repeat the entire story. State what stays the same and what changes:

“No, we’re still meeting Friday at the same restaurant. I’m only asking to move the time from 7 to 7:30.”

Or:

“Same study session tomorrow—just one hour instead of two.”

That sentence repairs the misunderstanding while making the size of the proposed change explicit.

Job 4: confirm the edited plan

The conversation is not finished when everybody sounds friendly. It is finished when both people can describe the new plan the same way.

Close with the details that changed and any detail that could still be confused:

• “Great—Friday at 7:30, same restaurant.”
• “Perfect. Sunday morning at 10 instead of Saturday.”
• “Thanks. Tomorrow at the library, but just for one hour.”

Two people can be extremely polite and still arrive at different times. Confirmation is less glamorous than politeness, but it has the useful habit of getting everyone to the same place.

Practice: the One-Variable Switchboard

For each situation, do not open the model immediately. First say aloud:

1. What stays fixed?
2. What single detail changes?
3. Your request.
4. A short reason only if useful.
5. One option or question.

Scenario A: the delayed train

Plan: Friday dinner, same restaurant. Original time: 7:00. Your train now arrives at 7:10.

Scenario B: shorten the study session

Plan: tomorrow at the same library. You originally agreed to two hours; you can now stay for one.

Scenario C: rain changes the place

Plan: same time and people. A park walk no longer works because of heavy rain.

Scenario D: your first alternative is rejected

You ask for 7:30. The other person says they must leave by 8.

Micro-challenge: make the edit before the explanation

Choose one real plan you could plausibly change. In your target language, say the change in one short sentence before adding any reason.

For example: “Could we meet half an hour later?”

The goal is not to win a word-count contest. It is to discover whether your actual request is visible. If your explanation arrives before the listener knows what you want, shorten the runway.

Do not translate these English examples word for word

The interaction jobs transfer better than the exact phrases do. Different languages—and different relationships inside the same language—handle requests, reasons, honorifics, softening, pronouns and directness differently.

So learn this sequence as meaning:

small change → useful context → workable option → confirmed agreement

Then learn how your actual target language performs those jobs in the register you need.

Turn the pattern into spoken reflex

Reading the method is the easy part. The harder moment is when the other person suddenly says, “7:30 doesn’t work,” and your prepared sentence has just died in public.

That is where variation helps: keep the communication job stable while changing the time, place, reason or response.

If English is your target language, you can practise changing one detail without rebuilding the whole conversation by choosing a speaking-practice path in FunFluen. Bring the CHANGE → REASON → OPTION → CONFIRM method with you and vary the scenario yourself. The destination provides general English speaking practice; this exact small-plan-change role-play is not preloaded, and FunFluen does not guarantee fluency.

The sentence to remember: edit, don’t reboot

A small plan change does not need a grand speech. Keep the parts that still work. Name the part that does not. Give the reason that helps. Offer a path forward. Then confirm what changed.

Next time 7:00 needs to become 7:30, you are not renegotiating the universe. You are editing one line.

Sources

• British Council LearnEnglish — Changing a meeting time
• Council of Europe — Common European Framework, goal-oriented co-operation descriptors