All resources · 2,198 words · 10 minute read

School inspection preparation software: what to look for

How to evaluate school inspection preparation software: framework mapping, double entry, export, permissions, Arabic support, and questions for vendors.

The useful question is not which product is best. It is whether the record you build inside it maps to the framework you are actually inspected against, whether evidence arrives from systems your staff already use, and whether you can take everything out again if you change your mind. A product failing any one of those three costs more than it saves, however good the demonstration looks.

What follows is an evaluation framework and a list of questions to put to any vendor, written to be useful whether you buy something, buy something else, or decide a spreadsheet is still the right answer, which for some schools it genuinely is.

First, decide whether you need self-evaluation software at all

A shared drive and a well-built spreadsheet are a legitimate answer, and a school running one properly often presents better than a school running a product badly. If you have one site, a small staff, one framework, and one disciplined person who owns the record, software will not fix a problem you do not have.

When a spreadsheet stops being a reasonable answer

The signals are practical rather than philosophical. Any two or three of these together usually mean the spreadsheet has become the constraint.

• Several people need to write to the record in the same week, and someone is now merging versions by hand.
• You need a history: who changed a judgement, when, and what it said before. Spreadsheets overwrite silently.
• Permissions matter. Appraisal notes and pupil-level data cannot sit in the same open file as the evidence base.
• Finding an artefact takes longer than filing it did. That crossover is the clearest single signal.
• You run more than one campus, or one campus against two frameworks, so evidence has to be tagged two ways.
• The record depends on one person who may be on leave during the inspection window.
• Someone outside the school (a reviewer, a board, a group office) needs a view of part of it, and your only mechanism is emailing a copy.

If none apply, keep the spreadsheet and spend the money on the evidence itself. If several do, the rest of this article is about how to choose.

Eight questions to ask of any school inspection preparation software

1. Does it map to the framework you are actually inspected against?

This eliminates most candidates. Many products are built around a generic quality-management model and then described as suitable for any inspection regime, which means your team performs the translation in their heads, every time, forever.

