Why should Nigerian schools use sessional teacher contracts?

Sessional contracts end with the academic session, giving both school and staff a clean renewal point each year. They work best issued from role-based templates so every staff member on the same role holds the same terms, with automated reminders before expiry so renewal happens on time.

What makes a digital staff contract trustworthy?

It must freeze at signing — once signed, neither the school nor the staff member nor an admin can edit the stored document. A signed contract that can be quietly changed afterwards will lose exactly the dispute it was meant to settle.

What did auditing a real school's staff records reveal?

In a 300-staff Nigerian school group, 26 people who had resigned were still marked active — visible in staff lists and technically eligible for payroll. Contract rollout forces a reconciliation of who actually works for the school, which alone justifies it.

Sessional teacher contracts: paper files rot, and your staff list is probably wrong

Most Nigerian schools run staff on a handshake plus a letter photocopied from last year. It works — until a salary dispute, a mid-session resignation, or a parent incident where you need to show exactly what a staff member agreed to. This July we moved a four-campus group with over 300 staff onto fully digital contracts. The rollout taught us more about school staff records than the contracts themselves. Start with the embarrassing part.

The audit finding first: resigned, but still "active"

Before issuing a single contract we audited the staff table against reality. Result: 26 people who had resigned were still marked active in the records — appearing in staff lists, eligible for payroll runs, technically still holding system access. No fraud, no drama; just entropy. People leave mid-term, the exit is handled verbally, and nobody updates the register. If a 300-staff group accumulates 26 ghosts, assume your school has some. The lesson: contracts force a reconciliation of who actually works for you — which alone justifies the exercise.

One template per role, not one contract per negotiation

We issue contracts from role-based templates — teaching staff, class teachers, non-teaching, security, kitchen, transport and so on — with the variable parts (name, salary, campus, session dates) filled per person. Templates mean every teacher on the same role holds the same terms, which ends the quiet chaos of "my own letter says something different". When a term changes — duty hours, conduct rules — you update the template once, and the next issuance carries it.

The contract must freeze at signing

The single most important property of a digital contract system: once signed, the document cannot change. Not by the school, not by the staff member, not by an admin with good intentions. Our contracts freeze at the moment of signature — what was signed is what is stored, permanently. Any system where a signed contract row can be edited afterwards is not a contract system; it is a shared document with extra steps, and it will lose you the exact dispute it was meant to win.

Sessional means expiring — and expiry needs a robot

Sessional contracts end with the session. That is a feature: it gives both sides a clean renewal point. But it only works if renewal actually happens on time, and September is precisely when nobody remembers contract paperwork. So expiry reminders are automated — the system nags before contracts lapse, not after a staff member has been working three weeks into a new session on nothing. Renewal becomes a batch operation from templates, not 300 individual scrambles.

Signing must be simple enough for the kitchen staff

A contract flow that assumes everyone has email and a laptop will exclude exactly the staff for whom written terms matter most. Signing here happens from a phone, against the staff member's own authenticated account, and the signed copy is theirs to view any time. Dignity matters: a security guard should be able to read and hold their own terms as easily as a vice principal.

Questions for your own staff records:

How many people on your "active" list no longer work for you? Are you sure?
Do two teachers on the same role hold the same terms? Would you bet a tribunal on it?
Can a signed contract in your records be quietly edited? By whom?
Who remembers to renew sessional contracts in September — a person, or a system?

School Guardian 360 runs staff, payroll and now contracts for a real school group. See the features, read how four campuses run on one system, or start a free trial.