Plan the year, publish the policy, show the evidence.
Running a school is not teaching. It is enrolment week, the exam window, the boiler service, the governors' pack and an inspection that arrives on short notice, all landing on the same few people. Noots puts the year on one calendar with a named owner against every date, turns leadership meetings into action lists somebody is actually holding, and keeps the term-start run, the policy acknowledgements and the training record in a state you can show on the morning you are asked.
9 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 an owner
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. When the inspection window moves by a week, drag it: the event goes to its new day keeping its time, a trip that runs Monday to Thursday draws as one continuous bar across the days it covers rather than four disconnected blocks, and sweeping across a run of empty days creates the event already dated. The office's master spreadsheet retires, and “who is picking this up” stops being a corridor question.
11:20
the policy goes out, and comes back acknowledged
The revised safeguarding policy is published in the Policy Library with its effective date, announced to the whole workspace, and the acknowledgements come back by name. By Friday the list of who has not answered is one filter rather than a reply-all thread that trails off, and “what is our policy on…” has exactly one answer.
16:10
the evidence is a filter, not a fortnight
The term-open procedure shows every step ticked, by whom, on what date. Training shows each certification with its provider and its status. The leadership minutes show the decision and the person who carried it out. When the call comes, none of that has to be reconstructed: it is the record of the work itself.
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 the procedure once - term open, enrolment, a trip, a fire drill - and run it every time it comes round. Each run is its own record, so last August's stays intact while this August's is in progress.
- One written procedure, run many times
- Every step ticked, with the person who ticked it
- Term start, staff onboarding, incident response
- The record of the run is the evidence
Announcements
The one place a whole-school update goes, so it is not competing with six other threads. Read receipts come back as they land, and where it matters an acknowledgement is required rather than hoped for.
- 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
Training
Safeguarding, first aid, fire marshal, the subject CPD somebody booked in March: every course and certification on one shelf, per person, with the provider and the link on it.
- 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, trips and inspections sit on shared calendars, synced both ways with Google and Microsoft
- Hands-On Scheduling is switched on for you: dates are changed by dragging them on the calendar and on the timeline rather than by opening a form, a multi-day trip draws as one bar across the days it spans, and the timeline keeps an undo and a redo with the thing you just moved lit up so you can see what changed
- Every project can add, rename, re-date and drag a milestone straight on its timeline and its calendar, in every plan and with no extension at all - so a moved deadline is a drag rather than a delete and a retype, and a task whose due date is tied to that milestone moves with it
- Leadership and governor meetings come back as owned action items, without anybody taking minutes - and the governors' running order rides on the scheduled meeting itself as its agenda, so it is not rebuilt each term
- Polls & Surveys settles the staff-meeting date, the training-day choice and the uniform question in one post, with the tally live as the votes land
- The Policy Library holds every rule with its effective date and one authoritative text
- Intake gives facilities, IT and admin requests one front door instead of a corridor conversation, and the Goals tab on every project carries the outcomes the institution reports against
- Forms covers the end-of-unit feedback, the staff pulse check and the question you need answered before Friday: blocks for a written answer, a multiple choice, a date or a note, a picture or a link on any of them, and a schedule if the same form should come round every week or every term. Replies can be anonymous, which is usually the point, and the creator sees the overall numbers and every individual answer on two tabs
- Offered at setup, one tick each: Codex for the staff handbook and onboarding, the Ledger for devices and rooms, Expense Claims for the trip, Approvals for the trip's sign-off, Recurring Tasks for the jobs that come round every term, Budgets and Goals & OKRs
- The Corkboard gives a department a wall to work on - notes you drag, a pen to scribble with and a reply thread on any note, with one shared board for the whole school
- 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 and not 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, and it does not arrange cover for an absent teacher.
- An acknowledgement records that a member of your workspace read a policy or an announcement. It is not a statutory safeguarding register, and it reaches members of the workspace only - parents are not in it.
- Training holds an expiry period per course, so a first-aid certificate carries the date it runs out and the holder is reminded before it does. What the product does not do is verify a certificate with the body that issued it.
- 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?
Can we move a date without rebuilding the plan?
How do we show that a policy was read?
Does the term-start checklist have to be rebuilt each year?
We have several schools in a trust. Does that work?
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