Lesson 1.1
Anatomy of a Good Prompt
The five building blocks of a prompt that gets useful work from Claude on the first attempt, with a before-and-after rewrite you can copy.
A prompt is simply the message you send Claude. Most disappointing results trace back not to the model but to a prompt that left out something the writer knew and Claude did not. The CCAO-F exam tests whether you can recognise the parts of a complete prompt and spot which part is missing when output goes wrong.
Why structure matters
Claude has no access to your inbox, your meeting notes or the half-formed intention in your head. It works only from what is in the conversation. A colleague given the same one-line brief would ask three clarifying questions; Claude will usually make reasonable assumptions and proceed. If those assumptions are wrong, the output is polished but useless. Writing a structured prompt is how you answer the clarifying questions before they are asked.
The five building blocks
Think of a good prompt as answering five questions. You do not need a heading for each one, but a prompt that silently skips one is a prompt that will need a second attempt.
| Block | Question it answers | Example fragment |
|---|---|---|
| Task | What exactly should Claude do? | "Draft a two-paragraph reply declining the proposal." |
| Context | What does Claude need to know to do it well? | "We worked with this vendor last year and the relationship is good." |
| Audience | Who will read or use the result? | "The reader is their head of sales, who is not technical." |
| Format | What shape should the output take? | "Plain email body, no subject line, under 150 words." |
| Constraints | What must it include, avoid or respect? | "Do not mention budget. Leave the door open for next year." |
A sixth, optional block is a role or persona ("act as an experienced HR business partner"). Roles help when they change how Claude should think, not merely how it should sound.
Before and after
A product manager wants help with a customer update. Here is the first attempt.
Write an update about the delay.
Claude will produce something generic, probably apologetic, probably too long, and it will have to guess what was delayed and why. Compare the rewritten version.
Draft a customer-facing update announcing that the invoicing feature
promised for 1 November will now ship on 15 November.
Context: the delay is due to extra security testing we chose to do.
Customers are mid-sized finance teams who have been asking for this
feature for months. We have already told our account managers.
Audience: existing paying customers, reading this in an in-app banner
and a follow-up email.
Format: give me two versions. Version A is one sentence for the banner.
Version B is a three-paragraph email with a subject line.
Constraints: be direct and confident, not apologetic. Mention the
security testing as the reason. Do not promise anything beyond the
new date. UK English.
Every block is present. Notice that the second prompt is not clever; it is merely complete. That is the lesson. Specificity beats sophistication.
Verbs that do work
Vague verbs ("help me with", "look at", "do something about") hand the decision back to Claude. Prefer verbs that name an operation: draft, summarise, compare, extract, rank, rewrite, critique, translate, classify, outline. Pair the verb with a measurable quantity where you can: "summarise in five bullets" rather than "summarise briefly".
Putting the important things first and last
Long prompts work, but order matters. State the task up front so Claude knows what the rest of the material is for, then supply context, then restate the format and the hard constraints at the end. If you paste a long document, say what to do with it before the paste and repeat the key instruction after it. Claude reads the whole prompt, but a clear frame at both ends reduces misreadings.
A pre-send checklist
Before pressing enter on anything that matters, run through this list.
- Does the first sentence name the deliverable?
- Have I said who the output is for?
- Have I told Claude the facts only I know (dates, names, decisions already made)?
- Have I specified length, structure and tone?
- Have I listed anything that must not appear?
- Would a new colleague be able to act on this brief without asking me a question?
If the last answer is no, neither can Claude.
Common mistakes the exam likes
Candidates often assume that more words always help. They do not. Padding a prompt with pleasantries or repeating the same instruction three times adds nothing. Equally, candidates assume Claude knows company-specific context it was never given, or expect it to infer an audience from a file name. The exam scenarios typically present a weak prompt and ask what single addition would most improve the result; the answer is almost always the missing block, not a stylistic flourish.
Exam focus
- A complete prompt covers task, context, audience, format and constraints; a role is optional and useful only when it changes reasoning, not just voice.
- Specific, operational verbs (draft, extract, compare) produce more reliable output than vague ones (help with, look at).
- Claude only knows what is in the conversation; facts you hold in your head must be written down.
- When a scenario shows poor output, identify which block the prompt omitted rather than suggesting a longer or more polite prompt.
- Stating the task before pasted material and restating format and constraints after it reduces misreadings on long prompts.
Check yourself
5 questions
1.A new analyst asks what makes a prompt effective for everyday business tasks in claude.ai. Which combination of elements best describes a well-formed prompt?
2.An HR lead types 'Write an email about the new leave policy' and receives a generic, 600-word message that misses the key change. What is the single most effective improvement to the prompt?
3.A strategy analyst needs to summarise a 40-page market report for an executive committee that has ten minutes to read it. Which prompt is most likely to produce a usable result first time?
4.A procurement manager starts prompts with 'Act as an experienced procurement specialist'. What does assigning a role like this actually do?
5.A consultant's standard prompt reads: 'Write a proposal for the client using the attached notes. Make it good. Don't make it too long but cover everything. It should be formal but also friendly. Include pricing.' Colleagues complain that the output varies wildly each time it is used. Which weakness most explains this?