Pratique du Shadowing: How to Give a Clear Work Update in English | Business English Speaking Practice - Apprendre l'anglais à l'oral avec la vidéo

English for Work, Speak with Confidence.

Hello, everyone, and welcome back to Business English for Success.

I'm Elena.

Today, we're going to work on something that comes up constantly in professional life, giving a clear work update in English.

And I'm Mark.

This is one of those skills that can look very simple until someone actually asks you for an update.

Your manager says, where are we with this?

Or in a team meeting, someone says, can you give us a quick update?

And suddenly, you have to decide what to say.

You may need one in a weekly meeting, a manager check -in, when another department is waiting for your work, or when a deadline is getting close.

And one very common answer is, I'm working on it.

Which is not wrong.

No, but it doesn't tell me very much.

If I'm your manager and you say, I'm working on it, I may still be wondering what has actually been completed.

What is still happening?

Are we still on schedule?

Is anything holding the work up?

So the problem is not that the sentence is bad English.

The problem is that the update may not give the listener enough useful information.

But people can also go too far in the other direction.

Imagine I ask, Mark, where are we with the client report?

And you say, well, on Monday, I reviewed two versions of the document, checked the comments, followed up with the team, and updated my notes.

And I'm still waiting to hear where the report actually stands.

All of those activities may be real, but a work update is not a diary of everything you did.

That's one of the most important ideas in this lesson.

A useful update is not everything you know about the work.

It is the information the other person needs to understand the situation now.

That matters because other people may be planning their own work or making decisions based on your update.

So today, we'll build a clear work update step -by -step.

We'll cover status, real progress, unfinished work, timing, delays and dependencies, and what happens next.

And later, we'll put everything together in complete work updates and realistic workplace conversations.

The goal is not to give you one long script to memorize.

It's to help you choose the information and English that fit the situation.

So let's say someone asks you for an update right now.

Where should you begin?

Start with the clearest thing they need to know.

Where does the work stand?

Okay, so my manager asks, where are we with the report?

What should I say first?

Usually start with the current picture.

Don't make the listener wait through a long history before they understand the status.

For example, if everything is moving normally, you might say, we're on track, or things are moving as planned, or we're making good progress.

Those all sound positive, but do they mean exactly the same thing?

Not exactly.

If I say we're on track, I'm usually saying that the work is progressing as expected and the plan still looks realistic.

So I might say we're on track for Friday.

Ah, okay.

So if Friday is our deadline, I'm telling you that Friday still looks realistic.

But if I say we're making good progress, I'm telling you that the work is moving forward well.

That sentence by itself does not necessarily tell you whether a particular deadline is confirmed.

So if someone asks, how's the new website going?

I could say, we're making good progress.

The main pages are finished, and the team is polishing the remaining details.

That sounds natural.

Now, maybe the work is almost finished.

Then you might say, we're almost done.

Or, we're in the final stage now.

Or, we're just finishing the last few items.

I like we're almost done, because it's very easy.

And very natural.

You don't always need business vocabulary to sound professional.

Sometimes, simple English is exactly what people use at work.

Would we're in the final stage now sound a little more neutral?

Yes.

For example, we're in the final stage now, the content is finished, and we're doing the final review.

That works well when you want to give a slightly more structured update.

And if the work is completely finished?

Then say that clearly.

For example, the report is finished, or we've completed the testing.

But sometimes you can give the listener more useful information by telling them what the finished work is ready for.

For example, the report is ready for review.

That is more useful than simply saying, the report is finished, because now I know what can happen next.

Compare these two.

The presentation is finished, and the presentation is ready to send to the client.

Both are clear, but the second one gives me a more useful picture of the current stage.

What if the work is not finished and it's still happening normally?

Then you can say, it's still in progress, or we're still working through the final changes, or the team is reviewing the last few items now.

So, if someone asks me, is the analysis finished?

I could say, not yet, it's still in progress, we're checking the final numbers now.

And now we know two things, it isn't finished yet, but we also know what is happening.

What if nothing is happening because we're waiting for another person?

Then the current status may simply be, we're waiting for final approval, or it's currently with legal for review.

And waiting does not automatically mean there is a problem.

Sometimes waiting is simply the normal stage of the process.

It's currently with legal for review can just tell people where the work is.

So, maybe we can think of this first part of an update as the headline.

That's a good way to think about it.

Before you add the details, give people a clear picture of where the work stands.

Let's try a few quick examples.

All right, here's the first one.

