Start here

Estimate the full response work, including reading, research and checking, alongside existing duties and agreed service requirements. Offer a window matching that capacity. Keep the commitment with the task and send an update before it expires if missing information or workload changes the timing.

You tell people you will answer soon because you want to be helpful. The reply sometimes comes that afternoon and sometimes three days later. They cannot tell when to follow up, and you feel pressure whenever another message arrives.

Look at how long this kind of response actually takes alongside your other work. Offer a window that matches that experience, subject to any agreed service requirements. If the question needs research, include that time rather than counting only the minutes spent writing.

Update the promise when it changes

If you will miss the window, send a brief update with a new date or explain which information is still missing. The person may need another route if their decision cannot wait.

Keep the response commitment beside the task, particularly when it arrives through a busy inbox. After several attempts, review whether the window remains realistic. You can make an occasional faster reply without setting a permanent expectation that every future question will receive the same speed.

Answering a question that needs checking

An illustrative example

Imagine a colleague asking about a process you need to verify in current documentation. Writing the answer might be brief, but checking the correct version takes longer. Instead of saying soon, offer a response during a slot you can use and explain if an external answer is required. Put that commitment beside the question. If the document remains unavailable, update the colleague with the specific dependency and a new check point. They may choose another route if their decision cannot wait. After several similar questions, compare the offered windows with actual effort. You can occasionally reply faster while keeping the ordinary expectation tied to time you can reliably provide.

Choose a usable response window

Tick the steps as you work through them.

0 of 5 steps checked

When you keep missing the window

Inspect what your estimate omitted. Research, interruptions or a required approval may need explicit space. Give a revised window based on recent examples and discuss the workload if required response times cannot be met. Avoid offering a faster promise merely because the first one was missed. If the sender needs another route, say so while they can still use it. Keep the distinction between a routine question and an agreed urgent requirement; both need timing the relevant people actually understand.

Write the response commitment

Your notes stay in this page. Copy them before leaving; they are not saved or sent to us.

Next useful stepHow to offer help with a clear scope and time limit →

Written by the Painless Success editorial team. Our upcoming book, Painless Success, brings these ideas together. Preview its contents or join the release waitlist.