Establish the expected result first
When a request is unclear, identify the actual result wanted. Does the person need an existing file sent over, a figure checked or a new piece of writing? Those differences determine whether you can respond immediately. The desired timing should also be understandable; “soon” can mean quite different things to two people.
Check whether an immediate answer is genuinely possible. If information must be obtained or a decision made first, treat the request as unfinished work. A quick promise such as “I'll do it straight away” otherwise creates an expectation before the scope or prerequisites are known. State the next dependable step instead of offering an uncertain completion time.
Capture unfinished work in a reliable place
Move a request you cannot complete immediately into the agreed task system. Record the desired outcome, the requester and the relevant date. A note saying “figures” may mean little tomorrow. “Check the sales summary for Tuesday and reply to Lena” describes an action that can be understood and checked later.
Link to the original message when useful rather than copying every detail again. Make sure the person responsible can still open that reference. If the request was spoken, summarise the important details briefly. This turns a memory into an understandable agreement without requiring a lengthy administrative procedure for a small task.
Avoid keeping several competing records for the same request. A personal note can serve as temporary capture, but move it promptly into the main personal or shared system. Otherwise the request can appear complete in a chat while remaining open on a scrap of paper, or disappear from one place before it has reached another.
Connect the response with completion
If a new request conflicts with work already promised, make the conflict visible. Agree priorities with the appropriate person rather than silently promising both deadlines. A smaller interim result or a reduced scope may be possible, but everyone involved should understand that decision. An unspoken change is likely to produce another follow-up request.
Close the task when the agreed result has been handed over or the request has explicitly been withdrawn. A finished draft on your own computer is not yet an answer to the requester. At handover, briefly explain where the result is and whether a response is still needed. This keeps a small request from getting lost between doing the work and communicating it.
