Listen to Real English at Work: Follow Polite Requests and Status Updates

Paul asks, “Emily, have you got a minute?” (00:00) Emily answers like a person who takes every word literally: “One minute exactly?” (00:03) “Should I start a timer?” (00:05) Paul turns the joke into the lesson: “I’m not asking for sixty seconds.” (00:09) “I’m asking, can we talk briefly?” (00:12)

This page goes with the episode and is written for B1 learners. The English in this conversation is not difficult word by word. The difficulty is what a polite sentence is doing in an office: asking for something now, asking for it today, or only mentioning it. The practice section below follows the video chapters, so you can pause at each scene.

Watch the episode: Listen to Real English at Work | Follow Polite Requests and Status Updates | Daily Life English on YouTube

Time: about 24 minutes to listen, and 35 to 40 minutes for the practice below.

Before you listen: think of a message you received at work or at school that sounded relaxed, such as “whenever you can” or “no rush.” Did you know by when it was needed? Write down what you did, then listen for the two short questions Paul and Emily use to find out.

How to use this page: listen once without stopping. Then read the key idea and the tables, and use the practice section for a second pass. The full transcript is at the bottom.

What You’ll Learn

• Why “soft” workplace English can hide a real deadline, and why you should not decide the deadline from one polite phrase
• Have you got a minute? as the opening of a short conversation, not a request for sixty seconds
• When you get a chance, could you…? and Could you take a look at…? as soft requests
• I’m still working on it. and I should have it by… for a status update with an expected time
• Do you need it by a certain time? to check the time, and Just to check, you’d like me to…? to check the scope
• How No rush, but… can still carry a real time boundary (before I leave at four)
• How to separate the urgent part of a task from the whole task (I’ll send page one first)
• Why one hedge is useful and five hedges make the listener “do detective work”
• A 60-to-120-second speaking task: accept a request, check the time, give your status, confirm the scope

Key Idea

Don’t guess the hidden meaning of a soft request. Hear what the sentence is doing, use the situation, and ask one short question when the answer would change what you do.

Paul says the first half of this in the first two minutes: “The skill is to notice the function.” (01:19) “Use the context and confirm instead of guessing.” (01:21) Later he adds the order: “Context first.” (03:36) “Then if timing matters, ask.” (03:38)

Step	What you do	Language from the episode
1. Hear the job	Decide what the sentence is for: opening a talk, asking, reporting, giving a time, checking	“Opening a short work conversation.” (06:10)
2. Use the situation	Look at what is happening around the phrase: a meeting at two-thirty, a call at three-fifteen	“Context first.” (03:36)
3. Check the missing piece	Ask about the time or the task if either could change your plan	Do you need it by a certain time? (03:53)
4. Say your plan	Tell the other person what you will do, and when	“Got it. I’ll send page one first.” (15:55)

Two warnings keep the method honest. “Soft does not automatically mean unimportant,” (03:20) “and polite does not automatically mean optional.” (03:23) But “we should not treat every soft request like an emergency.” (03:31)

Language from the Episode

Chunk	What it does	Example from the episode
Have you got a minute?	Opens a short conversation	“Often that opens a short conversation.” (04:27)
When you get a chance, could you…?	Softens a request	“That softens a request.” (04:41)
Could you take a look at…?	Asks someone to check or review something	“‘Take a look at’ can mean check, review, or examine something briefly.” (04:56)
I’m still working on it.	Says the task is not finished, but work continues	“It says the task is not finished yet, but work is continuing.” (05:09)
I should have it by three.	Gives an expected time	“That gives an expected time.” (05:18)
Do you need it by…?	Checks the deadline directly	“That checks the deadline directly.” (05:34)
Just to check, you’d like me to…?	Checks what the action is	“That is useful when the action itself is unclear.” (05:42)
No rush, but… before I leave at four.	Relaxed words with a real time boundary	“No rush sounds relaxed, but before I leave at four gives a real time boundary.” (14:55)
Got it. I’ll…	Closes the check with your plan	“Got it. I’ll look at it after I finish this email.” (04:01)

Soft does not mean slow

The office story in the episode shows the problem in one example. Emily asks, “When you get a chance, could you take a look at the last section?” (02:33) Paul hears “Okay, not urgent. I’ll do it tomorrow morning.” (02:47) But Emily is “planning to send the summary after my two-thirty meeting.” (02:56) Paul names the gap: “Your request is soft, but there is still a useful time boundary.” (03:03) Nobody was rude. The sentence simply did not carry the time.

Why should is not a promise

Emily gives a short rule for I should have it by three: “And ‘should’ here often expresses a reasonable expectation, not a perfect guarantee.” (05:19) Paul adds, “And the word ‘should’ leaves a little room for uncertainty.” (06:44) So the listener can still ask. If you need the work earlier, Emily gives the sentence: “I actually need to use it at three-thirty.” (07:00) “Is that possible?” (07:03)

