Skoolee school administration

Turn school administration into a connected, traceable operating process.

Skoolee brings school setup, users, admissions, enrollment, student and family records, attendance, conduct, permissions, reporting, and multi-school oversight into one governed administrative foundation.

  • Connected applicant-to-student record
  • Role-based administration
  • Multi-school coordination
  • Audit and reporting

Selected schools, universities, and organizations working with White Mountain Technologies.

  • Liwa University
  • Abu Dhabi University
  • Mohamed Bin Zayed University for Humanities
  • Al-Bayan Bilingual School
  • A'Takamul International School
  • Nouria

Overview

Create one administrative record that can support the rest of the school

Administrative work begins before a student is enrolled and continues long after the first registration is complete. Applications, documents, family relationships, class placement, status changes, attendance, conduct, official letters, and reporting all depend on accurate information and clear ownership.

Skoolee connects these activities around the same institutional structures and student record. Admissions information can become an enrolled-student profile without being re-entered. Class and section assignments can support timetables, teacher rosters, grading, portals, fees, and reporting. Updates can be controlled by roles and traced through the appropriate history.

The objective is not merely to digitize forms. It is to establish a dependable administrative foundation that other academic, financial, operational, and communication processes can trust.

Administrative capabilities

Manage the structures, people, records, and controls behind daily school administration

The exact configuration is aligned with the school’s curricula, branches, divisions, terminology, policies, and approval responsibilities.

01

School and academic setup

Configure schools, branches, divisions, cycles, grades, classes, sections, academic years, terms, calendars, and organizational structures.

02

Users, roles, and access

Manage administrators, principals, teachers, staff, students, parents, guardians, and access privileges by role and responsibility.

03

Admissions

Receive applications, documents, evaluations, interviews, entrance exams, decisions, letters, status tracking, and applicant communication.

04

Enrollment and registration

Register new and returning students, assign classes and sections, manage course choices, transfers, withdrawals, capacity, and confirmations.

05

Student and family records

Maintain demographics, relationships, contacts, documents, histories, status changes, academic placement, and institution-specific information.

06

Attendance, conduct, and merits

Record daily or course attendance, behavior, referrals, merits and demerits, follow-up actions, certificates, and relevant communications.

07

Multi-school administration

Support head-office visibility and consolidated reporting while maintaining each school’s approved structure, users, processes, and data boundaries.

08

Audit, letters, and reporting

Generate operational and official reports, certificates, letters, exports, dashboards, and user-action history according to permissions.

Applicant-to-student process

Move information forward without repeating it at every administrative stage

The flow can be adapted to the school’s policy, required documents, evaluation steps, fees, approvals, class structures, and communication standards.

  1. 01

    Receive and qualify

    Capture inquiries and online applications, required documents, evaluation criteria, interviews, tests, and admissions decisions.

  2. 02

    Convert and complete

    Create the student and family record, confirm acceptance conditions, complete required information, and prepare enrollment.

  3. 03

    Enroll and place

    Assign the academic year, curriculum, grade, class, section, courses, fees, services, and relevant operational arrangements.

  4. 04

    Maintain and govern

    Manage status changes, attendance, conduct, documents, letters, transfers, withdrawals, and corrections through authorized processes.

  5. 05

    Report and continue

    Provide accurate records to academics, finance, portals, services, official reporting, year-end progression, and the next registration cycle.

Governance

Make ownership, access, and record quality explicit

Administrative systems become unreliable when responsibility for a field, document, decision, or status is unclear. During implementation, the school should define who creates information, who validates it, who may change it, and when it becomes official.

Role-based access should reflect actual responsibilities rather than broad departmental labels. Admissions staff, registrars, principals, teachers, finance teams, nurses, transport coordinators, and head-office users should see and change only what their work requires.

The school should also define its correction and audit approach. Sensitive changes—such as identity data, enrollment status, class placement, attendance, conduct, or official documents—need clear authorization and traceable history.

01

Data ownership

Assign accountable owners for applicant, student, family, enrollment, attendance, conduct, and organizational information.

02

Access design

Map each role to the screens, records, actions, approvals, and reports required for its responsibilities.

03

Record standards

Define required fields, document rules, coding standards, duplicate prevention, validation, retention, and correction procedures.

04

Operational calendar

Align admissions, re-enrollment, registration, class placement, reporting, promotion, and year-replication milestones.

Implementation readiness

Prepare the administrative foundation before exposing dependent modules

Academic, financial, portal, and reporting processes depend on accurate administrative setup. The first implementation phase should therefore validate complete end-to-end scenarios, not only individual forms.

01

Source data

Identify existing databases, spreadsheets, paper files, documents, codes, histories, and duplicate records.

02

Configuration decisions

Confirm structures, terminology, numbering, statuses, required fields, workflows, letters, reports, and access privileges.

03

Migration and reconciliation

Map and clean the data, load controlled batches, reconcile counts and relationships, and obtain owner approval.

04

Operational testing

Test applicant, enrolled student, returning student, transfer, withdrawal, correction, attendance, conduct, and reporting scenarios.

05

User preparation

Train each role on its own responsibilities, exceptions, quality controls, and handoffs to other departments.

Questions

Frequently asked questions

Can an online application become a student record after acceptance?

Yes. The implementation can carry approved applicant information into the student and family record, reducing re-entry while preserving the admissions and enrollment history.

Can Skoolee support more than one curriculum or school division?

Yes. School structures, curricula, cycles, grades, classes, sections, and branches can be configured according to the institution’s approved model.

How are user permissions controlled?

Access is role-based and can be aligned with the screens, actions, data, approvals, and reports required by each responsibility.

Can attendance and conduct be shared with families?

Yes. Approved attendance, conduct, merits, follow-up, and related communication can be made available through portals and notifications according to school policy.

Can head office see consolidated information across schools?

Yes. Multi-school structures can provide consolidated and school-level views, subject to the configured data boundaries and user permissions.

Next step

Review your administrative lifecycle with the Skoolee team

A focused session can follow your admissions, enrollment, student records, roles, attendance, conduct, multi-school structure, reports, and migration requirements from beginning to end.