After Copilot training: a 30-day plan for Excel-heavy teams

Your team has completed a Microsoft 365 Copilot workshop. Now they return to the Excel workbooks, reporting deadlines, and analysis questions that fill their day. The next step is to connect what they learned with those existing workflows.

For the person sponsoring the training, the question is practical: what should happen next week? I would start with two recurring tasks, named owners, and a small set of checks. Here is a 30-day plan for an Excel-heavy finance or operations team.

The next four weeks at a glance

Week 1: choose two recurring tasks

Start with work that already happens. Preparing a monthly reporting narrative or turning reviewed analysis into a stakeholder update gives you a process to examine. Choose tasks with identifiable owners and a clear definition of a usable result.

For each workflow, capture:

• The input: which workbook, table, or approved analysis starts the task?
• The output: what would a usable result look like?
• The owner and reviewer: who does the work, and who checks it?
• The baseline: preparation time, review effort, and common corrections.
• The access requirements: which Copilot capabilities and approved data can the team use?

If the task happens only once a month, use a representative prior-period example for the initial test and revisit it during a live reporting cycle. The team’s tools, access, and policies shape what you can reasonably test.

Week 2: test a complete workflow

This is where Excel expertise matters. A polished summary still depends on sound calculations, appropriate comparisons, and an understanding of the workbook behind it. Document the context supplied to Copilot, the useful steps, and the checks applied afterward so another colleague can repeat the approach.

Week 3: support people while they use it

Schedule a working session or office hour around the selected tasks. Ask participants to bring an attempt, a question, or a point where they got stuck. Those examples give you something specific to improve.

Update the workflow guide as you learn. Explain when to use the approach, what inputs it needs, what to check, and when to ask for help. Keep it close to the work so people can find it during the next reporting cycle.

Week 4: decide what deserves to continue

Review the results with the workflow owners and internal sponsor. Did people use the approach? Was the output useful? Did preparation become easier without adding disproportionate review effort? Which barriers remain?

Small pilots provide directional evidence. Be explicit about how many attempts you observed and avoid turning one successful example into an organization-wide savings claim.

Who keeps this moving?

Someone needs to coordinate priorities, support practice, maintain the guides, and bring findings back to the sponsor. Those responsibilities can sit with an internal lead, with recurring outside support where it helps.

My work as a Microsoft Excel MVP, O’Reilly author, and LinkedIn Learning instructor starts with the reporting and analysis people already do. Fractional Copilot support extends that work through regular coaching and follow-through.