Enquiry to verified student
Track admission work before finalizing a student into Student Master so enquiry status and operational records do not become mixed.
Run everyday school work from one controlled system instead of scattered registers and spreadsheets.
School Master connects the operational work a school repeats every day: admissions, Student Master, staff, attendance, fee collection, results, parent access, reports, imports, backup and controlled offline-to-cloud sync. The goal is not to replace one pile of forms with another. The goal is to keep each record connected, permission-scoped and explainable from enquiry to report.
A school ERP should make the daily workflow clearer, not heavier.
Schools often begin with different Excel files, paper registers and separate tools for attendance, fee receipts, marks and parent communication. That can work while the number of records is small, but it becomes difficult to answer simple operational questions later: which student record is authoritative, who changed a fee entry, which class a teacher was allowed to access, whether a result was already finalized, or whether a parent account is linked to the correct child.
School Master is built around those hand-offs. An admission can become a verified student record. The same student identity is then used by attendance, fees, academic progress, results and school documents. Roles and class/division scopes restrict access, while audit and backup controls help the school preserve a dependable operational history.
Class-scoped daily attendance
Record present, absent and leave states inside the permitted class and division scope instead of relying on unrelated attendance sheets.
Collections with a clear receipt trail
Keep fee plans, discounts, late fees, receipts and collection history tied to the same student record used by the rest of the ERP.
Marks to controlled finalization
Validate marks, prepare results and stop ordinary changes after finalization until an authorized workflow reopens them.
Parent access without staff access
Keep parent identity and linked-child access separate from teacher, office and administrator permissions.
Bring existing school Excel data safely
Use the official template or map existing workbook headers, then preview and validate before committing records to the school workspace.
Built for schools that already have data.
Moving to an ERP should not require a school to pretend its old data is perfect. School Master supports an official import format as well as flexible column mapping for existing spreadsheets. A school can choose a worksheet, map its local headings to School Master fields, review the preview, resolve validation problems and then import through the same controlled transaction path.
The mapping step only translates column names. It does not bypass required-field checks, duplicate protection, tenant rules or other validation. This distinction matters because a convenient import is useful only when the school can still trust the records after the import is complete.
Practical starting point: prepare a small representative sample first. Confirm student identifiers, class/division naming and required fields before moving the full workbook.
Keep core work moving when internet reliability is a real problem.
For schools that need supported offline operation, an enrolled trusted school PC can run the core ERP against a local SQLite database. Local changes are queued and synchronized later through the hybrid sync workflow. The design keeps cloud user accounts, permissions and subscription edition authoritative so a local device cannot simply grant itself higher access or a paid plan.
Synchronization is designed around explicit device enrollment, local-to-cloud ID mapping, idempotent change processing and conflict review. When both sides change the same record, the workflow does not silently guess which side should win. The school can review the conflict and choose the intended result.
Security is part of the workflow, not a separate marketing page.
Tenant isolation
Operational data is scoped to the correct school workspace.
Operational data is scoped to the correct school workspace.
Role and action permissions
Viewing, adding and editing can be separated by user role and module.
Viewing, adding and editing can be separated by user role and module.
Teacher class scope
Teacher access can be restricted to assigned class/division combinations.
Teacher access can be restricted to assigned class/division combinations.
Parent separation
Parent accounts are designed around verified identity and linked children, not staff permissions.
Parent accounts are designed around verified identity and linked children, not staff permissions.
Backup and restore checks
Restore safety validates school ownership before accepting a backup into a workspace.
Restore safety validates school ownership before accepting a backup into a workspace.
Provider separation
Optional payment and messaging providers remain inactive until the school or platform completes the required provider setup.
Optional payment and messaging providers remain inactive until the school or platform completes the required provider setup.
Original implementation guides for school teams.
The public School Master knowledge center explains not only what each module is called, but how schools can prepare for it. Separate guides cover admissions, fee management, attendance, results, parent access, Excel import and hybrid offline work. The resources section provides preparation notes that can be reviewed before a school enters real data.
School ERP implementation
Plan the rollout so the ERP becomes the authoritative operational system instead of creating another parallel register.
Read guide →Admissions, fees and attendance
Set up everyday workflows around verified records, clear responsibility and predictable hand-offs.
Browse guides →Parents, privacy and product status
Understand what parents can access, how school-scoped data is handled and which optional integrations still require external setup.
View product status →Evaluate the workflow before uploading real school data.
Use the features, guides, FAQ and preparation resources to understand the system first. When the school is ready to work inside the ERP, open the separate secure application area.