Refusals, bad news and the message you would rather not send

Where the default register is exactly wrong

Most workplace writing is routine, and a helpful, warm, slightly hedging tone is fine for it. Then there is the other kind: the refusal, the bad news, the invoice that is ninety days late, the correction of somebody senior, the complaint response, the letter that ends an arrangement.

For these, the model's default register is not merely unhelpful. It is the specific thing that makes the message fail.

Why it hedges

These models are tuned on human preference judgements. People rate agreeable, softening, non-committal answers highly in the abstract, so the trained default drifts towards warmth and away from anything a reader might dislike. That default is baked in before you type a word, and it takes explicit instruction to override.

The result is a class of sentence you have seen a hundred times:

We may be unable to proceed with this at the present time.

The writer means no. The reader, entirely reasonably, reads "may", reads "at the present time", and comes back in a fortnight. Now you send a second refusal, the recipient feels misled, and the relationship is worse than if you had said no on Monday. A refusal that is not understood as a refusal is not a kindness; it is a cost passed to somebody else.

The shape that works

Ask for the structure explicitly, because the model will not choose it:

1. The decision, in the first sentence. Not the context, not the appreciation of their interest. The decision.
2. One reason, if you can give one honestly. Not three — three reasons invite three counter-arguments.
3. What happens next, with a date if there is one.
4. The one thing you can offer, if anything. If nothing, say nothing rather than manufacturing a consolation.

A brief that produces this:

Write a refusal to the attached proposal. First sentence states we are not proceeding. One reason: the work falls outside our remit for this financial year. State that no further review is planned. Offer nothing else. Four sentences maximum. No apology for the delay, no expression of enthusiasm, no invitation to resubmit.

The prohibitions are doing as much work as the instructions. Left to itself the model will add every one of them back.

Apologies, and a real legal wrinkle

Whether to apologise is not only a matter of tone, and this is one place where the law genuinely differs by country.

In England and Wales, section 2 of the Compensation Act 2006 states that an apology or offer of treatment does not of itself amount to an admission of negligence or breach of statutory duty. Many US states and several Canadian provinces have their own apology statutes, with varying scope — some protect only expressions of sympathy, others also protect admissions of fault. Many jurisdictions have no such provision at all, and in some contexts an insurer's policy conditions restrict what may be said regardless of the underlying law.

What follows for you is not a rule about apologising. It is that the wording of an apology in a regulated or contested matter is a question for your organisation's own guidance or a qualified adviser in your jurisdiction, and it is not a question to settle by asking a chatbot what is customary. Nothing in this course is legal advice, and this is one of the places where the difference matters most.

The message you write to get the anger out

There is one use here that is unambiguously good. Write the furious version. Every accusation, in your own words, with the facts you know.

Then: "Here is a message I will not send. Extract the factual claims and the outcome I am asking for. Rewrite it in four sentences with no evaluative language about the other party."

You supplied every fact, so there is nothing to invent. What is being removed is heat, and removing heat from your own words is the safest possible task to hand over. Read the result, put back the one firm sentence it softened too far, and send that.

Register is not universal

The model's default is a mid-Atlantic corporate voice. Directness that reads as clear and respectful in Amsterdam or Berlin can read as aggressive in Delhi, Tokyo or Jakarta; indirection that reads as courteous in one place reads as evasive in another. Seniority, age and whether the relationship is ongoing all move the line.

You know your reader; the model does not. Say so:

The recipient is a supplier we have worked with for nine years, in a business culture where a direct refusal to a long-standing partner is read as ending the relationship. Refuse this specific request clearly while making explicit that we intend to continue working together.

The condolence problem

A message of sympathy has value because somebody spent their attention on it. That is the whole content. Generate it and you have sent a well-formed object with the thing it was supposed to carry removed — and, increasingly, recipients can tell.

Use the tool here only to get past a blank page: ask what to avoid saying to somebody in that situation, close the window, and write three sentences yourself. Three clumsy sentences of your own are worth more than a polished paragraph that cost you nothing, and the recipient is the person who decides that, not you.

And it never sends

Every message in this lesson is one where being wrong is expensive and the send is irreversible. Draft in the tool, read it cold, and press send yourself.