How to Decline a Coworker’s Help Request Politely
A professional refusal does more than say you are busy. First establish what the coworker means by “help”: a five-minute answer, a review, shared execution, or complete takeover. Then respond with a precise capacity statement: “I can review the first page at 3 p.m., but I can’t own the revision or today’s delivery.” That keeps cooperation possible without silently moving the task onto your list. If the request conflicts with assigned priorities, ask the person authorized to set priorities to decide; do not negotiate someone else’s work plan on their behalf.
Diagnose the request before answering
“Can you help?” is not a usable unit of work. Ask for the deliverable, deadline, current owner, and the point where your input is needed. A request to explain a spreadsheet formula is different from a request to rebuild the spreadsheet and send it under your name. You can ask: “What is the exact output, when is it due, and which part are you asking me to handle?” This is not needless formality. It prevents a small favor from expanding after you agree and gives both people the same picture of completion. Also check whether the message is truly a peer request or relays an assignment already approved by a manager; the correct route differs.
Choose among three honest capacity responses
Use three options instead of treating every request as yes or no. Say yes when the scope fits and you genuinely want to help. Offer bounded help when one small contribution fits: a ten-minute check, one example, a link to the right file, or a scheduled review. Say no when even the bounded version would displace committed work. Each answer should include a limit: “I can show you the setup, but I can’t complete the entries,” or “I don’t have capacity before Friday, so I can’t help with Thursday’s deadline.” A false maybe is less courteous because it leaves the coworker planning around capacity that does not exist.
Keep the task owner visible
Helping with a step should not automatically transfer responsibility for the result. Name the handback point: “I’ll comment on the draft; you’ll make the edits and submit it.” Avoid opening the file and quietly finishing everything because that may solve today’s deadline while making next week’s ownership even less clear. If you provide an example, explain which part it illustrates rather than becoming the permanent reviewer. This distinction is especially useful when the coworker asks repeatedly: the assistance can build their ability to do the work, while the task and follow-through remain with the person assigned to them.
Route real priority conflicts to the right decision owner
A coworker may describe their task as urgent, but urgency does not automatically outrank your confirmed deliverables. State the collision with specifics: “I’m committed to the client summary until 4 p.m.; taking this on would move that deadline.” If both tasks matter and neither person has authority to reorder them, ask the responsible manager or project lead for a decision. Frame it as a choice between outputs, not a complaint about the coworker. Do not volunteer another colleague, promise staffing, or announce that the request is outside anyone’s role unless you have verified that information.
Respond differently to emergencies and repeated patterns
For a genuine immediate disruption, decide the smallest safe contribution you can make now and state what must be revisited afterward. A one-time exception should carry a boundary: “I can cover the customer reply for the next hour; tomorrow we need to confirm who owns follow-up.” For repeated requests, stop improvising a new excuse. Record the dates, approximate time, requested outputs, and work displaced, then propose a team conversation about routing, training, office hours, or responsibility. Focus on the pattern in the work system rather than accusing the coworker of laziness or bad intent.
Close the exchange without overexplaining
A complete reply can be short: acknowledge the need, state your capacity, define any bounded contribution, and confirm the owner or next decision. For example: “I see why you need a second check. I can’t review the whole deck today. I can look at slides 1–3 at 2:30, and you’ll keep the final edit and send.” If the answer is no, omit the invented alternative: “I’m committed through the deadline and can’t take this on.” Repeat the same factual boundary if pressed. Long personal justifications invite negotiation over whether your reason is important enough; workload, scope, and ownership are the relevant facts.
Common questions
Should I always offer an alternative when I refuse?
No. Offer only an option that fits your real capacity. A clear refusal is more useful than an alternative you cannot deliver.
What if the coworker says the request will take only five minutes?
Ask what finished means and decide for yourself whether it fits. A five-minute question can be accepted without accepting the whole task.
Will saying no make me look uncooperative?
Cooperation includes reliable commitments. A specific limit, respectful tone, and clear handoff usually provide more usable information than a reluctant yes that delays other work.