The research says the master schedule is "too often left to a lone programmer." nOS is built so it does not have to be — shared notes, a shared draft, live presence, and a record of who changed what.
Columbia Law School's Center for Public Research & Leadership put it bluntly: "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.
Three consequences worth knowing:
The single biggest risk in a school's scheduling process is that the method lives in one person's head and leaves with them. Shared-by-default storage is the least glamorous fix for that and by far the most effective one.
When more than one person from your school is in nOS, you can see it.
A People control in the top bar shows who else is in the product right now and which page they are on. You see their named cursors move in real time. And one click follows a colleague — mirroring their screen: the page they are on, the tab they have selected, how far they have scrolled in each pane, the dialog they have open, and their nOS AI conversation, read-only.
Administrators observe without broadcasting. Account administrators can see everyone's presence and cursors but do not publish their own, so looking in on a build never feels like standing behind someone.
Follow includes the assistant panel. While a colleague is following you, your open nOS AI transcript travels with the rest of the screen, read-only — so a walkthrough covers the question you just asked, not just the page. Tool payloads and hidden reasoning never travel, and your saved chats stay on your own account.
Right-click anywhere in nOS and choose Add a note here or Bookmark this. The note pins at the exact spot you clicked and stays glued there through scrolling, resizing and zoom.
Edits in nOS are staged rather than applied. That is a safety feature on its own — but the part that matters for a team is that everyone stages onto the same pending layer.
A Changes control on every page shows a count. Opening it gives a full before-and-after list of every pending edit, with a checkbox on each one and the fulfillment numbers that subset would produce. You commit some, all, or none.
So a department head can stage a change on Tuesday, the registrar can review it on Wednesday, and whoever is accountable decides what actually commits. The staged work survives a refresh and follows the account across devices.
Settings has an Activity tab: your school's own history of the product. Files imported, schedules built, saved, renamed, duplicated or deleted, scenarios created, workbook changes, SIS pulls and pushes — each with the name of the person who did it and when. Everyone on the account sees the same feed.