For small schools
Small school. Harder problem.
Fewer students does not mean easier scheduling. It means fewer sections to move things into, more courses that run exactly once, and usually one person doing all of it.
Small schools have the harder scheduling problem
This is counterintuitive enough that it is worth spelling out. A 3,000-student high school running eight sections of Algebra I has enormous flexibility — if a student cannot fit one section, there are seven others. A 280-student school running one section of Algebra I has none.
Everything is a singleton
A singleton runs exactly once, so every student who wants it must be free in that one period. As Berkeley's guide puts it, when "multiple singletons are scheduled during the same period, students must choose between them." If a student wants both, there is no fix — only a redesign of everything around it.
Staffing and rooms tighten it further. One person teaches AP Biology, Chemistry and the sophomore lab, so every course they hold is locked to their availability — and with one science lab and one art room, the courses needing them cannot move at all.
The upshot
A small school's schedule has fewer pieces and far less slack. That is precisely the shape of problem where an exhaustive search beats human intuition — because the number of arrangements is still astronomically large, but the number of valid ones is small enough that a person hunting by hand can easily miss all of them.
And you are probably doing it alone
Columbia Law School's Center for Public Research & Leadership found that "the bulk of master scheduling is too often left to a lone programmer who independently works out the complex puzzle of course requests and time constraints." Their recommendation is a core scheduling team of three to five people.
The category is built for districts
That leaves most schools in the country out. Federal data makes the scale of this clear: of 30,492 US private schools, 85.7% enroll fewer than 300 students and 93.8% enroll fewer than 500. The average private school enrolls roughly 158 students.
85.7%
Of US private schools enroll fewer than 300 students. 41.4% enroll fewer than 50.
NCES Private School Universe Survey, Table 8 (2019–20)
~158
Students at the average US private school — about 29,730 schools enrolling roughly 4.7 million students.
NCES Fast Facts: PSS (2021–22)
100+
Hours of nonstop work attributed to a single scheduler, over multiple weeks — the same load a small school gives to one part-time role.
Columbia CPRL, About Time, p.9 (2021)
What we did about it
Per-student pricing, so small stays cheap
nOS is $8 per enrolled student per year. A 300-student school pays for 300 students. There is no platform fee, no minimum-seat floor, and no pricing tier that only makes sense above a thousand students. Small schools are not subsidizing a product designed for districts.
No consultant, no implementation phase
Guided mode walks you through the whole build — tell nOS about your school, bring in your data, review the result, refine what is left. It is designed for the person who does this once a year and does not want to relearn a tool every spring.
The singleton problem is exactly what a solver is for
nOS places thousands of requests across five optimization goals, plus a best-overall mode that runs every strategy and returns the strongest. On a schedule dominated by singletons, that search reaches arrangements a person would not — because it can afford to test the ones that look unpromising.
What it takes to get started
Three things to plan for:
- Money. $8 per enrolled student per year. For a 300-student school that is $2,400. See pricing, including the current promotional rate.
- Data preparation. If your requests are already in an SIS or a spreadsheet, this is quick. If they are on paper, plan for a one-time entry project — covered here.
- A little time to learn it. Guided mode walks you through the whole build one decision per screen, and sixteen in-app walkthroughs cover each area — it is designed for someone who does this once a year.
Questions small schools actually ask
We only have about 200 students. Is this overkill?
Probably not, for the reason at the top of this page — 200 students with a rich elective catalogue can be a tighter constraint problem than 2,000 with a narrow one. The real test is whether your build currently takes weeks and whether requests go unfilled in ways you cannot explain. If both are no, you may genuinely be fine as you are.
We have one person who does scheduling. What happens if they leave?
This is the strongest argument for getting it out of one person's head. Data, constraints, notes and schedules all live on the school's account rather than an individual's — when someone leaves, their work stays.
Do we need IT involvement?
Only if you want to connect your SIS, which needs credentials and is restricted to an account administrator. If you are working from a spreadsheet, there is nothing to install and nothing for IT to configure — it runs in a browser.
Our schedule is unusual — rotating days, flex blocks, a middle school sharing teachers with an upper school.
Worth a conversation rather than a claim on a web page. Bring your actual structure to a demo and we will build against it live, and tell you plainly if it is not a fit. That is a better use of both our time than a feature checklist.
What if we start and it does not work?
Everything exports — student schedules, section summaries, rosters, teacher and room schedules, unfulfilled requests — as CSV, Excel or PDF. And if you are coming from an SIS, that SIS stays the system of record throughout, so your fallback is simply not pushing.