Board packs that write their own first draft from Excel

What is the real problem with board pack preparation?

Most board packs are assembled under pressure. Numbers arrive from several workbooks, each owned by a different team, and they rarely agree on definitions. The finance team then spends days reconciling them, copying charts into PowerPoint and writing commentary from scratch.

The hidden cost is not only the hours. It is the quality of the thinking that never gets time. When the narrative is written at the last minute, it tends to describe what happened rather than explain why it matters, and it leaves directors to work out the implications on their own.

• Days of manual copying between Excel workbooks and Word documents each cycle.
• Commentary written late, describing movements rather than causes.
• Surprise questions in the boardroom that could have been anticipated.
• Key-person dependency: one senior analyst holds the knowledge of how the numbers fit together.

What changes when Claude joins the process?

Claude works alongside the finance team rather than replacing it. Once the KPI workbooks are finalised, Claude reads them, compares the current period with the prior period and with plan, and identifies the movements that matter most. It then writes plain-English explanations of those movements, grounded in the figures and in any notes the team has recorded.

The output is a first draft of the board narrative in Word, structured to the company's usual format. Because the draft is produced in one pass, the CFO's team moves from assembling content to reviewing and improving it. The conversation with the board becomes more focused on decisions.

How does Claude connect to Excel, Word, PowerPoint and SharePoint?

Claude for Microsoft 365 works with the Office tools your team already uses. It can read the KPI workbooks held in SharePoint or OneDrive, draft the narrative in Word and help shape the summary slides in PowerPoint. The connection runs through Microsoft's secure connection layer, called Microsoft Graph, which means Claude only reaches the files each user is already allowed to open.

Company know-how, such as the house style, the list of approved KPI definitions and the usual board structure, can be packaged with Claude Skills so that every draft follows the same rules. You can explore the connection options in Claude for Microsoft 365 and read how Claude Skills keep company know-how consistent. A closely related automation is From blank page to finished proposal in Word, in your house style.

• Reads workbooks held in SharePoint and OneDrive, within existing permissions.
• Drafts the narrative in Word using your house style and approved definitions.
• Suggests headline messages for PowerPoint summary slides.
• Keeps a record of which figures each sentence relies on.

What does a typical day look like before and after?

Before Claude, the senior financial analyst spends the first three days of the cycle copying figures, chasing department heads for explanations and writing the first version of the commentary. The CFO receives a draft late and has little time to challenge it. Questions from directors surface in the meeting itself.

After Claude, the analyst reviews a first draft on day one. The explanations are already set against the numbers, and a list of likely questions is attached. The analyst spends the morning checking facts, adding context only the team knows and agreeing the final wording with the CFO. The afternoon is spent preparing answers for the questions most likely to be raised.

How are governance, security and approvals handled?

Claude never publishes anything on its own. A named finance lead reviews every figure and every sentence before the pack moves on. The draft carries references to its source cells so that reviewers can check each claim quickly. Every edit is recorded in Microsoft 365's version history, so the audit trail is complete.

Because Claude respects existing permissions, a commercial analyst who cannot see payroll data will not see it through the assistant either. Those who need stricter controls can ask for the design to be reviewed as part of the free automation audit, and the Anthropic Trust Center sets out the wider security and compliance information at trust.anthropic.com.

• Named finance approver signs off every figure before circulation.
• Source references allow every claim to be checked against the workbook.
• Full version history in Word and SharePoint.
• Existing permissions are respected; nothing is opened that a user cannot already open.

How do you measure whether it is working?

Measure the change in cycle time from the close of the books to the first circulated draft, the number of rounds of revision needed, and the number of questions raised in the meeting that were not anticipated. Teams typically see first drafts arrive several days sooner, and fewer revision rounds, though results vary with how clean the source data is.

Also ask directors whether the narrative helps them make decisions. A better board pack is one that makes the trade-offs clearer, not simply one that is produced faster. For a wider view of how this fits into the company's Microsoft 365 work, see how Claude and Microsoft 365 together lift productivity.

• Days from month-end close to first circulated draft.
• Number of revision rounds before final approval.
• Number of unanticipated questions raised in the board meeting.
• Director feedback on clarity of the narrative.

How should a team get started?

Start with one board cycle and one pack. Book a free automation audit so the team can review which workbooks, definitions and house-style rules are in place, and what the clean-up needs to be before Claude can read them reliably. The audit also identifies the approval steps and the people who should own them.

Once the first cycle is complete, capture the lessons: which explanations needed the most editing, which questions the board actually asked, and which parts of the house style need to be written down more clearly. Those lessons become the Claude Skills that make the next draft better.

• Choose one pack and one cycle for the first trial.
• Clean up KPI definitions and workbook structure before going live.
• Agree the named approvers and the review steps in advance.
• Review what worked after each cycle and refine the shared know-how.