Write your first useful prompt
You type "write a friendly message to the customer" and get something warm, fluent and missing half the details, plus a booking link nobody mentioned. The fix is telling the tool five things instead of one.

What you'll make
a reusable five-part prompt for your own task, a draft from it, and one focused revision.
What you'll need
ChatGPT, Claude, Gemini or Copilot in your work account, a few rough notes you’re allowed to use, and about fifteen minutes. No connected apps are needed.
Example result.
Your bike (service ref BK-2291) is ready. Please collect it from the workshop on Friday [date], 12:00–18:00, or by 17:00 on Saturday [date]. Bring your collection slip; the mechanic will talk you through the work. The balance of £38 is payable on collection.
Before sending: add both dates and the workshop address.
1. Decide what the answer is for
Choose one output, such as a customer message, a checklist or a short explanation. Name who will read it and what they need to do afterwards. Gather the facts that matter, including any that are missing.
A useful prompt has five parts:
- Task: what to make, so the tool doesn’t invent a bigger job.
- Reader: who it’s for and what they need to do, so the wording fits.
- Source: the facts to work from.
- Limits: what must survive, and what mustn’t be guessed.
- Format: the length, shape and tone that make it usable.
Why this works: “write a friendly message” gives the tool a tone and nothing else, so it fills the rest with guesses.
What you should see: one sentence each for task and reader, and your notes ready to paste.
2. Fill in the reusable prompt
Replace each bracketed part, and keep only the limits that matter for your task.
TASK
Create [one specific output].
READER
It's for [reader and what they need to do].
SOURCE
Use only these notes for facts:
[your notes]
LIMITS
Keep every fact, figure, date and condition exactly as given. Don't invent missing details, promises, links or charges. If something is missing or unclear, flag it rather than guessing.
FORMAT
Return [length and tone]. Put missing information in a separate "Before sending" list.
[one specific output] is the thing you’re making, such as “a short message to a customer”. [reader and what they need to do] might be “a customer who needs to collect their bike”. [your notes] are your facts, including the gaps. [length and tone] might be “under 100 words, plain and friendly”.
Why this works: separating the notes from the instructions shows the tool what to work from, and the “Before sending” list stops an unfinished draft looking ready to send.
What you should see: a draft that uses your facts, with gaps shown as [placeholders] or in the “Before sending” list.
3. Check it against your notes
Compare every fact in the draft with your notes: names, codes, times, amounts, conditions. Delete anything that isn’t in them. Then read it as the recipient: could they do what it asks without guessing?
Why this works: a fluent draft can still change one word that matters. You’ll only see it by checking.
What you should see: every fact matching your notes, and every gap still visible.
4. Revise one thing at a time
“Make it better” starts the guessing again. Name the problem, ask for one change, and say what must stay.
The draft is too long. Cut it to 70 words, keeping every fact and placeholder exactly as they are. Keep the "Before sending" list separate.
Recheck the facts after any revision: shortening is where conditions go missing. If the notes lack something essential, such as an address, get it from whoever knows. Making the prompt sterner won’t make an address appear.
Why this works: one change at a time means you can see what the revision did.
What you should see: a shorter draft with every fact intact. Now try the same template on another job, such as an email telling a customer their delivery is delayed.
Check the result
- Every fact in the draft is in your notes, with the same wording where it matters.
- Nothing has been added: no link, charge, contact or promise you didn’t give it.
- Missing information is in the “Before sending” list, not filled in.
- The reader could act on it without asking you a question.
The usual failure: one small word changes. “By 17:00” becomes “at 17:00”, “may” becomes “will”, “about” disappears. The draft reads naturally, so the change slips past. Read every time, date and condition against your notes, word by word.
The draft changes [what the notes say] to [what the draft says]. Put back the wording from my notes and keep everything else the same. Then check every other time, date and condition against my notes and list any other changes.
[what the notes say] and [what the draft says] are the two versions, such as “by 17:00 on Saturday” and “at 17:00 on Saturday”.
Worked example: a bike ready for collection
Fictional example. A bike workshop’s notes for a customer message:
Service ref BK-2291, ready.
Collect from workshop Friday 12:00–18:00, or by 17:00 Saturday.
Bring collection slip. Mechanic will go through the work done.
Balance £38, pay on collection.
Dates and workshop address: not yet added.
Weak: “Write a friendly message telling the customer their bike is ready.” It returned: “Great news, your bike is ready! Book a collection slot using the link below.” No reference, no times, no balance, and a link that doesn’t exist.
The five-part prompt from step 2, with these notes, did much better, apart from one line:
Please collect it by Friday, or come in at 17:00 on Saturday.
- The failure. “By 17:00 Saturday” became “at 17:00”, which reads like an appointment. The Friday window also lost its hours.
- The repair. The repair prompt with “by 17:00 Saturday” and “at 17:00 on Saturday” restored the deadline and, on rechecking, the 12:00–18:00 window. That’s the example result.
- What stayed open. Both dates and the address are still in “Before sending”. They come from the workshop, not the tool.
Try it
Compare three prompts and what each one produced
Example responses, written to show what each prompt tends to produce.
Weak: Tone only
The prompt
Write a friendly message telling the customer their bike is ready.
Notes:
Service ref BK-2291, ready.
Collect from workshop Friday 12:00–18:00, or by 17:00 Saturday.
Bring collection slip. Mechanic will go through the work done.
Balance £38, pay on collection.
Dates and workshop address: not yet added.Example response
Select a phrase in the response to inspect its support or weakness.
Why this prompt changes the task
A tone tells the tool how to sound, not what the customer needs to do or which facts to keep.
Length and two facts
The prompt
Write a customer message under 80 words. Include the service reference and the Friday collection time.
Notes:
Service ref BK-2291, ready.
Collect from workshop Friday 12:00–18:00, or by 17:00 Saturday.
Bring collection slip. Mechanic will go through the work done.
Balance £38, pay on collection.
Dates and workshop address: not yet added.Example response
Select a phrase in the response to inspect its support or weakness.
Why this prompt changes the task
Naming two facts protects those two. Everything else is still up for grabs.
Five-part prompt
The prompt
TASK
Create a short message to a customer.
READER
It's for a customer who needs to collect their bike.
SOURCE
Use only these notes for facts:
Service ref BK-2291, ready.
Collect from workshop Friday 12:00–18:00, or by 17:00 Saturday.
Bring collection slip. Mechanic will go through the work done.
Balance £38, pay on collection.
Dates and workshop address: not yet added.
LIMITS
Keep every fact, figure, date and condition exactly as given. Don't invent missing details, promises, links or charges. If something is missing or unclear, flag it rather than guessing.
FORMAT
Return under 100 words, plain and friendly. Put missing information in a separate "Before sending" list.Example response
Select a phrase in the response to inspect its support or weakness.
Why this prompt changes the task
The five parts give every fact a place to go and every gap a place to wait. You still check the draft against the notes.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: Ask for questions before the draft
For anything more complicated than a short message, ask the tool what’s missing before it writes.
Before drafting, list the information missing from my notes that would change the answer. Ask up to three questions. Don't fill the gaps yourself.
Answer the questions, then use the five-part prompt. You don’t need to ask for its hidden reasoning; ask for the sources, assumptions or calculations you need to check the work.
Optional training: Keep the prompt for next time
Save the step 2 prompt in your notes exactly as it is, and keep your notes, the prompt and the checked answer together. When the task comes round again, change the notes and the reader, run it, and check the new output just as carefully. A saved prompt is a good starting point, not a reason to stop reading. Always check the result: a good prompt makes mistakes easier to spot, not impossible.
Optional training: Record what a change did
If you use a prompt regularly and keep fixing the same fault, keep a short record. Describe the fault in terms you can see (“turned ‘by’ into ‘at’”), change one instruction, and compare the new result against the same notes.
Task and notes:
Original prompt and result:
Fault seen:
One instruction changed:
New result, checked against notes:
Better, worse or the same:
Answers vary from run to run, so try the change on a second example before relying on it.