Mistakes to Repair

The episode names these on purpose. Each repair adds the piece the listener was missing.

What goes wrong	Better	Why
“When you get a chance, do this now.” (12:25)	“Could you take a look at this now?” or “Could you check this before the meeting?” (12:36)	The words say “later” and the request says “now”; “say the timing clearly” (12:33)
“I’m working on it. Maybe later.” (12:10)	“I’m still working on it. I should have it by four.” (12:20)	“Communicatively weak if the other person needs timing.” (12:13)
“I should have it by three, definitely.” (12:51)	“I’ll have it by three” if you are certain; “I should have it by three” if you are estimating	“Don’t add definitely just to sound stronger.” (13:05)
“I think maybe I can possibly have it by three.” (13:09)	“I should have it by three.” (13:28)	“One hedge can be useful. Five hedges make the listener do detective work.” (13:22)
Check this. / When? / Not done. (13:40 to 13:57)	Could you take a look at this? / Do you need it by a certain time? / I’m still working on it. I should have it by three. (13:44 to 14:01)	The longer lines “add the missing relationship, timing, or status information.” (14:08)

Paul also warns about one phrase that learners over-read: “Sometimes learners hear, if possible, and think, oh, then the time does not matter.” (10:35) His advice is not a new rule: “The safest move is not to invent a rule.” (10:51)

Practice with the Episode

Pause the video at the timestamps below. Say your answers aloud before you check them.

1. Real English at Work: “Have You Got a Minute?”

Play 00:00 to 01:32.

1. Why does Emily ask about a timer?
2. What does Paul say he is really asking?
3. What does Emily say about the words and the job of the sentence?
4. Why does “when you get a chance” make Emily nervous?
5. What will the speakers practice today?
6. What is the skill, and what is the thing Emily does not want?

Answers

1. She takes “have you got a minute” literally: “One minute exactly? Should I start a timer?” (00:03)
2. “I’m asking, can we talk briefly?” (00:12)
3. “At work, the words can be simple.” (00:17) “But the job of the sentence is not always completely literal.” (00:20)
4. “If I hear soft language, I sometimes assume the task is low priority.” (00:48) Paul says that “can create a very real misunderstanding.” (00:52)
5. “We’ll practice hearing what the speaker needs, then checking the timing when the meaning is not clear.” (01:02)
6. “The skill is to notice the function. Use the context and confirm instead of guessing.” (01:19) Emily does not want a lesson in “guess your coworker’s secret meaning.” (01:26)

2. Workplace Scenario: Soft Requests and Timing

Play 01:32 to 03:41.

1. What is the office situation?
2. What does Paul understand from “Paul, have you got a minute?”
3. What does Paul think “when you get a chance” means?
4. What is Emily planning?
5. What is the “first key distinction”?
6. What is the opposite risk?

Answers

1. “We’ve just finished a team meeting, and you’re working on a short client summary.” (01:35) The first two sections are done, “but the last section still needs a careful review.” (01:49)
2. “You want a short conversation.” (02:25) He did not answer “yes, I possess a minute.” (02:19)
3. “Okay, not urgent. I’ll do it tomorrow morning.” (02:47)
4. “I’m planning to send the summary after my two-thirty meeting.” (02:56)
5. “Soft does not automatically mean unimportant, and polite does not automatically mean optional.” (03:20)
6. “We should not treat every soft request like an emergency.” (03:31) The answer is “Context first. Then if timing matters, ask.” (03:36)

3. Listen to a Natural Workplace Conversation

Play 03:41 to 04:18.

1. How does the conversation open?
2. What does Emily ask after “Yeah, of course”?
3. What does Paul give her?
4. What does Emily say she will do?
5. According to Paul, what does the listener not do?
6. Which question “is doing a lot of work”?

Answers

1. “Have you got a minute?” (03:45) “Sure. What’s up?” (03:46)
2. “Do you need it by a certain time?” (03:53)
3. “If you could send me your notes before two, that would help. I’ve got another meeting at two-thirty.” (03:55)
4. “Got it. I’ll look at it after I finish this email.” (04:01)
5. The listener “does not pretend to know the deadline.” (04:06) “The listener checks it.” (04:09)
6. “Do you need it by a certain time?” (04:13)

4. Key Workplace Phrases and Their Functions

Play 04:18 to 06:02.

1. What does Have you got a minute? often open? Name three things a coworker may want.
2. What does When you get a chance, could you…? suggest?
3. What can take a look at mean?
4. What does I’m still working on it tell the listener?
5. What does should mean in I should have it by three?
6. When is Just to check, you’d like me to…? useful, and what is Paul’s example?
7. What two outcomes can the check prevent?

Answers

