An alternative to PowerSchool scheduling

A school can keep PowerSchool as its student information system and build the master schedule somewhere else. nOS reads your students, teachers, courses, sections and rooms from PowerSchool and builds the schedule. The finished schedule returns as a reviewed handoff file your administrator imports into PowerSchool.

Updated October 2026

Who this is for

This is for schools that keep PowerSchool 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 PowerScheduler and want to see why each request missed.

You don’t replace PowerSchool. It stays the system of record the whole time.

Why some schools build outside PowerSchool

Mostly, they want 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 a plain-English reason.

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 nOS reads PowerSchool

A PowerSchool server or district administrator installs and enables a PowerSchool plugin that grants the read permissions. They copy the plugin’s OAuth Client ID and Client Secret into nOS and test the connection before anything is imported. We’ll do it with you on a call.

From PowerSchool, nOS reads students, teachers, courses, sections, rooms and current enrollments. Pull again whenever you choose, and you see what changed before it lands.

The PowerSchool connection has no course-request feed. Upload your course requests as a spreadsheet; without them, nOS reads current enrollments as next year’s demand.

The round trip, step by step

1. Connect PowerSchoolYour administrator enables the plugin and pastes its credentials into nOS.
2. Pull your dataStudents, teachers, courses, sections, rooms and enrollments come in. You review them first.
3. Add course requestsUpload them as a spreadsheet. Problems are marked on the cell, with a fix, before you build.
4. Write rules and buildRules are sentences, each marked hard or soft. Then nOS builds the schedule.
5. Fix what’s leftEvery unplaced request has a plain-English reason. Changes are staged until you commit them.
6. Approve the send listYou see every section and enrollment that will go to PowerSchool. Nothing in PowerSchool is deleted.
7. Import the handoff filenOS gives you two PowerSchool-format files. Your administrator imports them in PowerSchool.
8. Confirm the importYour administrator marks the files as imported in nOS. The download alone is not proof.

What stays in PowerSchool

Enrollment, grades, attendance and student records stay in PowerSchool, and so does every decision about what gets imported. Students must already exist in PowerSchool before the handoff file can place them.

nOS doesn’t write to PowerSchool on its own. Your administrator imports the file, and only then does nOS treat the schedule as delivered and read PowerSchool back to check it.

When to stay with PowerSchool’s own scheduler

A separate scheduler isn’t right for every PowerSchool school. Staying with PowerScheduler may make more sense if:

  • It already gives you a schedule you’re happy with, and your team knows it well.
  • You want the schedule never to leave PowerSchool, or a file import step doesn’t fit how your district works.
  • Your district relies on PowerSchool’s own training and support for scheduling.
  • You need something nOS doesn’t have, such as version history, an approval workflow or publishing schedules to staff. 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

Do we have to stop using PowerSchool?

No. PowerSchool stays your student information system. nOS is only where the master schedule is built, and the finished schedule goes back into PowerSchool.

Does nOS write directly into PowerSchool?

No. For PowerSchool, the finished schedule returns as a reviewed handoff file your administrator imports. Nothing in PowerSchool is deleted, and the schedule counts as delivered only when your administrator confirms the import.

Can nOS read our course requests from PowerSchool?

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 school needs to be involved?

A PowerSchool server or district administrator, twice: once to enable the plugin and issue its credentials, and once to import the finished schedule. Whoever builds the schedule does everything in between.

Can we try it before we decide?

Yes. The 1-hour free trial is the whole product on your own data, including the PowerSchool connection if your administrator sets it up.

More scheduling guides

School master scheduling software compared How to build a school master schedule How to collect student course requests When to start next year’s master schedule How to schedule singleton courses All SIS connections

Try it with your PowerSchool data.

Use the whole product on your own students and requests.

Start your free trial