Ask which national frameworks are supported by name (Oman's OAQA, the UAE School Inspection Framework, Saudi Arabia's ETEC arrangements, Qatar's QNSA), and see the mapping on screen rather than in a brochure. Then ask who updates it when an authority revises its framework, how quickly, and at whose cost. Names and structures change: Oman's authority was renamed the Oman Authority for Quality Assurance of Education by Royal Decree 12/2026, and parts of the web have still not caught up. A vendor who says "we will look at that when it happens" is telling you something.

For groups operating in more than one country, ask whether one artefact can be tagged against several frameworks at once, or whether you will maintain parallel records; we have written about running one evidence base against four frameworks separately.

2. Does evidence arrive from systems teachers already use, or does it require double entry?

This predicts whether the product is still in use in year two better than any other question. If a teacher has to log into a second system to upload something they produced elsewhere, the record decays by about November.

Ask what a classroom teacher has to do that they do not already do. If the honest answer is "log in and upload", plan for decay. If observations, attendance, assessment and CPD records are captured where the work already happens, you are buying a habit rather than an obligation. Ask what it connects to, and what happens to the connection when either side updates.

3. Can you export everything and leave?

Ask this early, in exactly those words, and watch the reaction; a confident vendor shows you the export during the demonstration. Does the export include the source files, not just a summary report. Does it preserve dates, authorship and the links between artefacts, or flatten everything into a list of documents whose meaning is gone. Is it self-service, and available after the contract ends. An evidence base you cannot remove is not your record; it is theirs, and you rent access to it.

4. Who can see what?

Self-evaluation, appraisal and evidence have different audiences, and a product that treats them as one pool will eventually cause a problem you cannot undo.

Ask whether permissions are genuinely role-based: whether a head of department can see another department's appraisal records, whether a teacher sees their own observations and only their own, whether an external reviewer can be given time-limited read-only access to part of the record, and whether there is a log of who viewed and changed what. That last protects your staff as much as your data.

5. Does it work in Arabic on the parent-facing pages as well as the admin console?

Many products localise the administrator interface and stop there. The parent portal, the automated messages and the generated PDFs stay in English, which is where families actually meet the system.

Right-to-left is not translation. Ask to see, on screen and not in a slide: the parent portal in Arabic on a phone; a generated PDF report in Arabic with its tables laid out right to left; a notification in Arabic; and a screen mixing Arabic text with English subject names and Western numerals, which is where layouts break. Ask whether Hijri dates display alongside Gregorian, whether the calendar defaults to a Sunday-to-Thursday week, and who wrote the Arabic: a translator familiar with education, or an engine.

6. What happens to your record when a member of staff leaves?

This is the question schools forget, and it is where evidence bases quietly lose their history.

Ask whether evidence is owned by the school or attached to the individual's account, what deactivating a user does to the observations they recorded and the CPD they completed, and whether a leaver's records can be reassigned to a successor role. Then the commercial version: if the licence is priced per user, does removing a departed member of staff remove their history from your view. The consequences are in our piece on CPD records that survive a teacher's departure.

7. Does it show you what is missing, not just what you have?

Any product can store files. The value is in the blanks: which standards have no evidence, which departments have not been observed this year, which artefacts are two years old and quietly ageing into irrelevance. Ask to see the view a deputy head would look at on a Tuesday morning to decide what to chase. If it is a list of uploaded documents rather than a map of coverage and gaps, the product is a filing cabinet with a search box.

8. What does implementation actually require, and who does it?

Migration is where the cost hides. Somebody has to move the existing folder in and tag it, and that somebody is usually your head of quality, in term time.

Ask how much historic evidence the vendor will migrate and tag, and at what cost; who trains the staff, in which language, and whether that is a webinar or a named person; what the first term demands in staff hours; and how pricing scales (by student, by staff member, by module), including what is not in the number you were given.

The checklist to take into any vendor meeting

Print this. It is useful even if you buy nothing.

1. Which national frameworks do you map to by name, and can you show me the mapping on screen?
2. Who updates that mapping when an authority revises its framework, how fast, and at what cost?
3. Can one piece of evidence be tagged to more than one framework?
4. What does a classroom teacher have to do in this system that they do not already do elsewhere?
5. Which of our existing systems does this connect to, and what breaks when either side updates?
6. Show me a full export now: what format, does it include the files, does it keep dates and authorship?
7. Is export self-service, and for how long is it available after the contract ends?
8. Can a reviewer be given read-only access to part of the record, for a limited period?
9. Can a head of department see other departments' appraisal records? Prove it.
10. Is there an audit log of who viewed and changed what?
11. Show me the parent portal in Arabic on a phone, and a generated PDF report in Arabic.
12. Are Hijri dates supported alongside Gregorian, and does the calendar default to Sunday to Thursday?
13. When a teacher leaves, what happens to their observations and CPD records, and does removing them from our licence remove their history?
14. Show me the screen that tells me what evidence is missing.
15. How much of our existing evidence will you migrate and tag, and at what cost?
16. Who runs the training, in which language, and are they a named person?
17. What does the first term cost us in staff hours, and what is not included in the price quoted?
18. Which schools like ours can we speak to without you in the room?

How to run the trial so it tells you something

Do not evaluate a product by watching a demonstration of the vendor's sample data, which has been arranged to look complete.

Take one real standard you are weak on and put your own evidence through it end to end: upload it, tag it, record an observation against it, write the self-evaluation paragraph, and generate whatever the product generates. Do it with two of your own staff, one of whom dislikes new systems. Then export what you created and open it on your own machine. That takes an afternoon and tells you more than a procurement process.

Signals worth pausing on

• A demonstration dataset in which every standard is fully evidenced.
• Reluctance to show export, or a change of subject when you ask.
• "We can build that for you" about something core.
• Per-module pricing for capabilities you assumed were included.
• No named person responsible for your onboarding.
• An Arabic interface shown only on marketing pages.

Before you buy anything, know what you are storing

Software organises an evidence base; it does not create one. If the underlying artefacts are undated, unattributed and show a single moment rather than a change, a product will store weak evidence more tidily. Start from what counts as evidence in a school inspection, get the observation cycle producing consistent records, and place both in the term-by-term sequence in our guide to Gulf school inspection readiness. Schools in Oman may want the background in our explanation of OAQA school evaluation first.

Frequently asked questions

Is a spreadsheet enough for school self-evaluation? For a single small school with one framework and one person who owns the record, yes. It stops being enough when several people need to write at once, when permissions matter, when you need a history of changes, or when finding an artefact takes longer than filing it did.

What should school inspection preparation software actually do? Map evidence to the framework you are inspected against, collect that evidence from systems staff already use, show you what is missing as clearly as what you have, control who sees what, and let you export everything and leave without losing the record.

How do I test a vendor's product properly? Put one real standard through it end to end with your own evidence and two of your own staff, rather than watching a demonstration of the vendor's sample data. Then ask for a full export of what you created and open it yourself.

What happens to our evidence if we cancel? Ask before you sign, and get the answer in the contract. You want a self-service export of all files and records, in an open format, including dates, authorship and the links between artefacts, available for a stated period after the contract ends.

How Asabya Academy helps

Asabya Academy is a product in this category, so read this as disclosure rather than recommendation and put it through the checklist above like any other. It maps self-evaluation and evidence to OAQA in Oman, the UAE School Inspection Framework, ETEC in Saudi Arabia and QNSA in Qatar, holds lesson observations, CPD, appraisal and stakeholder surveys alongside the evidence they produce, includes an external reviewer portal and a view of what is missing, and runs in Arabic and English on parent-facing pages as well as the admin console.