1. “A short conversation.” (04:27) A coworker may be asking for “help, an opinion, an update, or simply a quick discussion.” (04:33)
2. “It often suggests you don’t need to stop this second, but the real timing still depends on context.” (04:43)
3. “Check, review, or examine something briefly.” (04:58)
4. “The task is not finished yet, but work is continuing.” (05:09)
5. “A reasonable expectation, not a perfect guarantee.” (05:21)
6. “When the action itself is unclear.” (05:42) The example is “Just to check, you’d like me to review the numbers. Not rewrite the whole section.” (05:45)
7. It saves “an hour of work nobody asked for” (05:55), or doing “ten minutes when an hour was actually needed.” (06:00)

5. Listening Practice: Identify the Meaning

Play 06:02 to 07:07.

1. What job does Have you got a minute? do?
2. What does I’m still working on it do?
3. What does Do you need it by two? do?
4. What should Emily not do when she hears When you get a chance, could you take a look at this?
5. What does I should have it by the end of the day give?
6. What can you say if someone says “four” and you need it at three-thirty?

Answers

1. “Opening a short work conversation.” (06:10)
2. It is a “status update. The task is not done yet.” (06:16)
3. “Timing check.” (06:21)
4. She “should not automatically decide the deadline from that phrase alone.” (06:27)
5. “Expected completion time.” (06:40)
6. “Okay, I actually need to use it at three-thirty. Is that possible?” (06:59) Emily calls it “clear, calm, specific.” (07:04)

6. Workplace Misunderstanding: “When You Get a Chance”

Play 07:07 to 09:03.

1. What does Paul say after “Sure, no problem”?
2. What happens at one-thirty?
3. What did Paul think the phrase meant?
4. What did Emily mean?
5. What is the repair, and what is it not?
6. What are the “two confirmations”?
7. What else can be fuzzy at work besides vocabulary?

Answers

1. “It does, but I still haven’t said when I’ll do it.” (07:26) Paul’s answer sounded fine, but it did not say when.
2. Emily asks, “Hey, did you get a chance to look at that section?” (07:34) Paul says, “Not yet, I was going to do it first thing tomorrow.” (07:39)
3. “I thought ‘when you get a chance’ meant tomorrow was fine.” (07:46)
4. “I meant there was no need to drop everything, but I do need it before my two-thirty meeting.” (07:54)
5. “The repair is to make the timing visible.” (08:12) It is not “you should have known.” (08:08)
6. “The time and the scope.” (08:37) Paul asks about the time (“before two”) and Emily adds “the last section only.” (08:26)
7. “Time, scope, priority, or what ‘done’ actually means.” (08:52)

7. Supported Role-Play: Reviewing a Work Task

Play 09:03 to 11:08.

1. What task does Paul get in the slide role-play?
2. What deadline does Emily give, and why?
3. What does Paul check about the action?
4. What does he promise?
5. Why does Emily call his answer “a strong B1 response”?
6. What is the “full meaning” of the first-page role-play?
7. What does Paul say about if possible?

Answers

1. Slide six: “the chart looks a little crowded.” (09:18)
2. “Before lunch would be great. I’m showing the slides at one.” (09:27)
3. “Just to check, you want me to simplify the chart. Not change the numbers, right?” (09:31) Emily answers, “The numbers are final.” (09:39)
4. “I should have it back to you by eleven-thirty.” (09:41)
5. “Because you didn’t just say yes. You checked the deadline and the action.” (09:46)
6. “Short conversation, soft request, deadline check, scope check.” (10:26)
7. It “can simply soften the request. It may express flexibility or politeness or both.” (10:42) Use the situation “and ask if you need certainty.” (10:56)

8. How to Give Clear Status Updates

Play 11:08 to 12:06.

1. Why does Emily say requests are “only half the conversation”?
2. What does I’m still working on it give?
3. How do you add timing?
4. What should you do if “three” becomes unlikely?
5. What does Paul answer to the new time?
6. What does Emily say English is for here?

Answers

1. “Requests are only half the conversation at work.” (11:12) The other half is saying where a task stands.
2. “Status.” Paul says, “maybe I also need timing.” (11:24)
3. “I should have it by three.” (11:28)
4. Update early: “I should update you before three if I can.” (11:35) Then give the new time: “It’s taking a little longer than I expected. I should have it by four.” (11:40)
5. “Thanks for the update. Do you think you can send the first section by three? I can start with that.” (11:46)
6. “We’re not using English to hide the problem. We’re using English to make the current situation usable.” (11:56)

9. Common Workplace Mistakes and Better Responses

Play 12:06 to 13:33.

1. What is weak about “I’m working on it. Maybe later.”?
2. What is wrong with “When you get a chance, do this now”?
3. What are the two good ways to say “three, definitely”?
4. What is “too much fog”?
5. What is the lesson about hedges?

Answers

