Evaluating NexusPlan

What SIS-connected planning actually looks like across a term.

If you're comparing options rather than already signed on, the useful question isn't "what does the product do" so much as "what does the first term look like for my staff." This walks the same rollout path a new school follows, written for the person still deciding.

Most of the timeline below is set by how quickly your own staff can move through invitations and account setup, not by anything technical. The SIS connection itself takes a session with IT, not a project. What actually takes a term is the normal cadence of getting advisors, students, and families through their own first sign-in in an order that doesn't rush anyone.

Book a demo See the onboarding tutorials

Weeks 1–2 · Connect

The technical part is short, on purpose.

This is deliberately the shortest phase. The point of connecting first is that everything downstream, students seeing real assignments on day one, the admin console showing real workload data by the time you're ready to evaluate, depends on the sync having been running for a few weeks already.

Step 1 · Administrator

Stand up the school

Self-serve or a white-glove start, either way you land in a short setup wizard: school name, logo, color theme. This is the same first step whether you're piloting or fully committing.

Step 2 · IT

Connect the SIS

Veracross credentials, stored encrypted and scoped to your school, used only for your sync. Classes, rosters, schedules, assignments, and grades start flowing in without anyone re-entering anything. Coming soon for OneRoster, FACTS, Blackbaud, and Google Classroom.

Step 3 · Teachers

No teacher step

This is usually the deciding question in an evaluation: what does this cost my faculty's time? The honest answer is nothing. Teachers keep entering assignments and grades in the SIS exactly as they do now.

Weeks 3–4 · Staff

Advisors and IT get their seats before students arrive.

Step 4 · Administrator

Invite the team

Invite links carry an expiring code and a fixed role, for fellow administrators, advisors, and IT. There's no open signup to worry about while you're still deciding how far to roll this out.

Step 5 · Advisors

Link advisors to advisees

The administrator links each advisor to their advisees in the console, which is what powers the triage view. If you're piloting with one grade level, this is where you scope it down.

Step 6 · Administrator

Set the student home screen

Pick which cards students see, write a launch announcement, and confirm branding. Small, but it's what makes the first login feel like your school's tool rather than a vendor demo.

Weeks 5–6 · Students & families

This is the part that actually matters for evaluation.

Everything before this point is setup. The real test of whether this is worth rolling out past a pilot happens here, when actual students see their actual assignments turn into a ranked plan for the first time, and when you can watch, in the console, whether they keep coming back to it in week two and week three, not just on the day of the launch announcement.

Step 7 · Students

First sign-in, real work already there

Because the sync has been running since week one, a student's first screen is their own actual assignments, already ranked. There's no empty state to explain away in a pilot review.

Step 8 · Students

A short guided tour, then they're in

The ranked Work list, Calendar, Workload Radar, Insights. Students can add their own tasks immediately, so the plan covers more than the gradebook from day one.

Step 9 · Administrator

Watch adoption in the console

The admin console shows who's actually signing in and using the plan, plus workload hotspots by grade. This is the data an evaluation usually needs before deciding to expand past a pilot.

By the end of the term

What "fully live" looks like, so you know what to check for.

The SIS sync is stable: classes, rosters, schedules, assignments, and grades flow in on their own.
Students in the pilot group are signing in and working from a ranked plan of real assignments.
Advisors are linked to their advisees and the triage view is populated with real data.
The admin console shows adoption and workload patterns you can bring to a decision about expanding.
Teachers still haven't had to do anything differently.

For the detailed, role-by-role tutorials behind each of these steps, see the full onboarding tutorials. If you're still comparing this to other options, the fastest way to get a real answer is a working session against your own SIS rather than a slide deck: book a demo and bring a real week from your calendar.

Book a demo See onboarding tutorials

Next step

Talk through a rollout plan for your school.

Thirty minutes, your SIS, a realistic timeline for your calendar and staff.

Book a demo More resources