You have finished the first draft of a report, but your manager has not reviewed it yet.

What could you say?

You could say, the first draft is finished and ready for review.

Simple and clear next one your team is testing a new system everything is going normally

and Friday is still a realistic completion date you could say we're on track for Friday and

if you want to add a little more we're on track

for Friday the team is testing the final version now

so already instead of starting every update with I'm working on

it we have several ways to show the real situation but

100

if I tell you we're on track you may still have another question i probably do

101

so what has actually happened and

102

that is the next part of a useful update showing real

103

progress this is where i think a lot of people get stuck they know they've been working hard

104

but they're not sure how to turn that into a useful update

105

and a useful question to ask yourself is what is different now compared with the last update

106

because being busy

107

and making visible progress are not always the same thing let

108

me give you an example imagine someone asks how's the budget review going

109

and i say i reviewed two versions of the document checked the comments

110

and followed up with the team all of that may be true

111

but i still don't know what changed

112

so maybe the stronger update is we've agreed the final wording and sent the document for approval.

113

Now I can see the result of the work.

114

You don't have to report every activity that led to that result.

115

So when I prepare an update, instead of asking, what did I do, I can ask, what progress can I point to?

116

And that progress can look different depending on the work.

117

Sometimes you have completed one clear piece.

118

You might say, we've completed the supplier comparison i've finished the first draft

119

or we've sent the revised proposal to the client those are easy

120

because there is a clear completed action sometimes the progress is

121

a milestone for example the first phase is complete the new system is now live

122

or we've now interviewed all six candidates

123

and sometimes only part of the work is finished then you can be more specific For example, we've completed four of the six storage areas.

124

We're about halfway through the review, or most of the content is now finished.

125

Those are useful because they show how far the work has progressed without pretending it is complete.

126

And not every job gives you a perfect number or percentage.

127

You may not always be able to say, we're 70 % finished.

128

Especially because in many jobs, nobody actually knows whether something is exactly 70 % finished.

129

So you can also say, we've made good progress on the redesign, we've resolved the main technical issue, or we've made progress but there's still more to do.

130

The same idea works across different jobs.

131

In sales, we've sent the revised proposals to all three clients.

132

In operations, we've cleared most of yesterday's backlog.

133

The job changes, but the principle is the same.

134

Show the listener what progress has actually happened.

135

And usually, one or two useful pieces of progress are enough.

136

You don't need to prove how busy you were by listing everything.

137

Let's practice that.

138

Imagine you are helping with an inventory count.

139

There are six storage areas to check.

140

Four areas are finished.

141

How could you report the progress?

142

A simple answer is, we've completed four of the six storage areas.

143

Now, we know what has moved, but as the listener, I immediately wonder, what about the other two areas?

144

So we can add one more useful detail.

145

We've completed four of the six storage areas, and the remaining two are scheduled for Toirot.

146

Yeah, that already sounds like a real update.

147

It does.

148

And notice that we did not make the English complicated.

149

We simply selected information that helps the listener understand the situation.

150

Now let's connect this back to the first part of the lesson.

151

Suppose someone asks, where are we with the inventory count?

152

You might begin with the headline, where on track?

153

Then add the progress, we've completed four of the six storage areas, and then add the next useful detail.

154

The remaining two areas are scheduled for tomorrow.

155

So your update becomes, we're on track, we've completed four of the six storage areas, and the remaining two are scheduled for tomorrow.

156

That is already much more useful than we're working on it.

157

And the important thing is that we built it step by step.

158

First, where does the work stand?

159

Then, what progress has actually happened?

160

But most work updates are not about something that is completely finished.

161

There is usually still something happening, something to review, something to confirm, something we are waiting for.

162

So in the next part, we'll look at how to talk clearly about the work that is not finished yet without sounding vague, negative, or uncertain when you don't need to.

163

But in real life, a lot of the time, the work is somewhere in the middle.

164

Some things are finished, some things are still happening, And sometimes you're waiting for something before you can move forward.

165

Unfinished work does not automatically mean there is a problem.

166

Sometimes the work simply isn't finished yet.

167

So the next useful question is, what is still happening?

168

Let's say most of my report is finished, but there is one final review before I can send it.

169

How could I say that?

170

You could say, the only thing left is the final review.

171

Or, we just need to complete the final review.

172

Both make it very clear that most of the work is already done.

173

I like the only thing left is the final review, because it immediately tells me that we're very close.

174

And if there are several small things to do, you might say, we still have a few changes to make,