1. It is “grammatically possible. Communicatively weak if the other person needs timing.” (12:13)
2. “That fights with itself.” (12:30) If it needs to happen now, “say the timing clearly.” (12:33)
3. If you are certain: “I’ll have it by three.” If you are estimating: “I should have it by three.” (12:56)
4. “I think maybe I can possibly have it by three.” (13:09)
5. “One hedge can be useful. Five hedges make the listener do detective work.” (13:22)

10. Upgrade Your Workplace English

Play 13:33 to 14:27.

1. What are the three upgrades?
2. Why are the upgrades longer?
3. When is the shortest line still the best?

Answers

1. “Check this” becomes “Could you take a look at this?” (13:44); “When?” becomes “Do you need it by a certain time?” (13:50); “Not done” becomes “I’m still working on it. I should have it by three.” (13:57)
2. “They add the missing relationship, timing, or status information.” (14:08)
3. When someone asks if you finished the notes: “Not yet. I’m still working on them.” (14:23)

11. Real Work Scenario: “No Rush” and Changing Deadlines

Play 14:27 to 16:33.

1. How is this scene different?
2. What does the team lead say?
3. What does “no rush” mean here?
4. What new information arrives?
5. How does Emily check it?
6. What does the lead say is important?
7. What is the “emotional change”?

Answers

1. Paul is now the team lead, and Emily is “responsible for updating a shared document.” (14:35) Emily says it is a “different relationship” with “more pressure.” (14:40)
2. “No rush, but it’d be helpful to have the revised summary before I leave at four.” (14:45)
3. Not “whenever.” It is closer to “you don’t need to interrupt everything this second, but before four would be useful.” (15:07)
4. “The finance team needs the first page for their call at three-fifteen.” (15:39)
5. “Okay, just to check, you need page one before three-fifteen, but the rest can come a little later?” (15:43)
6. “Page one is the important part for that call.” (15:52)
7. A soft request “can feel vague.” (16:19) After the check, “I need a clearer picture of the task.” (16:24) Paul sums it up: “Clearer picture, smaller action.” (16:29)

12. Pronunciation Practice: Chunking a Confirmation

Play 16:33 to 17:54.

1. Which sentence do they practice?
2. What are the three chunks?
3. Why use chunks?
4. What does each pause organize?
5. How strong should the pauses be?

Answers

1. “Just to check, you need this by two, right?” (16:37)
2. “Just to check” (16:48), “you need this by two” (16:52), and “right?” (17:00)
3. “Not every word separately.” (16:44)
4. “I’m checking. Here is the action and time. Please confirm.” (17:20)
5. “We don’t need to overdo the pauses. In natural speech, they may be very light.” (17:26)

13. Quick Listening and Response Check

Play 17:54 to 19:02.

1. What job does each of the five lines do, and what is a useful response?

Answers

1. Have you got a minute? “opens a short conversation”; reply “Sure. What’s up?” (18:07) When you get a chance, could you take a look at the budget notes? is a “soft request”; if timing matters, ask “Do you need them by a certain time?” (18:17) I’m still working on it. I should have it by five. is “status plus expected completion time.” (18:30) No rush, but I need the first page before my three o’clock call. has “a real deadline for one part”; reply “Got it. I’ll send page one first.” (18:40) Just to check, you’d like me to comment on the wording, not the numbers? is “scope confirmation.” (18:56)

14. Final Workplace Listening and Speaking Challenge

Play 19:02 to 22:21.

1. What does Emily say the challenge is for?
2. How many patterns should you try to use?
3. How does the sample conversation go step by step?
4. What happens when the scope changes?
5. How long should your own answer be?
6. How can you make it personal?
7. What should you do if your first try is vague?

Answers

1. “This is your chance to produce the skill. Not just recognize it.” (19:04)
2. “At least four.” (19:22) Emily adds, “You do not need to force every phrase in. Use the ones that fit.” (19:43)
3. Accept (“Sure. What’s up?”), ask the time (“Do you need it by a certain time?”), give status (“I’m still working on another task, but I should have comments for you by one-thirty”), confirm the scope, and give a plan (“I’ll review the paragraph and send it back by one-thirty”). (20:14 to 21:00)
4. “Actually, just the final paragraph is enough.” (20:33) Emily says, “This is new scope information.” (20:40) so she checks: “Just to check, you want comments on the wording in that paragraph, right?” (20:44)
5. “Between about 60 and 120 seconds.” (21:08)
6. “Replace the project notes with something real or familiar.” (21:24) The examples are slides, an email, a report, a schedule, a shared document, or classwork.
7. “Retry once. On the retry, add one timing question and one scope confirmation.” (21:37)

15. Recap: Requests, Timing, Status, and Scope

Play 22:21 to 23:47.

1. What is the answer to the question from the beginning?
2. What does each of the phrases do?
3. What is “the useful habit”?
4. What is the one line to try aloud?
5. What is the joke at the end?

