No active announcements.
Governance
Every policy below is prepared by the VP Administration, reviewed by the Principal, and approved by the CEO, with a scheduled annual review.
| Field | Value |
|---|---|
| Policy Code | GV-01 |
| Version | 2.0 |
| Policy Owner | Board of Trustees |
| Approval Authority | Board of Trustees |
| Review Cycle | Biennial |
This Charter states, in one place, what kind of institution SULTAN is, who governs it, and what each level of authority may and may not decide alone — the highest document in SULTAN's governance library, which every other policy sits beneath.
SULTAN is a single institution operating four distinct schools under one Board of Trustees and one Executive Management Team — not four independently governed schools sharing a brand. Authority flows from the Board downward through clearly delegated channels; Islamic scholarship and secular educational leadership sit together in the Executive Management Team by design, a structural strength rather than something to flatten into a single generic role.
The Board approves this Charter, all Tier 1 governance documents, and appoints the CEO. The CEO directs day-to-day operation across all four institutions. Each institution's Principal or Head Teacher holds academic and disciplinary authority within their institution, but may not adopt a policy that conflicts with a Board-approved document across all four institutions.
When a named authority-role holder leaves, their authority passes to a confirmed successor or, until then, to their immediate superior — it never lapses or transfers informally. Where a role this Charter assumes is filled has no named holder (such as the Designated Safeguarding Lead today), that gap is tracked and reported to the Board until resolved, rather than left as a silent assumption.
This Charter does not establish SULTAN's legal corporate form, which requires confirmation from the school's own legal and corporate records, not an assumption made here.
Retrofitted from the original v1.0 draft to SULTAN's full 13-section institutional standard (Policy Information, structured sign-off, cross-referenced governance detail).
At SULTAN, assessment is the process by which the quantity and quality of teaching and learning are measured through various techniques, and organised into interpretable forms across a number of variables.
| Score | Grade | Interpretation |
|---|---|---|
| 80–100 | A+ | Outstanding |
| 75–79 | A | Excellent |
| 70–74 | A- | Very Good |
| 65–69 | B+ | Good |
| 60–64 | B | Fairly Good |
| 55–59 | C | Credit |
| 50–54 | C- | Credit |
| 45–49 | D | Pass |
| 40–44 | E | Pass |
| Below 40 | F | Fail |
Correct and final interpretation is the sole responsibility of the Principal and Vice-Principal Academics.
| Field | Value |
|---|---|
| Policy Code | AC-02 |
| Version | 2.0 |
| Policy Owner | Registrar, Royal College |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual |
This Regulation governs everything about a student's academic progress that the Assessment Policy doesn't already cover: how a score becomes a promotion decision, what happens when a student is struggling academically, how graduation and certification work, and how a guardian disputes an academic decision.
Qur'an College and the School of Arabic & Islamic Studies are explicitly exempted from the CA/Examination promotion mechanics above — their progression is measured by memorisation and Tajweed standard instead, governed by the Hifz Regulations.
A guardian disputing a grade, promotion decision, or probation placement raises it with the class teacher, then the Registrar, then the relevant Principal/Head Teacher — a distinct pathway from the Student Code of Conduct's disciplinary appeal.
Promotion thresholds, probation criteria, and special-consideration procedures are proposed structure built on the live Assessment Policy's grading scale — not yet a record of criteria SHRS currently applies, and requiring confirmation before use.
Retrofitted from the original v1.0 draft to the full 13-section institutional standard, adding the explicit Qur'an College promotion exemption and a defined appeals pathway.
| Field | Value |
|---|---|
| Policy Code | IQ-01 |
| Version | 2.0 |
| Policy Owner | Principal, Qur'an College |
| Approval Authority | Board of Trustees, informed by Qur'an College's scholarly staff |
| Review Cycle | Annual, jointly with the Ijazah Governance Framework |
This document gives Qur'an College's 24–36 month memorisation programme a written standard: how much a student memorises and by when, how retention is verified, how progress is assessed, and how the framework connects to the Ijazah a student ultimately earns.
Memorisation without retention is not progress — Muraja'ah (revision) is scheduled and tracked with the same rigor as new memorisation. A weekly consolidation check verifies the week's new memorisation is retained before moving to new material. Progress is measured in verified, examined Juz' completions, with Tajweed accuracy inseparable from memorisation itself.
Progression through the 30 Juz' is pace-based, not time-based — a student needing the full 36 months is not treated as behind if retention is strong. A student whose progress is interrupted by illness or documented hardship has their individual plan adjusted accordingly, rather than being penalised against the standard pace.
Full completion requires all 30 Juz' memorised, a retention-verification period passed, and Tajweed standard confirmed. This document governs the memorisation programme itself — it does not grant the Ijazah; once completion standards are met, the Principal puts the student forward for examination under the separate Ijazah Governance Framework.
Daily/weekly memorisation targets and pass standards are proposed structure pending review and confirmation by Qur'an College's own scholarly and teaching staff, who hold the subject-matter authority this document formalises.
v1.0 → v2.0: added the special-circumstances provision for documented illness/hardship interruptions and clarified the pace-based (not time-based) progression standard.
| Field | Value |
|---|---|
| Policy Code | IQ-02 |
| Version | 2.0 |
| Policy Owner | Principal, Qur'an College |
| Approval Authority | Board of Trustees, informed by Qur'an College's scholarly leadership |
| Review Cycle | Biennial, or immediately if a scholar's status changes |
This framework ensures that when SULTAN awards an Ijazah, the credential means exactly what it claims to mean — a verified, examined, properly transmitted qualification — so a graduate's Ijazah carries the same weight wherever it is presented. It does not itself establish religious authority to grant an Ijazah, which properly rests with the qualified Islamic scholars on staff.
Examination is conducted by the named Ijazah-granting scholar(s), not the student's own day-to-day Muhaffiz alone, separating teaching from certification. On successful examination, the Ijazah is granted and signed by the examining scholar(s), stating explicitly what has been certified. A failed examination results in a defined remediation period, not an automatic re-sit.
Every Ijazah issued is recorded permanently — student name, date, examining scholar(s), what was certified, and a unique reference number — retained indefinitely so it remains verifiable decades later. A third party may request verification, and the Registrar confirms only what the register states, not additional personal information about the graduate.
In the rare event an Ijazah is later established to have been granted in error or through fraudulent conduct, the Principal convenes the named scholars to review the original record before any revocation. A revocation is recorded alongside the original entry — never deleted, only annotated.
This framework should be reviewed and approved by SULTAN's own Qur'an College scholarly leadership before adoption — its role is purely to give their existing religious authority a consistent institutional process and a permanent record.
v1.0 → v2.0: added the third-party Ijazah verification procedure and a formal revocation provision (annotated, never deleted).
SULTAN provides adequate first aid to learners, staff, parents, and visitors during accidental or medical emergencies — ensuring safe use, storage, and administration of medicines, and preserving life.
Covers all members of the SULTAN community, in school and at off-school activities.
Final interpretation is the sole responsibility of the Principal, VP Administration, and Registrar.
SULTAN strives to provide every child with total education in a comfortable, safe environment. Objectives include fostering a safe environment, minimising injury potential, and preparing for and managing hazards.
Correct and final interpretation is the sole responsibility of management staff.
Visitor safety and site security fall under the Health & Safety Policy's security provisions. Every visitor signs in and out at the security post, and wears an identification badge at all times on the premises.
| Field | Value |
|---|---|
| Policy Code | SW-01 |
| Version | 2.0 |
| Policy Owner | Designated Safeguarding Lead (role defined; appointment pending) |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual, and after any serious incident |
SULTAN protects every child — from age 2 through boarding students at Qur'an College and Royal College — from abuse, neglect, exploitation, and harm, whether the risk originates inside the school, at home, online, from a peer, or elsewhere. Every adult connected to SULTAN has a clear, unambiguous duty to act, without delay, on any concern.
Every adult with unsupervised access to children is vetted before appointment. No visitor or contractor is left unsupervised with a child, regardless of sign-in status, per the Visitors Policy (SW-08).
The Parent Portal and the website's AI assistant are treated as safeguarding surfaces, not just IT systems — access is restricted to a child's own guardians and authorised staff, and the AI assistant is configured to direct any safeguarding concern to a named human contact rather than attempt to handle one itself.
This policy is fully defined and awaiting Board adoption. The Designated Safeguarding Lead role it depends on has been formally framed (see the Designated Safeguarding Lead Framework) but not yet filled — appointing one is the highest-priority action tied to this policy.
Retrofitted from the original v1.0 draft to the full 13-section institutional standard, including the explicit link to the Designated Safeguarding Lead Framework.
| Field | Value |
|---|---|
| Policy Code | SW-02 |
| Version | 2.0 |
| Policy Owner | CEO (document); Board of Trustees (appointment) |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual, or immediately upon a DSL appointment or transition |
This framework answers, concretely, the question the Child Protection & Safeguarding Policy raises but cannot resolve on its own: who is the Designated Safeguarding Lead, what do they do day to day, and how does the Deputy DSL structure work across SULTAN's four institutions.
The DSL sits at Executive Management level, not delegated to a single institution's staff, since a safeguarding concern doesn't respect institutional boundaries. The DSL is the first and final point of contact for every disclosure across SULTAN, deciding on internal handling versus external referral and maintaining a single cross-institution safeguarding log. A Deputy DSL per institution is the first point of contact locally, escalating to the DSL the same day.
As of this draft, no DSL has been appointed. Until the Board completes the appointment process, a safeguarding concern is handled jointly by the CEO and the relevant institution's Principal or Head Teacher — an interim arrangement, not a substitute for a real appointment, and tracked as an open governance gap requiring Board resolution.
A DSL appointment is never informal — it is a named Board decision, documented, with a clear start date. The DSL's independence from day-to-day management pressure is a structural requirement: the CEO resources and protects that independence but does not sit inside the DSL's reporting chain for case decisions.
The campus-scaling ratios this framework proposes for future growth need confirmation from a child-protection professional, not just Board judgement, given how much weight they carry.
Retrofitted from the original v1.0 draft to the full 13-section institutional standard, formalising the interim-coverage arrangement pending a DSL appointment.
| Field | Value |
|---|---|
| Policy Code | SD-04 |
| Version | 2.0 |
| Policy Owner | Principal, Qur'an College |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual |
Families entrust significantly more to the school when a child boards. This document gives SULTAN's boarding population a clear, written standard for supervision, safety, conduct, and welfare while resident.
A structured schedule covers wake time, prayer times, meals, study hours, Qur'an memorisation/Muraja'ah sessions for Qur'an College boarders, free time, and lights-out — published to guardians, not left to vary informally.
A boarding student leaves the premises only with prior guardian authorisation, logged by the boarding warden. Guardians are entitled to request a call with the boarding warden within a reasonable response window.
Supervision ratios and current boarding practice are proposed defaults pending on-site confirmation, and this document is awaiting Board adoption.
Retrofitted from the original v1.0 draft to the full 13-section institutional standard, adding the boarding daily-routine and leave-out communication detail.
| Field | Value |
|---|---|
| Policy Code | SW-09 |
| Version | 2.0 |
| Policy Owner | Institutional lead (to be confirmed) |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual, plus after every drill and every real incident |
This plan gives every student, staff member, and boarding house parent a single, rehearsed answer to "what do I do right now" for fire, medical emergency, security threat, and severe weather — rather than leaving each incident to be improvised.
Immediate evacuation via the nearest marked route to the assembly point, with class registers carried and a headcount reported to the Incident Commander — no re-entry for belongings. Medical emergencies beyond first-aid capability trigger an immediate call to emergency services and to the student's guardian, per the First Aid Policy.
A lockdown procedure secures doors, moves students from windows and sightlines, and holds silence until the Incident Commander gives the all-clear, with the security unit and Nigeria Police Force contacted if warranted. Given Lagos's rainy-season risk, severe weather moves students indoors and may delay dismissal if travel is unsafe.
Boarding wardens hold a current room list at all times, with a named on-call senior staff member reachable overnight. Off-site activities carry a current student list and guardian contacts, with the leading staff member acting as Incident Commander until the institutional lead is reached. Parent communication is always one controlled message, never multiple staff independently messaging.
SULTAN's site has not yet been assessed by a fire-safety professional as part of this draft — evacuation routes and assembly points must be walked and confirmed on-site before this plan is treated as operative.
v1.0 → v2.0: added post-incident review triggers, boarding/off-site coverage, and the drill-and-real-incident review cycle.
A caring, safe, friendly environment is necessary for effective teaching and learning. SULTAN aims to provide such an environment where learners develop in a relaxed, secure atmosphere.
Bullying is intentional, repetitive hurting of one person by another, often involving an imbalance of power. At SULTAN, expectations of good behaviour are defined by our Islamic creed. Aims include:
Applies to all members of the SULTAN community — learners, staff, visitors, parents, and guardians — in school and at off-school activities.
Final interpretation is the sole responsibility of the Principal, VP Administration, and School Guidance Counsellor.
| Field | Value |
|---|---|
| Policy Code | SD-02 |
| Version | 2.0 |
| Policy Owner | VP Administration |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual |
This Code states, in one place, what SULTAN expects of every student's conduct — in class, around campus, online, and off-site when representing the school — building on the Anti-Bullying & Disciplinary Policy rather than duplicating it.
Searching a student's belongings and any use of physical intervention are both deliberately narrow in scope — used only as a last resort, always logged, and always reported to the Principal the same day.
A guardian may appeal a suspension or more serious consequence to the Principal's immediate superior, decided by someone who was not part of the original decision.
Retrofitted from the original v1.0 draft to the full 13-section institutional standard, adding the graded-response ladder and appeal pathway.
| Field | Value |
|---|---|
| Policy Code | SD-03 |
| Version | 2.0 |
| Policy Owner | VP Administration |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual, in step with the Student Code of Conduct |
This Handbook teaches every SULTAN student — from Nursery through Qur'an College — what is expected of them and what they can expect from the school in return, written to be read and understood by the student themselves.
Report cards and grading follow the Assessment Policy; promotion criteria are in the Academic Regulations. Conduct expectations are governed in full by the Student Code of Conduct — this Handbook explains why the Code exists rather than restating its disciplinary procedure. Personal devices and school digital systems are used per the Acceptable Use Policy, and online conduct affecting another student is treated exactly like on-campus conduct.
Boarding students follow the Boarding Regulations for daily routine and conduct. A student with a welfare concern can raise it with any staff member, who acts the same day per the Child Protection & Safeguarding Policy. In an emergency, students know their assembly point and follow their teacher, per the Emergency Response Plan.
Uniform and presentation are governed by the Dress Code Policy, applying equally to every student regardless of institution. A student representing SULTAN at any off-site activity follows this Handbook's conduct expectations identically to on-campus conduct.
v1.0 → v2.0: added the Uniform & Extra-Curricular Activities section, and cross-links to every governing policy it summarises.
To establish a standard dress policy across staff categories. Appearance reflects on the school before students, parents, and visitors, and must be clean, decent, and professional, mindful of safety and role.
Applies to all SULTAN staff — permanent, contract, or otherwise employed.
Final interpretation is the sole responsibility of the Principal/VP Administration.
SULTAN is responsible for equality of opportunity in access and outcome throughout school life, so present and future life chances are widened, not impeded — though equal access does not necessarily mean equality of outcome.
Recognises and celebrates similarities and diversities among individuals and groups, working hard to help each person maximise their personal achievement.
SULTAN believes learners' future careers are crafted from their experience, progress, and achievements. Learners aged 11–17 receive independent career guidance.
Final interpretation is the sole responsibility of the Principal, management, and guidance counselling unit.
| Field | Value |
|---|---|
| Policy Code | IT-02 |
| Version | 2.0 |
| Policy Owner | ICT Head |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual, or after any data breach |
This policy states what personal data SULTAN collects about students, guardians, and staff; why; who can see it; how long it is kept; and what rights a guardian has over their own and their child's data — across the Parent Portal and the website's AI assistant.
A guardian can already see all data linked to their child(ren) via the Parent Portal dashboard. Correction requests are made directly to the Registrar. Data portability and erasure rights are still being defined and require a Board decision informed by legal advice. A separate image and media consent structure — asking guardians, at admission, whether a child's photo may be used internally, publicly, or not at all, recorded per child and revocable at any time — is proposed and awaiting Board adoption; until it is adopted, no identifiable student photo is published to a public SULTAN channel without the guardian's specifically confirmed consent.
The Parent Portal and AI assistant are hosted by real technology providers acting on SULTAN's instructions, not independent controllers of the data. Where a safeguarding concern requires sharing a child's data with an external statutory body, that duty overrides this policy's confidentiality provisions.
This policy does not certify compliance with the Nigeria Data Protection Act 2023 — retention periods, data-subject rights, and breach-notification timelines are open items requiring legal input before adoption.
Retrofitted from the original v1.0 draft to the full 13-section institutional standard, adding the explicit list of what the Parent Portal does and does not store.
SULTAN works closely with parents and guardians in a partnership that benefits every child. Complaints are handled fairly, openly, and honestly, per national educational guidance and global best practice.
Routine concerns are dealt with through class teacher discussion. Occasionally a concern develops into a formal complaint. Anonymous complaints are discouraged.
Final interpretation is the sole responsibility of the governing board and school management.
| Field | Value |
|---|---|
| Policy Code | PA-02 |
| Version | 2.0 |
| Policy Owner | VP Administration |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual |
This Handbook is the one document a family reads to understand how SULTAN works day to day — summarising and pointing to each governing policy's full procedure, rather than restating it, so nothing here drifts out of step with the source document.
Report cards and grading follow the Assessment Policy; promotion and academic standing follow the Academic Regulations. Any concern about a child's welfare is raised with the class teacher or the Designated Safeguarding Lead, per the Child Protection & Safeguarding Policy — this Handbook does not reproduce disclosure-handling detail meant for staff. Boarding families are pointed to the Boarding Regulations for the full supervision and routine procedures.
What the Parent Portal stores is described in full in the Data Protection & Privacy Policy. SULTAN's real fee schedule has not yet been finalised — the live admission page discloses this gap publicly rather than hiding it. In an emergency, guardians receive one controlled message via WhatsApp broadcast and/or Parent Portal notification, per the Emergency Response Plan.
A general concern goes to the Complaint Policy; a disciplinary decision to the Student Code of Conduct's appeal process; a grade or promotion decision to the Academic Regulations' appeal process; a data-protection concern to the Data Protection & Privacy Policy's appeal process — one signpost per situation, not a duplicate procedure.
v1.0 → v2.0: added the emergency-communication summary and consolidated per-topic signposting to each governing policy.
| Field | Value |
|---|---|
| Policy Code | PA-05 |
| Version | 2.0 |
| Policy Owner | CEO |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual |
This policy governs the principles behind SULTAN's admission process — who is eligible, how selection decisions are made, what happens to application data, and how a disputed decision is appealed — sitting above the live 12-stage admission process already published on the Admission page, not replacing it.
Admission decisions are based on the entrance exam, test, and interview, applied consistently regardless of a family's background, in line with the Equal Opportunity Policy. Required documentation is exactly what the live Admission page already states: birth certificate, two passport photographs, and a report sheet or testimonial from the previous school — verified for authenticity before an offer is confirmed.
A transfer student's previous-school report is reviewed for any disclosed disciplinary or safeguarding history, consulting the Designated Safeguarding Lead where a question arises, before an offer is confirmed. An applicant who meets eligibility but cannot be offered a place due to capacity is placed on a waiting list, in the order assessed, with a realistic estimate of when a place might become available.
Fee structure, scholarship criteria, and international-student arrangements are left deliberately open, exactly as the live Admission page already discloses to visitors — this policy does not invent figures to fill that gap. A guardian withdrawing a student notifies the Registrar in writing; refund terms are not yet defined, pending the school's fee schedule.
A guardian disputing a non-admission decision may request a review by the CEO, who was not part of the original entrance-assessment decision.
Retrofitted from the original v1.0 draft to the full 13-section institutional standard, adding the transfer-student and waiting-list provisions.
| Field | Value |
|---|---|
| Policy Code | IT-03 |
| Version | 2.0 |
| Policy Owner | ICT Head |
| Approval Authority | CEO |
| Review Cycle | Annual |
This policy gives students and staff one place that defines acceptable use of SULTAN's digital systems — the Parent Portal, the AI assistant, and any physical digital infrastructure — the detailed policy the Student Handbook and Staff Handbook both point to rather than restate.
A staff member posting in a capacity representing SULTAN does not share a student's image, name, or personal data without consent already governed by the Data Protection & Privacy Policy. A guardian's Portal account is provisioned at enrollment and deactivated per the Records Retention Policy; a staff member's access is deprovisioned the same day their employment ends.
Device- and network-specific rules (personal devices on campus, school Wi-Fi) remain open pending a description of SULTAN's actual infrastructure — this policy does not invent rules for infrastructure that may not exist yet.
v1.0 → v2.0: added the Social Media & Account Lifecycle section (provisioning at enrolment, deprovisioning on exit).
| Field | Value |
|---|---|
| Policy Code | IT-04 |
| Version | 2.0 |
| Policy Owner | Registrar, jointly with the ICT Head |
| Approval Authority | Board of Trustees |
| Review Cycle | Annual, or after any change to the Data Protection Policy's retention sections |
This policy sets, for the first time, how long each category of record SULTAN holds is kept — closing a gap the Data Protection & Privacy Policy, Academic Regulations, and Admissions Policy each correctly deferred to this document rather than inventing their own answer.
| Record category | Proposed period |
|---|---|
| Parent Portal account (guardian) | Last child's enrolment + 2 years |
| Student academic records | Enrolment + 7 years after leaving |
| Disciplinary records | Enrolment + 3 years |
| Safeguarding records | Until age 25, or 7 years, whichever longer |
| Ijazah register | Indefinite |
| Staff records | Employment + 6 years |
| Fee/payment records | 7 years |
Where litigation, a regulatory inquiry, or an ongoing safeguarding investigation makes early deletion of a specific record inappropriate, normal retention is suspended for that record until the hold is lifted. At each annual review, the Registrar and ICT Head jointly reconsider whether every category still reflects what SULTAN's systems actually collect.
Every period above is a proposed default grounded in common school-record-keeping practice, not yet a period SULTAN currently applies or one verified against a specific Nigerian statute — Board confirmation with legal input is required before this policy is treated as binding.
v1.0 → v2.0: added the legal-hold procedure and the periodic data-minimisation review at each annual cycle.
| Field | Value |
|---|---|
| Policy Code | IT-05 |
| Version | 2.0 |
| Policy Owner | ICT Head |
| Approval Authority | CEO |
| Review Cycle | Annual, or immediately on any material change to what an AI system may do |
This policy states what any AI system operating under the SULTAN name may and may not do, how it must identify itself, what data it may access, and when a human must be involved instead. SULTAN today operates exactly one live AI system — the website's chat assistant; a Parent AI, Student AI, or Admissions AI do not exist yet, and this policy is written to also cover those future touchpoints, not to describe them as already running.
A named staff member reviews the AI system's actual behaviour against this policy, not just its intended configuration. A change to the AI provider or model version is logged, with a note on whether the change was tested against this policy's scope boundaries. Before any new AI touchpoint goes live, it undergoes a pre-launch review against this policy and the Data Protection & Privacy Policy's Data Protection Impact Assessment requirement together.
Any AI system granted broader authority than these principles describe would require an explicit Board-approved amendment, not a quiet expansion in practice.
Retrofitted from the original v1.0 draft to the full 13-section institutional standard, adding the pre-launch review requirement for any new AI touchpoint.
I'm an AI assistant, not a staff member — I can answer questions about the school and help with schoolwork, but for anything official please use the contact details below.