How to propose a change at work in English (C1 advanced): calibrated predictions, an audited pilot and expansion conditions

A persuasive change proposal does not promise that the change will work. It shows where the problem lies, grades each prediction (“Delegation is likely to reduce waiting time, but it could produce inconsistent risk judgements.”), limits the test and names the evidence that will decide whether to expand. Speed alone is never that evidence. This C1 (advanced) topic is for managers and analysts who present change to a committee, then put it in writing. Fifteen minutes a day is enough.

Who this is for

Managers and team leads who need approval to change a process, a structure or who makes which decisions.
Analysts, operations and transformation leads who present a pilot to a committee and then send the written version.
Anyone who has heard “But how do you know it will work?” and wants an answer that is confident without overclaiming.
Too early: if a clear project update in English still takes effort, start with the B2 topic on updating someone who missed a meeting.
Too easy: if you already grade predictions and evidence naturally, move on to an incident record where this, that and it point to one clear thing.

Open the sample pages

Word cards

effective / efficient

adjective contrast. producing the intended result versus doing so with little wasted time or effort

The control is effective; the nine-minute review is efficient.

transform / transfer

verb contrast. change completely versus move from one person or place to another

The plan transforms the workflow and transfers low-risk authority.

robust

adjective. strong and reliable

A robust strategy combines audit data and staff interviews.

metrics

plural noun. statistics used to measure performance

The pilot uses speed, reversals and completeness as metrics.

hard data

uncountable noun phrase. information based on figures and measurements

Approval times provide hard data.

soft data

uncountable noun phrase. information based on opinions and experience

Reviewer interviews provide soft data.

cross-check

verb. verify by comparing sources

Owen cross-checks the dashboard against sampled files.

perspectives

plural noun. points of view

The review includes regional and central perspectives.

Conversation

Maya Today I’ll explain why we propose a six-week autonomy pilot in two regions.

Owen I understand the delay problem, but how will local teams interpret risk consistently?

Maya That concern is valid. We’ll standardize evidence fields and audit ten decisions each week.

Owen The pilot might reduce delay, but it could expose training gaps.

Maya Exactly. By the end, we will have compared speed, reversals and audit quality before deciding whether to expand.

Language pattern

will

future form. prediction based on experience, future information, promise, request or spontaneous decision

The audit found a gap, so I'll observe the next ten decisions.

going to

future form. prediction from present evidence or a prior plan/decision

The missing fields show the team is going to need coaching.

may / might / could / will

modal certainty scale. express open possibility through a direct prediction

The pilot might reduce delay and will expose the current baseline.

probably / perhaps / almost certainly

prediction adverbs. calibrate likelihood and normally sit with will in different positions

The pilot will probably improve speed but almost certainly won't remove every error.

likely / expected / certain / bound to

prediction adjectives. combine with be + to-infinitive to grade certainty

Experienced teams are likely to adopt first; removing support is bound to increase risk.

future continuous

future aspect. show an activity in progress at a particular future time

At Friday's review, auditors will be examining the tenth file.

future perfect

future aspect. show completion before a future point

By mid-June, the pilot will have processed six hundred requests.

future perfect continuous

future aspect. emphasize duration continuing to a future point

By mid-June, both regions will have been testing delegation for six weeks.

More practice

Analyse the case

Maya and Owen review the case documents at a desk.

Routine purchasing requests require three central approvals even when the value is below €2,000. Median approval time is 36 hours, although reviewers spend an average of nine minutes on each file. Two experienced regional teams propose a six-week pilot with local approval, standard evidence fields and a central audit of ten decisions per week. The sample may not represent newer teams, and no baseline exists for reversal quality. Leaders need a formal proposal, presented to the committee and then circulated in writing, that explains the problem, acknowledges concerns and distinguishes likely benefits from uncertain effects.

Study and adapt the decision brief

Subject: Proposal — two-region delegated-approval pilot

This proposal requests approval for a six-week pilot of local purchasing decisions below €2,000. It covers the current delay, the proposed controls and the decision gates.

Routine requests currently require three central approvals. Median completion is 36 hours, although reviewers spend nine minutes on a file. Delegation is likely to reduce waiting time in experienced teams, but it could produce inconsistent risk judgements. The pilot therefore standardizes evidence fields and keeps a central audit of ten decisions each week.

Maya will train both regional teams and publish escalation rules before 3 May, when the pilot begins. Owen will establish baselines for approval time, reversals and missing evidence. By mid-June, the pilot will have processed approximately 600 requests. We will not generalize the result to newer teams until they have been studied separately.

We understand the concern that decentralization may weaken accountability. Every decision will retain a named owner and audit trail, and any file with a supplier-risk gap will go to central review. Please send control questions by Wednesday; the committee will decide on Friday.

Defend the recommendation

Maya Approval time fell, but two audited files lacked supplier-risk evidence.

Owen Speed alone cannot justify expansion. Was the gap caused by training or workflow?

Maya I’ll observe the next ten decisions and coach both reviewers.

Owen Expansion should wait until completeness meets the threshold.

Draft and revise the decision brief

