SA-SAMS User Guide: How South African Schools Use It
Principals and school administrators face a recurring problem: the Department of Basic Education (DBE) requires learner data, assessment results, and compliance submissions through SA-SAMS, but the system is poorly documented and training is scarce. New staff struggle to find the right screens, sync failures leave data in limbo, and district offices expect correct submissions on time. An SA-SAMS user guide in plain language can reduce that friction. This guide explains what SA-SAMS is, who uses it, which modules matter for daily work, and how common tasks such as admissions, mark capture, and sync fit into DBE compliance.
We cover the main SA-SAMS modules and workflows, how to perform key tasks without getting lost in the menu structure, and where things often go wrong. We also point to practical resources such as our LURITS number guide and SA-SAMS problems in 2026 so you can troubleshoot issues and plan ahead.
What Is SA-SAMS and Who Uses It?
SA-SAMS (South African School Administration and Management System) is the free school administration system provided by the DBE for public schools. Most public schools use it to capture learner enrolment, attendance, assessment marks, and other data required for provincial and national reporting. Independent schools that report to the DBE may also use SA-SAMS or approved alternatives that sync with the same provincial systems.
Typical users include school administrators, bursars, data capturers, and educators who capture marks. The principal is ultimately accountable for the accuracy and timeliness of data submitted to the district. Because SA-SAMS is the official channel for many DBE returns, understanding its structure and workflows is essential for compliance. Schools that also use a commercial system for daily operations often keep SA-SAMS for official submissions; see SA-SAMS alternatives for South African schools for how modern platforms can reduce double data entry while staying DBE compliant.
Main SA-SAMS Modules and What They Do
SA-SAMS is organised into modules that map to different administrative and teaching tasks. Knowing which module to use saves time and reduces errors.
| Module area | Purpose | Typical users |
|---|---|---|
| Learner management | Enrolment, transfers, LURITS numbers, biographical data | Administrator, data capturer |
| Attendance | Daily register, absent/present, late coming | Educator, administrator |
| Assessment | Capture marks, term marks, report cards (when patches allow) | Educator, HoD, administrator |
| Staff | Educator and staff details for reporting | Administrator |
| Finance | Fee settings, basic financial data (varies by province) | Bursar, administrator |
| Sync/Submission | Send data to provincial database, receive updates | Administrator |
Assessment and report card generation depend on assessment patches released by the DBE before each term. When patches are delayed, schools cannot generate report cards or complete term-end submissions in SA-SAMS. This is one of the most common SA-SAMS problems in 2026; many schools keep a backup process or a parallel system that can produce report cards and store marks until SA-SAMS is updated.
Reporting Deadlines and EMIS
Schools must submit learner and school data to the provincial education department at set times. EMIS (Education Management Information System) returns often draw on the same data held in SA-SAMS: enrolment figures, learner movement, educator details, and infrastructure information. Missing SA-SAMS sync or incorrect data in key fields can lead to late or rejected EMIS submissions, which in turn can affect funding and trigger follow-up from the district.
Keeping SA-SAMS data complete and syncing regularly reduces the risk of missing deadlines. Designate someone to run sync at least weekly and to check that learner numbers, grades, and LURITS data are correct before major submission periods.
Key Tasks: Admissions, Marks, and Sync
Admissions and Learner Registration
New learners must be registered with correct biographical details and, where applicable, a LURITS number. For learners transferring from another school, use the existing LURITS number from the transfer document; do not create a new number. Creating a new number for a learner who already has one causes duplicates in the national database. The LURITS number guide explains who needs a LURITS number and how to avoid common mistakes.
Admission workflows in SA-SAMS vary by province. In general, you capture the learner’s details in the learner management module, assign a grade and class, and ensure the LURITS number is recorded if the learner already has one. Mid-year admissions can be a source of sync problems; capture data carefully and run a sync after major changes.
Capturing Marks and Generating Report Cards
Educators and HoDs capture assessment marks in the assessment module. Term marks must follow CAPS weighting and rating codes. SA-SAMS uses the standard 7-point scale (1–7) for GET and FET; Foundation Phase may use a different scale depending on provincial configuration. Report card generation is only available after the DBE releases the assessment patch for that term. Until then, schools often record marks in spreadsheets or in a separate system and then re-enter or import once the patch is available.
If your school uses CAPS-aligned assessment and report cards, understanding CAPS assessment requirements helps you align marks and comments with DBE expectations before they are submitted via SA-SAMS.
Synchronisation with the Provincial Database
SA-SAMS syncs with the provincial education database. Sync must run regularly so that learner data, marks, and other returns are sent to the district and so that updates (e.g. new LURITS numbers, policy changes) are received. When sync fails, data can be lost or duplicated; resolving sync errors often requires provincial helpdesk support or a visit from a technician. Many schools schedule sync during stable connectivity and avoid major data entry immediately before or after sync to reduce the risk of conflicts.
Sync usually requires a stable internet connection. During load-shedding or in areas with poor connectivity, sync may fail repeatedly. Schools in these situations often keep paper or spreadsheet backups and run sync when power and connectivity are restored. There is no built-in offline mode in SA-SAMS, which is why schools that need to work during outages sometimes use an SA-SAMS alternative with offline capability for daily capture and then sync to SA-SAMS when possible.
Common SA-SAMS User Guide Pitfalls
Even with a clear SA-SAMS user guide, a few pitfalls cause repeated problems.
Sync failures and data loss. Network interruptions, load-shedding, or provincial server issues can cause partial or failed syncs. Keep local backups of critical data and avoid editing the same records in multiple places. If sync fails, note the error message and contact the provincial helpdesk with the exact time and action that triggered the failure.
Wrong or missing LURITS numbers. Submissions are rejected when LURITS numbers are missing, duplicated, or incorrect. Check transfer documentation before registering a learner as new, and run regular checks for learners without a LURITS number. Correct any errors through the process prescribed by your province rather than changing numbers locally without authorisation.
Late or missing assessment patches. Report card generation and term-end submission depend on DBE patches. When patches are delayed, schools cannot complete these tasks in SA-SAMS. Schools that need to issue report cards on time often use a backup process or a system that can generate CAPS-compliant report cards and then align data with SA-SAMS when the patch is available.
Usability and training. New staff find SA-SAMS navigation non-intuitive. Menus are multi-level and error messages are often technical. Invest in a small set of school-specific instructions (which screens to use for admissions, marks, and sync) and assign a responsible person for SA-SAMS and EMIS so that knowledge is not lost when staff leave. Document the exact path to learner registration, mark capture, and sync in your province so that anyone covering the role can follow the same steps.
Who This Guide Is For
This SA-SAMS user guide is aimed at school principals, administrators, bursars, and data capturers in South African schools that use SA-SAMS for DBE compliance. It applies to public ordinary schools, many independent schools, and special schools that report through the same systems. The exact screens and workflows can differ by province; use this guide as a framework and confirm details with your district office or provincial SA-SAMS support.
SGBs and principals responsible for SGB financial management and governance need to ensure that someone has the time and training to maintain SA-SAMS and learner data, as accurate submissions affect funding, audits, and compliance.
Next Steps and Support
SA-SAMS remains the primary channel for many DBE submissions, but its limitations — delayed patches, sync failures, no offline capability, and poor usability — lead many schools to use a modern school management system alongside it. The right platform captures marks, attendance, and learner data once, generates CAPS-compliant report cards on time, and syncs with SA-SAMS for provincial returns so you avoid double data entry and stay compliant even when SA-SAMS is down or patches are late.
See how Fundisa helps South African schools manage learners, generate CAPS-compliant report cards, and stay DBE compliant with LURITS and SA-SAMS sync — all from one platform that works offline during load-shedding and speaks to parents via WhatsApp.
Written by
Fundisa Team