An update module is a short unit of learning that covers what has changed since a person was last trained or certified: new product features, new rules, revised limits, lessons from incidents. It assumes the learner already knows the foundation and teaches only the difference. It is the cheapest way to keep a credential true between full assessments.
Why do update modules matter for agent oversight?
Agents change more often than most systems people are trained on. A capability is added, a source is replaced, a limit moves, a new reason for holding an action appears. Each change alters what a reviewer sees and what the right decision is. Without an update, a reviewer certified six months ago may be applying rules that no longer hold.
The change is often on the agent's side. How organisations change agents safely is covered in how to update an AI agent without breaking it. An update module is the people side of the same change.
How does an update module work in practice?
A good update module is short, specific and tied to the change:
- What changed: the new capability, rule or limit, in plain words.
- Why it changed: the reason, so the reviewer can apply it sensibly to cases the module does not cover.
- What it looks like in the queue: real examples of the new held actions or verdicts.
- What to do differently: the decision rule, with an example of getting it wrong.
- A short check: a few questions to confirm it landed.
It should reach people before the change goes live, not after. Completion is recorded against each person, so the organisation can show who was told what, and when.
What is an example?
A bank's servicing agent gains a new capability: updating customer records in the core banking system, such as contact details, within limits. Changes to a customer's phone number are held for a person, because a changed number can be the first step of account takeover. The update module explains this, shows three held examples, and includes one where the request came from an email that does not match the customer's record. Reviewers complete it before the capability goes live. When the first held phone change arrives, they know what to check. The same applies when an agent starts updating records in a CRM.
How is an update module different from refresher training?
Refresher training repeats material the learner has already covered, to restore knowledge that has faded. An update module teaches new material because the work has changed. Both have a place. A reviewer whose skills are sound but whose agent gained a capability needs an update; one who has been away from the queue for months may need a refresher as well.
It is also different from the update that changes an agent's behaviour, which may introduce new automated decisions. The agent's update and the people's update should be planned together.
Which terms are related?
- Renewal quiz: the short check that often follows an update module at renewal.
- Continuing professional development: the ongoing learning update modules belong to.
- Recertification: the formal renewal they prepare for.
For the wider topic, read AI literacy and certification for people who work with agents.
Where the Academy fits
Renewal of Certified Pryme Operator in Pryme Intelligence Academy is an update module and a short quiz, and the certificate is valid for 12 months. Keeping knowledge current is also one of the eight Operator modules, so operators learn to expect change before they are asked to renew.
Questions people ask
How long should an update module be?
As short as the change allows: often minutes rather than hours. If it runs long, the change may be large enough to need fuller retraining.
Who should write update modules?
The agent's owner, with the person who made the change, edited by learning and development for clarity. The owner knows what changed; L&D makes it teachable.