175

or there are two items still outstanding.

176

Outstanding can be confusing, because people sometimes know that word as meaning excellent.

177

That's true.

178

But in this context, an outstanding item is simply something that has not been completed or resolved yet.

179

So, there are two items still outstanding means there are two things we still need to finish.

180

And that is probably enough explanation.

181

The important thing is knowing what the sentence lets you communicate at work.

182

Now, sometimes the unfinished work is actively happening.

183

For example, we're working through the final comments now.

184

The team is testing the new version.

185

Or, I'm making the final changes this morning.

186

So, instead of just saying, it's not finished, I can show what is happening now.

187

Compare, the report isn't finished yet, with, the report isn't finished yet, we're working through the final comments now.

188

The second answer gives the listener a much clearer picture.

189

What if the next step is not really in my hands?

190

For example, I've completed my part

191

but the client still needs to confirm the final wording then you can say

192

that directly we're waiting for the client to confirm the final wording

193

or procurement is confirming the revised unit price and

194

if there really is a problem I shouldn't make it sound completely normal just

195

because I want the update to sound positive right a professional

196

update should reflect the real situation we'll deal with actual risks

197

and delays in a moment what about explaining why something is unfinished, do I always need to give the reason?

198

No, only if the reason matters to the listener.

199

Imagine I ask, where are we with the presentation?

200

And you say, the main content is finished.

201

Design is polishing the final layout now.

202

That may be everything I need to know.

203

You don't need the whole history unless it changes the current situation.

204

So the question is still, what does the listener actually need? don't add detail just

205

because you learned another phrase use the language the situation actually

206

needs let's look at another example the report itself is finished

207

but it still needs final approval I could say the report is finished the only thing left is final approval

208

or if the normal process is that the director reviews it the report is finished

209

and is now with the director for final approval.

210

That sounds like a normal process.

211

Now compare that with we're still waiting for approval and it's starting to affect the schedule.

212

That is a different situation.

213

The first one simply describes where the work is.

214

The second one tells me the waiting is beginning to have a consequence.

215

Which we'll deal with later when we talk about risk and delay.

216

For now, there's one more question that often comes immediately after you explain what is unfinished.

217

I know the question.

218

When will it be ready?

219

And that is where a good work update requires more than just useful vocabulary.

220

You also need to be honest about how certain the timing really is.

221

I think this is one of the hardest parts of giving updates.

222

Sometimes people want a date even when you don't really have one yet.

223

And this is where your English needs to match the reality.

224

If the date is confirmed, you can sound definite.

225

If it is only your best estimate, your language should show that.

226

And if you genuinely cannot confirm the timing yet, you need a clear way to say that, too.

227

So let's start with the easy situation.

228

The date is confirmed.

229

If you know the work will be ready by Thursday, you can simply say, It'll be ready by Thursday.

230

Or, we'll send the final version on Thursday.

231

If the commitment is clear, your language can be clear, too.

232

What if Thursday looks very realistic, but there is still a little uncertainty?

233

Then you may hear, it should be ready by Thursday, or we expect to finish tomorrow.

234

You could also say, we're still on track to finish this week.

235

So those sound positive, but they don't sound exactly like a guarantee.

236

And that distinction matters.

237

For example, imagine the main work is finished, but one final review still has to happen.

238

You may genuinely expect Thursday, so it should be ready by Thursday may be more accurate than making an absolute commitment.

239

Then there's another situation.

240

Friday is our target, but we're not ready to say it is definitely going to happen.

241

Then you can say, we're aiming to finish by Friday, or we're targeting Friday afternoon.

242

That communicates the goal without presenting the goal as a confirmed result.

243

I think this is where people sometimes believe that sounding professional means sounding very certain.

244

And sometimes the professional thing is actually to be clear about uncertainty.

245

If you cannot confirm the date yet, you can say, I can't confirm the final date yet.

246

But it is often useful to add something more.

247

For example, I should have a clearer timeline tomorrow.

248

Or I can confirm the timing once we hear back from the supplier.

249

That second part is important, because if I only say, I don't know, the listener is left with nothing.

250

You may not have the final answer yet, but you can often tell them when you expect to know more.

251

For example, I can't give you a firm date yet.

252

I expect to know more tomorrow afternoon.

253

That is much more useful.

254

Let's take one question and see how the answer changes depending on the real situation.

255

Yeah, good idea.

256

The manager asks, will it be ready by Friday?

257

First situation, Friday is confirmed.

258

