Prepare for an executive meeting
Synthesize long reports and email threads into a concise 1-pager.
Create a weekly digest from multiple data sources.
A polished briefing document.
Weekly metrics, project status, and decision logs are internal performance data. If you don't have a licensed Copilot for step 2, think twice before pasting an unreleased metric or an unannounced decision into Claude — use Copilot referencing the SharePoint files directly instead.
The apps run in this order. At the AI step, pick whichever of these you have — they're alternatives, not a sequence.
Copilot works differently from the others: with a paid Microsoft 365 Copilot license it's built right into the app above, no copy-pasting needed. Without a license, use it the same way as ChatGPT or Claude — in its own chat window.
Write down the exact reporting period (e.g., "week ending Oct 3") first, then gather only the already-approved sources for that window — the weekly metrics report, project status pages, and any decision log — from their SharePoint libraries.
Pulling in a source that covers a different or overlapping period is the most common way a briefing ends up with a number that doesn't match what leadership saw last week.
If the source documents live in SharePoint or OneDrive, reference them directly from Copilot so it reads the actual files; if you're using Claude instead, paste in the approved material directly rather than summarizing it yourself first — let the AI work from the primary sources, not your own paraphrase of them, so nothing gets lost or distorted a second time before the real draft happens.
Prompt:
Create a concise executive briefing for the reporting period provided. Separate confirmed results, risks, decisions needed, and next steps. Keep all figures and dates exactly as stated in the sources, and flag any gaps instead of filling them in.
Go line by line through the draft and trace every metric, date, owner name, and decision back to the specific source document it came from.
Not a general sense that "this sounds right." Delete anything you can't trace, and clearly mark any figure that's an estimate rather than a confirmed number ("approx." or a footnote), since an executive reader will treat every number in the briefing as fact unless told otherwise.
Use Word's built-in Heading styles for the summary, key metrics, risks, and requested-decisions sections — not manual bold-and-larger-font — so the document has a working navigation pane and stays easy to scan if it grows.
Save it to the team's standard SharePoint briefing location (not a personal OneDrive folder) and link back to each source document, so a reader who wants to dig into a number can go straight to it.
A Word document stored on SharePoint.
Collecting source material (step 1) and formatting/publishing (step 4) are SharePoint/Word logistics, not AI work. The real value is step 2 pulling a consistent signal out of several separate sources at once.
Synthesize long reports and email threads into a concise 1-pager.
You have a budget export, a status report, and an email thread — and they disagree.
Get practical help with AI consulting or ask about training courses for your team.