AI for Work
The beginner's guide

Recipes for Your Job

Twenty ready-to-run task briefs for admin, marketing, finance, research and management. Copy, paste, adapt the nouns, keep the bones.

AI for Work
Chat gives answers. Agents give finished work.
1Today
You type
AI advises, you do the work
2The shift
It types
Agents finish tasks on your computer
3Chapter 4
First task
Delegated, checked, done
Plain English, real receiptsno vendor theatre, no recycled AI hype
Collab365
Mark Jones
Mark Jones · Collab365

It is 8:40 on a Tuesday and you can already see the whole morning. Forty minutes matching receipts to a claims spreadsheet. An hour turning meeting notes into an action list. A contact list two departments have quietly broken in different ways.

None of it is your actual job. All of it is on your list.

This is the bookmark chapter: twenty briefs to paste into an agent tonight, sorted by role. Chapters 1 to 9 explained why they work; this one hands them over.

What a recipe is

A recipe here is three things stapled together. The brief: the exact words to paste, safety rails already written in. A risk light with a time estimate. And what good looks like: the receipt to expect, meaning the agent's own report of what it did, so you can judge the result in two minutes.

The lights follow chapter 6's reversibility test. Green: you could undo the result in five minutes and nothing leaves your machine. Amber: real files, or numbers someone will act on, so it runs on copies and gets reviewed before use.

There are no red recipes here. None of the twenty asks an agent to log into anything, send anything to another human, or spend a penny. Where one brushes an amber rule, I say so next to it.

Every recipe runs, as written, in at least two of chapter 8's tools: point Claude Cowork at a folder, or hand ChatGPT Work the files uploaded or connected. In a Word or Excel file, Copilot's Agent Mode runs it in the file itself. The web-research recipes also suit Perplexity Comet or Claude in Chrome; I flag where the choice matters.

A wooden box of blank recipe cards beside a coffee mug and closed laptop
A recipe is a brief someone has already tested. Pull the card, swap the nouns, run it.
The brief is the recipe.

Every card below is paste-ready, safety rails included. Twenty cards, five roles, none red.

Admin and ops

If your job is keeping the machine running, your recipes are files, lists and documents that arrive messy and must leave tidy.

TimeRisk
1. The shared-drive tidy15 minAmber
2. Meeting notes into an action tracker10 minGreen
3. Two contact lists into one15 minAmber
4. The policy into a checklist10 minGreen
Admin and ops: the four recipes.

1. The shared-drive tidy

The team folder nobody dares reorganise: chapter 4's Downloads job, pointed at work. Amber, about 15 minutes. It touches real files, so it runs on a copy, always.

shared-drive-tidy.txt
I have made a copy of our team's project folder. Work only inside the copy. Sort every file into subfolders by file type, then by year and month using the last-modified date. Do not rename, delete or edit any file. Finish with a report listing every file and where it went, plus anything you were unsure about.

What good looks like: tidy subfolders plus a move report you can scan in two minutes. Nothing renamed, nothing missing.

2. Meeting notes into an action tracker

Raw notes in, an action table out, gaps kept visible. Green, about 10 minutes: it only reads, and the output is a fresh file.

actions-from-notes.txt
Here are my raw meeting notes from the last two weeks. Pull every action, decision and open question into a table with columns: item, type, owner, deadline, source meeting. If an action has no owner or no date, include it anyway and mark the gap. Do not invent owners or dates. Deliver it as a spreadsheet.

What good looks like: every row traces to a meeting, and ownerless actions are flagged, not guessed.

3. Two contact lists into one

Two exports, one truth. Amber, about 15 minutes: this list feeds real mailings, so the agent flags conflicts and you settle them by hand.

contact-list-merge.txt
Here are copies of two exported contact lists. Merge them into one new spreadsheet. Where the same person appears in both, keep one row. Where they disagree, for example two phone numbers, do not choose: keep both values and flag the row. Leave the original files untouched. End with a count: rows in, rows out, rows flagged.

What good looks like: one clean list, a small flagged pile, and a count that reconciles. If not, that is your sixty-second catch.

