School ERP modules
Find the modules your school needs first
School management software modules for admissions, student records, timetable, attendance, fees, exams, and family portals. Start with one student record and the academic calendar; later modules read those two.
One catalog, connected workflows
Search by the job your team needs to complete. Every module links back to shared student records, academic dates, permissions, and reporting instead of creating another isolated data store.
Platform & access
Every user gets the right access from day one. Schoolyi gives administrators fine-grained control over who can view and change student records, fees, exams, and settings, so each role sees a workspace built for their job.
Explore module
Calendar & structure
The academic calendar is the backbone of your school year. Terms, holidays, working days, and events flow into attendance, exams, fees, timetables, and leave, so every team works from the same dates and structure.
Explore module
Students & families
Keep complete student records, link parents and guardians, issue certificates, and give families a clear portal view of fees, grades, and attendance, all tied to class placement and the active academic year.
Explore module
Teaching & timetable
Define who teaches what, build and publish timetables, handle substitutes, and plan lessons against the same calendar your exams and attendance use, so teachers spend time teaching, not chasing schedules.
Explore module
Grades, homework & exams
From daily homework to full exam cycles, including papers, invigilation, seating, revaluation, and published report cards, with workflows that respect teacher assignments and homeroom scope.
Explore module
Admissions
Run admission cycles from public application through tests, interviews, shortlists, offer letters, and enrollment into the student roster, with a guardian-facing track page families can use without an account.
Explore module
Fees & finance
Fee structures, collections, receipts, online payments, autopay, and finance back office, including budgets, expenses, vendor bills, cash flow, and payroll runs, in one operational finance layer built for school bursars.
Explore module
Daily operations
Mark homeroom attendance aligned to the calendar, manage staff and student leave with overlap checks, publish notices, and keep events visible across the school. That is the daily rhythm class teachers and office staff rely on.
Explore module
Communication & portals
Internal messaging, channel conversations, in-app notifications, and dashboards tailored to staff, teachers, parents, and students, so announcements land where people already work, not in yet another inbox.
Explore module
Library & back office
Vendor master, purchase orders with goods receipt, inventory movements, library circulation, laboratory equipment, and a school file drive: the back office layer storekeepers, librarians, and admin teams need.
Explore module
HR & employment
Post jobs with public apply, onboard hired candidates, run monthly payroll with payslip PDFs, manage salary records, and handle expense claims, with HR and finance working from the same staff picture.
Explore module
Boarding & residential
Run day and boarding students on one roster: house assignments, mess menus, residential leave, health notes, and parent views that respect who lives on campus versus who commutes.
Explore module
AI assistant & tools
Staff get navigation help, notice drafts, and text polish, while learners get guided K-12 doubt clearing, explanations, practice, revision, and quizzes from a local AI worker on your server. Optional MCP registry connects approved external tools with role gates and audit.
Explore module
Reports & insights
Role based dashboards, a catalog of operational reports, and finance insights with charts, giving leadership visibility without exporting spreadsheets every Monday morning.
Explore module
Adoption order
Which modules to adopt first, and why the order matters
The modules depend on one another. Adopting them in dependency order means each phase builds on data that is already correct, instead of recalculating what an earlier phase got wrong.
Foundation
Student identity and the academic calendar
Nothing else can be correct until a student exists once, in one place, and until the platform knows which days the school is actually open. Every downstream number, attendance percentages, fee due dates, timetable slots, term boundaries on a report card, is calculated from these two things. Schools that skip straight to the module causing them the most pain end up rebuilding it once the roster is right.
Why not later: Every other module reads the student record and the calendar. Configuring them later means recalculating everything already entered.
Phase one
Admissions and fees
These are usually the two workflows with the clearest cost of the current process, and they sit next to each other for a reason: admissions creates the record and the guardian relationship that fee invoicing depends on. Running admissions in the platform while fees stay in a spreadsheet means re-keying every family, which is the specific duplication the platform is meant to remove.
Why not later: Fee ledgers attach to the student and guardian records admissions creates. Reversing the order means creating families twice.
Phase two
Timetable, attendance, and the family portal
Once the roster is trustworthy, teaching operations can move across. Timetable comes before attendance because the register is generated from it, and the family portal comes after both because it is the surface where errors in either become visible to parents. Opening the portal before attendance and fee data are reliable is the most common way schools lose family confidence in a new platform.
Why not later: Registers are generated from the timetable, and the portal exposes attendance and fee data to families. Both need to be right first.
Phase three
Assessment, reporting, and leadership views
Examinations and report cards come last, not because they matter least but because they aggregate everything above. A report card reads marks, attendance, and term dates; a leadership dashboard reads all of it plus fee collection. Moving assessment first produces reports that draw on data still living elsewhere, which is worse than leaving assessment where it is for another term.
Why not later: Report cards and dashboards aggregate marks, attendance, calendar, and fee data. They are only as accurate as the modules feeding them.
Full catalogue
Every module, in one list
The sequencing above covers the common path. This is everything, including the modules that only some schools need.
- Platform & accessSecure sign in, roles, and school wide settings
- Calendar & structureAcademic years, classes, and the calendar every module shares
- Students & familiesRoster, guardians, certificates, and family portals
- Teaching & timetableStaffing, period grid, substitutes, and lesson planning
- Grades, homework & examsGradebook through hall tickets, seating, and report cards
- AdmissionsPublic apply, track, offers, and enrollment to roster
- Fees & financeCollections, online pay, budgets, payroll, and insights
- Daily operationsAttendance, leave, notices, and school events
- Communication & portalsMessages, conversations, and role specific dashboards
- Library & back officeInventory, procurement, library, labs, and files
- HR & employmentHiring, payroll, appraisals, and staff finances
- Boarding & residentialHouses, mess, leave, and guardian visibility
- AI assistant & toolsOn-server help, learning support, and MCP integrations
- Reports & insightsDashboards, scheduled reports, and finance insights
Module selection FAQ
What schools ask when deciding how much of the platform to adopt, and in what order.
Do we have to adopt every module?+
No. Schools commonly run admissions, student records, and fees for a full year before adding anything else.
The modules read one shared student record, so adding a module later does not require re-entering data. A module you skip does not leave a gap the others cannot work around.
Which module should we start with?+
Start with the workflow currently costing your team the most hours, provided student records and the academic calendar are configured first.
In practice that is usually admissions or fees. Starting with the most painful workflow gives the rollout visible early value, which matters for staff confidence more than technical sequencing.
Can modules run alongside our existing systems?+
For a transition period, yes, and most schools do this for at least a term.
Avoid running two systems permanently for the same workflow, because the records diverge and staff learn to trust whichever one they entered data into. Set a date to switch off the old process when you plan the module.
How are modules connected?+
They read the same student records, guardian relationships, academic calendar, and permission model rather than exchanging copies.
A student marked as withdrawn stops appearing in registers, stops accruing fee instalments, and disappears from the parent portal because all three views read one record, not three synchronised ones.
What if a module does not fit how our school works?+
Tell us during evaluation with the specific case, not the general requirement.
Some constraints are configuration and can be changed; others are architectural and cannot. Knowing which one you are dealing with before you sign is the difference between a configuration task and a workaround you live with for years.
Do modules cost extra individually?+
Pricing is quoted for the scope you adopt rather than assembled from a public per-module price list, because student count, campus count, and implementation effort change the figure more than the module mix does.
The pricing page explains the assumptions behind a quote, so schools can compare a platform on the work required to go live.
Buyer guides
School software topics school leaders search for
Focused guides, not generic country templates. Each page explains how Schoolyi connects admissions, fees, exams, and family portals.
- Cloud school management systemBrowser based SMS for admissions, fees, exams, and family portals.Read guide
- School management softwareAdmissions, roster, fees, exams, transport, and family portals on one calendar.Read guide
- Best school management software2026 buyer checklist: calendar integrity, fee receipts, publish gates, phased rollout.Read guide
- Student information system (SIS)One roster for enrollment, fees, timetable, and exams, zero re-entry.Read guide
- K-12 school management softwareKindergarten through grade 12 on one platform, promotions without duplicate rows.Read guide
- Online school management systemBrowser-based SMS, no on-site servers, staff and families sign in from any device.Read guide
- School ERP softwareFinance, payroll, and vendor AP on the same cloud SMS roster.Read guide
- School CRM softwareInquiry to enrollment without spreadsheet chaos.Read guide
- School transport softwareRoutes, buses, and transport fees beside student records.Read guide
- School vendor managementVendor bills and purchase orders inside school finance.Read guide
- IB World SchoolsPYP, MYP, and DP on one SMS, calendar, fees, and gradebook.Read guide
- IGCSE & CambridgeBritish curriculum day schools, terms, options, and exams.Read guide
- International day schoolsMulti-board campuses with one roster and phased rollout.Read guide
- Software comparison guideEvaluate vendors with a practical buyer checklist.Read guide
- Admissions softwareApply, track, offer, and enroll into live roster records.Read guide
Need help choosing phase one?
Use the module finder or bring your student count, curriculum, and first-year priorities to a focused walkthrough.
Already using Schoolyi? Sign in