You could say, yes, we're on track to finish by Friday.

259

Second situation.

260

Friday is very likely, but there is still a final review.

261

Then, it should be ready by Friday.

262

Or, with a little context, it should be ready by Friday.

263

We just have the final review left.

264

Third situation.

265

You cannot confirm Friday because you're waiting for a supplier.

266

Then, don't pretend Friday is confirmed.

267

You might say, I can't confirm Friday yet.

268

I should know once the supplier responds this afternoon.

269

Same question.

270

Three different realities, three different answers.

271

And that is more important than trying to find one perfect sentence for, will it be ready by Friday?

272

What if the person asking really wants a yes or no?

273

You should still answer as clearly as the situation allows.

274

If it is yes, yes, we're on track for Friday.

275

If it is no, no, we won't be able to finish by Friday.

276

And if the reality genuinely is uncertain, Friday is still possible, but I can't confirm it yet.

277

That last one feels particularly useful.

278

It doesn't avoid the question.

279

You're answering the question and showing the real level of certainty.

280

Can we put this together with the language from the first part of the lesson?

281

Let's use a client presentation.

282

The main content is finished.

283

Design is polishing the final layout you expect the full presentation to be ready on Thursday, but you are not treating Thursday as an absolute guarantee yet.

284

You could say, the main content is finished, and design is working on the final slides now.

285

We expect to have the full presentation ready by Thursday.

286

That already gives me what is finished, what is happening now, and the expected timing.

287

And there is one principle I would remember from this section.

288

Don't make your English sound more certain than the situation really is.

289

If the date is confirmed, say it clearly.

290

If it is an expectation, say that.

291

If it is only a target, make that clear.

292

And if you genuinely cannot confirm the timing yet, tell people when you expect to know more.

293

Because a good update is not about sounding confident at any cost.

294

It's about giving people information they can actually rely on.

295

Now, sometimes timing is uncertain simply because the work is still in progress.

296

But sometimes there is a specific reason the plan may change.

297

Maybe you're waiting for approval.

298

Maybe another team is late.

299

Maybe a supplier hasn't delivered something.

300

Or maybe the deadline itself is now at risk.

301

And that is a different kind of update.

302

It is.

303

So next, we'll look at how to talk about a dependency, a risk, or a real delay clearly,

304

professionally, and without making the situation sound better or worse than it actually is.

305

Not every complication means the same thing.

306

Sometimes you have a dependency, sometimes there is a risk, and sometimes the delay has already happened.

307

Those are different situations, so your update should sound different too.

308

Let's start with a dependency.

309

What do we mean by that in a normal work situation?

310

A dependency simply means that one One part of the work cannot move forward until something else happens.

311

For example, we're waiting for legal to approve the final wording, or the next step depends on the test results,

312

or we're waiting on the supplier before we can confirm the delivery date.

313

Could I also say we're waiting on final approval?

314

That is common in workplace English.

315

For example, we finished our part, we're just waiting on final approval now.

316

That sounds natural in many professional conversations.

317

And if I want to make the connection even clearer?

318

You can show what happens after the dependency is resolved.

319

For example, we're waiting for legal to approve the final wording.

320

Once we have that, we can send the contract.

321

That already feels more useful, because now I know not only what we're waiting for, but also what it is holding up.

322

Now let's change the situation.

323

Suppose we're still waiting for the same approval, but the deadline is getting close.

324

That may no longer be just a normal dependency.

325

It may now create a risk.

326

So this is where I might say, there's a risk that we'll miss the deadline.

327

Or you could say, Friday may be difficult if we don't receive approval today.

328

Or the timeline is getting tight.

329

Or the final review may take longer than expected.

330

I think this distinction is important.

331

A risk is not the same as a confirmed delay.

332

If you say, there's a risk we'll finish late, you are saying the problem is possible.

333

You are not saying the deadline has already been missed.

334

So I shouldn't report a possible delay as if it has already happened.

335

But you also shouldn't hide the risk just because you hope it will disappear.

336

If the risk matters to the other person, they need to know about it.

337

Let's take a simple example.

338

The training pack is due Friday.

339

Most of the work is finished.

340

You're waiting for compliance to approve the final wording.

341

If compliance approves it today, Friday is still realistic.

342

How could I update my manager?

343

You could say, most of the training pack is finished.

344

We're waiting for compliance to approve the final wording.

345

If we get approval today, we should still be on track for Friday.

346

That sounds balanced.

347

I'm not saying everything is fine, but I'm also not saying we're definitely late.