Answers

1. “You listen for the function, use the situation, and make missing information visible with a short check.” (22:30)
2. Have you got a minute? “opens the conversation.” (22:38) When you get a chance, could you… “softens the request.” (22:44) I’m still working on it “gives status.” (22:45) I should have it by “gives an expected time.” (22:49) Do you need it by and Just to check, you’d like me to “help you confirm.” (22:56)
3. “Before you guess what a soft request means, check the part that could change what you do.” (23:05)
4. “Just to check, you need this by two, right?” (23:15) Then change the time to fit your own situation.
5. The next time a coworker says “have you got a minute?” Emily promises “not to start a sixty-second timer.” (23:39)

Your small action

Choose one real request you will send or receive this week and write the two checks for it before you need them: Do you need it by a certain time? and Just to check, you’d like me to ___, not ___, right? Make both lines true for your situation. Then say the second one aloud once, in three chunks, as in chapter 12.

Keep Practicing

Want a guide that does not need the episode? Try Soft Requests at Work in English: Check the Deadline Without Guessing. It turns the hear-it, check-it, say-it-back method into steps you can use on a real message, repairs five common sentences, and gives you drills with answers and a status update to say aloud.

Chapters

• 00:00 Real English at Work: “Have You Got a Minute?”
• 01:32 Workplace Scenario: Soft Requests and Timing
• 03:41 Listen to a Natural Workplace Conversation
• 04:18 Key Workplace Phrases and Their Functions
• 06:02 Listening Practice: Identify the Meaning
• 07:07 Workplace Misunderstanding: “When You Get a Chance”
• 09:03 Supported Role-Play: Reviewing a Work Task
• 11:08 How to Give Clear Status Updates
• 12:06 Common Workplace Mistakes and Better Responses
• 13:33 Upgrade Your Workplace English
• 14:27 Real Work Scenario: “No Rush” and Changing Deadlines
• 16:33 Pronunciation Practice: Chunking a Confirmation
• 17:54 Quick Listening and Response Check
• 19:02 Final Workplace Listening and Speaking Challenge
• 22:21 Recap: Requests, Timing, Status, and Scope

Full Transcript

Paul: Emily, have you got a minute?

Emily: Sure. One minute exactly? Should I start a timer?

Paul: And that is our first little workplace trap. I’m not asking for sixty seconds. I’m asking, “Can we talk briefly?”

Emily: Right. At work, the words can be simple, but the job of the sentence is not always completely literal.

Paul: Exactly. And here’s the harder one. Suppose I say, “When you get a chance, could you take a look at the last section?” Would you hear that as “tomorrow is fine,” or as “please do this soon, but you don’t have to stop everything right now”?

Emily: Hmm. That depends on the situation, and that’s where I can get nervous. If I hear soft language, I sometimes assume the task is low priority.

Paul: Which can create a very real misunderstanding. Today we’re listening to the kind of English coworkers use around requests, progress, and timing. We’ll practice hearing what the speaker needs, then checking the timing when the meaning is not clear.

Emily: So we’re not trying to read people’s minds.

Paul: No. That matters. Different workplaces and speakers use these phrases differently. The skill is to notice the function, use the context, and confirm instead of guessing.

Emily: Good. Because “guess your coworker’s secret meaning” is not a language lesson I want.

Paul: Same. Let’s put us in a normal office situation. We’ve just finished a team meeting, and you’re working on a short client summary.

Emily: I have the document open. The first two sections are done, but the last section still needs a careful review.

Paul: I walk past your desk and you say, “Paul, have you got a minute?”

Emily: And you say, “Sure, what’s up?”

Paul: That response already shows I understood the function. I didn’t answer, “Yes, I possess a minute.” I understood: you want a short conversation.

Emily: Then I say, “When you get a chance, could you take a look at the last section?”

Paul: I hear “when you get a chance,” and in my head I think, “Okay, not urgent. I’ll do it tomorrow morning.”

Emily: But I’m planning to send the summary after my two-thirty meeting.

Paul: There’s the gap. Your request is soft, but there is still a useful time boundary.

Emily: And I didn’t state it yet. So if you guess, you might guess wrong.

Paul: Right. This is the first key distinction: soft does not automatically mean unimportant, and polite does not automatically mean optional.

Emily: But the opposite is also true. We should not treat every soft request like an emergency.

Paul: Exactly. Context first. Then, if timing matters, ask.

Emily: Let’s hear the exchange naturally once.

Paul: “Have you got a minute?”

Emily: “Sure. What’s up?”

Paul: “When you get a chance, could you take a look at the last section?”

Emily: “Yeah, of course. Do you need it by a certain time?”

Paul: “If you could send me your notes before two, that would help. I’ve got another meeting at two-thirty.”

Emily: “Got it. I’ll look at it after I finish this email.”

