School quality assurance software moves accreditation preparation from a last-minute drive to regular work throughout the year. Most schools know the scene: before reviewers visit, files are gathered, documents printed and evidence hunted down in scattered drawers, and then everything stops until the next cycle. A good system makes self-evaluation, evidence and improvement plans part of everyday school management.
This page explains the quality and accreditation module in wakp's school management system: what it offers, how it works step by step, and how it uses the school's other data as evidence.
What problem does it solve?
- Late preparation: evidence is collected before the visit, so the chance to actually improve is lost.
- Standards without follow-up: the standards document exists, but nobody knows which indicators are met and which are not.
- Scattered evidence: documents on different computers and in different drawers, not tied to the indicator they support.
- Improvement plans with no owner: review notes are written but nobody is named to act, or given a date.
- Data that could be evidence: attendance and class placement are already in the system, but get re-collected by hand.
Accreditation in Egypt and Saudi Arabia: who decides?
Accreditation is an official body's decision in each country, and wakp does not stand in for it. In Egypt, the National Authority for Quality Assurance and Accreditation of Education accredits education institutions, including pre-university schools; its site describes it as a government body established by Law No. 82 of 2006. In Saudi Arabia, the Education and Training Evaluation Commission evaluates, classifies and accredits schools within its programmes. The standards, indicators and review procedures are issued and updated by these bodies, so every school should work from the current official document. wakp's role is to organise the school's own work around that document.
How wakp's school quality assurance software works, step by step
1. Quality units
You start by defining a quality unit for each quality school within the organisation (for example an Arabic-section school and a languages school), with a display name and the school's official code. Screens are filtered by unit, year and stage (primary, preparatory and so on), so each team works on its own unit.
2. The standards framework
The framework is built on 7 domains: supportive environment, learner personal development, teaching, learning and assessment, governance and leadership, the competent teacher, quality assurance and improvement, and learning outcomes. Under each domain are criteria and indicators such as building suitability, safety and security, school climate, support for students with special needs, teaching planning, a student assessment plan, leadership effectiveness, professional development, and attainment level in each subject.
Each indicator is recorded with a code, domain, title, description and stage scope. You can import indicators from a CSV file and document the source of the standards with a link to the official body's document, so every reviewer knows which text the framework was built on.
3. Assessing each indicator
Each criterion has three tabs.
Assessment: set the status: not assessed, not met, partly met or met. Write strengths, gaps and reviewer notes.
Evidence: add an item with a title and a kind: a document link, an uploaded file, or a snapshot of wakp data, such as students placed in classes, the classes themselves, and attendance, absence and lateness records. The last kind saves a great deal of effort because the evidence comes out of the system rather than a hand-made file.
Improvement: record the improvement action, its owner and the due date, so a gap becomes work with an owner and a deadline.
4. Analytics
The analytics screen shows the self-evaluation status, wakp's own indicators, the distribution of assessments across the four statuses, activity over the last 7 days, progress by domain, and review alerts. Management sees where the school stands now, not on visit day.
Capabilities table
| Capability | What wakp provides |
|---|---|
| Quality units | A unit per quality school with an official code and year and stage filters |
| Standards framework | 7 domains and indicators with code, title, description and stage scope |
| Import | Import indicators from CSV and document the official source |
| Assessment | Four statuses with strengths, gaps and reviewer notes |
| Evidence | Links, files and snapshots of wakp data |
| Improvement | Action, owner and due date per indicator |
| Analytics | Progress by domain, assessment distribution and alerts |
Evidence from school data: examples of the link
What sets wakp apart is that part of the evidence already exists in the system:
- Students and classes: a snapshot of student placement in classes from the student management system.
- Attendance, absence and lateness: snapshots from the records of the school attendance system.
- Assessment and results: evidence for assessment and attainment indicators can rest on data and documents from the student assessment system and school exam control system.
- Daily follow-up: items that need a decision appear for users who have the permission on the school management dashboard, while evidence and standards stay in this module.
- Teachers and professional development: the competent-teacher indicators connect to staff files in the school HR management system.
Document-link and file evidence remains necessary for what is not in the system, such as meeting minutes or written plans.
How a school can organise quality work
General practices that help any school:
- Name an owner for each domain instead of leaving everything to one coordinator.
- Start with honest assessment. An inflated rating hides the gaps that need fixing.
- Tie every rating to evidence. "Met" with no evidence is a claim, not proof.
- Turn each gap into an action with an owner and a date, and review them regularly.
- Review monthly, not yearly, so work does not pile up.
- Use the current official text of the standards, and check for updates the body issues.
An illustrative example: one indicator from assessment to improvement
The example shows a workflow; it is not about a particular school. Suppose an indicator in the "supportive environment" domain concerns safety and security:
- Assessment: the team rates the indicator "partly met" and writes that an evacuation plan exists but has not been tested, recording that as a gap.
- Evidence: the team uploads the evacuation plan and the safety meeting minutes, and adds a link to the official document if there is one.
- Improvement: it adds an action, "run and document an evacuation drill", with a named owner and a due date.
- Follow-up: the gap stays in the review alerts until done; afterwards the rating is updated and new evidence added.
- The overall picture: progress in the "supportive environment" domain moves on the analytics screen.
A suggested annual calendar for quality work
A general order that can be adapted to the accreditation cycle in your country:
- Start of the year: update quality units and indicators from the current official text, and assign owners to the domains.
- First months: an honest first self-evaluation and identification of the major gaps.
- Mid-year: review improvement plans and what was achieved, and refresh evidence.
- Before the official review: check evidence against indicators and revisit the indicators that are not met.
- After the review: record reviewers' notes and turn them into improvement actions.
Common mistakes in quality work
- Treating quality as a file prepared for a visit: its effect ends when the visit does.
- Collecting evidence unrelated to the indicator: a pile of paper is no substitute for the right proof.
- Not refreshing evidence: old evidence does not show how the school is now.
- Ignoring gaps: marking everything "met" does not improve the school and exposes it at review.
- Importing indicators from an old copy: make sure the imported document is the one currently in force.
Paper files or a quality system?
| Area | Paper files or Excel | wakp quality module |
|---|---|---|
| Standards | A separate document | Indicators recorded with code and domain, importable |
| Assessment | A sheet updated by hand | Defined statuses with strengths and gaps |
| Evidence | Scattered drawers and computers | Evidence tied to the indicator, including snapshots of school data |
| Improvement | Notes with no owner | Action, owner and due date |
| Follow-up | Periodic meetings | Analytics and review alerts |
An implementation checklist for the quality module
- Define quality units with the official code for each quality school.
- Import indicators from CSV using the current official text, and document the source link.
- Name an owner for each of the 7 domains.
- Assess each indicator and record strengths and gaps.
- Add evidence to each indicator, using wakp data snapshots where they fit (placed students, classes, attendance, absence and lateness records).
- Turn every gap into an improvement action with an owner and due date.
- Review the analytics regularly: progress by domain, 7-day activity and review alerts.
How do you prepare a quality review meeting?
The periodic review meeting is what turns data into a decision. A school can follow this agenda:
- Review the self-evaluation status: how many indicators are assessed and how many remain unassessed, and in which domain.
- Unmet indicators: what the gap is, which evidence is missing and who is responsible for completing it.
- Review alerts: items that need the reviewer's opinion or an update.
- Overdue improvement plans: every action past its due date and why.
- Meeting decisions: new actions with an owner and date, recorded on the indicator itself.
It is best that domain leads attend, not leadership alone, since each domain needs someone who knows its evidence, and that a short record is circulated after the meeting.
What the quality module does not do
The module does not grant accreditation and does not issue a quality certificate; that decision belongs to the competent official body in each country. Nor does it assess indicators on the school's behalf; it organises assessment, evidence and improvement and puts in front of the team what it needs to judge for itself. Responsibility for accurate assessment therefore stays with the school's team, and the system remains a tool for organisation, documentation and follow-up.
How wakp helps
- A clear framework of domains and importable indicators.
- Self-evaluation with defined statuses and reviewer notes.
- Evidence tied to the indicator, including live snapshots from school data.
- Improvement plans with an owner and due date.
- Analytics that show progress and alerts.
- An installable web app (PWA) with role-based permissions.
Who is it for?
Private, international, Azhar and national schools preparing for an official accreditation or evaluation in Egypt or Saudi Arabia, or wanting to manage their quality internally, especially organisations that run more than one school or stage. The other modules are on the school management system features page.
Frequently asked questions
What is school quality assurance software?
Software that organises a school's self-evaluation against a framework of standards and indicators, gathers the evidence that supports each indicator and tracks improvement plans, so accreditation readiness becomes year-round work.
Does wakp replace the accrediting body?
No. Accreditation is the decision of the official body in your country. wakp is an organising tool that helps the school prepare its evaluation, evidence and improvement plans.
Can the official body's standards be used in wakp?
Yes. Indicators are managed with a code, domain, title, description and stage scope, and can be imported from a CSV file, with the source of the standards documented by a link to the official document. A school should use the current official text, not an outdated template.
What kinds of evidence does the system accept?
A document link, an uploaded file, or a snapshot of wakp's own data, such as students placed in classes and attendance, absence and lateness records.
Can one organisation have several quality units?
Yes. You define quality units, each representing a quality school with a display name and an official code (for example an Arabic-section school and a languages school), and filter by unit, year and stage.
Can improvement plans be tracked?
Yes. Each indicator has an improvement tab recording the action, owner and due date, and the analytics show progress by domain and review alerts.
Sources
Update log
- — English version written alongside the Arabic feature page
- — On-page SEO check; internal links to the home page, the features hub and neighbouring features; all links point to English URLs; link to the dashboard page