Topics inside this course
Awareness and induction depth — not an accredited occupational qualification.
- What a request for records looks like
- Information officer and deputy roles at staff level
- Do not freelance a refusal or a release
- Overlap with POPIA data-subject requests
- Fees and grounds of refusal are specialist — staff only escalate
Built for the people who take the training
Anyone who reads inbound email, reception, legal-adjacent teams, and deputies who might receive a PAIA form without expecting it.
What learners leave able to do
- Recognise a PAIA request in a form or in an ordinary email
- Escalate immediately to the information officer path your manual names
- Avoid deleting, ignoring, or drafting an informal refusal
- Understand that timelines exist and are the organisation’s problem, not a personal favour
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.
- 1Access to information
Why PAIA exists beside POPIA.
- 2What a request looks like
Forms, emails and calls that are still requests.
- 3Escalate, don’t decide
Who owns the clock.
- 4What you must not do
Delete, delay, or negotiate informally.
- 5Knowledge check
Short scored assessment.
Short scored assessment for recognition and escalation. Not training to apply refusal grounds.
Written for the workplace, not for the statute book alone
PAIA failures often start at the first inbox. Someone treats a request as a nuisance email, or answers with a partial dump of files, or lets the statutory clock run because “legal is in a workshop”. This course trains recognition and escalation, not decision-making.
Reception, finance and operations all receive requests that are PAIA in substance even when the sender did not attach the form. Learners practise pausing, logging, and handing the matter to the information officer named in your manual.
POPIA overlap is named so people do not open a second unofficial track. If it might be a data-subject request, it still goes to the same owned process. Subpoenas and litigation discovery are flagged as “send to legal” — not PAIA DIY.
Generate from PAIA extracts, Regulator forms, and your manual in Kre8AI so names and addresses are real. Keep placeholders out of a live LMS package. Export as SCORM or HTML.
Public and private bodies both need this. Private-body staff often assume PAIA is “a government thing”. The course corrects that without turning everyone into an information officer.
Play the library demo, or generate PAIA request handling from your manual in Kre8AI.
What you would upload in Kre8AI
PAIA manual, information officer procedure
- PAIA 2 of 2000 (selected sections on requests and information officers)
- Information Regulator PAIA forms and guidance
- Your PAIA manual and information-officer procedure
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.