The year repeats. The work shouldn't.
A term-start procedure written once and run every August with a tick and a name against each step. An announcement you can prove landed. Staff training tracked to the certificate. Choose Education at setup and all three are queued.
Default project tabs
Goals is on for the outcomes you report; Capacity is off — teaching load lives in the timetable.
Projects created on day one
- Academic Year
- Staff & Training
- Facilities
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
07:45 — the term-start routine runs itself
Write the enrolment and term-open procedure once, then run it each August. Every step carries a tick and the name of the person who ticked it, so the question stops being “did we do it” and becomes “who did, and when”. Nobody rebuilds the list from last year's email.
11:20 — the safeguarding update reaches everyone, and you can show it
An announcement goes to the whole workspace, the important ones pin, and read receipts — or a required acknowledgement — come back. The policy itself lives in the Policy Library with its own effective date, so “what is our policy on…” has exactly one answer.
16:10 — the certificate is on the shelf, not in an inbox
The Learning Hub tracks every course and certification from planned to in progress to completed, with the provider and the link attached. A training audit becomes a filter rather than an archaeology project across six people's mailboxes.
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working — or install any one of them on its own, later, from the marketplace.
Checklists & SOPs
Write a standard procedure once — enrolment, term open, a trip, an inspection — then run it whenever you need it, ticking each step with a record of who did what.
- One written procedure, run many times
- Every step ticked, with the person who ticked it
- Onboarding, term start, incident response
- The record of the run is the evidence
Announcements
Workspace-wide updates that pin when they matter, with read receipts — or a required acknowledgement — coming back to you.
- Post to the whole organisation at once
- Pin the ones that must stay visible
- Read receipts as they land
- Required acknowledgement where it counts
Learning Hub
Every course, certification and mandatory training on one shelf, from planned to in progress to completed, with the provider and the link attached.
- Courses and certifications per person
- Planned → in progress → completed
- Provider and link on every entry
- Filter the shelf by status
How Education actually runs.
Each of these is a project in Noots — its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
These sit on top of the whole product.
- Leadership and governor meetings become owned action items without anyone taking minutes
- The Policy Library keeps every rule with its effective date and one authoritative text
- Codex, the workspace handbook, holds runbooks and staff onboarding as searchable pages
- Intake gives facilities, IT and admin requests one front door instead of a corridor conversation
- Ten interface languages, a high-contrast palette and a text-size setting on every account
The honest edges.
- Noots is not a student information system or a virtual learning environment. It holds staff and operational work — not pupil records, grades, attendance or coursework.
- Timetabling is not built in. Noots reads each person's declared working hours; it does not generate a teaching timetable.
- An acknowledgement records that a member of your workspace read a policy or an announcement. It is not a statutory safeguarding register.
- Noots holds no FERPA, SOC 2 or ISO 27001 attestation, and does not claim one.
Built for the way your trade actually runs.
The ones buyers ask first.
Can we keep pupil data in Noots?
How do we show that a policy was read?
Does the term-start checklist have to be rebuilt each year?
What happens if we turn one of these off later?
Open a workspace that already knows Education.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required