You need to decline a guest contribution, and the AI draft sounds warm: “We loved your proposal and hope to work with you very soon.” The problem is that nobody has approved either statement. Politeness has become an invented evaluation and a possible commitment.
A useful rejection email tells the recipient what was decided, gives only an authorised explanation, and makes the next step clear. This worked example focuses on an ordinary editorial submission. It complements our guide to preserving uncertainty: here, you must also preserve a decision's finality instead of softening a definite no into an implied maybe. Employment, legal, and other regulated decisions need their own approved processes.
Give the model a decision record before asking for tone
Start with a few factual notes. In this fictional example, a community newsletter received an unsolicited article proposal about balcony gardening. The editor has decided not to commission it for the October issue because that issue is already fully planned. The editor has not evaluated the contributor's writing, has no confirmed opening for another issue, and is not inviting a revised pitch.
Those facts define the message. They do not authorise “Your writing is excellent,” “We received hundreds of outstanding submissions,” or “Please send another version.” Each may sound conventional, but each says something different from the record. When the record is incomplete, ask the decision owner for the missing information rather than asking AI to make the email feel complete.
Remove personal details that the tool does not need. A placeholder name and the approved reason are usually enough for a drafting exercise. Keep private evaluations and confidential correspondence out of the prompt unless you are authorised to share them in that tool.
Recognise the draft that creates extra work
Consider this flawed draft: “Dear Sam, we were incredibly impressed by your wonderful balcony-gardening proposal. Unfortunately, due to the exceptional volume of submissions, we cannot move forward at this time. We would love to keep the conversation going and hope to find a place for your work in a future issue.”
The compliments imply an assessment that did not happen. The submission-volume explanation is invented. “At this time” and the final sentence invite the recipient to wait, follow up, or send more material, even though the editor has no next step to offer. The draft sounds considerate while making the decision harder to interpret.
Do not solve that by replacing enthusiastic adjectives with quieter synonyms. The problem is what the sentences commit the sender to. Mark every clause as decision, reason, acknowledgement, or next step. A clause that does not match an approved fact needs removal or confirmation.
Rewrite the message around the actual decision
A faithful version could be: “Dear Sam, thank you for sending your balcony-gardening proposal. We will not be commissioning it for our October issue because the issue is already fully planned. Thank you for thinking of the newsletter. Best, Alex.”
This version acknowledges the action Sam took without judging work that was not reviewed. It states the scope of the decision and the real reason. It does not promise future contact. A useful subject line would be “Your balcony-gardening proposal for October,” which helps the recipient identify the message without exaggerated urgency.
If the organisation has an approved sentence clarifying that revised pitches are not being requested, use it when the recipient needs that information. Do not add unnecessary instructions to a message that is already complete. Likewise, do not write “This decision is final” just to sound decisive when a plain statement of the decision is sufficient.
Change the wording when the facts change
Suppose the editor really does want a new proposal for February. Then the email needs a genuine next step: what kind of proposal, when it should arrive, and whether sending it guarantees anything. An approved invitation might say, “You are welcome to send a short proposal for our February gardening issue by November 10. We will review proposals after that date; an invitation to submit does not guarantee a commission.” These dates and terms are fictional examples, not a default policy.
Conversely, if the reason cannot be shared, do not manufacture a harmless-looking substitute. Ask for approved wording that states the outcome without disclosing the reason. A brief accurate message is preferable to a detailed explanation that is false. The sender remains responsible for choosing what they are authorised to communicate.
Use a prompt that protects the boundary
Try: “Draft a short, considerate email using only the decision record below. State the decision clearly near the beginning. Acknowledge the recipient's action without inventing praise. Include only an approved reason. Do not imply reconsideration, future work, another submission, or follow-up unless the record explicitly authorises it. After the draft, list any sentence that needs the sender's confirmation.”
The National Archives' plain-language principles recommend writing for the reader, organising information, and using familiar language. Applied here, that means the recipient should be able to locate the answer without interpreting ceremonial phrases. It does not mean that every rejection must use the same blunt template.
You can use the AIUndetectable humanizer to revise stiff wording after the facts are settled. Keep the decision and any approved next step unchanged, then compare the result with the record. A detector score cannot verify whether the sender actually authorised a promise.
Read once as the person receiving it
Before sending, ask three questions: Do I know the outcome? Am I being asked to do anything? Should I expect another message? If the draft gives answers that differ from the decision record, fix the wording. Also verify the name, proposal title, issue, and sign-off against the actual correspondence.
The finished email may be only a few sentences. Its value comes from leaving the recipient with an accurate understanding, not from filling the space with reassurance. Keep the courtesy, remove the invented story, and let a clear answer be the useful thing you provide.