The direct answer: distinguish an estimate from a promise
When someone says ‘about five minutes’, do not silently convert that estimate into a guarantee of exactly five minutes. Ask whether it is a rough duration or a firm commitment, and agree when the person will provide the next update if the timing matters.
A practical reply is: ‘Is five minutes your current estimate, or do we need to plan for a longer window? Could you update me if that changes?’ This respects uncertainty while giving both people something usable. It does not demand that an uncertain future event become magically exact.
Did You Know? ‘About’ changes what a number commits the speaker to
Cambridge Grammar Today explains that about makes a time, number or quantity less specific and more approximate. Its guide to approximations shows how words such as around and roughly signal imprecision in spoken English.
That matters in everyday interaction. ‘The bus arrives at four’ sounds more exact than ‘the bus arrives around four’. It is reasonable to ask for a firmer time if you must make a connection, but unreasonable to claim the speaker promised a precise instant merely because they used a number.
The mechanism: forecast, commitment and update are three different acts
A forecast is what someone currently expects. A commitment is an action they agree to take. An update is a message they agree to send when information changes or at a chosen check-in point. Mixing these produces unnecessary conflict.
Suppose a friend says, ‘I’ll be there in about five minutes.’ The current estimate may be based on how far away they think they are. The person receiving the message might instead interpret it as ‘I promise to arrive five minutes from now.’ If traffic or a delayed lift changes the journey, the two people may accuse each other of broken promises when they never agreed on what was guaranteed.
Repair the mismatch by marking what can be controlled. A person may not be able to control a train, but they can often agree to send a reliable status update. ‘I expect another five to ten minutes, and I’ll message you after I check the next train’ gives more useful structure than repeating ‘five minutes’ with greater confidence.
An estimate is not useless because it is uncertain. It becomes usable when the conditions, tolerance and follow-up are clear enough for the listener’s decision.
The estimate–window–update technique
Begin with an accurate restatement: ‘So five minutes is an estimate.’ That single phrase prevents an approximate statement from being presented as a certainty.
Next, ask whether a range is more appropriate: ‘Would five to ten minutes be a more realistic window?’ Do not invent the range yourself; let the person who has the information state what they can support. When no reliable range is available, record the limit honestly.
Then identify what decision depends on the timing. Are you waiting before starting dinner, leaving school, joining a video call or arranging a collection? A good question names the consequence: ‘Should we begin without you if you are not here by six?’
Finally, agree a next update rather than a false arrival promise. The message might be ‘I’ll check again at 5:45 and let you know’, provided the person can reasonably make that update. If communication is impossible, agree an alternative plan in advance.
Fictional dialogue: primary school homework
Fictional home demonstration. Child: ‘I’m nearly done. About five minutes.’ Parent: ‘Is that your estimate, or do you need more time to check the last two questions?’ Child: ‘I still have to explain one answer.’ Parent: ‘All right. Let me know when you finish that explanation. We can set the table first.’
The parent did not treat the child as dishonest for misjudging the work. Nor did the parent grant endless extra time without a plan. The next meaningful event is finishing the explanation, not winning an argument over whether five minutes has passed.
Fictional dialogue: a teenage project team
Fictional school demonstration. Student A: ‘The graph should be ready in about ten minutes.’ Student B: ‘We present at three. Is ten minutes a rough estimate, or can you confirm the graph by 2:40?’ Student A: ‘I can finish the labels by 2:40, but I need someone to review the figures.’ Student B: ‘Then let’s distinguish labels finished from review completed. I’ll ask Maya to review at 2:40.’
Here the first number was not the real issue. The project depended on two distinct activities. Repairing the conversational commitment revealed an action that the group could actually schedule.
Fictional dialogue: collecting someone from a station
Fictional adult-life demonstration. Traveller: ‘I’ll be outside in about five minutes.’ Driver: ‘Is that a rough estimate? I’m in a short-stay area.’ Traveller: ‘Yes. The exit queue is longer than I expected.’ Driver: ‘Please message when you reach the exit. I’ll use the designated waiting area until then.’
The two people separate what is unknown from what can be coordinated. Parking regulations and safety come from the actual location, not from a general language lesson. Their wording is useful because it avoids pretending the exact arrival time is known.
Fictional dialogue: a workplace repair update
Fictional teamwork demonstration. Colleague: ‘The system will be back in about five minutes.’ Manager: ‘Is that a confirmed restoration time or your current estimate?’ Colleague: ‘It’s an estimate; the provider hasn’t confirmed an end time.’ Manager: ‘Then we’ll tell the team it is still unavailable, give no guaranteed restoration time, and update them when the provider confirms more information.’
The manager does not transform an unsupported estimate into a public assurance. For consequential systems, published status should depend on the responsible technical team or official provider, not on conversational optimism.
Register and tone: polite clarity, not a cross-examination
With family, ‘About five minutes, or might it take a bit longer?’ is natural. With a school group, ‘Is that a rough estimate? What should we do if it takes longer?’ is cooperative. In a professional setting, ‘Could you clarify whether this is an estimated time or a confirmed deadline, and advise when the next update will be available?’ is appropriate.
Aggressive versions such as ‘So you promised five minutes, right?’ insert a commitment the speaker did not make. On the other hand, ‘Whenever, I suppose’ may be too vague for a task that has a real deadline. Politeness and precision can coexist.
Cambridge’s discussion of politeness shows how questions and softened requests can maintain good relations. The point is not to hide the deadline but to ask about it without turning an estimate into a moral accusation.
What often goes wrong
Mistake one: replacing ‘about’ with ‘exactly’ when repeating someone else’s message. A parent who tells a sibling ‘She said exactly five minutes’ has changed the original commitment. Mistake two: assuming that an estimate means ‘any amount of delay is acceptable’. An estimate still needs proportionate communication and a sensible fallback.
Mistake three: demanding an exact minute when the speaker lacks information. The listener may need a decision such as ‘start without me’, not a fabricated timestamp. Mistake four: using ‘approximately’ to avoid taking responsibility for an update that the person could reasonably send.
A final error is mixing time of arrival with duration of the task. ‘It will take about five minutes’ describes a duration, but ‘I’ll be there around five’ describes a clock time. In spoken English, context usually helps; when the consequence matters, ask which one was intended.
Diagnostic questions for a real conversation
Is the number a duration, a clock time or an arrival estimate? Is it confirmed by a reliable source? What new information could change it? Do I need a range, a deadline or simply an update? Who is responsible for communicating a change? What should happen if the event is later than expected?
One well-chosen question is better than six repeated demands. ‘When should I check back?’ often gives more reliable information than ‘Are you certain?’ when nobody can know the exact timing yet.
Retrieval practice: three short repairs
Cover the page and complete these from memory: ‘Is that a ___ or a confirmed time?’ ‘What is a realistic ___?’ ‘When can you send the next ___?’ The answers are estimate, window and update. Then write one sentence that gives the listener a fallback action.
Try a dialogue where a classmate says ‘The poster will be ready in around twenty minutes.’ Ask what is left to do, which time is estimated and when the next progress message will come. Then try a friend saying ‘I will arrive about eight’. Ask whether eight is a clock time and what will happen if they are delayed.
Check your response for invented facts. Did you quietly substitute an exact deadline? Did you treat uncertainty as dishonesty? Did you leave the listener with no practical action?
A four-week practice sequence
Week one: identify approximation words in short examples: about, around, roughly and approximately. Week two: contrast estimates with firm appointments and commitments. Week three: write brief messages that contain an estimate and a next check-in. Week four: practise making a fallback plan when the estimate changes.
This is a suggested learning routine, not an observed programme outcome. A student can track a simple success criterion: ‘I represented the uncertainty fairly and agreed on a useful next action.’
Guidance for parents, students and teachers
Parents can explain that estimating time is a skill, and children may not yet know how long tasks take. Instead of calling a child a liar after an overoptimistic estimate, ask what remains and help them make a more grounded forecast. Clear household boundaries can still apply.
Students working in groups should distinguish ‘I expect to finish the graph by two’ from ‘I will send the reviewed final graph by two’. If the latter is impossible, say so early and propose a revised plan. Teachers can practise this distinction during ordinary project discussions without inventing a formal assessment standard.
The language also supports Mathematics and Science thinking: an estimate is not the same as a measured exact value. However, a scientific measurement’s uncertainty has more technical meaning than a casual conversation’s timing estimate. Use subject-specific definitions when the context requires them.
Transfer to other situations
The same repair helps with ‘about ten pages’, ‘roughly twenty participants’ or ‘around one hundred dollars’: identify what is approximate, what decision depends on precision and where a more reliable number can be obtained. Do not replace official prices, quotas or regulated deadlines with casual guesses.
Related eduKate lessons cover repeating exact numbers and dates before acting and distinguishing by from until. This lesson deals with a different job: preventing a deliberately approximate forecast from becoming a false promise.
Frequently asked questions
Is ‘about five minutes’ a promise? Not automatically. ‘About’ signals approximation; context and any explicit agreement determine what the speaker actually committed to.
Should I always ask for a range? No. If the timing is unimportant, an estimate may be enough. Ask for a range when another decision depends on it.
What if the estimate changes? State what changed, provide only supportable new information and communicate the agreed next check-in.
Is it impolite to request a firm deadline? Not when a real obligation requires one. Ask plainly and respectfully, allowing the other person to say whether they can commit.
What if no estimate is available? Say that the timing is unknown and agree a next source of information, fallback plan or update point rather than inventing an exact number.