How to move school work from scattered registers and spreadsheets into a controlled workflow.
These guides are written around School Master’s real product workflows. They explain the decisions a school should make before importing data, assigning permissions or switching a daily process. The goal is not to replace school policy; it is to make the operational steps easier to understand and audit.
Start with the workflow, not the software screen
A reliable ERP setup begins by deciding what the school treats as authoritative: the GR or admission identifier, class/division names, fee heads, academic year, who may collect fees, who may reopen results, and which parent email is trusted for a child. Once those rules are clear, software becomes much easier to configure.
School ERP implementation guide
A step-by-step framework for moving from registers and Excel files to a tenant-scoped digital school workspace.
ADMISSIONSAdmissions workflow
How to structure enquiry, follow-up, admission confirmation, GR assignment and Student Master creation.
FEESFee management guide
Plan fee heads, collection controls, discounts, late fees, receipts and reconciliation without duplicate ledgers.
ATTENDANCEAttendance workflow
Design class-wise attendance rules, teacher authority, correction responsibility and parent visibility.
RESULTSMarks and result finalization
Prepare subjects and maximum marks, validate entries, finalize results and control authorized reopen.
PARENTSParent Portal setup
Link verified parent identities to children without exposing staff permissions or unrelated student records.
DATA MIGRATIONExcel import and column mapping
Prepare school data, map custom headers, review duplicate errors and stage imports safely.
OFFLINEHybrid offline-to-cloud
Understand trusted PC enrollment, local work, queued changes, conflict decisions and safe reconnect.
SECURITYSecurity and tenant isolation
Review School Master’s public explanation of tenant scope, roles, sessions, restore safety and provider boundaries.
What these guides deliberately do not do
They do not contain copied school data, pre-filled real student records, or a one-size-fits-all promise that every school should use the same fee structure. Each school remains responsible for verifying its own legal, financial, academic and identity data before it becomes authoritative inside the ERP.
A simple implementation order
- Set the school profile, academic year and financial year.
- Standardize class/division names and student identifiers before import.
- Import or create students and staff, then verify a sample manually.
- Configure staff accounts and restrict module/class access.
- Set fee plans, attendance and result workflows only after master data is stable.
- Enable Parent Portal links after parent email identities have been verified.
- Take a backup checkpoint before any large import or restore action.
- Use optional external providers only after their real credentials and templates are approved.
Need a product overview first?
See what is already live in the School Master platform and which third-party services still require setup.
View Product Status →