Write a brief, not a request

The gap between what you asked and what you meant

Type write a professional email declining the invitation and you get an email. It will be fine. It will also be nobody's email, because the model was given a category, not a situation.

You know things it does not: that you have declined this person twice already, that you want the door open for March, that your organisation does not use the word "unfortunately", that it goes to somebody who reads on a phone between meetings. None of that is in the request, so none of it is in the draft, and you spend fifteen minutes putting it back.

The upgrade is not a magic phrase. It is switching from a request to a brief — the thing you would send a competent freelancer who has never met your organisation.

Five parts of a brief

You will not need all five every time. Two or three lift the quality of the output more than any amount of "act as an expert".

1. The situation, in your own words. What has happened, who is involved, what has already been said. This is the part people skip and it is the largest single source of improvement. Three sentences of context beats three paragraphs of instruction.

2. The reader. Not "a professional audience". A specific person or a specific type: a district officer who receives forty of these a week; a parent who is already angry; a client who does not know what an indemnity is. Naming the reader changes vocabulary, length and structure at once.

3. The constraint. Length, in words or in physical space. Format. Reading level. Things that must be said. Things that must not be said. "One side of A4", "under 120 words", "must include the refund date", "do not apologise, we did nothing wrong" — these are the instructions that actually bite.

4. What good looks like. One line is enough: success is that they reply with a date and do not ask what we mean by 'in principle'. You would be surprised how often this alone fixes an otherwise flat draft, because it converts a writing task into a purpose.

5. What bad looks like. Optional and powerful. Do not open with "I hope this finds you well". Do not use "reach out". Do not make it sound like a form letter. Negative constraints are weaker than positive ones — that is a real limitation of these models, and it is why "do not be verbose" underperforms "maximum 120 words" — but naming a specific banned phrase works well because it is concrete.

A worked pair

Weak: Write a polite but firm reminder about an overdue invoice.

Better:

A client of six years is 47 days late on a ₹2,80,000 invoice. Their accounts contact has not replied to two emails. I know the director personally and want to keep the relationship. This is the third reminder and should be the last before I involve our accountant. Under 150 words, no threats, one clear ask with a date. It goes to the director, not to accounts.

Same task. The second one produces something you might send after two edits, because everything the writer knew is now in the room.

Iterate on one thing

When the draft is not right, most people rewrite the whole prompt and change six things at once. Then the next one is worse in a different way and they conclude the tool is unreliable.

Change one thing and look. "Too formal" is not an instruction; "cut the first paragraph and start with the ask" is. "Make it better" is not an instruction; "same content, 90 words" is. Editing a draft in front of you is far more effective than re-describing what you wanted from scratch, because the draft is now context too.

And when three attempts have not got there, stop prompting and start typing. A draft that is 80% right is a starting point, not a negotiation. The moment you are arguing with it, you have crossed the line where doing it yourself is faster — which is the verification-cost trap from the first module, wearing different clothes.

Where the brief goes

Once you have written a good brief for a recurring document, you have made an asset, not a message. Save it. Replace the specifics with blanks. Next month, fill in the blanks.

That is the whole idea behind saved prompts, custom instructions and the "project" features in the major tools, and it is covered properly in the last module. For now, keep a plain text file. Six good briefs in a text file will do more for your week than any subscription.

The honest limit

A brief improves the draft. It does not make the facts true. Everything in the brief you supplied is reliable, because you supplied it. Everything else in the output — the statistic it added, the regulation it cited, the deadline it inferred — is still unverified, and a beautifully briefed document is exactly the kind that gets read quickly and signed without checking. Brief well, then check the specifics anyway.