Break down an office task

What you will learn

• How to split one office task into small steps an AI tool can handle
• How to turn meeting notes into a follow-up email and a task list
• How to review AI output before you send it to anyone
• Why your company's data rules come before any prompt

The idea

Many office tasks are really several tasks in one. "Follow up on the meeting" means: pull out the decisions, list who does what by when, and write an email people will actually read. If you ask for all of that in one line, the tool has to guess what matters. Splitting the task into steps gives you better results and makes each part easier to check.

A simple pattern is extract, check, then write. First ask the tool to pull out the facts: decisions, tasks, owners and dates. Check that list against your notes. Only then ask it to write the email from the checked list. That way a mistake gets caught before it spreads into a polished message.

Always review before sending. AI can give a task to the wrong person, invent a deadline, or make a polite note sound too firm. You are the sender, so you are responsible for what the message says.

Before you start, check your company's rules. Many organisations have a policy on which AI tools staff may use and what data can go into them. Meeting notes often contain client names, budgets or personal details. If you are not sure, remove or replace those details, or ask your manager. Also look at the tool's privacy settings, the options that control whether your chats are stored or used to improve the tool. Give the right context has more on deciding what to leave out.

Example

Priya has rough notes from a project meeting. She replaces the client's name with "Client A" and deletes a colleague's phone number. Then she sends step one:

From these meeting notes, list:
1. Decisions made
2. Tasks, each with an owner and a due date
If an owner or date is not in the notes, write "not stated". Do not guess.

Notes:
[pasted notes, client name replaced]

The list shows one task with "not stated" as the owner, and one date the tool read as the 13th instead of the 15th. Priya checks her notes, adds the owner and fixes the date. Then she sends step two:

Using only the corrected list below, write a short follow-up email to the team.
Under 150 words. Start with the decisions, then the tasks as a bullet list.
Friendly and clear. Do not add any new commitments.

[corrected list]

She reads the email once more as if she were on the team, puts the client's real name back in, and sends it.

Practice now

1. Take the notes from a recent meeting, or write five lines of made-up notes.
2. Remove or replace names, clients, figures and anything private.
3. Ask any AI tool to extract decisions and tasks, with owners and dates, and to write "not stated" where something is missing.
4. Check the list against your notes and fix anything wrong.
5. Ask it to write a short email using only the corrected list.
6. Read the email as if you were the person receiving it.

At the end you should have a checked task list and a draft email ready for your own final review.

Copy this template

I need to turn meeting notes into a follow-up. Work in two steps and stop after step 1.

Step 1: From the notes below, list:
- decisions made
- tasks, each with an owner and a due date
Write "not stated" when an owner or date is missing. Do not guess or add tasks.

Step 2 (only after I confirm the list): write a follow-up email to [audience].
Length: under [number] words. Tone: [for example, friendly and direct].
Structure: decisions first, then tasks as a bullet list.

Mark anything in the notes that is unclear or that you are unsure about.

Notes (sensitive details removed):
[paste notes]

Asking AI to flag uncertainty does not make its answer correct. Keep checking the parts that matter.

Check the output

• Is every task from your notes on the list, with nothing extra added?
• Is each owner and date correct, or clearly marked "not stated"?
• Does the email promise anything that was not agreed in the meeting?
• Is the tone right for the people receiving it?
• Have you put back any names you replaced, and kept out anything that should stay private?

Common mistakes

• Asking for everything in one prompt. Mistakes hide inside a polished email. Extract the facts first, check them, then write.
• Pasting notes before checking company policy. Client and staff details may not be allowed in outside tools. Check the rules or remove the details.
• Sending without reading. A wrong owner or date in a team email causes confusion. Read the whole message before you press send.
• Letting the tool fill gaps. If a date was never set, the tool may invent one. Tell it to write "not stated" instead.