Paul: That feels normal because the listener does not pretend to know the deadline. The listener checks it.

Emily: And notice how little English we needed. “Do you need it by a certain time?” is doing a lot of work.

Paul: Let’s pull out the language by function, not as a phrase list to memorize blindly. First, “Have you got a minute?” Often, that opens a short conversation.

Emily: It can be very casual. A coworker may be asking for help, an opinion, an update, or simply a quick discussion.

Paul: Second, “When you get a chance, could you…?” That softens a request. It often suggests, “You don’t need to stop this second,” but the real timing still depends on context.

Emily: Third, “Could you take a look at…?” Very common and useful. “Take a look at” can mean check, review, or examine something briefly.

Paul: Fourth, if you are the person giving an update, “I’m still working on it.”

Emily: I like that one because it is honest and simple. It says the task is not finished yet, but work is continuing.

Paul: Fifth, “I should have it by three.” That gives an expected time.

Emily: And “should” here often expresses a reasonable expectation, not a perfect guarantee.

Paul: Right. If the timing is critical, the other person can still confirm. Sixth, “Do you need it by…?” That checks the deadline directly.

Emily: And seventh, “Just to check, you’d like me to…?” That is useful when the action itself is unclear.

Paul: For example, “Just to check, you’d like me to review the numbers, not rewrite the whole section?”

Emily: That sentence saves me from doing an hour of work nobody asked for.

Paul: Or from doing ten minutes when an hour was actually needed.

Emily: Let me test my listening. You say a line, and I’ll tell you what job it is doing.

Paul: “Have you got a minute?”

Emily: Opening a short work conversation.

Paul: Good. “I’m still working on it.”

Emily: Status update. The task is not done yet.

Paul: “Do you need it by two?”

Emily: Timing check.

Paul: “When you get a chance, could you take a look at this?”

Emily: Soft request. And I should not automatically decide the deadline from that phrase alone.

Paul: Exactly. If you’re listening, try the next one before Emily answers. “I should have it by the end of the day.”

Emily: Expected completion time.

Paul: Yes. And the word “should” leaves a little room for uncertainty.

Emily: That detail matters at work. If somebody says, “I should have it by four,” and I absolutely need it at three-thirty, I should not smile and hope.

Paul: You can say, “Okay. I actually need to use it at three-thirty. Is that possible?”

Emily: Clear, calm, specific.

Paul: Now let’s return to our client summary, because the interesting part is what happens when neither person is being rude or careless.

Emily: I say, “When you get a chance, could you take a look at the last section?”

Paul: And I reply, “Sure, no problem.”

Emily: That sounds fine.

Paul: It does. But I still haven’t said when I’ll do it.

Emily: True. Then at one-thirty I ask, “Hey, did you get a chance to look at that section?”

Paul: And I say, “Not yet. I was going to do it first thing tomorrow.”

Emily: And now I’m surprised because I need my notes before two.

Paul: I say, “Oh, I thought ‘when you get a chance’ meant tomorrow was fine.”

Emily: And I say, “I can see why. I meant there was no need to drop everything, but I do need it before my two-thirty meeting.”

Paul: That is our turning point. The soft phrase did not carry enough timing information by itself.

Emily: So the repair is not, “You should have known.” The repair is to make the timing visible.

Paul: Exactly. I can say, “Just to check, you need me to review it before two, right?”

Emily: “Yes. The last section only. You don’t need to check the whole document.”

Paul: “Got it. I’ll do that next.”

Emily: Much better. And there are actually two confirmations there: the time and the scope.

Paul: That’s important. At work, misunderstandings are not always about vocabulary. Sometimes the sentence is perfectly clear grammatically, but the task boundary is fuzzy.

Emily: Time, scope, priority, or what “done” actually means.

Paul: Right. And you do not need a long formal sentence to fix that.

Emily: Let’s practice a short supported conversation. I’ll be your coworker. You’re editing slides for a team update.

Paul: I’m ready.

Emily: “Hey, have you got a minute?”

Paul: “Sure. What’s up?”

Emily: “When you get a chance, could you take a look at slide six? The chart looks a little crowded.”

Paul: “Of course. Do you need it by a certain time?”

Emily: “Before lunch would be great. I’m showing the slides at one.”

Paul: “Okay. Just to check, you want me to simplify the chart, not change the numbers, right?”

Emily: “Exactly. The numbers are final.”

Paul: “Got it. I should have it back to you by eleven-thirty.”

Emily: That is a strong B1 response because you didn’t just say yes. You checked the deadline and the action.

Paul: Now you try the same role. I’ll give you the coworker lines, and you can answer aloud if you want. “Hey, have you got a minute?”

Emily: A simple response could be, “Sure. What’s up?”

Paul: “When you get a chance, could you review the first page?”

Emily: You could say, “Sure. Do you need it by a certain time?”