348

Now, let's move to the third situation.

349

The delay is no longer a possibility.

350

It has actually happened.

351

Okay, so now I need to be more direct.

352

You might say, we're running two days behind, or the delivery has been delayed until Monday, or we won't be able to finish by Friday.

353

I think learners sometimes try to soften bad news so much that the real message disappears.

354

That can happen.

355

For example, if Friday is definitely no longer possible, saying, Friday might be a little difficult is too vague.

356

If the delay is confirmed, say it clearly, we won't be able to finish by Friday.

357

Then give the useful context.

358

So not just we're delayed.

359

For example, we're running two days behind because the final data arrived later than expected.

360

The analysis is continuing, and we now expect to finish on Monday.

361

That gives me the delay, the reason, the work that is still continuing, and the new expected date.

362

What if some of the work can continue, even though one part is blocked?

363

That is very common, and it is useful to say so.

364

For example, we're still waiting for approval, but we're continuing with the parts that don't depend on it.

365

Or, the final figures aren't confirmed yet, but we can continue preparing the rest of the report.

366

That sounds much more useful than simply, we're blocked.

367

Because we're blocked can make it sound like nothing is moving.

368

But sometimes one part is blocked and the rest of the work can continue.

369

Let's use a marketing example.

370

The design files are arriving one day later than expected, but the copy is already finished, and the team can continue building the other pages.

371

How would you update that?

372

You could say, the design files are arriving a day later than expected, but the copy is finished, and we're continuing with the other pages.

373

And if Friday is still possible, but it's getting tight.

374

Then you could add, Friday is still possible but the timeline is tight

375

so the full update might be the design files are arriving a day later than expected

376

but the copy is finished and we're continuing with the other pages Friday is still possible

377

but the timeline is tight

378

that is a realistic update it tells people what changed what is still moving

379

and what the current risk is what if we already know Friday is impossible.

380

Then change the language.

381

For example, the design files are arriving a day later than expected.

382

We're continuing with the other pages, but we won't be able to finish by Friday.

383

We're now aiming for Monday morning.

384

And that difference matters because people may need to respond differently.

385

A normal dependency may need no action.

386

A real risk may require people to prepare for a change.

387

A confirmed delay may force them to change a plan, move a meeting, or inform a client.

388

And that brings us to the next part.

389

A work update should not leave people thinking, okay, so what happens now?

390

I think this is where some updates just stop.

391

Someone says, we're waiting for approval.

392

And then, silence.

393

Sometimes that is enough.

394

But often, the listener also needs to know what happens next.

395

And there are a few common ways to make that clear.

396

Let's start with the easiest one.

397

I know what I'm going to do next.

398

Then say it.

399

For example, next I'll update the final figures, or I'll send the revised version this afternoon, or we'll start the final review tomorrow.

400

Very simple.

401

It should be.

402

The point isn't to make the ending sound impressive.

403

It's to remove uncertainty.

404

What if I can't do the next step until something else happens?

405

Then show that connection.

406

For example, once we have approval, we'll send it to the client.

407

Or, as soon as testing is complete, we'll move to the next phase.

408

Or, once finance confirms the figures, I'll update the report and send the final version.

409

That is useful because now I can see the sequence.

410

Sometimes the next useful thing is not another action.

411

It is another update.

412

For example, when I still don't know the final date.

413

Then you could say, I'll give you another update tomorrow morning.

414

Or, I should have a confirmed date this afternoon

415

or I'll let you know as soon as I hear back from the supplier

416

that last one is very common

417

and it gives the listener a clear expectation they know

418

when to expect more information what

419

if I actually need something from the person I'm updating then you can make

420

that clear too for example the only thing we need now is final approval

421

or I just need confirmation on the budget before we move forward

422

or if you can approve the revised version today we can send it to a client tomorrow.

423

But we don't want to turn this into a whole lesson on making requests.

424

We only need enough language to complete the update.

425

If the listener needs to do something, say what you need clearly.

426

If they don't, don't add a request just because you learned one.

427

But if the situation is less clear, the next step becomes more useful.

428

For example, we're waiting for the supplier to confirm the delivery date.

429

I should hear back this afternoon, and I'll update the schedule as soon as I have confirmation.

430

Now the listener knows what we're waiting for, when we expect more information, and what we'll do next.

431

Now that we have the pieces, let's put them together and see how the shape of a complete update changes with the situation.

432

Let's start with the easiest situation.

433

Nothing is wrong.

