Monitoring and evaluation teams reviewing provider evidence
SETA and QCTO Monitoring
Review provider evidence through a read-only auditor view. Verify a certificate hash at the public verification endpoint instead of trusting a PDF that can be edited.
Outcomes
What changes in practice
- Auditor role restricted to read-only evidence and audit-log access.
- Public certificate verification returns NOT_FOUND for fabricated hashes.
- NLRD File 27/28/29 generators with a quality gate and batch manifest.
Evidence
Where it is implemented
- Daily Merkle roots over the audit ledger
- Public verification endpoint backed by sealed ledger lookups
- SETA MIS mapping profiles for Services SETA, merSETA, MICT, W&RSETA and CHIETA
Every capability described here is part of the same audit chain. If a step depends on an external
provider credential, the platform labels that dependency rather than presenting a simulator as a
live connection.
Start with a real cohort
A pilot uses one programme and one month of real attendance, so the evidence is comparable.
Agree the evidence policy
Attendance modes, geofence radius, approval SLA and stipend policy are configuration, not code.
Test the audit query
Pick the question that caused the most rework last cycle, and answer it from the platform.
Talk to us about seta and qcto monitoring.
A working session, not a slide deck. Bring a real cohort and a real audit question.