A school ERP built around controlled daily workflows, not just data entry screens.
School Master is a reusable multi-school ERP platform for schools that want to organize admissions, students, staff, attendance, fees, academics, parent communication, reports and operational records in one tenant-scoped system.
Why the product exists
Many schools already have useful data, but it is spread across registers, individual spreadsheets, messaging groups and staff computers. The problem is not only digitization. The harder problem is deciding which record is authoritative, who may change it, and how one workflow should feed the next without creating duplicate versions.
School Master is therefore designed around connected workflows. An admitted student becomes part of Student Master. That same student record is then reused in attendance, fees, results and school documents. A teacher account can be restricted to its classes. Parent access is separate from staff access. Large imports go through validation instead of silently inserting every row.
Generic product, school-specific data
School Master is not a copy of one school's database. A reference implementation may help shape workflows, but each customer school supplies its own profile, logo, signature, stamp, student data, staff data, fee structures and operational rules. School-specific records remain scoped to that school's workspace.
Cloud and offline are treated differently on purpose
The cloud workspace remains the authority for users, permissions and subscription edition. An enrolled local PC can continue supported core work offline, but it cannot grant itself new users or a higher paid plan. This keeps the convenience of local operation separate from security and commercial authority.
Software readiness and provider activation are not the same thing
School Master can contain complete integration code for services such as Meta/WhatsApp or Razorpay while the real provider is still not active. The public Product Status page deliberately separates “code ready” from “provider configured” so schools are not told that an external service is live before credentials, approvals and controlled testing are complete.
What we optimize for
- clear school ownership of authoritative data;
- tenant isolation between different schools;
- least-privilege access for teachers and staff;
- repeatable import and backup procedures;
- parent access limited to linked children;
- practical operation on desktop, tablet and mobile screens;
- safe offline work for supported core workflows where internet reliability is a concern.