School management software training
LiveSchools365 user guide
Operate the school ERP from student admissions and attendance through exams, fee collection, payroll, and parent communication. This is the same workshop order used during client onboarding.
Approved training pack
Current workflow walkthrough
How to use this guide
Operate the school from intake through reporting
- Begin with the student lifecycle and admissions process.
- Use the academic, attendance, and exam workflows as daily operations.
- Review finance, communication, and resource modules before governance and access checks.
One-page handout
Print-ready summary for client sharing
- One trusted student record from inquiry to admission keeps enrolment organized and auditable.
- Daily school work is managed in one connected system: attendance, leave, timetable, and exams.
- Teacher allocation, class schedules, and marks entry improve academic control and visibility.
- Finance remains transparent through fees, accounting, receipts, and payroll in one cycle.
- Communication is streamlined through notices, parent updates, and class messaging without exposing private teacher contact details.
- Governance is protected through master data, permissions, and role testing so each user sees the correct experience.
Forms involved
- Admissions dashboard
- Student inquiries
- Student registration
- Student records
- Printed admission form
- Student promotions
- Student transfers
Important points
- Start with the family enquiry and decide whether it is ready for enrolment.
- Complete guardian, address, and placement details before saving the student record.
- Always check campus, class, and section before finalizing a student placement.
- Use the printed admission form as the official handover document for family and admin records.
Forms involved
- Teacher subject allocation
- Timetable
- Study materials
Important points
- Match each teacher to the right subject and class before any timetable is published.
- Show the client how to spot timetable clashes before the schedule goes live.
- Keep learning resources aligned to the exact class, subject, and academic term.
Forms involved
- Attendance dashboard
- Attendance register
- Leave management dashboard
Important points
- Explain that the class register is the daily source of truth for attendance tracking.
- Review late attendance, absences, and exceptions before closing the register for the day.
- Leave should be approved by policy and entitlement, not by informal agreement.
Forms involved
- Exam management
- Marks entry
- Online assessments
Important points
- Walk through the exam calendar and term setup before the paper is published.
- Use marks entry to protect fairness by checking max marks and valid paper rules.
- For online assessment, confirm timing, availability, and publish state before learners begin.
Forms involved
- Finance dashboard
- Fees and payments
- Accounting workspace
- Payroll management
Important points
- Show clients that finance is about traceability: fee, receipt, and posting must match.
- Review all invoice and payment details before closing the financial cycle.
- Payroll should be explained as a controlled approval process, not just a calculation screen.
Forms involved
- Communication portal
- Notice board
- Parent-teacher connect
Important points
- Explain the difference between notices, broadcasts, and direct family contact before sending anything.
- Use the right audience filter so the message reaches the correct class, role, or parent group.
- Parent-teacher communication works best when it stays inside the approved school channel and record trail.
Forms involved
- Purchase management
- Store management
- Shop management
Important points
- Train the user to follow the full stock trail: order, receive, issue, and sell.
- Store operations should show who requested the item, who approved it, and who received it.
- In the shop flow, pricing and stock availability must be checked before the sale is confirmed.
Forms involved
- Master data
- Teacher registration
- School settings
Important points
- Explain that master data is the foundation of the system and should be consistent everywhere.
- Teacher registration is where staff identity, teaching roles, and payroll readiness are aligned.
- School profile and settings should reflect the real institution so reports and documents look correct.
Forms involved
- User permissions
- Role experience testing
- School profile
Important points
- Show the client that permissions are about what a role should see, not just what it can click.
- Use persona testing before rollout to check the exact experience for different user types.
- School profile updates should be reviewed carefully because branding and system identity affect many screens.
Additional forms added
Missing operational and governance forms now included
- Student onboarding and learner profile management
- Leave management, leave balances, and policy setup
- Online assessment dashboard, papers, and intelligence reports
- Teacher registration, school settings, profile, and user permissions
Forms involved
- Student onboarding
- Student records
- Student transfers
- Student lifecycle profile
Important points
- This is the student master record that the rest of the school depends on.
- Keep family, placement, and contact information aligned so the student experience stays consistent.
- Transfer history should be used to preserve continuity and explain any movement between campuses or grades.
Forms involved
- Leave dashboard
- Leave entry
- Leave balances
- Leave policy setup
Important points
- Explain that leave is managed by policy, entitlement, and evidence, not by ad hoc approval.
- Review staff and student leave balances before finalizing decisions or closing the period.
- Use policy setup to standardize decisions and reduce confusion across schools and teams.
Forms involved
- Online assessment dashboard
- Assessment papers
- Question bank and blueprints
- Assessment reports
Important points
- Use the assessment analytics view to catch quality, difficulty, and coverage issues early.
- A strong paper setup makes result publishing smoother and keeps assessments fair.
- The reporting layer helps the school act before small issues become bigger academic problems.
Forms involved
- Teacher registration
- School settings
- School profile
- User permissions
Important points
- This is where the school defines who staff are, what they do, and what they can access.
- Check branding and profile values early because they appear across documents, reports, and public communication.
- Permissions should be reviewed before role changes go live so access stays aligned with responsibility.
Forms involved
- User permissions
- Role experience testing
- School security setup
- Access validation
Important points
- This is the quality-check step: make sure each role sees only the screens it should see.
- Persona testing is the easiest way to show the same system from the administrator, teacher, or parent view.
- Access review is part of governance and should be repeated whenever roles or campus settings change.