How are school results compiled under continuous assessment in Nigeria?

Teachers enter component scores (CA1, CA2, exam) defined by an assessment structure that totals 100; the system computes term totals, applies the school's grade bands, and generates report cards. Third term additionally carries sessional results — cumulative averages across all three terms with positions ranked on them.

Why do computed grades sometimes come out wrong or ungraded?

A common trap: averages produce decimals like 69.5, and grade bands defined on whole numbers can miss them entirely, producing an ungraded or wrong result. The fix is to round consistently before banding, and to verify the score sheet, report card and printed card agree to the digit.

Should report card scores be editable after release?

No — approved results should lock, with corrections only through an explicit, logged unlock. This protects the school in disputes and protects teachers from claims that marks were changed after the fact.

78,796 scores, four campuses, no midnight spreadsheets

Result week is where school software goes to die. Anyone can demo a neat report card; the question is whether the system survives what actually happens in a Nigerian school — assessment structures that change mid-term, subjects renamed halfway through a session, a teacher entering CA marks at 11pm on deadline day. Our platform compiled 78,796 score entries for a four-campus school group this session, from daycare progress reports to SS-level sessional results. These are the lessons.

1. Scores enter as components, and the system does all arithmetic

Teachers enter CA1, CA2, exam — whatever your assessment structure defines — and never touch a calculator. The structure guarantees components total 100, the term total computes itself, and the grade comes off the school's own grade bands. The moment a human sums columns by hand, you buy transposition errors and "my child's total changed" meetings.

2. Grade bands have a trap nobody notices until it hits

Here's an implementation detail with parent-facing consequences: averages produce decimals — 69.5, 74.25 — and if your grade bands are defined on whole numbers, a 69.5 can fall between bands and come out ungraded, or worse, silently wrong. We learned to round before banding, everywhere, consistently — score sheet, report card and printed card must all agree to the digit. Check any system you evaluate: enter a 69.5 average and see what grade it prints.

3. The mid-term change will happen — plan for it

In a perfect world, assessment structures are fixed before marking starts. In a real school, a campus head changes the CA breakdown after two weeks of entries exist. A brittle system either blocks the change or corrupts the totals; a serious one migrates the existing scores onto the new structure and can show you exactly what moved. Ask your vendor what happens to already-entered scores when the structure changes mid-term. Watch their face.

4. Positions and averages must span the session, not just the term

Third term report cards in Nigeria carry sessional results: the cumulative average across all three terms, and positions ranked on it. That means the system has to union subjects across terms correctly — including the subject a student took in first and second term but dropped in third. Naive compilations quietly drop those rows and the sessional average flatters or punishes at random. Ours unions across the session, aliases renamed subjects (Core Mathematics = Mathematics), and ranks on the cumulative — the way examiners actually expect.

5. Approved results must freeze

Once results are approved and report cards go out, scores lock. Corrections after that point go through an explicit, logged unlock — not a quiet edit. This is the difference between "our records say" and "our records prove". It also protects your teachers: nobody can claim a mark was changed after the fact when changes are impossible without a trail.

6. The report card is a print product — treat it like one

Parents keep report cards. Ours generate as print-ready pages with the campus's own logo and name — a Montessori campus prints under its own identity, the secondary school under its — with layout measured so tables never spill or clip mid-word. And the digital copy reaches the parent on WhatsApp the day results are approved, which is why our result-release days generate messages, not queues at the office.

Stress-test any result system with these:

Enter a 69.5 average — what grade does it print?
Change the CA structure after scores exist — what happens to entered marks?
Drop a subject in third term — is it still in the sessional average?
Edit a score after approval — is it possible, and is it logged?
Print a report card — does the second page start where the first ended?

School Guardian 360 compiles results for a real school group every term — read how results should reach parents, see the features, or run a term beside your current process.