September is planned in June. Every date has an owner.
A school year runs on dates fixed months in advance: enrolment, term open, exam windows, the inspection that arrives on short notice. Noots puts the whole year on one calendar with a name against every deadline, turns leadership meetings into owned action lists, and keeps the term-start procedure, the policy acknowledgements and the training record ready to show - not scattered across six inboxes.
7 apps queued at setup - untick any of them before you finishDefault 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 year is on one calendar, and today has owners
Enrolment week, the exam window, the boiler service, Thursday's governors' meeting: every fixed date sits on a shared calendar with a project behind it and a person against it, synced both ways with Google and Microsoft. The registrar's master spreadsheet retires, and “who owns this” stops being a corridor question.
11:20
the safeguarding update goes out, and comes back signed
The revised policy is published in the Policy Library with its effective date, announced to the whole workspace, and acknowledgements come back by name. By Friday the list of who has not answered is one filter - not a reply-all thread that trails off. When someone asks “what is our policy on…”, there is exactly one answer.
16:10
the inspection folder is a filter, not a fortnight
The term-open checklist run shows every step ticked, by whom, on what date. The Learning Hub shows each certification with its provider and status. The leadership minutes show the decision and who carried it out. When the call comes, the evidence is already in the record of the work itself - nobody spends two weeks reconstructing it.
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.
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 one to the top of everyone's home screen, in either home layout
- Read receipts as they land
- Required acknowledgement that really asks, and tells you who has not answered
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
These sit on top of the whole product.
- Term dates, exam windows and events live on shared calendars, synced both ways with Google and Microsoft
- 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?
We're a research group or a university department - is this the right page?
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