Copilot training: what should change in the working day?

Choose a job you can recognise when it is finished

“Get better at Copilot” gives you no way to judge progress. “Prepare the Friday service update from the incident log and team notes, with every open action checked” does. Name the inputs, the person receiving the result, its deadline and the decisions that remain with the team.

Start with one frequent, bounded task. If nobody can agree which file is current or who owns the final answer, settle that first. Those problems will also affect the AI-assisted version.

Prepare for different access in the room

Ask participants to open the approved tool before the session. Check their account, available features and access to the training files. Give them a permitted fallback if a feature is missing, so they can still practise questioning and checking.

Microsoft states that Copilot experiences vary with licensing and organisational configuration. Do not promise that everyone will see the same controls. Demonstrate with the actual setup, and distinguish what the team can do now from capabilities that would require a change.

Make checking part of the job

Ask the learner to explain why an important conclusion is supported. Open the source, compare the date or figure and identify anything that still needs a person to decide. A request for “no assumptions” is an instruction, not a guarantee.

Also check the working output. A chat response saying a spreadsheet has been corrected is not evidence that the relevant cell changed. A drafted email in chat may still need to become a reviewed draft in the mail application.

Return to the next real example

Book a short follow-up around the next occurrence of the job. Ask what happened when the inputs differed: a missing attachment, a renamed column or a colleague's late correction. Improve the working instructions from those exceptions.

Measure preparation, checking and rework as well as generation time. Record whether the output was accepted, what the person needed help with and whether they completed the next job independently. A faster first draft with a longer correction process is not automatically an improvement.

For a small pilot, keep a simple before-and-after record for the same type of task. Avoid turning one good session into an organisation-wide savings estimate.