Audit evidence pack
Explain what was taught and how it was governed, and export it.
Explains the Knowledge Foundry audit pack and how it answers questions asked months after release. Covers learning design evidence, such as structure and how outcomes connect to assessment logic, and governance evidence, such as integrity checks and change history. Also shows exporting a full audit pack or a focused learning design pack.
Next: After go-liveTranscript
Generated from the video's narration and lightly edited for readability.
0:00You know, building a learning program, that's really only half the job. The other half is being able to actually explain it later. Welcome to this explainer, where we're going to dive into how the Knowledge Foundry audit pack takes post-release program governance from a frantic, messy mystery and turns it into a rock-solid, defensible business asset. If you've ever had to hunt down proof of exactly what was taught and how it was controlled, well you are absolutely in the right place.
0:25Alright, so let's tackle this massive question that leadership inevitably asks, usually months after a release. Because the reality is memory fades right? Six months down the line people start asking, hey what did learners actually see? Or how did that assessment work again? What changed along the way? And wait, who actually signed off on all this? If you can't answer those questions quickly, you've got a pretty major blind spot.
0:50And it really comes down to a stark contrast in how you work. If the answers to those critical questions live exclusively scattered across, you know, old inboxes, Slack threads, maybe some buried meeting notes, you're basically forced into what we call inbox archaeology. And honestly, it makes the whole organization fragile. The alternative, inspectable evidence. Clear, organized proof that just naturally travels with the program itself, completely ready to be reviewed at a moment's notice.
1:15So moving on to our first pillar, learning design evidence, which is really the blueprint of teaching. This first group of evidence proves the program is actually coherent as a learning experience, not just that a bunch of random files exist on a server somewhere. The audit pack consolidates this proof beautifully. So rather than digging through old drafts, we have immediate access to concrete examples. We can see the overarching core structure at a glance and crucially, exactly how the learning outcomes seamlessly connect to the assessment logic.
1:46It lays out the exact pedagogical intent behind the program. Now what this does is brilliantly separate a really complex conversation into two manageable parts. We can easily shift from asking, hey, is this well-designed, which is your design proof, directly into assessing the control quality, which asks, was this responsibly released? You absolutely need both, for sure, but they are distinctly different types of proof. Which brings us to our second pillar, governance evidence, also known as the control story.
2:17While that first group was all about the teaching, this pillar focuses strictly on control, safety, and traceability. The crucial point here is having immediate, group-level proof of a responsible release. We do this by capturing essentials like integrity checks, so you know for a fact the program hasn't been tampered with, alongside a completely transparent, detailed history of what actually changed over time. That gives you full explainability of exactly how a program evolved and who authorized its journey to the learner.
2:46And that leads us to our final section, exporting portable evidence or proof beyond the Console. Because here's the practical hurdle, right? How do we actually prove all of this to quality stakeholders, compliance teams, or evaluators who aren't logging into the Production Console every single day? Evidence isn't really useful if it's locked away in a system your leadership doesn't even use. So the answer is simple. You just take it with you.
3:10You can export a full audit pack to show both the teaching and governance, or generate a focused learning design pack if someone only needs to see the pedagogical structure. It creates a completely portable record that you can attach to an email, drop in a shared drive, and hand directly to the people who need it. This really shifts our perspective entirely because when knowledge transfer is this defensible and highly traceable, inspectability is no longer just some technical curiosity.
3:35It becomes a massive organizational asset. It builds trust. It literally speeds up audits. And it unequivocally proves that your organization governs its learning responsibly. So, I'll leave you with this vital question to ask of literally any new learning initiative. Can we explain this program later, without having to resort to inbox archaeology? Well, with the Knowledge Foundry audit pack, you can boldly say yes, and you can export the exact proof to back it up.
More explainers
Start here
See it work
Trust and control
Prove value
Go deeper
Bring a subject. Leave with a framework.
A 45-minute working session with our team on a real subject or program you own. You see the system operate on your material, and you keep the framework it produces.
We reply within one business day.








