No Code for Education: Tools Your School Can Build Itself
No code for education means the people who run the school — registrars, business managers, heads of year — build the tools they need instead of waiting on a vendor or an IT backlog. Describe the process, get a working tool with logins, permissions and an audit trail.
Free to start: 1 member, 3 projects, no credit card.
Every school runs on a spreadsheet nobody trusts
Attendance in one file, incidents in another, admissions in an inbox, and a single member of staff who understands how it all fits together. When they are off sick, the process stops.
What no code for education actually replaces
Not the student information system. The dozen small processes that live around it, which no vendor sells and every school runs by hand.
The shared spreadsheet with no access control
Everyone with the link can edit any row, including the ones holding student data. Nobody can say who changed a mark or a contact number, or when.
The process that lives in one person's inbox
Admissions enquiries, trip consent, supply cover. It works because someone remembers the steps, which is not a system.
The report rebuilt by hand every term
Someone exports three files, pastes them together, fixes the formatting and emails a PDF. Six hours, every time, and the numbers are already stale.
The vendor quote you cannot justify
A module for one workflow, priced per student per year, with a twelve-month contract and a rollout that lands in the middle of exam season.
Six tools schools build first
Each one is small enough to finish inside a single planning period and useful enough that staff notice the difference the same week.
| Tool | What it replaces | Build time |
|---|---|---|
| Attendance and absence log | A shared sheet plus a paper register | 2–3 hours |
| Admissions enquiry pipeline | An inbox and a colour-coded spreadsheet | 3–5 hours |
| Behaviour and incident record | A form nobody fills in, filed in a drawer | 3–4 hours |
| Facilities and maintenance requests | Emails to the site manager | 2–3 hours |
| Trip consent and payment tracking | Paper slips and a tally on a whiteboard | 3–4 hours |
| Budget and purchase approvals | A signed form walked between offices | 4–6 hours |
Building education apps with AI covers learning platforms and student portals. This page is about the operational tools that run the school itself.
Student data needs permissions and an audit trail
This is the reason a shared spreadsheet is the wrong home for anything about a child. A tool built here comes with role-based access, single sign-on and an audit log recording who changed what and when — so a form tutor sees their own group, the safeguarding lead sees what they are entitled to, and the office can answer a records question with evidence rather than memory.
- Role-based access, so a teacher, a head of year and the office each see a different slice.
- Audit logs on every change — who, what, when — available on every plan.
- Single sign-on, so accounts follow the staff list instead of a shared password.
- Shared databases, so admissions, attendance and reporting read the same records.
Rules differ by country and district. Confirm your own obligations before a tool touches student records — in the United States, the Department of Education's Student Privacy Policy Office is the reference point.
US Department of Education student privacy guidanceAn audit log showing every change to a student record
How a school rolls this out in one term
The schools that succeed do not start with the biggest process. They start with the one that annoys the most people and is safe to get wrong.
- 1
Week 1 — pick one annoying process
Maintenance requests or trip consent. Low stakes, high visibility, and no student records in version one.
- 2
Weeks 2–3 — build it with the people who use it
Describe the process in plain language, get a working tool, then sit with the office staff and change what is wrong while they watch.
- 3
Weeks 4–6 — run it alongside the old way
Keep the spreadsheet until the tool has survived a full cycle. Trust is earned by the tool being boring, not by a launch email.
- 4
Rest of term — add the second and third
Once one process has moved, the next is faster because the staff list, the permissions and the habits already exist.
What it costs a school
Priced per project and per member of staff who builds, not per student. That is the difference that makes this affordable for a single department: the free plan covers three projects with no card, Solo is $25/month for five, and Builder is $49.99/month for ten with two builders — less than most single-workflow modules cost per year.
Prices are per account, not per pupil. Compare the full plan lineup before you commit a department budget. See all AgentUI plans
No code for education: common questions
What is no code for education?
It is the practice of letting school staff build their own operational tools — attendance logs, admissions pipelines, approval workflows — by describing the process instead of writing code. The tool comes with logins, role-based permissions and an audit trail, so it is safe to use around student data.
Do we need an IT department to use it?
No. The people who already run the process build it. IT is worth involving for single sign-on and for deciding which staff roles see which records, but they do not need to write or maintain anything.
Will this replace our student information system?
No, and it should not try to. Your SIS stays the record of truth for enrolment and grades. This covers the processes that live around it, which no vendor sells as a product and most schools run on spreadsheets.
Is it safe for student data?
The controls you need are there on every plan: role-based access, single sign-on and an audit log of every change. What varies is your own legal obligation, which differs by country and district, so confirm it before a tool touches student records.
What happens when the person who built it leaves?
This is the failure mode that kills spreadsheet-based processes. The tool stays in the school's account rather than one person's file, permissions survive the handover, and the audit log shows what changed. A real team also reviews builds and helps with integrations.
How much does it cost per student?
Nothing. Pricing is per project and per staff member who builds, not per pupil, which is why a single department can afford it. The free plan covers three projects with no card required.
Start with the process nobody enjoys
Bring the spreadsheet your school actually runs on and turn it into a tool with logins, permissions and a record of every change.
Free to start: 1 member, 3 projects, no credit card.