School administration
School setup, users, roles, admissions, enrollment, records, attendance, conduct, multi-school coordination, audit, and reporting.
School management and student information system
Skoolee brings the information, processes, and people of a K–12 school into one configurable platform—from first inquiry and enrollment through teaching, assessment, reporting, finance, school services, and family engagement.
Overview
School information is created and used across admissions, registration, academics, finance, student services, communications, and leadership. When those areas depend on separate files and disconnected applications, staff repeat work, information becomes inconsistent, and families receive an incomplete view of the student experience.
Skoolee provides a shared system of record and a coordinated working environment. Schools can configure academic structures, curricula, users, roles, workflows, reports, and operational rules around their own model rather than forcing every department into a generic process. A multilingual user interface can support schools and groups operating across different language environments.
Because the platform is modular, an institution can implement the capabilities it needs first and extend the scope in controlled phases. The result is not simply a database; it is a working environment that helps administration, teachers, students, parents, and guardians carry out their responsibilities with clearer information and stronger continuity.
Connected lifecycle
Skoolee keeps each stage connected so information entered once can support the next academic, administrative, financial, and communication process.
Receive online applications, documents, evaluations, interview or entrance-exam decisions, and applicant communications.
Create student records, assign classes and sections, confirm programs or curricula, and manage re-enrollment or transfers.
Plan courses and lessons, publish assignments, manage attendance, support learning resources, and coordinate daily academic work.
Record grades, maintain gradebooks, publish report cards, manage exams, appraisals, transcripts, deliberation, and promotion decisions.
Coordinate tuition and receivables, transport, medical, library, activities, e-store, payroll, accounting, and other school operations.
Keep students and families informed through portals, mobile access, calendars, notifications, conferences, news, and historical records.
Platform scope
The modules work independently where needed and together where shared information creates more value.
School setup, users, roles, admissions, enrollment, records, attendance, conduct, multi-school coordination, audit, and reporting.
Academic structures, curricula, planning, timetables, lesson plans, assignments, exams, grading, gradebooks, report cards, and transcripts.
Admin, teacher, student, parent, and guardian portals; calendars; notifications; activities; conferences; and community communication.
Accounts receivable, tuition, payroll, accounting, transportation, medical, library, e-store, activity management, and operational reporting.
Role-focused self-service experiences that make responsibilities, schedules, posts, attendance, results, and communication easier to reach.
Data migration, external-system exchange, configurable reports, dashboards, analytics, security, cloud deployment, and implementation services.
One school community
Skoolee connects people without giving everyone the same screen or the same authority. Role-based access keeps each experience relevant and controlled.
Coordinate structures, policies, records, workflows, reports, and cross-school visibility from a trusted institutional view.
Work with schedules, rosters, lesson plans, assignments, attendance, conduct, grading, appraisals, and student progress.
Review schedules, assignments, learning resources, results, announcements, activities, and responsibilities through an accessible self-service experience.
Follow attendance, assignments, conduct, academic progress, school communications, conferences, and relevant financial information.
Manage receivables, services, facilities-related processes, payroll, accounting, transport, medical, library, store, and operational reporting.
Maintain consolidated visibility while preserving the structures, users, processes, and reporting needs of each school or branch.
Implementation
A strong implementation begins with how the school actually works—not with a generic feature checklist.
Document the school structure, curricula, branches, roles, processes, reports, integrations, data sources, and priorities.
Set up academic structures, security, workflows, forms, calculations, reports, portals, notifications, and school-specific terminology.
Clean and map existing data, load approved records, reconcile totals and histories, and test complete operational scenarios.
Prepare administrators and user groups, run workshops and checkpoints, launch in controlled phases, and support adoption after go-live.
Published customer experience
WMT has published Skoolee implementation stories and customer feedback from schools in Lebanon, Kuwait, Saudi Arabia, and the wider region.
“Implementing Skoolee saved us up to 3 hours of work per day.”
“Skoolee brought the parents and teachers closer, and comforted our donors and funders.”
Customer quotations are short excerpts from testimonials published on the current White Mountain Technologies website. Publication and logo permissions must be reconfirmed before production launch.
Questions
Skoolee supports K–12 schools with different curricula, divisions, branches, academic structures, and operating models. The configuration is tailored to the institution rather than limited to one curriculum or school type.
No. Skoolee is modular. Schools can begin with priority areas and expand the scope in phases, provided the implementation sequence respects data and process dependencies.
Yes. Skoolee provides role-based portals and mobile access for administrators, teachers, students, parents, and guardians, with the information and actions controlled by each user’s role.
Yes. Multi-school and head-office structures can provide consolidated visibility while preserving school-level configuration, users, data, and reporting.
Yes. Data migration is planned around the school’s existing sources, data quality, history requirements, mapping rules, reconciliation, and approval process.
Yes. The integration scope can use agreed files, APIs, database tables, views, or other controlled exchange methods, depending on the connected system and the school’s technical environment.
Next step
A focused demonstration can follow your school structure, curricula, admissions and enrollment flow, academic processes, portals, finance, operations, integrations, and phased implementation priorities.