At the end of Term 2 2026, the Citrix environment that hosts SA-SAMS became unavailable. The impact was immediate and province-wide: schools across Gauteng could not access learner administration records, capture marks, complete roll call, or print report cards. The Gauteng Department of Education publicly apologised for the delayed report cards, and the system was only fully restored on 26 June — the final day of term — with thousands of learners nearly going on holiday without their Term 2 progress reports.
For school administrators, the lesson wasn't that SA-SAMS is bad software. It's that a single system with no offline fallback is a single point of failure — and term-end is exactly when you can least afford one.
What Actually Broke
SA-SAMS itself is a desktop application, but many schools access it through a centrally hosted Citrix environment. When that environment went down, everything routed through it went down too:
- Mark capture — teachers couldn't enter term marks
- Roll call and attendance — daily registers couldn't be completed in the system
- Report cards — term reports couldn't be generated or printed
- Learner records — administrative queries and updates were frozen
The timing multiplied the damage
An outage in week 3 of a term is an inconvenience. An outage in the final week — when every mark must be captured, every report generated, and every parent is expecting a report card — is a crisis. Term-end is precisely when system load and system dependence both peak.
The Two-Layer Continuity Plan
Layer 1: Back up your SA-SAMS database
Keep a current local backup of your school's SA-SAMS database. If the hosted environment is unreachable, a school with a local database copy can keep working in SA-SAMS offline and reconcile once the connection returns. Make the backup part of your weekly routine — and more often during submission windows and term-end.
Layer 2: Don't run daily operations through SASAMS alone
The schools that felt the outage least were the ones whose daily operations don't depend on SASAMS being reachable. Schools running MyEncore kept working straight through:
- Roll call continued in the MyEncore app — teachers mark attendance on their phones or tablets
- Demerits and discipline were logged as normal
- Marks were captured by teachers in MyEncore's marks module
- Report cards were generated and printed with MyEncore's Report Printer — custom-styled, DBE-compliant reports, published digitally to the parent app
- When SA-SAMS came back online, the term's data exported to SASAMS in validated, ready-to-import format
That's the practical meaning of redundancy: SASAMS remains the official system of record for the DBE, but the school's ability to operate — and to hand every parent a report card on time — no longer depends on one hosted environment staying up.
A Term-End Resilience Checklist
- Weekly SA-SAMS database backup, daily during the last two weeks of term
- Verify the backup restores — an untested backup is a hope, not a plan
- Capture marks continuously, not in a term-end rush — whichever system you use
- Have a second way to print reports. If your report cards can only come out of one system, you have a single point of failure
- Know your export path. If you run a school management system alongside SASAMS, confirm the SASAMS export works before you need it under pressure
Keep Your School Running — Whatever Goes Down
MyEncore is a school management system in South Africa with SASAMS integration: roll call, demerits, marks, and custom-styled report printing that keep working when SASAMS can't — then sync when it's back. First month free.
Get Started Now