Skoolee feature map
Skoolee covers the academic, administrative, financial, operational, and communication responsibilities of a modern K–12 school while keeping each module connected to the same trusted institutional data.
Selected schools, universities, and organizations working with White Mountain Technologies.
Capability map
The categories below are designed for clarity. Individual modules can share data, workflows, users, reports, and notifications across domains.
School lifecycle
The student record gains value as it moves through admissions, enrollment, teaching, assessment, services, finance, communication, and historical reporting.
Online applications, document collection, evaluations, interviews, entrance exams, decisions, and applicant communications.
Student profiles, family relationships, class and section placement, curricula, course selection, fees, and registration confirmations.
Academic calendars, programs, course planning, lessons, timetables, rosters, assignments, resources, and daily teaching activities.
Attendance, conduct, merits, online exams, assessments, appraisals, grades, gradebooks, report cards, transcripts, and deliberation.
Medical, transport, library, activities, store, payments, announcements, notifications, conferences, portals, and mobile access.
Dashboards, reports, historical data, operational analytics, multi-school consolidation, audit history, and year-to-year continuity.
Shared foundations
A module is most useful when it can trust the people, academic structures, roles, dates, records, and policies used by the rest of the platform.
Users, relationships, responsibilities, access privileges, and role-specific experiences are managed consistently across the platform.
Years, terms, cycles, grades, classes, sections, courses, curricula, calendars, and scheduling structures are reused by relevant modules.
Demographics, documents, relationships, enrollment, academic history, services, and communications remain connected.
Operational reports, dashboards, statistics, exports, historical views, and supported AI-assisted summaries draw from governed source data rather than disconnected spreadsheets. Availability depends on the deployed Skoolee release and configuration.
Notifications, messages, calendar events, posts, and portal visibility can be triggered from the processes that create them.
Configuration, data migration, training, testing, rollout, support, and future expansion are managed as a coordinated program.
Skoolee continues to evolve through operational improvements such as responsive workflows, parent requests and approvals, stronger mobile experiences, academic-planning enhancements, and additional reporting and analysis capabilities. Production availability is confirmed against the version and modules deployed for each school.
Choosing the right scope
A school may want to improve admissions, replace grading spreadsheets, introduce parent access, consolidate multiple branches, or establish a complete operational platform. These are different starting points and should lead to different implementation sequences.
The first release should include the structures and data that later modules depend on. For example, reliable grading requires courses, classes, students, teachers, periods, assessment rules, and access privileges to be ready. Parent engagement depends on the underlying academic and operational information being accurate enough to publish.
WMT therefore treats module selection as an implementation-design exercise. The goal is to create a manageable first phase that produces visible operational value while preserving a clear path to the broader platform.
Identify the processes causing the greatest delay, duplication, risk, or communication burden.
Assess the quality, ownership, history, and migration effort of the records required by the selected modules.
Sequence shared setup, users, academics, enrollment, finance, portals, and reporting in a way that supports complete scenarios.
Match training, testing, communication, and rollout pace to the school’s staff, calendar, and change-management capacity.
Questions
No. These are coordinated modules and capabilities within the Skoolee platform. They can be implemented selectively, but they share institutional structures, data, users, and reporting where appropriate.
The first phase should be based on business priorities, data readiness, process dependencies, available implementation resources, and the value the school expects to demonstrate early.
Yes. Skoolee is modular and can be expanded in phases. The original setup and data model should anticipate the agreed roadmap so later modules can build on a stable foundation.
Reporting and analytics are available across the platform, with the exact reports, dashboards, calculations, exports, and permissions confirmed during implementation.
Yes. Skoolee is configured around the school’s structures, roles, terminology, processes, and approved rules within the capabilities of the platform and the agreed implementation scope.
Next step
A discovery session can map your current applications, processes, data, user groups, pain points, and desired rollout sequence to the most appropriate Skoolee modules.
