Product/Teaching Logbook

This is what nobody else does well. Not a lesson diary — a teacher-accountability, syllabus-coverage and payroll-governance system in one. Every teacher logs what they actually covered, measured against the real syllabus per subject. Students confirm the lesson happened; parents back up the little ones. When a class falls behind, the HOD sees it before the exam does. And if the school chooses, payroll releases only when the work — and the notes — are actually done. Sold on its own; grandfathered into any LMS plan.

Coverage → payroll8 capabilities5 receipts
What this cluster carries

8 signature capabilities

01

Lesson-by-lesson coverage, planned vs actual

Every period: topic covered, planned vs actual, engagement notes. Coverage % is colour-coded across the whole department, and the HOD is alerted automatically at more than two weeks behind plan — before it becomes an exam problem.

02

Syllabus per subject, aligned to the scheme of work

Planning runs off the canonical HOD scheme of work — not a parallel list. Topics, subtopics, full content and budgeted hours per topic. Co-teachers each get their share, and their parallel progress rolls up into the subject's true total, so you're certain the work is covered by year-end.

03

Students confirm the lesson happened

Coverage isn't just self-reported. The class confirms the lesson took place; parents back up minors; prefects can confirm or dispute. Accountability with a second signature — the only logbook that closes the honesty loop.

04

Substitute dual-attribution

When someone covers a class, both the absent teacher and the substitute are credited correctly — coverage goes to the lesson, the hour goes to whoever taught it. Pay and coverage both stay honest, automatically.

05

The salary-release gate (optional)

Schools can choose: incomplete coverage → payroll holds. Justifications — illness, elections, protests — release the month with a written reason and HOD review. The only system that ties teacher accountability to teacher pay in a way you can defend to a union.

06

Lesson-note conformity

Require lesson notes your way — all upfront before teaching, monthly, or before every class. HOD or school approves; missing notes can gate salary too. Full control per school, or leave it entirely off.

07

Catch-up sessions with pay models

When a class falls behind, approve extra sessions with their own pay treatment — double-period Saturdays, holiday windows. Coverage recovers, the record shows exactly why, and the payroll follows the plan.

08

Nightly compliance recompute

A daily job scores every teacher's coverage and note conformity, so the HOD dashboard and the payroll gate are always current — no one runs a report by hand, and no month closes on stale numbers.

Real-world use case

Mid-October, Form 5 Mathematics. The HOD opens the logbook dashboard. The class has covered 38% of the term's plan against a 55% target, and the tile is amber. She clicks in. The teacher's entries — confirmed by the class — explain it: a week lost to elections, three days to protests, a sick week. She approves a catch-up plan: double-period Saturdays for four weeks, on the holiday pay model. Coverage recovers to 89% by term end. Because the school runs the gate, the teacher's pay was never in question — the justification released every month with a written reason on file. The students sat the exam ready.
What makes Teaching Logbook elite

The receipts

  • Coverage measured against the real syllabus per subject — not a parallel list.

  • Students confirm, parents back up minors, substitutes credited correctly.

  • Optional salary gate — accountability tied to pay, defensibly, with justification override.

  • Lesson-note conformity — require, approve, and optionally gate on notes.

  • Sold on its own at $0.40/student/mo — or grandfathered into any LMS plan.