Paul: “Before three, if possible.”

Emily: And you could confirm the task: “Just to check, you want feedback on the wording, right?”

Paul: Good. Passive listeners, stay with us. The full meaning is: short conversation, soft request, deadline check, scope check.

Emily: I want to add something small here. Sometimes learners hear “if possible” and think, “Oh, then the time does not matter.”

Paul: Yes, but that phrase can simply soften the request. It may express flexibility, or politeness, or both. The safest move is not to invent a rule. Use the surrounding situation and ask if you need certainty.

Emily: That’s the principle I want to remember: don’t turn one polite phrase into a universal priority code.

Paul: Nicely put.

Emily: Now can we look at status updates? Because requests are only half the conversation at work.

Paul: Absolutely. Suppose I ask, “How’s the report going?”

Emily: I could say, “I’m still working on it.”

Paul: That gives me status, but maybe I also need timing.

Emily: Then I can add, “I should have it by three.”

Paul: Good. What if three becomes unlikely?

Emily: I should update you before three if I can. Maybe: “I’m still working on it. It’s taking a little longer than I expected. I should have it by four.”

Paul: Clear. And I might respond, “Thanks for the update. Do you think you can send the first section by three? I can start with that.”

Emily: So we’re not using English to hide the problem. We’re using English to make the current situation usable.

Paul: Exactly. That is the communication skill.

Emily: Let me make a common mistake on purpose. “I’m working on it. Maybe later.”

Paul: Grammatically possible. Communicatively weak if the other person needs timing.

Emily: Better: “I’m still working on it. I should have it by four.”

Paul: Another one: “When you get a chance, do this now.”

Emily: That fights with itself. If it truly needs to happen now, say the timing clearly: “Could you take a look at this now?” or “Could you check this before the meeting?”

Paul: Right. Softness is fine. Hidden timing is the problem when timing matters.

Emily: Here’s another awkward one: “I should have it by three, definitely.”

Paul: If you are certain, “I’ll have it by three” is clearer. If you’re estimating, “I should have it by three” is honest. Don’t add “definitely” just to sound stronger.

Emily: And one more: “I think maybe I can possibly have it by three.”

Paul: Too much fog.

Emily: I knew you were going to say that.

Paul: One hedge can be useful. Five hedges make the listener do detective work.

Emily: Better: “I should have it by three.”

Paul: Exactly.

Emily: Can we upgrade a few short workplace lines without making them sound stiff?

Paul: Let’s do three. First: “Check this.”

Emily: Better: “Could you take a look at this?”

Paul: Second: “When?”

Emily: Better: “Do you need it by a certain time?”

Paul: Third: “Not done.”

Emily: Better: “I’m still working on it. I should have it by three.”

Paul: Notice the upgrades are not longer because longer is better. They are longer because they add the missing relationship, timing, or status information.

Emily: And sometimes the shortest line is still the best. If you ask, “Did you finish the notes?” I can simply say, “Not yet. I’m still working on them.”

Paul: Exactly.

Emily: Now I want a harder workplace scene.

Paul: All right. This time I’m your team lead, and we’ve just finished a short project check-in. You’re responsible for updating a shared document.

Emily: Different relationship, more pressure.

Paul: And we’re using chat as well as speech. I say, “No rush, but it’d be helpful to have the revised summary before I leave at four.”

Emily: Ooh. That sentence is interesting. “No rush” sounds relaxed, but “before I leave at four” gives a real time boundary.

Paul: Exactly. The meaning is not “whenever.” It is closer to “You don’t need to interrupt everything this second, but before four would be useful.”

Paul: Let’s make the scene more natural. I’ll play the team lead from the top.

Emily: Go for it.

Emily: “Sure. What’s up?”

Paul: “No rush, but it’d be helpful to have the revised summary before I leave at four.”

Emily: “Okay. I’m still working on the figures. I should have the full version by three-thirty.”

Paul: “That works. One more thing—the finance team needs the first page for their call at three-fifteen.”

Emily: “Okay, just to check, you need page one before three-fifteen, but the rest can come a little later?”

Paul: “Yes. Page one is the important part for that call.”

Emily: “Got it. I’ll send page one first.”

Paul: “Perfect. Thanks for checking.”

Emily: That feels very real to me because the language is soft, but the work is specific.

Paul: And the listener has to update the action, not just hear the words.

Emily: There’s also an emotional change. At the start, a soft request can feel vague. After the clarification, I don’t need more confidence in general. I need a clearer picture of the task.

Paul: Exactly. Clearer picture, smaller action.

Emily: I like that.

Paul: Now let’s work on one pronunciation line you can actually use. The sentence is: “Just to check, you need this by two, right?”

Emily: We’ll use chunking. Not every word separately.

Paul: First chunk: “Just to check…”

Emily: “Just to check…”

Paul: Second chunk: “you need this by two…”

