About the Session

Benefit from an introduction to the different types of AI and use cases in the workplace for a BC Practitioner. Dig into how a continuity program replaced a web of disconnected spreadsheets with a single connected system – built by practitioners, not developers, working session by session with an AI collaborator.

Gain a new perspective on AI and potential practical applications. Lead into a real-world case study in building compliance tooling differently: one shared dataset instead of a dozen spreadsheets, a data-loss bug that rewrote the architecture, and the unglamorous engineering habits that turned out to be audit evidence in disguise.

Every mature continuity framework tells you exactly what to build; 

• A business impact analysis
• A risk register
• Single-point-of-failure treatment plans
• An exercise program 
• Document registry
• KPI tracking
• Business resumption plans
• Disaster recovery plans
• Crisis management program
• Crisis communication program

What it doesn't tell you is how to leverage AI in day-to-day use, and then a deeper look at a way to hold all of it together once a program spans many business units, and the person responsible for making it work also has to keep it current, defensible, and ready for an auditor's questions.

This session follows one program's answer: rather than buying generic compliance software or hiring a development team, a couple of continuity practitioners co-built a connected system directly with an AI collaborator, across dozens of working sessions. Attendees will hear the real story behind that system, including a data-loss bug that reshaped its entire architecture, and leave with five concrete, transferable lessons for making any compliance program's data trustworthy enough to survive audit scrutiny.

key takeaways

1. Types of AI & how you could integrate AI into your program to reduce manual tasks
2. Why connected data beats even well-organized spreadsheets under audit scrutiny
3. How a real production failure, not a design workshop, produced the system's most important safeguard
4. Which "boring" habits (validation, testing, version control) double as compliance evidence
5. A practical model for you to co-build your own program tooling with an AI collaborator, and without a development team