434

The work is progressing normally.

435

Imagine your team is preparing a monthly performance report.

436

The deadline is Thursday.

437

The first draft is finished.

438

The team is checking the final figures now.

439

A natural update could be, we're on track for Thursday.

440

We've finished the first draft, and the team is reviewing the final figures now.

441

We expect to finish the review tomorrow and send the final version on Thursday.

442

Matt is very straightforward.

443

And that is exactly what it should be.

444

There is no need to create a problem just to make the update sound more complete.

445

So we don't need to add, there are no blockers.

446

Not unless someone needs to know that.

447

If everything is moving normally, just tell people what matters.

448

Now, let's make the situation even simpler.

449

The report is nearly done.

450

Then the update can be shorter.

451

For example, the report is almost finished, the analysis and recommendations are complete, and I'm making the final formatting changes now.

452

It should be ready for review this afternoon.

453

That's probably only 15 seconds.

454

And 15 seconds may be exactly right.

455

A simple situation does not need a 30 -second explanation.

456

So a longer update is not automatically a better update.

457

Definitely not.

458

The listener needs clarity, not length.

459

Now let's make the situation less certain.

460

Most of the hiring paperwork is finished, but you're waiting for the candidate to confirm the start date.

461

You could say, most of the hiring paperwork is finished.

462

We've prepared the offer and onboarding plan, but we're still waiting for the candidate to confirm the start date.

463

If we hear back today, I should be able to finalize the onboarding schedule tomorrow morning.

464

That update does something different.

465

It shows good progress, but the final timing depends on confirmation from someone else.

466

So the update changes because the reality changes.

467

Not because we are trying to use a different template.

468

Now let's take a more difficult situation.

469

The work is progressing, but Friday is starting to look tight.

470

Imagine the content is finished, but the design files are arriving later than expected.

471

You could say, we've made good progress, but Friday is looking tight.

472

The content is finished, but the final design files are arriving later than expected.

473

We're continuing with the sections we can complete now, and I should have a clearer timeline this afternoon.

474

That feels professional, because the risk is visible immediately.

475

The speaker does not hide it, but they also do not make the situation sound worse than it is.

476

They explain what is still moving, and when more information will be available.

477

Let me try a weaker version.

478

We have a problem with design, and I don't know if we can finish.

479

That tells me there is a problem, but it leaves several important questions unanswered.

480

What is already finished?

481

Can any work continue?

482

Is Friday impossible or only at risk?

483

And when will we know more?

484

So I don't necessarily need more words.

485

I need better information.

486

There is something interesting about those four updates.

487

They don't all have the same structure.

488

The first one included status, progress, and timing.

489

The second was much shorter because the work was almost complete.

490

The third needed a dependency and conditional timing.

491

And the fourth needed a risk, continued work, and a point when the timeline could be confirmed.

492

So if viewers remember one thing here, it should probably be, don't ask, how many parts should my update have?

493

Ask, what does this situation require?

494

That will help you sound much more natural.

495

Of course, there is one problem with prepared updates.

496

People respond to them.

497

Which is usually how conversations work.

498

Unfortunately.

499

So after you give an update, someone may ask, what's still outstanding?

500

Are we still on track?

501

What's causing the delay?

502

When will you know?

503

Or do you need anything from me?

504

And I think this is where some learners start repeating the whole update again.

505

But most of the time, you don't need to start from the beginning.

506

answer the question they just asked let's say i've already given my update then my manager asks

507

what's still outstanding you could simply say just the final approval everything else is complete

508

or we still have two comments to resolve

509

but the main work is finished short answer

510

because the question is specific next question are we still on track if the answer is yes yes Yes,

511

we're still expecting to finish on Friday.

512

If the deadline is possible but not confirmed, Friday is still possible but I can't confirm it yet.

513

And if the answer is no, no, we won't be able to finish by Friday.

514

We're now aiming for Monday.

515

Again, the answer follows the reality.

516

What if someone asks, what's causing the delay?

517

Then answer the cause directly.

518

For example, the final data came in later than expected.

519

Or, we've found an issue during testing that needs to be fixed before we release the new version.

520

I don't need to repeat the entire project history.

521

If they need more detail, they can ask.

522

This one comes up a lot.

523

When will you know?

524

And this is where giving a clear information point is useful.

525

For example, the supplier is due to respond by 3 this afternoon.

526

I should know after that.

527

Or, we have another test this morning.

528

I should have a clearer answer by lunchtime.