4. The policy into a checklist

Twelve pages of policy nobody reads, turned into one page somebody will. Green, about 10 minutes. In Word, Copilot's Agent Mode builds it in the document itself.

policy-to-checklist.txt
Attached is a copy of our expenses policy. Turn it into a one-page checklist a new starter could follow, in plain English. Every item must trace to a specific policy section; put the reference in brackets after it. If the policy is ambiguous anywhere, list those points separately rather than guessing.

What good looks like: a section reference on every line. Spot-check three against the policy before it goes anywhere.

Marketing

Marketing recipes lean on the browser and the draft pile. Nothing here publishes or sends anything, per chapter 6.

TimeRisk
5. The competitor scan30 minGreen
6. One piece, five formats15 minGreen
7. Campaign exports into one report20 minAmber
8. The mention sweep15 minGreen
Marketing: the four recipes.

5. The competitor scan

Chapter 5's competitor scan, made weekly: it tightens that brief to the last three months and adds a comparison table. Green, about 30 minutes of the agent's time, not yours. Needs a browsing tool: Cowork, ChatGPT Work, Comet or Claude in Chrome.

competitor-scan-weekly.txt
Visit these 12 competitor websites: [paste your list]. For each one, note what they sell, who they seem to aim it at, pricing if published, and anything announced in the last three months. Then write a two-page briefing note: a comparison table plus five bullet points on where we look different. Use only what the sites actually say. If pricing is not published, write 'not published', never an estimate.

What good looks like: a two-pager where every claim came from a visited page. Spot-check two sites yourself.

6. One piece, five formats

You wrote it once; stop rewriting it by hand. Green, about 15 minutes. Everything returns as drafts for review.

content-repurpose.txt
Here is a blog post we published [attach or paste it]. Draft, as separate files: three LinkedIn posts each taking a different angle from the piece, a five-line email newsletter item, and a short summary for our sales team. Match the tone of the original. These are drafts for my review. Do not post or send anything anywhere.

What good looks like: five drafts that sound like the original, with genuinely different angles, not just lengths.

7. Campaign exports into one report

The monthly copy-paste marathon across ad platforms. Amber, about 20 minutes: these numbers go to your boss, so check a sample against the source files. In Excel, Copilot's Agent Mode is a natural fit.

campaign-rollup.txt
Here are copies of last month's CSV exports from our ad platforms, plus the previous month's combined report. Build one spreadsheet: a tab per platform, and a summary tab showing spend, clicks and leads per campaign with totals. Then write ten lines on what changed since last month. Read figures exactly as exported; never fill a missing number. Flag anything odd instead of smoothing it over.

What good looks like: totals that match the exports on a three-campaign spot-check, and a note that flags odd numbers.

8. The mention sweep

Who talked about you last month? Green, about 15 minutes, browser tools again.

mention-sweep.txt
Search the web for mentions of [company name] and [product name] from the last month. Ignore our own websites and social accounts. Give me a table: where it appeared, date, link, one-line summary, and whether the tone reads positive, negative or neutral. If you find little or nothing, say so plainly. Do not pad the list.

What good looks like: a short honest table with working links. An empty result is valid; a padded one is the failure.

Finance

Every finance recipe is amber, deliberately. Confident wrong numbers are chapter 7's failure mode and money is where they sting, so every brief bans guessing and every receipt gets checked.

TimeRisk
9. The invoice pile20 minAmber
10. The expense cross-check15 minAmber
11. Budget versus actuals, first draft15 minAmber
12. The contract terms table20 minAmber
Finance: the four recipes.

9. The invoice pile

Chapter 1's 38-PDF pile, as a recipe: this is the chapter 1 brief, word for word. Amber, about 20 minutes. Before anything leaves your desk, check five rows against the PDFs.

invoice-pile-brief.txt
Open the folder 'Invoices copy' on my Desktop. It holds 38 supplier invoices as PDFs. Build me one spreadsheet called invoice-summary.xlsx with a row per invoice: supplier name, invoice date, invoice number, net amount, VAT and total. Add a second sheet with a total per supplier. If a PDF will not open or a value is unclear, do not guess. Leave the cell blank and list the file in your report. Ask me before you touch anything outside this folder.

