The AI Documentation Audit

You can access recordings whenever you need to.

It is live. Four weeks, one 90-minute session per week, with the cohort running August 21 to September 13, 2026. Sessions are recorded, so you keep access, but the value is in the room. You audit alongside other people and get your grade pressure-tested in real time.

No. If you can open a spreadsheet and use the product you are auditing, you can do this. The scoring framework is built into the workbook, and the course teaches you to read a product the way a first-time user does, not the way an engineer does.

Plan for the 90-minute live session plus about two hours of between-session work on your own audit. The assignments are not busywork. Each one moves your real audit forward, so by Week 4 your capstone is nearly finished.

A complete, defensible audit of a real AI product: a letter grade, a regulatory gap map across three jurisdictions, a prioritized remediation plan, and a one-page scorecard you can put in front of your team. It is a work sample, a portfolio piece, and a repeatable skill, all at once.

One you choose. It can be your own company's, a competitor's, or a tool you rely on. The only rule is that you can access and use it, and that its grade is one you would genuinely want to know.

No. The workbook is the instrument. The course is where you learn to run it with authority, defend your scores against pushback, and turn a grade into something your team acts on. Workbook owners tend to get the most out of the cohort, because they already know where the tool exceeds what they can do alone.

Documentation engineers and DevRel professionals who need a standard instead of an opinion. Founders and product leads who suspect their AI documentation would not survive scrutiny. And people moving into technical writing, AI governance, or compliance who want a market-ready skill and an artifact to show. Different seats, same problem.

Every session is recorded and posted within a day. You will not fall behind on the material. I do recommend attending live when you can, because the calibration and hot-seat segments are hard to replicate on a recording.

The August 2, 2026 EU deadline is why the timing matters, and we map every audit against the EU AI Act, Colorado, and California. But the skill outlasts any single regulation. You are learning to audit documentation, which stays useful no matter which law lands next.

I spent years as a documentation engineer at Meta serving more than 3,000 developers, I am a selected MIT AI Safety Fellow, and I grade real AI companies on their documentation every week in my newsletter, The Documentation Engineer. This course teaches the exact framework I use to do it.

Capped at 25, so I can review every capstone and grade every final presentation myself. When the seats are gone, the cohort is closed until the next run.