Anatomy of a strong automation prompt

Free sample lesson from Prompting for Automation and Workflow Efficiency · about 10 minutes · no payment or email needed

In this lesson you learn the five parts of a clear prompt by turning rough weekly notes into a status update with the same structure every time, flagging anything unclear instead of guessing.

The scenario

Every Friday you write a status update email for your manager from your own notes. It takes 40 minutes and always reads differently.

A weak prompt and a strong prompt

Weak prompt: Write my weekly update.

The AI invents progress you did not make, because you gave it nothing to work from.

Strong prompt, in five parts:

  • Role: Act as a project coordinator writing for a busy manager.
  • Context: Below are my notes for this week. Audience: my manager, who reads for 30 seconds.
  • Task: Turn the notes into a weekly status update.
  • Format: Three headings: Done, In progress, Needs a decision. Maximum 120 words in total.
  • Limits: Use only what is in the notes. If something is unclear, list it under "Questions for me".

What the strong prompt returns

The AI returns the same clean structure every week and asks you about anything unclear instead of guessing.

Why it works

Each part of the prompt does a different job.

  • Role and audience shape the tone and the level of detail.
  • A fixed format makes the output predictable, which is what automation needs.
  • Limits stop the AI from inventing work that did not happen.

The five parts of a clear prompt

A clear prompt has five parts: Role, Context, Task, Format and Limits. Together they tell the AI who it is writing as, what is true, what to produce, what shape it should take and what to avoid.

The point of the structure is simple: the AI fills any gap you leave with a confident guess, so the more you supply, the less it invents.

  • Role: whose voice the AI writes in
  • Context: the true facts it must work from
  • Task: exactly what you want produced
  • Format: length and structure
  • Limits: tone, things to avoid, and "use only the facts above"

Watch out

AI fills gaps with confident guesses. If your notes are thin, the output will contain invented details. Always read before you send.

Try it yourself

Paste this into ChatGPT, Claude or your organization's approved AI tool and run it. Then change the facts to your own and run it again, and compare the two drafts.

Act as a project coordinator writing for a busy manager.
Context: Below are my notes for this week. Audience: my manager, who reads for 30 seconds.
Task: Turn the notes into a weekly status update.
Format: Three headings: Done, In progress, Needs a decision. Maximum 120 words in total.
Limits: Use only what is in the notes. If something is unclear, list it under 'Questions for me'.
Notes:
- Finished the supplier contract draft; legal has it
- Started the Q1 budget; waiting on two team numbers
- Customer onboarding checklist: not sure who owns the final sign-off
- Office move date still not confirmed