What good looks like: a clean sheet, a per-supplier totals sheet, and blank cells listed honestly in the report. Zero problems on a messy pile deserves suspicion.

10. The expense cross-check

Claims on one side, receipts on the other, an agent doing the matching. Amber, about 15 minutes, though it changes nothing: it only sorts claims into piles.

expense-check.txt
Here are copies of a claims spreadsheet and a folder of receipts as images and PDFs. For each claim row, find the matching receipt and compare amount and date. Change nothing in either place. Give me three lists: claims that match, claims where the numbers disagree, and claims with no receipt found. Put the receipt filename next to every match.

What good looks like: three lists with filenames you can open. Verify two matches and one mismatch before acting.

11. Budget versus actuals, first draft

The month-end commentary nobody enjoys writing. Amber, about 15 minutes: the draft never goes out unedited. In Excel, Copilot's Agent Mode runs it inside the workbook.

variance-first-draft.txt
Attached are copies of this year's budget and the actuals to date. Build a variance table by line: budget, actual, difference, difference as a percentage. Flag every line more than 10% adrift in either direction. Then draft one plain-English paragraph per flagged line describing what the numbers show, clearly marked as a first draft for me to correct. Do not speculate about causes the data cannot show.

What good looks like: arithmetic you can verify in seconds and commentary that describes rather than invents. “The data cannot show why” in a draft is a good sign.

12. The contract terms table

Renewal dates hiding in a folder of PDFs. Amber, about 20 minutes: a wrong notice period costs real money, so the brief demands a page number for every fact.

supplier-terms.txt
This folder holds copies of our supplier contracts as PDFs. Make one table: supplier, start date, renewal date, notice period, payment terms, and the page number where you found each fact. If a contract does not state one of these, write 'not stated' rather than inferring it. Sort by renewal date, soonest first.

What good looks like: a table you can audit. Confirm the dates of the two soonest renewals on the quoted pages.

Research and analysis

The analyst's recipes share one bone: quotes and figures come back verbatim with sources attached, so checking takes minutes, not a re-read.

TimeRisk
13. The source sweep20 minGreen
14. Survey answers into themes15 minGreen
15. The cleaning pass with a change log15 minAmber
16. The two-sides brief15 minGreen
Research and analysis: the four recipes.

13. The source sweep

Ten reports you were supposed to have read by Thursday. Green, about 20 minutes.

source-sweep.txt
Here are links to ten reports and articles on [topic]. Read each one. Build a table: source, publication date, its three main claims, and any figure it cites, quoted exactly with the page or section it came from. Where two sources contradict each other, put both versions in a 'disagreements' section at the end. Do not add sources of your own.

What good looks like: a claims table you can trace, and a disagreements section that stops you citing two contradicting numbers.

14. Survey answers into themes

Four hundred free-text answers, one afternoon back. Green, about 15 minutes.

survey-themes.txt
Column C of the attached spreadsheet holds free-text survey answers. Group them into themes. Give me a table: theme, how many answers fall into it, and two example quotes per theme copied word for word with their row numbers. If an answer fits no theme, put it under 'other' rather than forcing it. Do not paraphrase the quotes.

What good looks like: theme counts that sum to the number of answers, and quotes that match their rows.

15. The cleaning pass with a change log

Messy data in, clean data out, every change on record. Amber, about 15 minutes: it rewrites real data, so it works on a copy and logs every touch.

csv-clean.txt
Here is a copy of a messy CSV. Clean it into a new file: one consistent date format, trimmed spaces, one row per record, blank rows removed. Keep a second file logging every change you make, row by row. Never guess a value: if a cell is ambiguous, leave it as it is and log it as a question for me. The original file stays untouched.

What good looks like: a clean file, a change log, a short questions list. The log is the receipt; skim it first.

16. The two-sides brief

For the question your team keeps arguing about. Green, about 15 minutes, browser tools again.

