The whole platform, screen by screen.
Four places to be, in the order you meet them. Everything below is the product running on this page, so use it.
A workbook that argues with you first.
Your data arrives from your student information system or a spreadsheet, and nOS matches the columns itself. What comes back is six editable sheets that re-check as you type, so a course nobody teaches surfaces here and not at the end.
| # | Student ID | Course requested | Grade | Check |
|---|---|---|---|---|
| 41 | 270041 | Concert Band | 10 | Matched |
| 42 | 270042 | Pre-Calculus | 11 | No course by that name |
| 43 | 270043 | Studio Art | 9 | Matched |
| 44 | 270044 | Chemistry | 11 | Matched |
Merge, not replace
A second import updates what changed and leaves your edits alone. Column mappings are remembered, so next year is one click.
Nine file formats
Excel, CSV and OpenDocument, five files at once, each with a receipt of what was read and what was skipped.
Any calendar
Semesters, trimesters, quarters, A/B days, rotating cycles, flex blocks. A fall class and a spring class do not collide.
Forty-one kinds of rule, typed as sentences.
One per line, in the words you would use with a colleague. Each is marked hard or soft: a hard rule is never broken, a soft one is a preference the build will pay for if it must. If two cannot both hold, nOS shows you the smallest set that conflict.
The kinds of thing you can say
Cap a course. Keep a teacher's period free. Keep two students apart. Hold a course to one period, or two courses out of the same one. Balance sections by size or gender. Give a room to a department.
What the five goals do
Max Fulfillment places as many requested courses as possible and is the default. The others even out class sizes, even the gender mix across sections of one course, give upperclassmen first pick, or balance size and gender together.
The result, reported without spin.
Fulfillment overall and by grade, every student's day, every roster, and how close the build came to the best your data allows. Results only reads, which is why it is safe to hand to a department head.
What is left, ranked by how much it matters.
Studio lists the remaining problems worst first, with the evidence for each one and a link to the class or the students. It does not suggest fixes. You make the change in Make changes, it is staged, and nothing is final until you apply it.
The Board, with everyone on it.
Drag a section and conflicts flag as you move. Colleagues appear live, and you can follow one around the schedule.
Presence and follow
See who else is in the schedule and where. Click a name to follow their page and their scrolling. It is conflict detection with the last change visible, not shared typing.
Notes pinned in place
Right-click anywhere to leave a note or a bookmark. It stays put, belongs to the school rather than to you, and anyone can resolve it.
Staged changes
Every edit lands in a shared pending layer with a checkbox and an impact preview. Commit some, discard the rest. It survives a refresh.
Two roles, member and account administrator. We set your team's accounts up, so there is no user-management screen to learn.
nOS AI works inside the build.
Ask why a student missed a class, what moving a section would do, or what the smallest change is. It shows the checks it ran, names who is affected, and any change it offers is staged for your approval, never applied by itself. Included with nOS.
Raise the section capacity from 16 to 17. That clears the overage in one move, and it affects one student, who is in the over-capacity seat and would then fit legitimately.
Raise the section capacity from 16 to 17. That clears the overage in one move, and it affects one student, who is in the over-capacity seat and would then fit legitimately.
Both courses they asked for run only in period 3, and Concert Band filled first. The tie broke toward Studio Art.
Nothing breaks, and four students gain a seat in Precalculus. Fulfillment goes from 97.0% to 97.3%.
Nothing goes back until you have read the list.
Every line is counted before a single write. Writes are additive, so nothing is deleted, and afterwards nOS reads the system back to check.
See it run on your own numbers.
Bring next year's course requests and we will build against them live.