A small school has the harder problem.
Fewer sections to move a student into, and more courses that run exactly once. Being small does not make the schedule easier. It removes the slack.
The singleton problem.
A course that runs once has exactly one period, and every student who wants it must be free then. Two singletons in the same period means somebody gives one up. Three is a knot.
A large school solves this by running a second section. A small school cannot, because there is one teacher and eleven students. So the schedule has to be arranged around the singletons rather than the other way round, and every other decision bends to fit.
That is a search problem, and it is exactly what nOS is for. The chains of swaps that free a stuck student are the part a person cannot hold in their head, and they are the part that matters most when there is nowhere else to put anybody.
It gets out of one person's head
Data, rules, notes and schedules live on the school's account. When someone leaves, their work stays and the reasoning behind it is written down.
You pay like a small school
Under ten dollars per enrolled student per year, quoted for your school. There is no setup fee and no minimum.
Nothing to install
It runs in a browser. You only need IT involved if you want your student information system connected, and from a spreadsheet you do not need them at all.
Fair questions.
We only have about 200 students. Is this overkill?
Probably not. Two hundred students with a rich elective catalog can be a tighter problem than two thousand with a narrow one. The real test is whether your build takes weeks, and whether requests go unfilled in ways you cannot explain. If both are no, you may be fine as you are.
One person does our scheduling. What happens if they leave?
This is the strongest argument for getting it out of one person's head. Data, rules, notes and schedules live on the school's account, not an individual's. When someone leaves, their work stays.
Do we need IT involved?
Only to connect your student information system, which needs credentials and an account administrator. Coming from a spreadsheet there is nothing to install. nOS runs in a browser.
Our schedule is unusual. Rotating days, flex blocks, shared teachers.
nOS handles A/B days, rotating cycles, flex mods, block and trimester schedules, and a fall course and a spring course that share a period. Bring your structure to a demo and we will build against it live, and tell you plainly if it is not a fit.
What if we start and it does not work?
Start with the thirty-day trial, which is the whole product on your own data, before any money changes hands. If you stop later, everything exports as CSV, Excel or PDF: student schedules, section summaries, rosters, teacher and room schedules, and unfilled requests. If you came from a student information system, it stayed the system of record the whole time.
Bring the singletons. We will build around them.
A demo is a working session on your own course requests. The trial is thirty days of the whole product, on your own.