Module 6 of 6
Handover
Updates, governance and what happens when it drifts.
A knowledge base decays from the day it is built. Write down who adds material, who approves it, how often the whole set is reviewed, and what triggers an out-of-cycle update — a price change, a policy revision, a regulatory notice.
Include a short section on how to tell it has drifted, and what a user should do when an answer looks wrong. A named person and a two-line reporting route is enough. Without it, people quietly stop trusting the system and go back to asking a colleague, and nobody ever tells you that happened.
Name who updates it, how often, what triggers an early review, and where a user reports a wrong answer.
That is the last module. What you hand in is Reusable knowledge base an AI can work from — the rubric it is marked against is on the course page.