Emily: “you need this by two…”

Paul: Final check: “right?”

Emily: “right?”

Paul: Now together: “Just to check, you need this by two, right?”

Emily: Again, naturally: “Just to check, you need this by two, right?”

Paul: The small pauses organize the meaning: I’m checking; here is the action and time; please confirm.

Emily: And we don’t need to overdo the pauses. In natural speech, they may be very light.

Paul: Let’s put it inside a mini-dialogue. “Could you send me your notes this afternoon?”

Emily: “Sure. Just to check, you need them by two, right?”

Paul: “Two would be great.”

Emily: Nice. The pronunciation supports the communication task.

Paul: Time for a quick listening-and-response check. I’ll say a workplace line. Decide what it is doing and what a useful response could be.

Emily: First one.

Paul: “Have you got a minute?”

Emily: It opens a short conversation. A natural response: “Sure. What’s up?”

Paul: Second: “When you get a chance, could you take a look at the budget notes?”

Emily: Soft request. If timing matters, ask: “Of course. Do you need them by a certain time?”

Paul: Third: “I’m still working on it. I should have it by five.”

Emily: Status plus expected completion time.

Paul: Fourth: “No rush, but I need the first page before my three o’clock call.”

Emily: Not immediate, but there is a real deadline for one part. A useful response: “Got it. I’ll send page one first.”

Paul: Last one. “Just to check, you’d like me to comment on the wording, not the numbers?”

Emily: Scope confirmation. The speaker is checking exactly what work is needed.

Paul: Good. Now the longer challenge. This is your chance to produce the skill, not just recognize it.

Emily: Imagine you are at work after a team meeting. A coworker and a team lead speak to you over the next few minutes. Your job is to listen for the function, respond naturally, and make the task clear.

Paul: Try to use at least four of these patterns during your response: “Have you got a minute?”, “When you get a chance, could you…?”, “Could you take a look at…?”, “I’m still working on it,” “I should have it by…”, “Do you need it by…?”, and “Just to check, you’d like me to…?”

Emily: You do not need to force every phrase in. Use the ones that fit.

Paul: Here are your partner lines. I’ll leave a short space after each one. First: “Hey, have you got a minute? I wanted to ask about the project notes.”

Emily: Sure. What’s up?

Paul: Second: “When you get a chance, could you take a look at the final paragraph? It feels a little unclear.”

Emily: Your response should accept or decline honestly, then check timing if needed. For example: “Sure. Do you need it by a certain time?”

Paul: “Before two would help. I’m sending the document at two-thirty.”

Emily: Now confirm the action or give a realistic status. “Okay. I’m still working on another task, but I should have comments for you by one-thirty.”

Paul: “Actually, just the final paragraph is enough. You don’t need to review the whole document.”

Emily: This is new scope information. You can say, “Got it. Just to check, you want comments on the wording in that paragraph, right?”

Paul: “Yes, mainly the wording. And if you see one obvious typo, fix it, but don’t change the numbers.”

Emily: Finish with a clear plan: “Understood. I’ll review the paragraph and send it back by one-thirty.”

Paul: Now try the whole exchange again without our sample answers. Keep it between about sixty and one hundred twenty seconds. Your goal is not to sound perfect. Your goal is to make the request, timing, scope, and status clear.

Emily: And for a more independent version, personalize it. Replace the project notes with something real or familiar: slides, an email, a report, a schedule, a shared document, or classwork if you don’t work in an office.

Paul: If your first attempt becomes vague, retry once. On the retry, add one timing question and one scope confirmation.

Emily: Here’s a shorter sample, not the full task: “Sure. What’s up? Yes, I can take a look. Do you need it by a certain time? Okay, I’m still working on something else, but I should have comments by one-thirty. Just to check, you want feedback on the wording, not the numbers, right? Got it.”

Paul: That short model contains the whole skill: hear the request, check the time, give status, confirm scope.

Emily: And it also answers our question from the beginning. How do you understand soft workplace English without guessing too much?

Paul: You listen for the function, use the situation, and make missing information visible with a short check.

Emily: “Have you got a minute?” opens the conversation. “When you get a chance, could you…?” softens a request. “I’m still working on it” gives status. “I should have it by…” gives an expected time.

Paul: And when the timing or action matters, “Do you need it by…?” and “Just to check, you’d like me to…?” help you confirm.

Emily: The useful habit is small: before you guess what a soft request means, check the part that could change what you do.

Paul: Today, try one line aloud: “Just to check, you need this by two, right?” Then make it personal with a time that fits your own situation.

Emily: If this episode was useful, keep listening to real English in complete situations, not only isolated phrases. Context is where these lines start to make sense.

Paul: And the next time a coworker says, “Have you got a minute?”

Emily: I promise not to start a sixty-second timer.

Paul: Progress.

Emily: Practical progress.