Everything a school runs on.Nothing it has to stitch together.
Most schools operate four or five disconnected tools and reconcile them by hand. Tavech holds the whole operation on one record set, so the register, the invoice and the report card are describing the same child.
5
Product pillars
20+
Operational modules
1
Student record
School operations
The people a school is responsible for
Every person the school holds a duty of care or a contract with, on one record each — and linked to each other where the relationships actually matter.
Online admission
A family applies from your own website, and an accepted application becomes a student record, a class placement and a first invoice — without anybody retyping the form.
Students
Admission through graduation on a single profile: enrolment, class history, attendance, results, fees, documents and guardians.
Guardians
One guardian to many children, one child to many guardians, with the relationship and the primary contact recorded. A guardian exists whether or not they ever sign in.
Staff & teachers
Employment records, departments, subject and class assignments, and the permissions that follow from the role rather than from a list somebody maintains.
Staff attendance
Who was in today, across teaching and non-teaching staff, on the same footing as the pupils’ register, and where the pay run reads from.
Classes & departments
Streams, sections, subject allocation and the teaching assignments that decide who is responsible for whom, and who may open what.
School operations
The academic year, start to finish
Years, terms, registers, timetables, assessments and published results — configured to how your school actually grades and promotes, not to a model we chose.
Attendance
Daily and per-period registers designed to be fast: a teacher marks a full class in seconds, not clicks. Patterns and chronic absence surface automatically.
Card & fingerprint attendance
Where a school has readers at the gate, arrivals post to the same register a teacher marks by hand. One attendance record, however it was captured.
Timetable
Build it by class, and the teacher and room timetables fall out of the same entries — one source, three views, never typed twice.
Clash detection
A teacher in two rooms, a class with two lessons, a room booked twice: all three are caught as the entry is saved, not on Monday morning.
Rooms
Rooms are records, not a text field, so a lab or a hall can be allocated, seen on its own timetable, and protected from a second booking.
Timetable generation
Hand it the classes, subjects, teachers and rooms and it drafts the week for you. You still move what you want moved — it only removes the blank page.
Assessments
Continuous assessment, exams and marks entry built for bulk work — a teacher entering a class set should never fight the interface.
Schemes of work
What each class is meant to cover this term, against what has actually been taught — so a syllabus falling behind is visible in week four rather than at the exam.
Results & report cards
Your weighting, your comment structure, your crest and colours. Publication is a deliberate, permissioned, audited act rather than a button anyone can reach.
Your own grading scale
Name the scale, set each band’s marks, its grade and its remark. A school that grades differently from its neighbour needs nothing changed by us.
Totals, averages and position
Worked out from the marks already entered — total, average, grade and position in the class — so nobody adds a column by hand and nobody checks it twice.
School calendar
Terms, holidays, examination windows and events in one place, so the dates the timetable and the fee schedule both depend on are stated once.
Business
Money, with a trail you can defend
Fee structures, invoices, payments and arrears — where every figure can be traced to who entered it and when.
Fees & invoicing
Fee structures per class, term or category. Assign, invoice, and track what is outstanding against each student and each family.
Payments & receipts
Record payments, issue receipts, and reconcile. Money is never shown as done before it is done — the screen confirms only what has actually been recorded.
Financial reporting
Collection against expectation, arrears by class or family, and the term-on-term picture a board asks for.
Payroll
Salaries, allowances and deductions for all staff, with Uganda PAYE and NSSF worked out in the pay run and filed from the same figures.
Payment providers
A provider-agnostic payment layer, so mobile money and card rails can be added without reworking the finance module.
School operations
Talking to families, on the record
Communication that is attached to the student record, so a conversation about a child is part of that child’s history rather than lost in someone’s phone.
Messaging
Direct and group messages to guardians and staff, with delivery status and a permanent record against the recipient.
Announcements
School-wide or targeted notices, scheduled or immediate, with a defined audience rather than a broadcast to everyone.
Documents
Admission papers, certificates and reports stored against the student, staff member or school, with permissions on who may open them.
School operations
The day around the lesson
Where a child sleeps, how they travel, what they borrowed and the morning they spent in the sick bay. Schools are held responsible for all of it, and it is usually the part kept furthest from the student record.
Boarding & hostel
Houses, dormitories and bed allocation, with boarders on the same record as day students — so a matron, a class teacher and a bursar see one child, not three lists.
Transport
Routes, stops and who is on which bus, against the same guardian contacts the rest of the school already uses — so a missed pickup reaches somebody who can act.
Library
Titles, copies, loans and what is overdue, attached to the borrower’s own record rather than a ledger that walks out when the librarian does.
Clinic & sick bay
Visits, treatment and the guardian who was told, kept where a nurse can read it and a class teacher cannot. A medical note is not school-wide news.
Intelligence
What the records are telling you
A school with everything on one record can be asked questions no single book could answer. This is the part that only works because the rest is connected.
Insights & risk
Attendance, results and fee status read together, so the child quietly slipping on all three is surfaced while the term can still be changed.
Automation
The reminders and routine steps a school currently remembers by hand — an arrears notice, an absence message to a guardian — run on rules you set.
Reports & exports
Enrolment, attendance, collection and results as figures you can hand to a board or a ministry, and as files you can take away whenever you want them.
AI assistance
Drafts a report card comment from a pupil’s own marks, and says in words why the risk view flagged a child. It never sees a name — records are pseudonymised first.
Public website
The school’s own public pages and its admission form, served from the same system that holds the records they feed, so an application is already a record.
Your own domain
Run the whole thing on your school’s own web address, not a supplier’s. Parents sign in at your name, under your crest, from the first byte.
Platform & administration
The layer that makes the rest safe
Identity, tenancy, permissions and audit are not an admin screen bolted on at the end. They are the first thing built, and every module inherits them.
Roles & permissions
Capability-based permissions, plus custom roles a school defines for itself — Examination Officer, Registrar, Librarian — without asking us for a code change.
Audit
Who changed this mark, approved this waiver, published these results, or granted this permission. Append-oriented and readable by leadership, not just engineers.
School settings
Grading, terms, attendance rules, finance settings, notification channels, branding and document templates — configuration, not a support ticket.
Users & access
Invitations, account status, session control and the security policies your school chooses to enforce.
Built for your kind of school
One platform. Configured to how you actually operate.
A nursery and a college run on the same foundation and almost nothing else in common. Pick yours — every difference below is configuration rather than a separate product.
Nursery & primary
Fewer systems, less admin, more time with the children.
Smaller schools carry the same obligations as large ones with a fraction of the office staff. The work that has to disappear is duplicate data entry and chasing fees by hand.
- A register a class teacher completes in under a minute
- Guardian contacts that are correct when it matters
- Fee collection without a parallel spreadsheet
- Report cards that assemble themselves
Walk through it with your own workflow.
Bring a real process from your school — an admission, a term's results, a fee cycle — and we will show you exactly how it runs.