An alternative to Rediker scheduling
A school can keep Rediker as its student information system and build the master schedule in a separate tool. nOS reads students, teachers, courses, sections and rooms from Rediker, builds the schedule from course requests you upload as a spreadsheet, and returns it as a reviewed handoff file you import into Rediker.
Updated November 2026
Who is this for?
Schools that keep Rediker for enrollment, grades and attendance but want a different place to build next year’s master schedule. Many build in a spreadsheet or on a board today, and want to see why each request missed and keep a record of how the schedule was made.
You don’t replace Rediker. It stays the system of record the whole time.
Why do some schools build outside Rediker?
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 Rediker?
Through OneRoster. A Supervisor turns on Send Data for OneRoster Integration in Administrator’s Plus’s TeacherPlus Setup & Sync Manager and copies TeacherPlus’s OneRoster Client ID, Client Secret and Token URL into nOS. Or they run AdminPlus’s OneRoster Export and upload its files. See Rediker, step by step.
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 Rediker and back?
What stays in Rediker?
Enrollment, grades, attendance and student records stay in Rediker, and so does every decision about what gets imported. Students, teachers and courses must already exist in Rediker before the handoff file can be imported.
nOS doesn’t write to Rediker on its own. The schedule counts as delivered only once you confirm the import.
When should you stay with Rediker’s own tools?
A separate scheduler isn’t right for every Rediker 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 Rediker, 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 Rediker?
Yes. nOS reads your data from Rediker, 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 Rediker?
No. Rediker stays your student information system. nOS is only where the master schedule is built, and the finished schedule goes back into Rediker.
Can nOS read our course requests from Rediker?
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.
Does the Rediker import place students in their classes?
No. The TimeTabler import creates the classes, and the archive lists each student placement to make in Rediker. nOS can’t yet read a Rediker import back, because Rediker gives each class it creates its own ID.
Can we try it before we decide?
Yes. The 3-day free trial is the whole product on your own data, including the Rediker connection once it’s set up. You can also book a free demo call first.
Try it with your Rediker data.
Use the whole product on your own students and requests.