Guided labFree preview
Guided lab:you'll work with the real tools, usually with your own free account. Follow the steps below at your own pace.
Practice files are under Lab resources on this page. Everything in them is made up.
Goes with Brief AI like a new colleague · About 20 minutes · Any AI assistant, free tier
Send a lazy prompt, see the generic answer it gets, then rebuild the same request with the six parts of the briefing card and compare the two answers side by side.
weekly-sync-notes-messy.txt: rough notes from a weekly sales and operations meeting at Kavora Workspace Solutions, an invented office furniture company with offices in Pune, Bengaluru, Hyderabad and Dubai.Everything in the practice file is made up. Practise with it, not with your own team's notes.
Start a new chat. Paste this, then the whole practice file underneath:
Summarise these notes and write an email to the team.
[PASTE THE MEETING NOTES HERE]
Read the answer, and score it from 1 (useless) to 5 (I would send it as is). Save it somewhere: you'll compare it in step 4.
Check: look for things the AI had to guess. Who is the email from? Who is "the team"? Did it give deadlines that aren't in the notes? Did it decide who calls Rohan, when the notes left that unclear?
Before you write the new prompt, answer the six questions on paper or in a note. Here is one way to fill it in for this task:
| Part | For this task |
|---|---|
| Role | An operations coordinator who writes short, clear follow-up emails |
| Context | Weekly sync at Kavora, 27 October. I'm Neha, I took the notes. Sneha was on leave. |
| Task | Turn the notes into a follow-up email with decisions and actions |
| Audience | The six people who attended, plus Sneha. Busy, reading on their phones. |
| Format | Subject line, three-line summary, an actions table, open questions, next meeting |
| Limits | No invented owners or dates. Flag anything unclear. Under 250 words before the table. |
Start another new chat (so the first answer doesn't steer this one). Paste:
Role: You are an operations coordinator at a mid-sized office furniture
company. You write short, clear follow-up emails that people actually read.
Context: These are my rough notes from our weekly sales and operations sync
on Tuesday 27 October 2026. I am Neha Iyer (operations) and I took the notes.
Sneha Joshi was on leave and needs to catch up from this email.
Task: Write the follow-up email to everyone who attended, plus Sneha.
Audience: Busy sales, finance, operations and warehouse colleagues, mostly
reading on their phones. They want to know what was decided and what they
personally have to do.
Format:
- A subject line.
- A summary of the meeting in no more than three lines.
- A table of actions with the columns: Action | Owner | Deadline | Notes.
- A short list of open questions that nobody owns yet.
- The date of the next sync.
- Sign off as Neha.
Limits:
- Use only what is in the notes. Do not invent owners, deadlines or numbers.
- If an owner or deadline isn't clear, write "not decided" or "not set".
- Flag anything the notes left unclear, and don't resolve it yourself.
- Keep everything above the table under 150 words.
Notes:
[PASTE THE MEETING NOTES HERE]
Put the two answers side by side and score the second one.
What good output looks like:
Go through the briefed answer against the notes, line by line:
If something is wrong, give one specific round of feedback in the same chat, for example: The call to Rohan should be marked as "Kiran, to confirm with Vikram". Change only that row.
| Lazy prompt | Briefed prompt | |
|---|---|---|
| Score (1–5) | ||
| Actions found | ||
| Invented owners or dates | ||
| What you'd still fix by hand |
Keep your briefed prompt. With the names and details swapped out, it becomes your own meeting follow-up template in Lab D.