AI for Everyday Work: Writing, Research, Meetings & DataAI work basics · Lesson 2 of 17

The everyday prompt formula

Article · 12 min · 8 min lecture

Video lecture

The everyday prompt formula

10 chapters · about 8 min · full transcript

Coming soon

Chapter 1 of 10

The everyday prompt formula

  • Four ingredients
  • Works in any assistant

The narrated lecture is in production

Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.

Chapters

Four ingredients

You don't need special tricks to write good prompts. Most everyday tasks go well when you include four ingredients. Remember them as W-A-R-F: Who, Aim, Rules, Format.

  • Who: who you are and who the audience is.
  • Aim: what you want the AI to produce and why.
  • Rules: tone, length, things to include or avoid.
  • Format: how the result should look (email, bullets, table, steps).

The template

Who: I'm a [your role]. This is for [audience].
Aim: Please [write / summarize / plan / explain] [what] so that [goal].
Rules: [friendly / formal / simple], [length], include [x], avoid [y].
Format: [email with subject line / 5 bullets / table with columns ...].
My notes: [paste your notes, draft or information]

Before and after

Before: "Write a message about the office party."

After:

Who: I'm the team coordinator. This is for our 25-person team.
Aim: Write a short message inviting everyone to our end-of-year dinner so they reply by Thursday.
Rules: warm and inclusive, under 100 words, mention that vegetarian and halal options are available, avoid alcohol references.
Format: a Teams message with a clear call to action.
My notes: Dinner on 18 December, 7pm, at the restaurant near the office. Reply in the poll.

The second prompt produces a message you can send with a quick check. The first produces a generic invitation you'd have to rewrite.

Three follow-ups that fix most problems

AI rarely gets everything perfect the first time. Instead of starting over, reply with one of these:

  1. "Shorter and simpler." Great for emails and announcements.
  2. "Keep the structure, but change [specific thing]." Keeps what works.
  3. "Ask me what you need to know to make this better." Lets the AI fill gaps by asking you.

Give examples when style matters

If you want a particular style, paste an example: "Here's a message I wrote last month that my team liked. Match this style." Examples are one of the fastest ways to get output that sounds like you.

Save your best prompts

Create a simple document called "My prompts". Each time a prompt works well, save it with a title like "Team announcement" or "Polite follow-up". Replace the specific details with [brackets] so you can reuse it. Within a month, you'll have a personal toolkit that saves hours.

Worked example

Bilal, a customer service team lead in Karachi, needs to explain a new refund process to his team. His first attempt ("explain refund process") gives a generic explanation of refunds. Using the formula, he adds his role, the audience (new agents), the aim (process refunds correctly in the new system), the rules (simple English, numbered steps, include the approval limit) and pastes the policy text. The result is a clear 8-step guide. He checks it against the policy, fixes one step and shares it.

Sample output check

A good response to the dinner prompt is under 100 words, includes the date, time, place and reply deadline, mentions both dietary options, and ends with a clear action ("Please vote in the poll by Thursday"). If any of these is missing, ask for it specifically rather than regenerating.

Break big tasks into steps

For larger tasks, don't ask for everything at once. Ask for a plan first, then work through it one step at a time: "First, list the sections this guide needs. Wait for my approval before writing." Smaller steps give you more control and better results, and they make it easy to spot where something went wrong.

Hands-on: three before-and-after prompts

Try each "after" prompt in your own assistant and compare it with the "before" version.

1. A status update

Before: Write a project update.

Who: I'm a project coordinator. This is for our regional director, who has two minutes.
Aim: Summarize this week's progress on the Jeddah store fit-out so she knows whether to worry.
Rules: plain English, under 120 words, lead with the overall status (on track / at risk / late), no jargon.
Format: one status line, then three bullets: done, next, risks.
My notes: flooring done; lighting delayed 4 days (supplier); signage approved; opening date still 14 Oct.

Typical result: "Status: on track, with one risk. Done: flooring complete, signage approved. Next: lighting installation (now due Thursday). Risk: a further lighting delay would compress the final inspection window; opening still planned for 14 October."

2. A how-to guide for a colleague

Before: Explain how to do expenses.

Who: I'm the finance assistant. This is for new sales staff who have never used our system.
Aim: Explain how to submit an expense claim so it is approved the first time.
Rules: numbered steps, simple English, include the rule that receipts over 50 need a photo, avoid finance jargon.
Format: numbered list of at most 8 steps, then a "common rejections" box.
My notes: [paste the policy text]

3. Planning a small event

Before: Plan a team lunch.

Who: I'm a team lead in Manchester. This is for 12 people, including two vegetarians and one person who doesn't drink.
Aim: Give me three lunch options within a budget of 25 pounds per head (illustrative) that I can book this week.
Rules: walking distance from the city center, inclusive options, no chain restaurants.
Format: a table: option, why it fits, what to check when booking.

Note the last line of the table request: "what to check when booking". Asking the AI to tell you what to verify is a small trick that pays off in every task.

Let the assistant remember your W and R

If you type the same "Who" and "Rules" every day, store them once: custom instructions in ChatGPT, profile preferences or a Project in Claude, a Gem in Gemini, or saved prompts in Copilot. Then your everyday prompt shrinks to Aim, Format and notes. You'll set this up properly in the "Projects, memory and custom instructions" lesson.

Measure it

A prompt is good when the first answer needs only light edits. Track "rounds to a usable answer" for a week. If most tasks take three or more follow-ups, your Who or Rules are too thin.

Pitfalls

  • Leaving out the audience; tone depends on it.
  • Asking for "everything" in one go. Break big tasks into steps.
  • Forgetting to paste the actual information the AI needs.

Key takeaways

  • W-A-R-F: Who (you and the audience), Aim (what and why), Rules (tone, length, include/avoid), Format (shape of the result).
  • Always paste the facts the AI needs; it cannot know your notes, numbers or policies otherwise.
  • Fix drafts with targeted follow-ups (shorter, keep structure but change X, ask me questions) instead of starting over.
  • Save prompts that work, with [brackets] for details, and store your usual Who and Rules in custom instructions or a Project.

Check your understanding

Quick questions to lock in the lesson. They don’t count towards your certificate.

  1. Which ingredient tells the AI who will read the output?
  2. Your AI draft is good but too long. What's the best next step?
  3. Why save prompts with [brackets] instead of the specific details?

Put it into practice

Rewrite three prompts you use regularly using W-A-R-F and save them in a 'My prompts' document.

Enrol for free to save your progress

Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.