Skip to content

By His Power · For His Glory

Planning, evidence,
governance. One system.

The academic operations platform of Swakopmund Christian Academy — built by the Academy, for the Academy. Co-plan lessons across grade levels, see learning trends while there is still term left to act, and keep every approval on the record.

RLS
Row-level security
on every table
Append-only
Audit trail with no
update or delete path
One tenant
Hosted for the
Academy alone
Grade 6 Mathematics, sample workspace

Illustrative figures · not Academy data

Curriculum coverage
94.2%
+4.1 pts this cycle
Mean SBG level
3.1
of 4 · +0.3 on term 1
Flagged for support
7
before reporting
Mastery trend · last 10 assessments
A1A5A10

— Built on

Next.jsSupabase PostgresCommon CoreUtah SEEdNamibian hosting
§01 — APPROACH

Three disciplines.
One record.

A planner is only worth using if it survives contact with a real term. These three commitments are what the system is built to hold: plans that are shared, evidence that arrives early enough to act on, and permissions that live in the database rather than in the interface.

— §01.1 / Planning

Lessons planned together, not in parallel.

Two teachers can build the same scheme of work without emailing versions back and forth. Plans cite curriculum standards by code, carry their own resources, and move through draft → submitted → approved with the decision recorded against a name.

3-tier
Daily, weekly and unit plans in one repository
— §01.2 / Evidence

Drift visible in week three.

Standards-based mastery per learner, per subject, over time, with attendance beside attainment because the two explain each other more often than either explains itself. A slide shows as a slope rather than a surprise at reporting time.

1–4
Standards-based grading levels, not percentages
— §01.3 / Governance

Permissions in the database.

Row-level security on every table, four roles with a genuine ceiling, and an append-only audit trail with no update or delete path. A hidden button is not a control; a policy is. Records cannot be quietly rewritten.

4 roles
Teacher · grade lead · admin · superadmin
§02 — AUTHORISATION

Who may do what.

Four roles, each with a real ceiling. The scope column is enforced by Postgres row-level security policies, not by hiding a button — a teacher requesting another grade's learners receives no rows, whatever the interface shows.

Only a platform owner can change who holds which role, and that change is itself written to the audit log.

→ Roles are assigned by IT Operations. Ask the school office to be set up.
Permissions by role: record scope, lesson-plan rights, analytics scope and platform settings access
RoleRecordsLesson plansAnalyticsSettings
TeacherClassroomOwn classesPlan · submitOwn learners
Grade leadHead of departmentGrade bandPlan · approveGrade band
AdminAcademic officerSchool-widePlan · approveSchool-wideRead
SuperadminPlatform ownerSchool-widePlan · approveSchool-wideWrite
“Train up a child in the way that he should go; and when he is old he will not depart from it.”
— Proverbs 22:6
Swakopmund, Namibia
§03 — ACCESS

For staff with a term to
plan.

Every teaching member of staff gets an account scoped to their own classes. Heads of department and academic officers get approval and oversight rights. Speak to the school office to be set up, or book a walkthrough for your department.