Capture Once, Create Many: A Repeatable Copilot Workflow for Process Documentation

Jennifer Buchholz

Every organization has the same problem: the people who know how the work gets done don’t have time to write it down — and the documentation that does exist is stale the day after it’s published.

This session flips the model. Instead of authoring SOPs from a blank page, we capture the work as it happens and let Copilot do the writing.

We’ll walk the full pipeline end to end: capturing a process with a Teams meeting recording or Clipchamp, landing the recording and transcript in Stream or SharePoint, and prompting Copilot to generate a complete Process Knowledge Package — SOP, checklist, FAQ, troubleshooting guide, and a new-hire training version — from a single capture.

Because the quality of the output depends entirely on the quality of the narration, we’ll dig into the TEACH narration framework and a shared vocabulary of trigger phrases (“Before you begin…”, “Be careful not to…”, “You’ll know it worked when…”) that reliably map to structured SOP sections. We’ll also cover prompt scaffolding for consistent formatting across an organization, a Red/Yellow/Green data-sensitivity model for deciding what should never be recorded, and a maintenance approach where you re-record and regenerate instead of editing.

Rethinking Data Resilience for Microsoft Copilot and AI

Vanessa Toves

Microsoft Copilot and autonomous agents rely on grounding data across M365, Azure, and SaaS apps. Because of this, your organization’s data dependencies require a strict resilience plan. Driven by cyberattacks, compromised identities, overprivileged agents, and the unintentional mistakes users make, the risks to business continuity are compounding rapidly. In a Microsoft Copilot and AI world, operational data resilience is essential. Join Vanessa as she elevates your knowledge on Copilot and AI resilience.