two-sides-brief.txt
I need to understand the debate around [contested question]. Search for credible material on both sides. Give me a one-page brief: the strongest three arguments for, the strongest three against, each with its source linked, plus a short list of points where the two sides are simply using different definitions. Do not tell me which side is right.

What good looks like: six linked arguments and a definitions list. If one side reads like a caricature, re-brief: argue each side as its supporters would.

Manager

A manager's recipes produce drafts and prep, never decisions. The judgement stays yours; the assembling does not have to.

TimeRisk
17. The Monday report15 minGreen
18. The one-to-one prep sheet10 minAmber
19. A thread into a decision memo10 minGreen
20. The meeting diet10 minGreen
Manager: the four recipes.

17. The Monday report

Chapter 2's recurring status doc, and the star of chapter 11, where it learns to write itself. Green, about 15 minutes by hand.

monday-report.txt
In this folder are my team's status notes from last week and the report I sent the previous Monday. Draft this week's report in the same structure and length: done, in progress, blocked, next week. Pull only from the notes. Where a project has no update, write 'no update received' rather than carrying last week's text forward. Leave it as a draft for me to edit.

What good looks like: a draft in your voice and format, silence made visible. Watch for stale text dressed up as news.

18. The one-to-one prep sheet

Ten minutes of prep you never quite get to. Amber for a different reason, about 10 minutes: these are notes about a real person. Use your work account, and keep anything HR-serious away from agents entirely.

one-to-one-prep.txt
Here are my notes from the last three one-to-ones with [first name], plus our shared actions list. Make a one-page prep sheet: open actions and their ages, topics I promised to revisit, and three suggested questions based only on the notes. This is for my eyes only; nothing here gets shared or sent.

What good looks like: a page that reminds you what you promised. Questions should trace to the notes.

19. A thread into a decision memo

Forty emails, one actual question. Green, about 10 minutes. In Word, Copilot's Agent Mode can draft the memo in place.

thread-to-memo.txt
Attached is an exported email thread about [decision]. Turn it into a one-page memo: the question, the options raised, who argued what, in neutral language, and what remains unresolved. Attribute a view only to someone who clearly stated it in the thread. End with the single question that, once answered, unblocks the decision.

What good looks like: a memo everyone in the thread would call fair, ending on one sharp question. Check the attributions.

20. The meeting diet

The calendar audit you keep postponing because you are in meetings. Green, about 10 minutes.

meeting-diet.txt
Here is a list of my recurring meetings: name, length, attendees, purpose [paste it]. For each one, tell me whether it could be an email, a shorter meeting, or should stay, with one line of reasoning from the purpose given. Then draft a tighter agenda template for each meeting you recommend keeping. I make the decisions; you are producing a first pass.

What good looks like: an honest first pass you can disagree with, plus agenda templates worth stealing.

Swap the nouns, keep the bones

None of these twenty will fit your job exactly. Good: they are recipes, not spells.

The nouns are yours: file names, column headings, the topic, the 10% threshold, the competitor count. Swap freely.

The bones are what every brief above shares, and they do not move:

  • Work on a copy. The original is never in play.
  • Name the output shape. A table with these columns, a one-page memo, a draft in this structure.
  • Never guess. Gaps get flagged, not filled.
  • Define done. Totals row, page references, closing summary: finished means something specific.
  • Draw the do-not line. What stays untouched, uninvented and unsent.

Strip those out and a recipe collapses back into a wish.

Want the invoice pile for timesheets? Swap invoices for timesheets, supplier for person, VAT for overtime, and leave every safety line where it stands. Same bones, different dinner.

When there is no card for the job

When nothing fits, build your own card from chapter 5's five questions. Answer them in order and the brief writes itself:

  • What does finished look like? The outcome, not the steps.
  • What am I handing over? The files, links and examples.
  • What are the rules? Formats, thresholds, things to leave alone.
  • How will we both know it is done?
  • When should it stop and ask me?

Write the five answers as plain sentences and stack them. Every card here was built exactly that way.

Twenty cards is a start, not a library. The habit that matters is reaching for one the next time a Tuesday morning tries to eat itself.