AI for a small school with no IT department

Almost every article about AI in schools quietly assumes a technology lead, a procurement process, and someone to configure things. Plenty of schools — small day schools, yeshivos, single-site primaries — have none of that, and the guidance does not scale down. It scales down like this.

What you can skip

Some of the standard advice exists because large organisations have problems you do not.

• Single sign-on integration. Useful at two thousand students, unnecessary at two hundred. Email and password is fine.
• A formal procurement process. You need the vendor's answers in writing, not a tender.
• A dedicated pilot committee. One teacher who is willing and one person who can make decisions is a pilot.
• Elaborate acceptable-use documentation. One page that staff actually read beats twelve that they do not.

What you cannot skip

Someone must own it

Not a department — a person, by name, who decides what is on the blocked list and who staff go to. The failure mode in small schools is that everyone assumes someone else is handling it, and the answer to "who set these rules" is nobody.

You must test the filter yourself

Twenty minutes, once, before students have accounts. Set a blocked topic, try to reach it in chat, then try the image tool, then try on your own phone. You do not need technical knowledge for this — you need to try to break it and notice what happens.

Parents must be told first

This costs nothing and is the difference between a school that informed its community and one that was found out. In a small school, where word travels faster and relationships are closer, it matters more rather than less.

The assessment question is unavoidable

No tool solves it, and it is not a technology problem. Which tasks measure unaided ability, and how do you know they still do? A small school can answer this in one staff meeting, which is an advantage over a large one.

Choose for the absence of an administrator

The properties that matter most when nobody is watching the dashboard:

• Sensible defaults. If the tool is only safe once configured by an expert, it is not the right tool for you.
• Server-side filtering. Anything requiring installation on devices means someone maintaining installations, and that person does not exist.
• Fails closed. Nobody is monitoring whether the safety check is running, so it needs to protect itself.
• Locked categories that no administrator can switch off — including an administrator who clicks something without understanding it.
• A short review page rather than a dashboard requiring interpretation.

In other words, exactly the properties that matter for a big school, but load-bearing rather than merely desirable, because there is no team to compensate for their absence.

A realistic plan for a small school

1. One person owns it. Write the name down.
2. That person spends twenty minutes trying to break the filter, including on a personal phone.
3. One staff meeting: what it is, the three use categories, who to ask.
4. One letter to parents before any student account exists.
5. One class for three weeks.
6. Widen. Review at the end of term, for half an hour.

That is the whole programme. It fits in a term without anybody's job changing.

The advantage you have

Small schools do this better than large ones more often than anyone expects. You can change the blocked list the afternoon you decide to. Every teacher can be in one room. You will hear about a problem the day it happens rather than in a report next term.

The thing large schools have is process, and process is mostly a substitute for the direct knowledge you already have.