Sample course · Beginner · 9 lessons

Getting real work done with AI assistants

Practical prompting, checking and safe habits for everyday office work

A hands-on course in using AI assistants such as ChatGPT, Claude, Gemini or Copilot for real tasks: writing clear prompts, giving the right context, iterating on drafts, and summarising, drafting and analysing with confidence. You will finish able to check what an assistant produces, decide what is safe to share with it, and turn the tasks you repeat into reliable workflows.

What you'll learn

  • Judge which everyday tasks suit an AI assistant and which do not
  • Write prompts that state the task, the context and the format you want
  • Improve a first draft through focused follow-up requests
  • Draft emails and documents that sound like you
  • Summarise long documents and meetings without losing decisions and actions
  • Use an assistant to compare options and analyse simple data, and verify the numbers
  • Check output and protect private information before it goes anywhere
  • Build reusable prompt templates and workflows for repeated tasks

Who it's for

  • Office and admin staff who have tried an AI assistant but get patchy results
  • Small business owners and freelancers who want to save time on writing and admin
  • Anyone new to AI assistants who wants practical, safe habits from the start

Syllabus

  1. 1.Asking well

    What assistants are good and bad at, how to write a prompt that gets a useful answer first time, and how to improve it from there.

    1. What AI assistants are good at, and where they trip up
    2. A prompt that works: task, context and format· checkpoint
    3. Treat the first answer as a draft
  2. 2.Everyday work tasks

    Drafting in your own voice, summarising long material without losing what matters, and using an assistant to compare options and work with numbers.

    1. Drafting emails and documents that sound like you· checkpoint
    2. Summarising documents and meetings without losing what matters
    3. Comparing options and working with numbers· checkpoint
  3. 3.Working safely and building habits

    Checking what comes out, deciding what never goes in, and turning the tasks you repeat into reliable workflows.

    1. Checking output before it goes anywhere
    2. Privacy: what to share and what never to paste· checkpoint
    3. Turning one-off prompts into repeatable workflows

Lesson 1

What AI assistants are good at, and where they trip up

What you'll learn: what AI assistants genuinely help with at work, where they reliably go wrong, and how to sort your own to-do list into good and bad fits.

Meet Rosa and her week

Rosa is the office manager at Hollins Landscape Design, a firm of 12 people who design and build gardens. She handles everything that is not digging or drawing: client emails, supplier orders, the newsletter, meeting notes, the monthly report for the two directors, and a steady stream of small surprises.

Her firm has just given everyone access to an AI assistant. Rosa has tried it a few times and found it hit and miss. One day it wrote a lovely email in seconds; the next it produced three paragraphs of waffle and got a date wrong. She has decided to give it a fair trial with one real week of work, and this course follows that week.

On Monday morning, her list looks like this:

  • Reply to Mr Okafor, a client who is upset that his patio is two weeks late.
  • Write the spring newsletter for past and current clients.
  • Turn Tuesday's 90-minute project meeting into notes and actions.
  • Compare three quotes from paving suppliers.
  • Produce the monthly report for the directors.

What we mean by an AI assistant

By AI assistant we mean a chat tool built on a large language model: ChatGPT, Claude, Gemini, Microsoft Copilot and others. You type a request in ordinary language and it replies in writing. Many can also read files you upload, search the web, or work inside email and document software, but these features vary between products and plans and change often. This course sticks to skills that work in any of them.

One thing is worth knowing about how they work. An assistant writes its reply by predicting, word by word, what a helpful answer would most likely say, based on patterns learned from huge amounts of text. That is why it is so fluent. It is also why it can produce something that sounds right and is not: it is aiming for plausible, and plausible is usually, but not always, correct.

A useful way to think about it

The most helpful picture is a bright temp on their first day. They are quick, well read, never tired and happy to redo a task five times. They can write in almost any style and summarise a long document in moments.

But they know nothing about your firm. They have never met Mr Okafor, have not seen the paving quotes and do not know that the directors hate long reports. If you give them a vague instruction, they fill the gaps with sensible-sounding guesses. And they will rarely say "I'm not sure"; they hand over their work with the same confidence whether it is right or wrong.

Treat the assistant like that temp. Brief it well, check its work, and never let it send anything in your name unread.

Where assistants shine

Assistants are consistently good at:

  • Drafting: emails, letters, announcements, job adverts, first versions of almost anything.
  • Rewriting: shorter, friendlier, more formal, simpler, in a different structure.
  • Summarising: pulling the main points out of long text you provide.
  • Brainstorming: options, angles, questions you had not thought of.
  • Explaining: a confusing clause, a technical term, a spreadsheet formula.
  • Structuring: turning messy notes into a tidy list, table or plan.

Where they trip up

They are much weaker at:

  • Facts they were not given: your prices, your dates, your clients. Anything specific to your work must come from you.
  • Recent events: their knowledge stops at a training cutoff unless a web search feature is switched on and used.
  • Precise arithmetic on lots of numbers: they can slip, especially with long tables.
  • Exact quotes and references: they can invent a plausible-looking source.
  • Judgement calls about people: they do not know your colleagues or clients.

Sorting Rosa's list

Rosa sorts her week by asking two questions of each task: is this mostly writing or rearranging information I can supply, and how bad would a mistake be?

TaskGood fit?Why
Reply to Mr OkaforYes, with careDrafting is a strength; the facts and tone must be hers
Spring newsletterYesDrafting from her notes; she checks every claim
Meeting notes and actionsYesSummarising a transcript she provides
Comparing paving quotesPartlyGood for laying out differences; totals need checking
Monthly reportPartlyGood for structure and wording; figures must come from the accounts

