About¶
Why this exists¶
Every time someone stands up data & AI governance in a new organisation, the first few months look the same: draft the framework, draft the policies, build the RACI, stand up the committee, build the registers, write the board pack. Months of work — and almost none of it is secret. It's the same scaffolding every organisation needs.
This kit gives that scaffolding away. It's a genuinely open resource — CC BY 4.0, no accounts, no paywall, no email capture. Take it, adapt it, and spend your months on the parts that are actually specific to your organisation.
What it is — and isn't¶
It is a set of practical starting templates covering data and AI governance end to end, including EU AI Act readiness.
It is not legal advice, a compliance guarantee, or a substitute for professional judgement. Governance is contextual: your jurisdiction, sector, size, and risk appetite all change what "good" looks like. Use these as a head start, then make them yours and have the material bits reviewed by qualified counsel.
Who maintains it¶
Maintained by Lali Devamanthri.
Corrections and contributions from other practitioners are welcome and credited in the repository history — see Contributing.
Not on GitHub? Most of this kit's audience — governance leads, DPOs, lawyers — have no reason to hold a GitHub account, and you should not need one to tell us something is wrong. Send corrections, questions, or "this template does not work in my sector" straight to Lali Devamanthri on LinkedIn. Anything substantive gets raised as an issue and credited.
How current is this?¶
Regulation moves, and the EU AI Act pages are the most likely part of this kit to age.
- The EU AI Act timeline and readiness checklist carry a last-reviewed date and version at the top of the page.
- Both cite primary sources on EUR-Lex alongside secondary commentary. Where the two disagree, the official text wins.
- Every page is generated from versioned data files in the public repository, so you can see exactly what changed and when in the commit history.
If you spot something stale, open an issue — that is the fastest way to get it fixed.
How it's built¶
A static site generated with MkDocs Material and hosted free on GitHub Pages. The whole thing is Markdown in a public repo — which means anyone can read the source, suggest changes, or fork their own version.
Get involved¶
See Contributing. Corrections and additions from practitioners are what keep a resource like this accurate and alive.