An alternative to Skyward scheduling
A school can keep Skyward as its student information system and build the master schedule in a separate tool. nOS reads students, teachers, courses, sections and rooms from Skyward, builds the schedule from course requests you upload as a spreadsheet, and returns it as a reviewed handoff file you import into Skyward.
Updated November 2026
Who is this for?
Schools that keep Skyward for enrollment, grades and attendance but want a different place to build next year’s master schedule. Some build in a spreadsheet or on a board today; others use Skyward’s own scheduling, where students request courses and staff lay out the master schedule on a drag-and-drop board before students are scheduled, and want to see why each request missed.
You don’t replace Skyward. It stays the system of record the whole time.
Why do some schools build outside Skyward?
Usually to see more of the build. Before it starts, nOS works out the ceiling: the largest share of your requests any schedule could fill with your courses, sections and rules. Afterwards, every request it couldn’t place is listed with one of 12 plain-English reasons.
Rules are written as sentences. Every change, from the Board or from nOS AI, is staged for you to review before it’s applied.
How does nOS connect to Skyward?
Through Skyward’s OneRoster 1.1 REST provider. Your district turns it on and issues a Base URL, an OAuth Client ID and a Client Secret with read permissions, which you paste into nOS and test before anything is imported.
nOS reads students, teachers, courses, sections, rooms and current enrollments. Pull again whenever you like, and you see what changed before it lands.
The connection has no course-request feed, so upload your course requests as a spreadsheet. Without them, nOS reads current enrollments as next year’s demand.
What are the steps, from Skyward and back?
What stays in Skyward?
Enrollment, grades, attendance and student records stay in Skyward, and so does every decision about what gets imported. Students and teachers must already exist in Skyward before the handoff file can place them.
nOS doesn’t write to Skyward on its own. The schedule counts as delivered only once you confirm the import.
When should you stay with Skyward’s own tools?
A separate scheduler isn’t right for every Skyward school. Staying put may make more sense if:
- Its scheduling tools already give you a schedule you’re happy with, and your team knows them well.
- You want the schedule never to leave Skyward, or a file import step doesn’t fit how your school works.
- You need something nOS doesn’t have, such as a counselor or parent login, or the app in a language other than English. See what nOS doesn’t do.
If you’re unsure, build the same year in both and compare what each one placed. See how the options compare.
Common questions
Can you build the master schedule outside Skyward?
Yes. nOS reads your data from Skyward, builds the master schedule from your course requests, explains every request it could not place, and returns the finished schedule as a reviewed handoff file you import.
Do we have to stop using Skyward?
No. Skyward stays your student information system. nOS is only where the master schedule is built, and the finished schedule goes back into Skyward.
Can nOS read our course requests from Skyward?
Not through the connection, because it has no course-request feed. Upload your requests as a spreadsheet. Without them, nOS reads current enrollments as next year’s demand.
Who at our district needs to be involved?
Whoever manages Skyward for the district, to turn on the OneRoster provider and issue its credentials, and to import the finished schedule. Whoever builds the schedule does everything in between.
Can we try it before we decide?
Yes. The 3-day free trial is the whole product on your own data, including the Skyward connection once it’s set up. You can also book a free demo call first.
Try it with your Skyward data.
Use the whole product on your own students and requests.