Your student information system is the record of your school — enrollment, grades, transcripts, state reporting. Nothing here suggests replacing it. The scheduling module bolted onto it is a different question.
SIS migrations are among the most disruptive projects a school can undertake. This is not one of them, and if anyone pitches replacing your student information system as a way to fix scheduling, be suspicious.
Columbia's landscape analysis of eight scheduling tools found seven of eight alert on course conflicts — but only four of eight when a student is scheduled into a course they already took, or is missing one they need to graduate.
An account administrator connects your SIS. Credentials are encrypted at rest and the connection is scoped to what scheduling actually needs.
nOS imports courses, sections, teachers, rooms, students and course requests. A pull report tells you exactly what came across and what it could not read, rather than silently dropping rows.
The Data Cleaner surfaces the problems that exist in every real dataset — duplicate course codes, requests pointing at retired courses, teachers loaded past the number of periods in a day. You fix them before anything is built.
Generate across five optimization goals, compare scenarios side by side, drag sections on the Board with live conflict detection, and type constraints in plain English. Every edit is staged and previewed before it commits.
Before anything is sent, an administrator sees exactly what nOS would write into the SIS. This is the step that makes the round trip safe — you approve a diff, not a black box.
The finished schedule goes back into your SIS. Every push is recorded with counts, outcomes, and the exact schedule snapshot it came from.
nOS speaks to 19 student information systems, and 18 of the 19 can receive a schedule back — Clever is pull-only. Eleven of them ride a shared, live-tested OneRoster 1.1 connector.
The rest are vendor-specific connectors, and nOS shows each one's status inside the app rather than presenting them all as equivalent — so you always know exactly what you are working with. Tell us which system you run and we will confirm where yours stands before you plan around it.
| A built-in SIS scheduler | nOS | |
|---|---|---|
| System of record | Your SIS. Correctly so. | Still your SIS. nOS builds; it does not replace. |
| Unfilled requests | Usually a count, sometimes a code. | Each one carries the specific reason it could not be placed. |
| Trying an alternative | Typically overwrites the current result, so it rarely gets tried. | Scenarios saved and compared side by side; promote the winner. |
| Expressing a rule | Codes, flags and weights whose interactions are largely undocumented. | Type it in plain English; nOS compiles it into a solver constraint. |
| Manual adjustment | Form-based edits, often without live validation. | Drag on a resource × period Board; validity shown before you let go. |
| Writing back | Native — it is the same database. | Preview the exact diff, then push. Supported on 18 of 19 connectors. |
| Asking a question of the schedule | Run a report, read the report. | Ask in plain English and get an answer from the live schedule. |
| Cost | Bundled — which makes it feel free and makes it hard to evaluate. | $8 per enrolled student per year, stated publicly. Pricing. |
"A built-in SIS scheduler" describes the common pattern across the category rather than any single named vendor. Check the rows against your own module.