Theoperatingsystemfor schools.
Admissions, academics, attendance, finance and communication in one secure place — where every record connects, every change is traceable, and your school is set up your way.
Nursery → University
One platform, every stage
Role-based access
Down to the individual permission
Immutable audit
Every change, attributable
yourschool.tavech.app/attendance
0:00
P5 Blue — morning
12 present · 0 absent
Tap a name to mark them absent
A working register, with demonstration names. Try it.
Built for every kind of institution
Nursery schools
Primary schools
Secondary schools
International schools
Vocational institutes
Colleges
School groups
Multi-campus networks
Built for a Monday morning, not for a demo.
Dense enough for an administrator who lives in it all day, legible on the phone a teacher is holding at the classroom door — and different for each of them. Switch roles below and watch the screen change.
Your School
Overview
Students
Attendance
Timetable
Assessments
Results
Fees
Messages
Insights
School website
Term 2 · Week 6 · Head teacher
Today at Your School
The shape of the school, and who needs attention.
Students enrolled
0
Attendance today
0.0%
Staff on duty
0
Fees collected
0%
Attendance, last 14 days
School-wide, all year groups
Needs attention
Raised by your school's own rules
Amara O.S3 Blue
Attendance below 80% for 3 weeks
Daniel K.S2 Gold
Maths average down 14 points
Grace N.S4 Blue
Fees outstanding past second reminder
Illustrative interface shown with sample data. Every module in the sidebar ships today.
Not a bundle of modules. One system, on five pillars.
Most school software grows by bolting on another module. Tavech starts from the platform layer — identity, tenancy, permissions and audit — so every module inherits the same security and the same configurability instead of reinventing them.
Platform
The foundation everything else stands on. Who somebody is, and what they are allowed to do, were the first things built — not features bolted on afterwards.
- Your school, kept separate
- Roles & permissions
- An audit that cannot be edited
- Notifications & documents
School operations
The daily work of running a school: who is enrolled, who turned up, what they were taught and how they did.
- Students & guardians
- Staff & departments
- Attendance & timetable
- Assessments & results
Business
Fees, invoices and collection, with the financial trail a bursar can defend in a board meeting.
- Fee structures
- Invoices & receipts
- Payment providers
- Arrears & reconciliation
Administration
A school configures its own rules — grading, terms, approvals, branding — without waiting on an engineer.
- School settings
- Custom roles
- Branding & domains
- Approval workflows
Intelligence
On the roadmapMoving from “here are your reports” to “here is what needs attention”, with the evidence behind every flag.
- Early-warning signals
- Intervention tracking
- School health
- Explainable insights
Most school software stores what happened. This one tells you what to do about it.
Any system can hold a register and print a report card. The difference is what happens between the record and the decision — and that is a loop, not a module you can bolt on later.
01
One record
A student is one record, not six systems.
Academics, attendance, finance, guardians, communication and documents describe the same child. That connection is what makes everything below possible — and it is the thing a bundle of modules can never retrofit.
02
Signals
The system tells you what needs attention.
Chronic absence, a grade trending down, arrears building, a class whose attendance broke pattern. Not another report to go and read — a short list of what changed, surfaced to the person who can act.
03
Your rules
You define what counts as a problem.
Three absences or five. Arrears at one term or two. A drop of ten points or twenty. Schools differ, so the thresholds, the approvals and the escalations are configuration rather than our opinion in code.
04
Intervention
And what the school did about it.
Flagged, assigned, acted on, parent contacted, followed up, resolved. Six weeks later leadership can answer the question that actually matters: did it help?
05
Accountability
Every change has a name against it.
Who changed this mark from 62 to 74. Who approved this fee waiver. Who published these results. Not a server log an engineer retrieves — a record school leadership can read.
A school that has run on Tavech for two years does not just have cleaner records. It has evidence of what it tried, and what worked.
A child is not six spreadsheets.
In most schools a student's attendance lives in one system, their fees in another and their results in a third — so nobody can see that the child falling behind is the same child whose fees lapsed in March. Tavech keeps one record and lets every workflow write to it.
See how the record connectsAcademics
Classes, subjects, assessments and published results.
Attendance
Daily registers, patterns and chronic absence.
Finance
Invoices, payments, arrears and receipts.
Guardians
Who to call first, and who may see what.
Communication
Every message sent about this student.
Documents
Admission papers, reports, certificates.
You are handing us your children's records. That deserves proof, not assurances.
Four commitments hold up everything else. They are built in rather than promised, which means they hold on your first day and on your ten-thousandth student.
Your records never leave your school
Your school has its own address, its own accounts and its own records. Nothing outside it can reach in — that is checked on every request, not left to a setting.
Permission, not appearance
Hiding a button is not security. What each person can do is checked every single time they ask — not merely left off their menu.
Every change is attributable
Who changed this mark from 62 to 74, and when? Leadership can answer that without opening a server log.
Your rules, not ours
Grading, terms, attendance thresholds, approval chains and roles are configuration — not a change request to our engineers.
The same system. Five different mornings.
A bursar and a parent do not need the same dashboard, and a parent must not be able to reach another family's child. Role decides what a person sees; ownership decides which records that applies to.
What needs attention today — attendance dips, unresolved cases, collection against target.
See it with your school's own data.
We will walk you through Tavech against a real workflow from your school — an admission, a term's results, a fee cycle — and answer the hard questions about migration and security.