--- title: "One-day Copilot training in Italy · Davide Scalera" description: "What 8 hours of Copilot training should cover for a team in Italy: where the tool goes wrong, how to ask, what to save. And how to check a programme." url: https://davidescalera.it/en/guides/one-day-copilot-training-in-italy lang: en --- # One-day Copilot training for a team in Italy: what happens in the day, and how to check the programme We’ve been sent an 8-hour Copilot programme for our people in Italy: is it any good? short answer A good day of Copilot training has three parts: understanding what the tool does and where it goes wrong, learning to ask with a brief, and saving what works so the group keeps it. Exercises use participants’ real tasks, in their working language; the first result comes within half an hour; the usage rules sit inside every part. by **Davide Scalera**, trainer on Microsoft Copilot, Claude and Gemini, in English and Italian · updated 11 October 2026 ## What should an 8-hour Copilot programme contain? Three movements, in this order. ▸ Understand: what Copilot does with your data, why it sometimes gets things wrong, who checks the result. ▸ Ask: write a request that works first time, on the tasks people do every week. ▸ Save: turn the requests that work into material the group owns, which someone opens again the next day. Before any content, a good programme knows which licence the people in the room have. Copilot Chat and the full Microsoft Copilot (formerly Microsoft 365 Copilot) licence do different things. A programme written for one and delivered to people who have the other shows features nobody will find again at their desk. In a group this is easy to miss: the licence mix in the Italian office is not always the one at headquarters. The usage rules, meaning what goes in, what doesn’t and what gets read again, belong inside each part, at the moment they are needed. Left to a final chapter, they arrive when attention has run out. ## How is the day split? Eight hours can run as one full day or as two half days a few days apart. The second shape works better: between the two halves people try things on their own work and come back with their own questions. The sample programme I use splits each half day into three blocks, with two short breaks. The breaks come before people get tired, because a group that stops when it is already worn out restarts worse. The first concrete result arrives within the first half hour. Everyone takes a task of their own, an email to write or a document to summarise, and leaves with a draft they can use. It settles the doubt that the tool isn’t for them, and from there the group works differently. Inside every block the order is the same: first I show it, then we do it together, then you do it on your own files. ## Part one: what does Copilot do, and where does it go wrong? The day starts with how it works, in plain words, because that is where both the fear and the wrong expectations come from. ▸ What it sees: Microsoft says Copilot only surfaces organisational data that the person already has at least view permission for. That removes a common fear and raises a useful point: if your shared folders are a mess, Copilot will make it visible. ▸ Where it goes wrong: Microsoft also says the responses aren’t guaranteed to be 100% factual, and that people should review them before sending them to anyone. This is where the rule for the whole day comes from: the tool proposes, the person approves. ▸ What the licence changes: Copilot Chat comes with eligible Microsoft 365 licences and works mainly from the web and the files you give it; the paid licence extends it to email, meetings, chats and documents across the organisation. By the end of this part everyone has done a first exercise on their own work and knows what to expect. Sources: [Microsoft Learn, Data, Privacy, and Security for Microsoft Copilot: only organisational data the user has at least view permission for; responses not guaranteed to be 100% factual, to be reviewed before sending ↗](https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-privacy) (read on 11/10/2026) · [Microsoft Learn, Overview of Microsoft Copilot Chat: included with eligible Microsoft 365 licences, mainly web grounded; the paid licence reasons across email, meetings, chats and documents ↗](https://learn.microsoft.com/en-us/copilot/overview) (read on 11/10/2026) ## Part two: how do you teach people to ask? With one idea: a good request is a good brief. Goal, context, audience, constraints and references, the same pieces you need to hand a job to a colleague. Microsoft’s own prompt guide for Copilot boils them down to four: goal, context, source and expectations. Then the ways of asking, one at a time and always on a real task. ▸ All in one message, when the task is clear and repeats. ▸ In steps, when the result of one request feeds the next: first the summary of the minutes, then the actions, then the email to the people who have to act. Each step gets checked before moving on. ▸ Asking Copilot to show its reasoning, when the task is less obvious and you want to see where the answer takes a wrong turn. ▸ Asking Copilot to put the questions to you, when you aren’t sure where to start. For a team in Italy the exercises run in the language people write their documents in. If they write to customers in Italian and report to headquarters in English, they practise both, because those are the two requests they will make on Monday. Sources: [Microsoft Support, Get started writing prompts in Microsoft Copilot: goal, context, source and expectations ↗](https://support.microsoft.com/en-us/topic/learn-about-copilot-prompts-f6c3b467-f07c-4db1-ae54-ffac96184dd5) (read on 11/10/2026) ## Part three: how do you save what works? Requests that work, left in each person’s chat history, are lost within a month. ▸ The group’s context: who you are, how you write, what you never promise. Written once, in a file, and pointed to in requests instead of explained again every time. ▸ Saved requests: Copilot’s Prompt Gallery lets people save the ones that work and share them with their team. They become the group’s library, organised by task. ▸ A checklist before a text goes out: names, dates, figures, quotes, tone. Five lines to keep next to the keyboard. ▸ The draft usage rule: what goes in, what doesn’t, who decides in unclear cases. In a group, this draft is checked against the policy headquarters already has. People who leave the day with these four pieces know where to start the next morning. Sources: [Microsoft Learn, Understand Prompt Gallery in Copilot: available in Microsoft Copilot and Copilot Chat; prompts can be saved and shared across teams ↗](https://learn.microsoft.com/en-us/microsoft-365/copilot/copilot-prompt-gallery) (read on 11/10/2026) ## What changes when the team is in Italy and you aren’t? The content of the day stays the same wherever it runs. What changes is what you have to settle from a distance. ▸ The licences: check what the people in the Italian office have, person by person. The programme is written on that, not on the group’s standard. ▸ The language: ask the participants which language they write their documents in. I teach in English and Italian, on site and remote, so the choice follows the team. ▸ The examples: if the programme was written at headquarters for every country, the structure can stay and the exercises have to be local. The Italian office may have a different customer mix and a different approval chain. ▸ The owner: someone in Italy who keeps the saved requests alive and answers the questions that come up the week after. Agree on who it is before the day, so participants know who to ask. ## How do you tell whether the programme you were sent holds up? Read it with six questions in hand. ▸ Which tasks does it work on? If the examples are generic, the day will be generic. ▸ When does each participant get a first concrete result? If the first hour is all theory, half the room has already decided this isn’t for them. ▸ How long do people work on their own files, compared with watching the trainer’s screen? ▸ Which licence is it written for? It has to match the one your people in Italy have. ▸ What is left in writing at the end: saved requests, the group’s context, a checklist, a usage rule? ▸ Where do the usage rules sit: inside the blocks, or in a final chapter? If a programme answers all six well, it holds up even if the topics come in a different order from mine. ## Frequently asked questions - Is one day enough to learn Copilot? It is enough to start well: understand the tool, learn to ask, save the first requests. Changing how a team works usually takes several sessions one or two weeks apart; there is a separate guide on how many hours. - One full day or two half days? Two half days a few days apart, when the calendar allows. In between, people try things on real work and come back with their own questions, which become the material for the second half. - Do people need the paid Microsoft Copilot licence for the course? No. The course works with Copilot Chat, which comes with eligible Microsoft 365 licences. The programme has to be written for the licence people have, because with the paid licence Copilot also works across email, meetings and the organisation’s documents. - Can the day run in English for a team in Italy? Yes. I teach in English and Italian, on site and remote. The exercises run in the language people write their documents in; with a mixed group the language is decided beforehand, because it changes the examples and the material. - What do participants take away? The requests that work on their own tasks, saved and shared with the team; the group’s context written once; a checklist for any text that goes out; and a draft usage rule. The sample programme, with languages, formats and how I adapt it to your team’s tasks, is in the trainer profile. ## The trainer profile One PDF with what a decision-maker needs: courses, languages, formats, how I work, the criteria for choosing, the numbers. Plus a sample 16-hour Microsoft Copilot programme. - the courses I can deliver right away, by area, with durations - languages, locations, formats - how I run a session and what participants keep - the criteria for choosing an external instructor - the numbers, with their basis - a sample programme: Microsoft Copilot, 16 hours If you need the courses, the languages and the delivery formats before the programme: [the training page](https://davidescalera.it/en/training) If you own the company and the licences have been sitting there for months with nobody using them, the Update Labs guide starts from that symptom and ends with the Update Check. [Read the Update Labs guide ↗](https://updatelabs.it/en/guides/copilot-licences-nobody-uses) related guides - [How many hours does Copilot training take, and how do you split themWe have the licences and need to train people: how many hours, and how do we organise them?](https://davidescalera.it/en/guides/how-many-hours-copilot-training) - [Claude training for your team in Italy: what it covers and how to set it up from abroadWe use Claude across the group and need to train the people in Italy: what should the course cover, and what do we settle first?](https://davidescalera.it/en/guides/claude-training-for-teams-in-italy) - [What an AI trainer costs per day in Italy, and what drives the rateWe have two quotes for the same AI course in Italy and they’re far apart: why?](https://davidescalera.it/en/guides/ai-trainer-day-rate-italy)