Topics inside this course
Awareness and induction depth — not an accredited occupational qualification.
- Approved tools versus unofficial use
- What never goes into a prompt
- Spotting hallucinated or biased outputs
- Labelling AI-assisted work and keeping an audit trail
- When to escalate a novel use case for approval
Built for the people who take the training
Knowledge workers, managers and anyone allowed to use generative AI for work tasks.
What learners leave able to do
- Know what they may and may not put into AI tools
- Spot hallucinated or biased outputs before acting on them
- Protect confidential and personal information when using AI
- Escalate novel use cases through the right approval path
Modules you can expect
Structure may tighten when you localise from your own source pack in Kre8AI — this is the shape of the library title.
- 1AI is already at work
Why unofficial use is the real risk.
- 2Approved tools and bans
Your organisation’s shortlist and hard stops.
- 3Data you must not paste
Personal, confidential and client information.
- 4Verify before you act
Fluent answers that are still wrong.
- 5Ask before you experiment
Approval paths for new use cases.
- 6Knowledge check
Scored assessment for knowledge workers.
Scored assessment aligned to your AI use policy. Coach answers stay inside approved material.
Written for the workplace, not for the statute book alone
Staff are already using AI. The risk is unofficial use with client data, invented facts in client deliverables, and no audit trail. This course sets expectations: approved tools, what never goes into a prompt, how to verify outputs, and when to ask before you experiment.
It treats generative AI as a workplace tool with the same confidentiality rules as email and cloud drives. Learners practise spotting fluent but wrong answers, labelling when AI helped produce work, and refusing prompts that would paste personal or confidential information into a model.
Managers get guidance on approving new use cases without inventing shadow processes. Procurement and IT get a staff-facing companion to the tool list they already maintain.
Pair it with your real policy. Generate in Kre8AI from that policy so the course cites the same rules your legal and IT teams already approved. Publish as SCORM or HTML. The product’s own AI coach follows the same grounding rule this course teaches — answers from approved material only.
If you already block certain tools at the network layer, say so in the course. If you allow a shortlist, name it. Vague “use AI responsibly” slides do not change behaviour; named tools and banned prompt contents do. Revisit the module when your approved tool list changes rather than hoping people read the IT wiki.
Play the library demo, or build responsible-AI awareness from your acceptable-use pack in Kre8AI and ship it to your LMS this week.
What you would upload in Kre8AI
AI use policy, data classification, approved tool list
- Your AI use / acceptable use / data classification policies
- Privacy and confidentiality rules that apply to tools
- Approved tool list and banned-use examples
Formats, coach and provenance
- Standalone HTML to play in the browser; SCORM 2004 for your LMS.
- Optional AI course coach on Growth and Scale — grounded in approved material; off on quizzes and final assessment by default. Course plays offline; coach needs a network.
- Built in Kre8AI and reviewed before we published it. Not a substitute for your organisation's own policy — review before you make it mandatory.
Get the SCORM package while you are here.
Same course, SCORM 2004. Load it to settle the tracking question — and keep it as a course your people can take after you review it.
Request the package
SCORM 2004 zip. We ask for an email so we know which LMS you are testing — and so we can send the download.