Write & communicate

Decline a request while preserving the relationship

Give a clear no, an accurate reason, and only alternatives you can genuinely offer

4 min setupTested with:ChatGPTReviewed: 2026-08-28
1

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

2

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Write a professional email declining the request while preserving room for future cooperation.

Request and relationship:
[request]

Decision, boundary, and shareable reason:
[decision]

Authorized alternatives, dates, or referrals:
[options]

State the decision early and unambiguously. Acknowledge the request without excessive apology or praise. Give only the shareable reason and do not invent policy, blame another person, or imply the decision may change when it will not. Offer alternatives only if they are genuinely available; label anything requiring approval. End with a concrete, low-pressure next step. Return: subject, send-ready email, boundary check, and claims requiring confirmation.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Request and relationship
A long-term freelance designer asked us to reserve 20 hours every week for the next three months. We value the relationship and may need project-based work later.
Decision and reason
We cannot guarantee a weekly retainer because the approved Q4 workload is variable. This is a final decision for Q4, not a judgment on their work.
Available alternatives
We can invite them to quote on defined projects as they arise. The first possible project brief may be ready in late October, but it is not approved or guaranteed. We may share it only after internal approval.

Example output

Subject: Q4 working arrangement

Hi Alex,

Thank you for asking about reserving 20 hours each week for the next three months. We’re not able to commit to a weekly retainer for Q4 because our approved workload varies, so I want to be clear that we cannot reserve those hours. This decision is about the current workload, not the quality of your work.

We would still like to invite you to quote on defined projects when they are approved. A possible brief may be ready in late October, but it is not yet approved or guaranteed. If it receives approval, I’ll ask before sharing it rather than assuming your availability.

Best, [Sender name]

Boundary check: the Q4 retainer is clearly declined; no project or date is promised. Confirm the recipient and sender names and that the workload reason may be shared.

Why this works

  1. 1

    An early, direct decision prevents polite language from creating false hope.

  2. 2

    Authorized alternatives preserve goodwill without creating a new commitment.

Check the result

  • Will the recipient understand exactly what is being declined?

  • Are all reasons and alternatives accurate and authorized?

  • Does the wording avoid false hope, blame, and unnecessary defensiveness?

More ways to explore

Where this recipe fits

Text promptsWriting & communicationChatGPT prompts

Keep the work moving