Soft Requests at Work in English: Check the Deadline Without Guessing

A coworker writes: When you get a chance, could you look at the last page? No rush.

By when?

Three readers answer three ways. One says tomorrow. One says this afternoon. One says, “It depends on the day.” All three are reasonable, and that is the problem: the message is polite, the grammar is clear, and it still does not say when. This guide gives you a habit for these messages, in three steps: hear what the sentence is doing, check the one thing that changes your next move, and say your plan back. Then it covers the other half of work talk, the update you give when someone asks how it is going.

The phrases come from a podcast episode about English at work. Messages and names marked written for this page are not from the podcast.

What a soft request does and does not say

Soft language is not a code. It tells you how the speaker wants to sound, and often very little about the time.

What you hear	What it usually does	What it does not tell you
When you get a chance, could you…?	Softens the request; you may not need to stop everything this second	When the person actually needs it
No rush, but…	Keeps the tone relaxed	Whether a time limit follows (…but before I leave at four)
If possible	Softens the request; may show flexibility, politeness or both	Whether the time matters
Have you got a minute?	Opens a short conversation	How long it will take, or what it is about

The episode puts both warnings in one place: soft does not automatically mean unimportant, and polite does not automatically mean optional, but you should not treat every soft request like an emergency either. So do not invent a rule such as “if possible means it can wait.” Use the situation, and ask when you need to know.

Step 1: Name the job of the sentence

Before you decide anything, say to yourself what the sentence is for. Six jobs cover most of what the hosts practice.

Job	Line	You will probably need to
Open a short talk	Have you got a minute?	Answer Sure. What’s up? and listen
Soft request	Could you take a look at this?	Decide if the time or the task is unclear
Status	I’m still working on it.	Note that the work is not done but is going on
Expected time	I should have it by three.	Plan around three, and ask if three is too late
Time check	Do you need it by two?	Answer with a real time
Scope check	Just to check, you’d like me to…?	Say yes, or correct the task

A useful test is to ask “what would I do differently if I heard this?” If the answer is nothing, it is probably an opener or a status line. If the answer is “start now” or “start later,” you are in time-and-scope territory, which is Step 2.

Step 2: Ask only the question that changes your next move

Two short questions do almost all the work.

The time question: Do you need it by a certain time?
The scope question: Just to check, you’d like me to ___, not ___, right?

Choose by looking at what is missing, not by asking both every time.

What the message already says	What is still unclear	Ask
Could you review the schedule? I’m sending it before my three o’clock call. (written for this page)	The time is clear; the amount of review may not be	Maybe the scope question
When you get a chance, could you look at the new logo? (written for this page)	No time at all	The time question
No rush, but it’d be helpful to have the revised summary before I leave at four. (from the episode)	The relaxed words hide a real boundary: four	Nothing about time; plan for before four
Could you send me your notes before two? (written for this page)	Nothing	Nothing, or a one-line confirmation

The scope question earns its place because the same verb can mean very different amounts of work. In the episode, the check is Just to check, you’d like me to review the numbers, not rewrite the whole section? One answer sends you off for ten minutes, the other for an hour. Notice the shape of the sentence: it says what you think the task is, then what it is not, and ends with a question the person can answer in one word.

Step 3: Say your plan back

A check is only finished when you say what you will do. The pattern is Got it plus the action plus the time.

Got it. I’ll look at it after I finish this email.

When the answer changes the picture, change your plan out loud. In the episode, a team lead says the summary is wanted before four, then adds that the finance team needs the first page for a call at three-fifteen. The reply that works does three jobs in a row:

1. Check what changed: Just to check, you need page one before three-fifteen, but the rest can come a little later?
2. Get the one-word answer: Yes.
3. Split the work: Got it. I’ll send page one first.

Separating the urgent part from the whole task is often the most useful thing you can say at work.

Reporting back with a status and a time

Requests are only half of work talk. The other half is the answer to “How is it going?” A good update has two parts: where the task stands, and a time the other person can plan around.

Situation	What you say
You are not finished, and you know when you will be	I’m still working on it. I’ll have it by three.
You are not finished, and the time is an estimate	I’m still working on it. I should have it by three.
The time is slipping	I’m still working on it. It’s taking a little longer than I expected. I should have it by four.

