How to Write a Polite Email When You Need to Set a Boundary

Decide what boundary you need

Before replying, identify the actual constraint. Is the request outside your responsibilities, impossible within your current workload, or arriving through a channel you do not use for this kind of work? A precise answer helps you avoid a vague refusal that invites repeated follow-ups.

Separate the limit from your feelings about the sender. You do not need to prove that the request is unreasonable. For example, “I don’t manage vendor approvals” is clearer and less personal than “I can’t keep dealing with these requests.” If the issue is capacity, describe what you can realistically take on rather than making a broad statement about being busy.

Lead with acknowledgment, then be direct

A brief acknowledgment shows that you understood the request; it does not mean you have agreed to do it. Then state the boundary in a straightforward sentence. Put the decision near the beginning instead of burying it beneath several paragraphs of explanation.

Use a calm, neutral tone. “I’m not able to review this today” communicates a limit more clearly than “I’ll try,” if you already know you cannot fit it in. Avoid apologies that make the boundary sound negotiable. A simple “Thanks for checking with me” may be enough warmth.

Hi [Name],

Thanks for sending this over. I’m not able to take on the full draft this week because my current priorities are already committed.

I can review one specific section by [date] if that would help. Otherwise, [appropriate person or team] may be able to advise on the full draft.

Best,
[Your name]

Offer an alternative you can actually support

An alternative can keep the exchange constructive, but it should not quietly recreate the work you are declining. Consider offering a smaller task, pointing the sender toward the right role or process, or suggesting a time when you can reconsider. Make clear whether you are offering help, information, or a handoff.

If you do not know who can take the request, do not guess or volunteer someone else. You can instead say what the sender should do next, such as contacting the team responsible for that area. If no useful alternative is available, a clear, courteous no is better than a referral that may send them in circles.

Set limits on timing and communication channels

When capacity is the issue, be specific about the scope you can manage. “I can answer one question by Friday” gives a more usable expectation than “I’ll get back to you soon.” Only name a date if you can reasonably meet it, and distinguish a possible review from a promise to complete the work.

If the request came through a channel you cannot monitor, explain which channel works for this type of communication and what the sender should include. Avoid implying that a message sent elsewhere will be handled promptly. A channel boundary is most useful when it gives the other person a clear way to reach you instead.

Keep the explanation proportionate

A short reason can make your decision understandable, but a long defense often creates room for negotiation over details that do not change the limit. Share only what the sender needs to know. You can state that the work sits outside your role without listing internal disagreements or criticizing how the request was assigned.

If the sender pushes back, repeat the boundary calmly and restate any alternative you can offer. You do not have to produce a new explanation each time. If the request needs a decision from a manager or another responsible person, say that the sender should take it to them rather than implying you have authority you do not hold.

Check the message before sending

Read the draft from the recipient’s point of view. Can they tell what you will not do, what—if anything—you can do, and what they should do next? Remove wording that sounds like an uncertain promise if your decision is final. Check names, dates, recipients, and any commitments before sending.

After sending, confirm the boundary worked by looking at the response and the next action, not by expecting a particular reaction. If the sender acknowledges the limit or follows the suggested route, the message was understood. If they ask again, respond consistently and briefly. When a commitment depends on another person or process, make that dependency explicit rather than treating it as guaranteed.

• Boundary: Is the limit stated in one plain sentence?
• Alternative: Is it realistic and within your control?
• Next step: Does the sender know who should act or what to do?