AI4BCM Guidance · Release 2026.09 · CC BY 4.0

Take AI4BCM Guidance with you.

22 markdown units, each small enough to read whole and cite. Free to use, share, adapt and build on — commercially included — as long as the authors are named.

Download

Two formats, one text.

01 / Print edition

PDF

The whole guideline set for A4, for reading away from a screen and for handing to a colleague who will not clone a repository.

PDF · 19 pages · 339 KB

Download the PDF

02 / Machine edition

Markdown

All 22 units in one file, each under its own path, each keeping the citation line at its foot. Drop it whole into the assistant you use and ask it questions.

Markdown · 21 units · 89 KB

Download the Markdown

03 / Source

The repository

Where the units are written and versioned. Corrections arrive as pull requests; releases/2026.09.json resolves this release to a commit and a hash per file.

Git · issues and pull requests

Open the repository

Licence · CC BY 4.0

Use it, adapt it, sell work built on it — name the authors.

Everything AI4BCM publishes — AI4BCM Guidance and the maturity playbook — is released under Creative Commons Attribution 4.0. That is free to use, share, adapt and build on, commercial use included, and it is irrevocable: once a version is published this way it stays free. The one condition is attribution, and the licensor sets the wording. This is the credit line to carry.

The attribution string
Hoekstra, W., Gerner, K., et al. (2026). AI4BCM: Guideline for using AI by BCM professionals. CC BY 4.0.

Citing one unit rather than the whole guideline? Name the unit and the release; the form is the same line with the path in it, and every unit carries it at its foot:

Hoekstra, W., Gerner, K., et al. (2026). AI4BCM: Guideline for using AI by BCM professionals, 2026.09, <unit path>. CC BY 4.0.

releases/2026.09.json in the repository resolves the release tag to a commit and to a hash per citable file, so a citation naming a tag names the text as it stood at that tag.

What is inside

22 units, in the order the work travels.

The data rules come first because they are the one rule you cannot recover from: what is pasted into the wrong tool cannot be unpasted.

Foundations and vocabulary

  • Data Rules units/data-rules.md
  • Principles units/principles.md
  • Where You Stand units/levels.md
  • Tools units/tools.md
  • Workflow Design units/workflow-design.md
  • Glossary units/glossary.md
  • References and further reading units/references.md

The six lifecycle stages

  • Establishing and Governing BCM units/stages/govern.md
  • Embedding BCM in the Organisation units/stages/embed.md
  • Analysis: Business Impact and Risk units/stages/analysis.md
  • Continuity Strategies and Solutions Design units/stages/design.md
  • Implementing Continuity Arrangements units/stages/implement.md
  • Validation, Exercising, Review and Improvement units/stages/validate.md

The prompts

  • Prompts units/prompts/README.md
  • Drafting units/prompts/draft.md
  • Awareness content units/prompts/awareness.md
  • BIA support units/prompts/bia.md
  • Review and challenge units/prompts/review.md
  • Exercise scenario units/prompts/exercise.md
  • Management reporting units/prompts/management-report.md
  • Prompt evaluations units/prompts/evaluations.md

Next

Reading it is one way in. Running it is another.

The same units install into the assistant you already use, behind a router that points you at the unit, the prompt and the maturity level your situation needs — and reads your files inside your own tenant.