Two details matter. First, should here expresses a reasonable expectation, not a perfect guarantee, so use I’ll have it by… only when you are certain. Second, if the time is going to slip, say so before the old time arrives. The person who asked can then react, perhaps with Do you think you can send the first section by three?

What if you hear I should have it by four and you need it at three-thirty? Do not smile and hope. Say it plainly: I actually need to use it at three-thirty. Is that possible? It is clear, calm and specific.

Five sentences to repair

What goes wrong	Better	Why it works
Sure, no problem. (and nothing else, after a soft request)	Sure. Do you need it by a certain time?	“No problem” does not say when, so you each assume a different time
When you get a chance, do this now.	Could you check this before the meeting?	The softness and the urgency fight each other; give the real time
I’m working on it. Maybe later.	I’m still working on it. I should have it by four.	“Maybe later” gives the listener nothing to plan around
I think maybe I can possibly have it by three.	I should have it by three.	One hedge helps; five make the listener do detective work
I should have it by three, definitely.	I’ll have it by three. or I should have it by three.	Choose certain or honest; do not add definitely just to sound stronger

Three drills on soft requests

Drill 1: Name the job. Match each line with a job: opens a short talk, status, time check, expected time, scope check, soft request.

1. Have you got a minute?
2. I should have it by the end of the day.
3. Do you need it by two?
4. Just to check, you’d like me to fix the typo, not the numbers?
5. I’m still working on it.
6. When you get a chance, could you take a look at this?

Drill 2: Decide what to ask. For each message (written for this page), choose: ask the time, ask the scope, or ask nothing.

1. Could you read the draft before my three o’clock call?
2. When you get a chance, could you look at the new poster?
3. No rush, but could you fix the problems in the summary?
4. Please send me the numbers before two.

Drill 3: Remove the fog. Rewrite each line in one clear sentence.

1. I think maybe I can possibly finish it this afternoon.
2. Almost done, probably soon.
3. Not done. (add a status and a time)

Answers

Drill 1: 1. opens a short talk. 2. expected time. 3. time check. 4. scope check. 5. status. 6. soft request.

Drill 2: 1. The time is already clear (before three o’clock), so ask the scope if it is unclear: Just to check, you’d like comments on the wording, right? 2. Ask the time: Do you need it by a certain time? 3. Both are open. “Fix the problems” could be a few typos or a rewrite, so ask the scope first, then the time. 4. Ask nothing about the time; it is two. A one-line confirmation is fine: Got it. You need them by two.

Drill 3: 1. I should have it by four. 2. I’m still working on it. I should have it by three. 3. I’m still working on it. I should have it by three.

A 60-second reply to say aloud

Use your own situation, such as slides, an email, a report, a schedule or classwork. Say the request out loud, then answer it in 60 to 120 seconds. Your aim is not perfect English. Your aim is to make four things clear: the request, the time, the scope and your status.

1. Sure. What’s up?
2. Yes, I can take a look. Do you need it by a certain time?
3. Okay. I’m still working on something else, but I should have comments by one-thirty.
4. Just to check, you want feedback on the wording, not the numbers, right?
5. Got it.

That five-line model is short on purpose. If your own first try becomes vague, try again once and add one time question and one scope check.

The last line you will use most is the check itself, so say it in chunks, not word by word: Just to check, / you need this by two, / right? The pauses can be very light. They organize the meaning: I am checking, here is the action and the time, please confirm.

Hear it in a real conversation

Want to hear the whole exchange, including the misunderstanding about “when you get a chance” and the pronunciation practice? Go to the Show Note for the episode: Listen to Real English at Work: Follow Polite Requests and Status Updates.

What to take to your next message

• Say what the sentence is for before you decide what to do.
• Ask the time question or the scope question only when the answer would change your next move.
• Finish the check with Got it and a plan, and split out the urgent part when there is one.
• Give a status and a time: I’m still working on it. I should have it by three.
• Choose between I’ll have it by… (certain) and I should have it by… (estimating), and tell people early when the time slips.