529

So even if I don't have the final answer, I can still give people something concrete.

530

Then your manager asks, do you need anything from me?

531

If you don't, not at the moment.

532

I'll let you know if that changes.

533

If you do, yes, I just need approval on the revised budget.

534

Or, if you can review the final version today, we can send it to the client tomorrow.

535

Again, answer the question.

536

Don't restart the update.

537

let's try one together listen to this update testing is complete

538

but final approval hasn't come through yet we expect it this afternoon now your manager asks

539

so can we launch tomorrow a useful answer might be

540

if approval comes through today tomorrow should still be possible i'll confirm as soon as we have it notice what

541

that answer does it does not say yes

542

when the answer is not fully confirmed but it also does not avoid the question the follow -up changes what information matters,

543

so answer that question instead of restarting the whole update.

544

So now we've reached an important point.

545

Giving the initial update is only part of the skill.

546

At work, your update often leads to another question.

547

And that question may change what you need to say next.

548

Which means a good update is not just a prepared speech.

549

It is the beginning of a conversation.

550

And that is what we'll do next.

551

We'll stop breaking the skill into separate pieces and listen to complete workplace conversations.

552

One will be a routine team update.

553

One will involve a dependency and uncertain timing.

554

And one will involve a situation where the deadline is genuinely at risk.

555

Listen to what information each person chooses, how the follow -up questions change the response, and how the conversation moves toward a clear next step.

556

Okay, next item.

557

Mark, can you give us a quick update on the onboarding materials?

558

Sure.

559

We're on track.

560

The main guide is finished, and we've updated the training checklist with the feedback from HR.

561

I'm making the final changes to the Welcome Pack today, so everything should be ready by Wednesday afternoon.

562

Great.

563

Will that give the regional teams enough time before Friday's onboarding session?

564

Yes.

565

If we send everything on Wednesday, they'll have Thursday to review it.

566

Perfect.

567

Please send me the final version as well. Will do.

568

Very simple.

569

There was no problem to explain, so the update did not invent one.

570

I gave the current status, the meaningful progress, and the expected timing.

571

Then your follow -up question only needed one short answer.

572

That is what a routine update often sounds like.

573

It does not need to be long to be useful.

574

Now, let's make the situation less certain.

575

This time, most of the work is complete, but one important piece is still outside the employee's control.

576

Listen to how the employee stays clear without promising a date that cannot yet be confirmed.

577

Do you have a minute?

578

Sure.

579

Where are we with the customer renewal report?

580

Most of it is finished.

581

The summary and risk notes are complete, and I've updated the renewal tracker.

582

We're still waiting for two account managers to confirm the final renewal dates before I can finalize the report.

583

Do you still think we can send it tomorrow?

584

Tomorrow is still possible, but I can't confirm it yet.

585

The two account managers said they expect to confirm the dates by 3 this afternoon.

586

If they do, I should be able to finish the report this evening.

587

And if those dates aren't confirmed today?

588

Then tomorrow morning would be difficult.

589

If the confirmations come through first thing tomorrow, I'd expect to send the report later in the day.

590

Okay.

591

When will you know for sure?

592

I should know by 4.

593

I'll send you an update as soon as I hear back from them.

594

Good.

595

No need to wait for our chuck -in tomorrow.

596

Just let me know once you have confirmation. Will do.

597

Notice that the employee never pretended to know more than she knew.

598

But she also didn't stop at, I'm waiting for the account managers.

599

She explained what was already finished, what the report depended on, what tomorrow depended on, and when the manager could expect a firmer answer.

600

That gives the manager something useful to plan around, even before the final timing is confirmed.

601

Now, let's take the most difficult situation.

602

The plan has changed, and there may be a real consequence.

603

This is where people sometimes make one of two mistakes.

604

They hide the problem for too long.

605

Or they make a possible problem sound like the whole project is falling apart.

606

In this conversation, listen for three things.

607

What has changed, what can still continue, and what the team knows about the deadline right now.

608

Before we move on, I need to flag a timing issue with the product launch materials.

609

Okay.

610

What's changed?

611

The copy and product information are finished, but the final images from the agency are arriving later than expected.

612

We were supposed to receive them this morning.

613

They're now expecting to send them tomorrow afternoon does

614

that put Friday's launch at risk yes it does Friday is possible

615

but the timeline is very tight now the team is continuing with the pages

616

that don't need the final images

617

so the rest of the work is still moving what can

618

we realistically finish today we can finish the product pages the email copy

