Copilot training for small business teams: what to teach in the first 30 days

A 30-day Copilot training plan for small business teams: free vs paid seats, the tasks staff take to fastest, a weekly update prompt, and how to measure it.

Someone in a training session has two spreadsheets open, each holding a long column of ID numbers. Normally they would write a lookup formula, drag it down, and then scan for errors. This time they drag both files into Copilot and ask which IDs show up in one list and not the other. A clean list of mismatches comes back in a few seconds.

Across our Copilot sessions, moments like that get a bigger reaction than a six step prompting formula. People learn Copilot fastest when they see it handle a piece of their own work. The plan below is built around that, and around the parts of Copilot that trip people up. If you're an owner or manager of a team already running on Microsoft 365, we'll show you how to get started.

First, sort out which Copilot your team has

Microsoft sells two levels, and the names keep changing. (Microsoft 365 Copilot was recently renamed Microsoft Copilot, so you'll see both names for a while.)

Copilot Chat comes with eligible Microsoft 365 business plans at no extra cost. It answers from the web and from whatever you give it: pasted text, uploaded files, and files you point it to. Inside Outlook it can also work with your inbox, calendar, meetings and some chats.

The paid Copilot license is an add-on. For businesses with up to 300 users, Microsoft sells it as Copilot Business, listed at $21 per user per month on an annual commitment as of October 2026. The main thing you pay for is what Microsoft calls work grounding: Copilot can search across your email, Teams chats, meetings, calendar and files on its own, without you uploading anything. Paid seats also get the full Copilot experience inside Word, Excel, PowerPoint and Teams, priority access when the service is busy, and Microsoft's built-in agents such as Researcher and Analyst. Microsoft lays out the differences in its Copilot Chat overview.

About half of our trainings ran on free Copilot Chat and the rest on paid seats. For most of what we teach in the first month, the difference was small. Uploading a spreadsheet and asking questions about it works on both. So does cleaning up a messy file and asking for a summary of an email thread.

The difference shows up when someone wants one answer drawn from everywhere at once: email, Teams chats, meeting transcripts and shared files. Free Copilot Chat can read your inbox inside Outlook, but only a paid seat can search all of those sources together and find what it needs on its own.

Our advice to owners: start everyone on Copilot Chat. Buy paid seats first for the people whose work is spread across meetings, Teams threads and shared files, such as managers, project leads and analysts. Add more seats once you can see who is actually using it.

Before day one: check who can see what

If you're buying paid seats, do this before training starts. Copilot only shows people files they already have permission to open. The catch is that many small businesses have shared folders that are open to everyone, because nobody ever needed to lock them down. Once Copilot can search everything a person has access to, an old salary spreadsheet in a company-wide folder becomes much easier to find.

Microsoft notes that SharePoint's sharing settings start at the most permissive option by default. Its guide to getting ready for Copilot walks through tightening them. If an IT provider manages your Microsoft 365, ask them to review sharing on your main SharePoint sites and OneDrive folders before the paid licenses go out.

Week 1: navigation, then a first win with a spreadsheet

The most common frustration we hear is about finding things. Copilot's layout doesn't match ChatGPT or Claude, and it isn't obvious where things live. In our sessions people struggle to find prompts they saved, they don't know what Notebooks are for, and a week later they can't find the chat where they worked something out. Answers can also be weaker than what people are used to from other tools, which makes good prompts matter more. A tool people can't find their way around gets abandoned, so we spend real time on this in week one:

• where saved prompts live and how to reuse them
• how to rename and find past chats
• when to use a Notebook, which is best for an ongoing project where you keep adding files and notes and coming back to them
• the difference between Copilot Chat in the browser and Copilot inside Outlook

Then we give people a spreadsheet task, because it's where reactions are strongest. Comparing two lists of IDs is a good first exercise. It's internal, the answer is easy to spot-check, and it replaces formula work that crowds out the parts of the job that need a person's attention.

Week 2: turning messy data into clean spreadsheets

Once people trust Copilot with a spreadsheet, show them it can build one from material that isn't a spreadsheet at all.

In one session we took a raw data export in XML, the kind of file that looks like code to most people, and asked Copilot to match each record to a client report by ID number. The result was a clean spreadsheet with one row per client and the details of each upload laid out in columns. Before, someone would have built that by hand, and those hours would have come out of their other priorities.

Have each person bring an export, a report or a list they rebuild regularly, and work on that. Good first tasks are internal, repeat often, and produce output you can check at a glance. Tasks like that can eventually run without anyone checking every result. Save anything that goes to customers or moves money for later, when someone will review each output.

Week 3: email

A lot of a team's project knowledge lives in email, and email is famously disorganized. Decisions, dates and client requests sit across dozens of threads. Copilot is good at bringing order to that.

The uses that landed best in our sessions:

• Asking Copilot to pull back everything about a project: what was decided, what's still open, who's waiting on what.
• A weekly pull of email context into the projects someone is working on, so their notes stay current without copy and paste.
• A Monday "state of the union": what happened last week, what might have been missed, and what needs a follow-up.

The Monday report is a good one to set up as a habit, because it catches the follow-up that would otherwise sit unanswered until someone chases it. Asking about a project or for the Monday report works on free Copilot Chat when you do it inside Outlook, since Copilot can read your inbox there.

Week 4: the weekly update for your manager

This is the prompt that both employees and managers ask us for after a session. Writing a weekly update takes time because the week's work is scattered: some of it is in email, some in Teams, some in meeting notes, some in documents. Copilot can gather it into one draft.

Using my Microsoft 365 activity from this past Monday through today (emails, Teams chats and channel posts, meetings and transcripts, calendar, and documents I created or edited), write a weekly update for my manager. It will be pasted into an email.

Format: bullet points only, under 250 words, first person, professional but plain tone. Open with a one-line summary of the week.

Sections:
1. Project progress: the main projects or workstreams I worked on. Identify and group them yourself from my activity. For each, give the result or current status in one line, not the activity.
2. Day-to-day work: recurring or routine tasks that took meaningful time. Combine into 2-4 bullets.
3. Escalations and unplanned work: any urgent issues, fire drills, or escalations that pulled my time. State what happened, how it was resolved (or its current status), and roughly how much time it took if that's evident.
4. Blockers and risks: anything stalled or waiting on someone, and who or what I'm waiting on.
5. Next week: top 3 priorities based on open threads, upcoming meetings, and unfinished documents.

Rules:
- Prioritize outcomes and decisions over a log of meetings and emails.
- Weight items by time and impact. Skip minor items.
- Exclude personal, HR, and other sensitive content.
- If you're inferring a status rather than seeing it stated, mark it "(verify)".
- After the summary, list the source items you relied on (meeting names, thread subjects, file names), separate from the email text, so I can check them.

A few notes on why it works. The "(verify)" rule and the list of sources at the end let the person check the draft in a minute or two before it goes to their manager. The rule about outcomes over activity keeps it from turning into a list of every meeting attended.

This prompt needs a paid Copilot license to work as written, because it asks Copilot to search Teams, meeting transcripts and documents on its own. On free Copilot Chat, a narrower version works inside Outlook, where Copilot can see your email, calendar and some chats and meetings. It's a good reason to start your paid seats with managers and project leads.

Day 30: ask people what they're using it for

At the end of the month, send a short survey: what are you using Copilot for, and roughly how much time does it save you in a week?

After one of our sessions, a survey like this went to a 200-person division. Added up, people estimated Copilot was saving them 276 hours a week on day-to-day tasks. That figure is self-reported, so it's a rough guide to the size of the gain. What made the survey valuable was the list of tasks people named. It showed which uses had stuck and which teams needed a second session.

Use your own results the same way. The tasks people name tell you what to teach next, and the people who name the most tasks make good go-to helpers for their teammates. Microsoft's Copilot adoption page for small businesses has a downloadable success kit with checklists and template emails you can send to staff.

How we run Copilot training

Our AI training sessions use your team's own spreadsheets, inboxes and reports in whichever version of Copilot you have, and we help decide who should get paid seats before you buy them. If you're still choosing a tool, our comparison of Copilot and Claude for teams covers which fits which kind of business, and our guide to running an AI workshop for employees covers how to structure the session itself. We work on-site around Rochester and Western New York and remotely with teams anywhere.