None of the tasks is a straight "no", but two come with a clear warning. Rosa also notices that nothing on the list is "find out a fact I don't know", which is where assistants are least trustworthy.

What a good week will look like

By the end of this course, Rosa will have:

  1. A way of writing requests that gets a useful first draft most of the time.
  2. A habit of improving drafts in a few quick rounds rather than starting over.
  3. Methods for drafting, summarising and comparing that keep her in control of the facts.
  4. A checklist for anything that leaves her desk.
  5. Clear rules for what she never pastes into an assistant.
  6. A small library of reusable prompts for the jobs she does every month.

Recap

  • An AI assistant is a chat tool built on a language model; product names and features vary and change.
  • Think of it as a bright temp on their first day: fast and capable, but knowing nothing about your work unless told.
  • It is strong at drafting, rewriting, summarising, brainstorming, explaining and structuring.
  • It is weak at facts you did not supply, recent events, heavy arithmetic, exact references and judgement about people.
  • Sort tasks by whether you can supply the information and how costly a mistake would be.

Lesson 2

A prompt that works: task, context and format

What you'll learn: how to write a request that gets a useful first answer by stating the task, giving the context and asking for the format you need.

Rosa's first attempt

Rosa starts with the most pressing job on her list: Mr Okafor's complaint. His new patio should have been finished a fortnight ago, and his email is short and angry. She types:

Write a reply to a client complaint.

The assistant obliges with a polished, generic letter. It thanks the client for their feedback, apologises "for any inconvenience", promises to "look into the matter" and signs off "Kind regards, [Your Name]". It is grammatically perfect and completely useless. Mr Okafor would be even angrier.

The assistant did exactly what it was asked. The problem is that Rosa asked for almost nothing. It did not know what went wrong, who Mr Okafor is, what the firm can offer or how Rosa writes. So it guessed, and guesses are generic.

The sandwich counter

Think about ordering at a sandwich counter. Say "a sandwich, please" and you will get something edible, but probably not what you wanted. Say "chicken and avocado on wholemeal, no mayo, toasted, to take away" and you get exactly your lunch.

A prompt works the same way. The assistant can make almost anything, but it cannot read your mind. Every detail you leave out, it fills with the most average choice.

The three essentials

Almost every good prompt contains three things.

The task

What exactly do you want produced? "Write a reply" is a start. "Write an email reply that apologises, explains the delay and gives a new completion date" is a task the assistant can actually aim at.

The context

What does the assistant need to know to do it well? This is the part people skip, and it makes the biggest difference. Context includes the facts, the audience, the background and what you are trying to achieve. The assistant knows nothing about your situation except what you tell it.

The format

What should the result look like? Length, tone, structure, and anything it must include or avoid. "Under 150 words, warm but professional, no jargon, end with my direct phone number" removes a lot of guesswork.

Rosa's second attempt

Rosa tries again, this time with all three. Her prompt reads:

Write an email reply to a client, Mr Okafor, whose new patio is two weeks late. He is frustrated and his email was short and sharp.

What happened: our stone supplier delivered the wrong colour of paving, and we refused it. The correct stone arrives this Thursday. Our team will finish the patio by next Wednesday.

What we can offer: a free planting of the two large pots by his back door, which he asked about in the spring.

Format: under 150 words, plain and warm, a genuine apology without grovelling, no phrases like "any inconvenience". Sign off as Rosa, Office Manager, with my direct line 01632 960 418.

The draft that comes back is far better. It names the problem honestly, gives the new date, offers the planting and sounds like a person. It is not perfect, but it is a solid starting point that Rosa can finish in a minute.

A fuller checklist

The three essentials cover most requests. For bigger or more important tasks, a few extras help.

IngredientThe question it answersRosa's example
TaskWhat should be produced?An email reply to a complaint
ContextWhat does it need to know?The delay, the cause, the new date
AudienceWho will read it?An annoyed long-standing client
GoalWhat should the reader do or feel?Feel heard and trust the new date
ConstraintsWhat must it include or avoid?No "any inconvenience"; include the offer
FormatWhat shape, length and tone?Under 150 words, plain and warm
ExampleWhat does good look like?One of her past emails (Lesson 4)

You do not need every row every time. A quick question needs a quick prompt. But when the first answer disappoints, this table usually shows what was missing.

Let the assistant ask you

If you are not sure what context matters, you can turn the job around. Add a line like this to the end of your prompt:

Before you write anything, ask me up to three questions about anything you need to know.

The assistant will often ask exactly the questions a thoughtful colleague would: "Has Mr Okafor been told about the supplier problem before?" "Do you want to offer anything to make up for the delay?" Answering them takes a minute and saves several rounds of correction.

Common habits that do not help

Some popular prompting tricks matter less than people think.

  1. Shouting. Capital letters and "VERY IMPORTANT" rarely beat a clear, calm instruction.
  2. Magic phrases. Secret formulas that promise better answers come and go. Clear tasks and real context work across every assistant.
  3. Excessive politeness. Courtesy does no harm, but "please" cannot replace missing information.
  4. Very long role-play setups. "You are a world-class communications expert" can help set a tone, but it adds nothing if the facts are missing.

Recap

  • Vague prompts get generic answers, because the assistant fills every gap with the most average choice.
  • Like ordering at a sandwich counter, the detail you give is the detail you get.
  • Every good prompt states the task, gives the context and specifies the format.
  • For bigger jobs, add the audience, goal, constraints and an example.
  • When unsure what to include, ask the assistant to ask you questions first.

This lesson ends with a 2-question checkpoint, graded in the app.

7 more lessons in this course

Start it in Akadyo to read on, take the checkpoints and keep your place, with a tutor beside every lesson.