619

and most of the campaign setup the home page will have to wait for the new images

620

And when can we make a decision about Friday?

621

The agency said they'll confirm the exact delivery time by 11 tomorrow.

622

Once we have that, we should know whether Friday is still realistic or whether we need to move the launch.

623

Alright.

624

Let's not change the launch date yet, but we should be ready for that possibility.

625

Agreed.

626

I'll keep the team working on everything we can complete today, and I'll update everyone after we hear from the agency tomorrow morning.

627

Good.

628

Please include sales in that update as well they'll need to know

629

if the date changes I will that update had more information

630

because the situation had more consequences

631

but notice what it did not do it did not blame

632

the agency for five minutes it did not say the launch was definitely delayed

633

when that had not been decided

634

and it did not pretend everything was fine the team now understands the risk what work can continue

635

when they'll know more and who may need to act

636

if the date changes

637

that is what makes the update useful now it's your turn

638

this time don't think about one of our examples think about

639

one real piece of work you're responsible for it could be

640

a report a customer request a hiring task a presentation a system change, an order, a project deliverable,

641

anything that is real for you.

642

And you do not need to tell us confidential information.

643

Just choose something you can safely describe in general terms.

644

We're going to build your update one piece at a time.

645

And remember, you may not need every piece.

646

Use only what fits your situation.

647

First, give the current picture and one useful piece of progress.

648

Where does the work stand right now and what has actually changed since the last update.

649

Choose one clear starting point and one piece of progress that matters.

650

For example, we're on track.

651

We finished the first draft.

652

But use the situation that is true for your work.

653

Now ask, is anything important still happening or waiting for someone else?

654

And what can you honestly say about timing?

655

You may have a confirmed date, an an expectation, a target, or no confirmed date yet.

656

For example, we're waiting for IT to confirm access.

657

It should be ready by Thursday.

658

If nothing important is still outstanding, skip that part.

659

Finally, is there a dependency, a risk, or a real delay the listener needs to know about?

660

If there is, say it clearly.

661

Then add the next step if it helps.

662

For example, Friday may be difficult if we don't receive the data today.

663

I'll give you another update tomorrow morning.

664

If there is no risk or dependency, don't invent one.

665

Now look at the pieces you chose.

666

You probably do not need every part.

667

Take the two, three, or four pieces that matter and put them together into one short update.

668

Try to say it out loud.

669

Don't worry about making it impressive.

670

Make it useful.

671

Here is one example.

672

Imagine you're coordinating an equipment order for your team.

673

You might say, we're on track to complete the equipment order this week.

674

We've received all three supplier quotes and compared the options.

675

We're just waiting for final budget approval.

676

Once that's confirmed, I'll place the order and send the delivery schedule to the team.

677

That update needed four pieces because there were four useful things to communicate.

678

Status, progress, one remaining dependency, and the next step.

679

But your update does not have to sound like that.

680

Imagine the situation is much simpler.

681

The inventory report is complete.

682

Your manager only needs to review it.

683

You could simply say, the inventory report is finished and ready for review.

684

I'll send it to you this afternoon?

685

That is also a complete professional work update.

686

The goal is not to make your answer longer.

687

The goal is to give people the information they need.

688

So the next time someone asks, where are we with this, you don't need to search your memory for one perfect business English sentence.

689

Start with the real situation.

690

Add the progress that matters, what is still happening, and what you can honestly say about timing.

691

If something is affecting the plan, make that clear then tell people what happens next

692

when they need to know sometimes that will take 20

693

or 30 seconds sometimes it will take two sentences

694

and sometimes one clear sentence is enough here's one thing you

695

can do after this lesson choose one real task from your work

696

and give yourself a 20 or 30 second update out loud And if you want to practice in the comments, write one short work update there.

697

You could tell us where the work stands, one useful piece of progress, and what happens next.

698

Just remember not to share confidential information about your company, clients, or co -workers.

699

Keep the details general if you need to.

700

You don't need complicated English to give a strong work update.

701

You need clear information and language that matches the real situation.

702

Thanks for joining us for this lesson.

703

We hope your next work update in English feels a little easier to give.

704

We'll see you in the next lesson.

705

Bye for now.

Qu'est-ce que la technique du Shadowing ?

Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.

Pratique du Shadowing: How to Give a Clear Work Update in English | Business English Speaking Practice - Apprendre l'anglais à l'oral avec la vidéo

À propos de cette leçon

Qu'est-ce que la technique du Shadowing ?