Repeated student data
The same student and family information may be entered separately by admissions, academics, finance, medical, transport, and activities.
K–12 solution
A connected operating environment for the whole school community.
Bring administration, academics, communication, student services, finance, and day-to-day school operations into a coordinated model built around the needs of leaders, staff, teachers, students, and families.
- Administration and academics
- Students, teachers, and families
- Finance and school services
- Single- or multi-school operation
K–12 solution
Support the full school year—not isolated transactions.
A school information environment must do more than store student records. It must support admissions, enrolment, academic setup, class organisation, attendance, assessment, grading, communication, finance, transport, activities, health information, reporting, and the daily interaction between the school and families.
The WMT K–12 solution combines Skoolee with implementation and integration services so schools can improve these processes as one connected operating model. The approach can support an individual school or a multi-school organisation, with roles and visibility aligned to the approved structure.
K–12 solution
Reduce fragmentation across offices, classrooms, and families.
Disconnected communication
Teachers, offices, students, and families can receive inconsistent information when each process uses a separate channel or record.
Curriculum and calendar complexity
Grade levels, programmes, subjects, assessment, reporting periods, and school calendars require a coherent academic structure.
Limited cross-school visibility
School groups need controlled head-office insight without weakening the responsibilities and context of each school.
K–12 solution
Skoolee as the operational core.
Skoolee is WMT’s school management and student information system for desktop and mobile use. Its published scope includes user management, academic setup, admissions, enrolment and re-enrolment, registration, assignments, grading, gradebooks, report cards, attendance, conduct, assessments, scheduling, online examinations, portals, communication, reporting, account receivables, library, medical, bus management, activities, payroll, accounting, e-store, alumni, and multi-school management.
The implemented scope is selected according to school priorities. Roles, terminology, curriculum structures, reports, access, notifications, and workflows are confirmed during discovery and configuration.
Skoolee operational core
Connect school administration, academics, engagement, finance, reporting, and selected services in one configurable platform.
Explore SkooleeRole-based portals and mobile
Give administrators, teachers, students, and parents or guardians access appropriate to their roles and school policy.
Explore Portals and MobileImplementation and integration
Prepare data, configure the school model, connect approved systems, train users, and launch around the academic calendar.
Explore ImplementationK–12 solution
Organise the programme around school readiness.
Implementation should follow the school calendar and avoid introducing unnecessary risk during admissions, registration, grading, or year-end processing. A phased plan may begin with academic and user setup, student data, admissions and registration, then expand to portals, assessment, finance, and operational modules.
Data preparation, policy decisions, report requirements, staff availability, training, and family communication are treated as part of the programme—not as activities left until launch.
- 01
Discover the operating need
Clarify objectives, stakeholders, processes, data, constraints, dependencies, risks, and measures before deciding scope.
- 02
Design the connected model
Agree roles, system boundaries, workflows, integrations, migration, governance, security, and the implementation sequence.
- 03
Configure and validate
Build or configure through controlled checkpoints, realistic data, representative scenarios, testing, and hands-on user review.
- 04
Launch, stabilise, and improve
Support adoption, monitor operation, resolve early issues, measure outcomes, and manage later enhancements through change control.
K–12 solution
Connect school roles without exposing more than they need.
Administrative, teacher, student, and parent/guardian portals provide role-appropriate access. Communication, alerts, calendars, events, requests, and published information can be coordinated through the approved channels. Mobile access can extend selected functions to users away from a desktop environment.
Where another platform must remain, the project defines the approved exchange, ownership, timing, validation, and support model. Availability of specific integrations, online services, mobile functions, or custom workflows depends on the selected release and implementation scope.
Shared school records
Use consistent student, family, academic, class, staff, financial, and service context across approved processes.
Role-appropriate access
Separate administration, teaching, student, family, finance, and operational responsibilities without fragmenting information.
School-calendar delivery
Phase setup, migration, testing, training, and launch around admissions, registration, grading, and year-end risk.
K–12 solution
Create a clearer school-wide operating picture.
Leaders gain more consistent reporting and oversight. Offices reduce repeated entry and manual reconciliation. Teachers receive clearer access to class, assignment, attendance, assessment, and communication processes. Students and families receive a more coherent view of information and actions relevant to them.
The outcome is not simply a larger database. It is a more disciplined way to manage the school year, with records, responsibilities, and communication connected around the student.
Clearer administration
Reduce repeated entry, reconciliation, and disconnected records across school offices.
Better classroom context
Give teachers dependable access to classes, learners, attendance, assignments, assessment, and communication.
More consistent family service
Provide students and families with clearer information and actions through approved portals and mobile functions.
Stronger leadership visibility
Create more consistent reporting across academic, administrative, financial, and operational activity.
K–12 solution
Confirm data, curriculum, roles, and calendar constraints.
Readiness begins with the school structure, academic year, grade levels, curricula, courses, classes, users, access profiles, student data, family relationships, policies, and reporting expectations. Existing identifiers and duplicate records should be reviewed before migration.
The school should also identify decision owners for academics, admissions, finance, technology, student services, and communications. Clear ownership shortens configuration cycles and makes acceptance testing more representative.
Decision ownership
Name the people who can resolve policy, data, scope, and acceptance decisions.
Representative validation
Use realistic records, scenarios, exceptions, and roles during testing.
Adoption capacity
Protect time for configuration review, training, communication, and early support.
Questions and answers
Frequently asked questions
Is this only a student information system?
No. The solution can combine student information, academics, portals, communication, finance, reporting, mobile access, and selected school operations according to approved scope.
Can it support more than one school?
Skoolee includes published multi-school and head-office capabilities. The organisation structure, reporting, data separation, and access model are confirmed during implementation.
Which curricula can be configured?
Skoolee’s published scope includes national, high-school, International Baccalaureate, and British curriculum models. The exact academic structure is configured for the school.
Can families and students use portals or mobile access?
Yes, approved student and parent/guardian portal and mobile functions can be included. The available functions depend on release, configuration, and school policy.
How is data moved from existing systems?
Migration follows profiling, mapping, cleansing decisions, trial loads, reconciliation, user validation, and final sign-off.
Can we implement selected modules first?
Yes. A phased implementation can prioritise the processes with the greatest operational need while preserving a coherent long-term architecture.
Next step
Discuss the operating challenge and the right solution path.
A focused conversation can clarify priorities, product fit, services, data, integration, implementation sequence, and the decisions needed to move forward.