For a finance team, finishing the spreadsheet is often just one part of finishing the report. Someone still needs to explain a variance, follow up on a question from the review meeting, draft the commentary, and prepare the slides. Those tasks can take the work through Outlook, Teams, Word, and PowerPoint.
Microsoft 365 Copilot training should reflect that wider process. Excel deserves a place in the agenda, alongside the communication and review work that surrounds it. A program built around a familiar reporting task gives analysts, managers, and other team members a practical way to learn the tools.
Designing that program starts with three decisions: what participants need to produce, where Copilot can help, and how they will check the result.
Choose a workflow before choosing features
Begin with a task the team regularly needs to finish. Monthly reporting is one option. Preparing for a management meeting, reviewing an expense policy, or coordinating responses to an information request could also work.
Once the task is clear, map out the information and applications involved. A monthly report might draw on an Excel workbook, department updates in Outlook, a discussion in Teams, and a management memo in Word. The training can follow that sequence, with an exercise for each part of the work.
| Where the work happens | What people could practice | What they need to check |
|---|---|---|
| Outlook | Summarize a long email thread and draft a reply asking for the missing information. | Did it pick up the latest answer? Does the reply ask for what we actually need? |
| Teams | Use the available meeting transcript to pull together decisions, open questions, and action items. | Was that a decision or just a suggestion? Were an owner and deadline actually agreed? |
| Word | Turn checked results and supporting notes into a first draft of a management memo. | Does each explanation have a source? Are any unresolved questions being presented as settled? |
| PowerPoint | Develop a short presentation from an approved summary. | Do the numbers, dates, and qualifications survive the move onto slides? |
| Excel | Explore an unfamiliar workbook, explain a formula, or help build and check an analysis. | Are the inputs and calculations correct? Can someone inspect and reuse the work? |
This also helps define who the training is for. An analyst may need more practice exploring and checking the workbook. A manager may get more use from reviewing commentary, preparing for a meeting, and following up on decisions. Both can work through the same case.
Build one complete exercise
Consider an exercise on monthly budget-versus-actual commentary. Keep the materials manageable: a departmental report, a few notes explaining the larger variances, an email exchange, and a meeting transcript.
Start with the workbook. Calculate the variances and define which ones need attention. For example, the exercise might flag an unfavorable variance only when it exceeds both 5% and $25,000. That gives participants a rule they can check before asking Copilot to help explain the results.
Next, work through the supporting discussion. Learners could summarize the email thread to find the latest explanation for an overspend, then use the meeting transcript to identify decisions and unanswered questions. Including a revised explanation or an unresolved item gives them something meaningful to review.
Use the checked results and notes to draft the commentary in Word. A prompt could look like this:
Using the approved variance summary and the department notes provided, draft a short update for the finance director. Cover the material unfavorable variances and use only explanations supported by these sources. If a cause is missing or still being investigated, say so. Finish with the questions we need answered before the report is finalized.
Participants can then compare the draft with the source material. Does each explanation have support? Has anything been left out? Would the update make sense to someone who missed the meeting?
Once the commentary is approved, use it to develop a short PowerPoint presentation and draft the email requesting any outstanding information. The numbers and explanations need to stay consistent as the work moves between apps. “We’re investigating the cause” should not somehow become “The cause was higher supplier prices” by slide three.
The exercise gives participants a complete piece of work to examine. It also shows how the same habits, such as identifying a source and checking a claim, apply in several applications.
Six things to include in the training
1. The tools and source material people can actually use
Check licenses, application versions, file access, and relevant organization settings before building the exercises. A Copilot button in one application does not establish which features are available elsewhere. Microsoft’s feature availability documentation provides a starting point for that check.
For meeting exercises, confirm that the necessary transcript will be available. Microsoft explains that asking Copilot about spoken meeting content after the meeting requires a transcript. That is worth sorting out before the session begins.
Source preparation matters too. In Excel, it may mean consistent headers and a structured table. Across Microsoft 365, it also means knowing which document is current, where the approved version lives, and who can access it. A folder full of files named Final_v7_USE_THIS gives both people and Copilot a difficult starting point.
2. A clear division between AI assistance and repeatable reporting
Summarizing a discussion, drafting a memo, explaining a formula, and suggesting questions are useful tasks to practice. Participants also need to recognize when a job requires a repeatable calculation or transformation.
For a recurring report, keep those steps in reviewed formulas, Power Query, or other tools the team can inspect and refresh. Copilot can help build or explain the steps. Once they are checked, the team should be able to run the process without describing the whole report again each month.
The same distinction is explored in this article on Copilot and routine reporting. Training should help participants decide where AI assistance fits and what remains part of the established reporting process.
3. Prompting habits that transfer across applications
Saved prompts can provide a useful starting point. Participants also need practice adapting them when the audience, source material, or assignment changes.
Microsoft’s prompting guidance identifies four elements: the goal, context, expectations, and source. In a finance exercise, those might be a variance summary, a finance director as the audience, a short written update, and an approved set of results and department notes.
Those choices apply across the apps. A follow-up exercise could change the audience from the finance director to a department manager, or change the output from a memo to an email. Learners then have to adapt the instructions and assess whether the result fits.
4. A review step within each exercise
Review should be part of the work participants complete. Give them time to compare the output with its sources, check important figures and dates, and identify missing qualifications.
For a meeting summary, that means distinguishing a suggestion from an agreed action. For an email draft, it includes checking that nobody has been volunteered for work they never accepted. For financial commentary, it means tracing an explanation back to the supporting information.
Microsoft’s guidance on validating Copilot output makes the same practical distinction between improving the wording and verifying the content. A clearer paragraph can still contain an unsupported claim.
The exercises should also apply the organization’s rules for sensitive information, approved tools, and sharing. Use a short checklist that participants can refer to while they work.
5. Materials and responsibilities that fit the participants
A useful practice pack can include budget versus actual, department notes, an email thread, and a draft memo or slide deck. Fictional or anonymized materials can still reflect the decisions and complications people recognize from their jobs.
Assign activities to suit the audience. Analysts might check the calculations and supporting explanations. Managers might review the summary, identify decisions, and prepare questions for the next meeting. This lets the group use a shared scenario without assuming everyone has the same responsibilities or Excel skills.
6. Enough time to practice and apply the work
Match the scope to the time available. A short session can introduce the tools and give participants practice with one task. Covering a complete reporting cycle across several applications requires more time for working through the materials, comparing results, and making corrections.
That could mean a workshop on reporting and communication, a full day built around one scenario, or several shorter sessions with practice between them. Adding another application to the agenda only helps if participants have time to understand its role and use it.
A sample finance and accounting training outline can help make the discussion about scope more concrete.
Decide what the training should change
Before finalizing the agenda, agree on what participants should be able to do afterward. Make the objectives specific enough to observe: prepare a management update from checked sources, review a meeting summary, or draft a request for missing information.
- Audience: Which responsibilities and experience levels does the program need to accommodate?
- Output: What will participants actually produce during the session?
- Access: Can they complete the exercises with their licenses, settings, and practice materials?
- Review: How will they judge whether the output is accurate and usable?
- Application: Which recurring task will they try after the training?
That last point provides a practical basis for follow-up. Look at whether the update is easier to prepare, how much correction it needs, and whether the meeting’s open questions are easier to track. Time spent reviewing and fixing the output belongs in that assessment too.
Design around the whole reporting process
Microsoft 365 Copilot training for finance and accounting should connect the analysis with the work needed to explain, discuss, and act on it. Excel remains an important part of that process. The balance across applications should reflect the team’s responsibilities and the tasks it needs to complete.
Start with one familiar workflow, prepare the source materials, and make review part of each exercise. Participants should leave with a process they can apply during the next reporting cycle and a clearer sense of when Copilot is useful.
If you’re planning a program for your finance or accounting team, discuss Microsoft 365 Copilot training with Stringfest Analytics. Share the roles involved and a recurring workflow you’d like the training to address.