Maya State the change proposal with calibrated certainty.

Owen Delegation is likely to reduce routine delay, but could expose training gaps, so two regions should test it.

Maya What controls the next decision?

Owen Weekly audits, reversal quality and missing-evidence rates through June.

Audit the final message

evidence

Every claim has an observable basis.

Name the sample, period or event.

boundary

Unknowns and excluded perspectives are visible.

State what the evidence cannot prove.

action

The request is proportionate to the evidence.

Use a pilot or gate when uncertainty matters.

ownership

Someone owns each next step and review.

Name the owner and deadline.

Learn this unit

How would you like to learn?

Have an account?

A free account opens one unit for good.

A change proposal in five lines

A manager proposes letting two regional teams approve routine purchases; a colleague raises the obvious risk. The reply accepts the concern and adds a control.

Listen: how long and how wide is the pilot, and what will be compared before expansion? (Six weeks, two regions; speed, reversed decisions and audit quality.)

Maya Today I’ll explain why we propose a six-week autonomy pilot in two regions.

Owen I understand the delay problem, but how will local teams interpret risk consistently?

Maya That concern is valid. We’ll standardize evidence fields and audit ten decisions each week.

Owen The pilot might reduce delay, but it could expose training gaps.

Maya Exactly. By the end, we will have compared speed, reversals and audit quality before deciding whether to expand.

Speculating responsibly: certainty and future forms

Nobody knows yet how a change will play out, so grade every prediction. Might and could mark open possibilities; be likely, certain or bound (+ to-infinitive) climb towards certainty. Probably and almost certainly go after will but before won’t.

Going to predicts from visible evidence; perfect forms tie the pilot to dates.

“The pilot will probably improve speed but almost certainly won’t remove every error.”
“Experienced teams are likely to adopt first; removing support is bound to increase risk.” (probable versus near-certain)
“The missing fields show the team is going to need coaching.” (visible evidence)
“By mid-June, the pilot will have processed six hundred requests.” (complete by a deadline)
“By mid-June, both regions will have been testing delegation for six weeks.” (duration up to that point)

Separate speed from success: the language of evidence

If approvals take 36 hours but reviewers spend nine minutes per file, the delay is waiting time, not review effort: delegation can shorten the queue, but that does not prove decisions stay sound. Hard data comes from figures, soft data from opinions; a robust case cross-checks both.

“Approval times provide hard data; reviewer interviews provide soft data.”
“The control is effective; the nine-minute review is efficient.” (the right result versus little wasted effort)
“The plan transforms the workflow and transfers low-risk authority.” (change completely versus move to someone else)

Acknowledge the concern before you advise

Show you understand the reasoning first; acknowledging is not agreeing. Then offer a proportionate solution, tentatively, and hold your position if the evidence supports it.

“I can see where you’re coming from; speed alone is not enough.”
“It might be worth agreeing one definition before Friday.”
“Have you tried pairing each new reviewer with a central auditor?”
“I still think you should cross-check five files from each region.”

Learn this unit your way

Present it, then write it: 170–200 words in six moves

In the meeting, define terms and flag your main point: “By delegated approval, I mean local decisions below two thousand euros.” “And this is my key point: expansion depends on completeness, not speed alone.” Then circulate the written version.

Request: “This proposal requests approval for a six-week pilot of local purchasing decisions below €2,000.”
Problem: waiting time versus review effort, in figures.
Prediction: one likely benefit, one uncertain effect.
Controls and owners, with a start date.
Limit: “The sample may not represent newer teams.”
Gate and response: “We will decide on expansion only when audited completeness meets the threshold. Please comment by Friday.”

Common mistakes

These make a proposal sound overconfident or imprecise:

“The pilot will reduce delay.” as a bare promise. Say “is likely to reduce”.
“The pilot won’t probably remove every error.” Say “probably won’t”.
“By June, we will process six hundred requests.” For completion by a deadline: “will have processed”.
“More effective” when you mean faster. Faster means more efficient.
“Approval time fell, so we should expand.” One metric is not success.

A 15-minute daily practice routine

Use a change you would like to make at work.

3 minutes: make three predictions about it, with might, likely to and will have.
7 minutes: draft a 170–200-word proposal in six moves.
3 minutes: argue aloud: are flatter organizations better for employees, or just cheaper? Start with “I can see where you’re coming from, but …”.
2 minutes: shadow the exchange line by line.

What comes next

Next: an incident record where this, that and it point to one clear thing, then recording a disagreement between teams with emphasis, not blame.

Frequently asked questions

How do you write a change proposal in English?

Open with the request and scope, then the problem in figures, a graded prediction, controls and owners, the limits of the evidence and the condition for expanding, in 170–200 words.

What is the difference between “likely to” and “bound to”?

“Likely to” means probable: “Experienced teams are likely to adopt first.” “Bound to” means almost certain: “Removing support is bound to increase risk.” Use it only when little doubt remains.

What is the difference between “effective” and “efficient”?

“Effective” means producing the intended result; “efficient” means doing so with little wasted time or effort. A nine-minute review can be efficient yet still miss supplier risk.