RosterSync
Keeps Google Classroom in step with your student information system.
RosterSync keeps Google Classroom in step with your student information system (SIS). It creates one Classroom course per SIS class with the right teachers and students, keeps rosters current as schedules change, archives courses at the end of the term, and proposes copying returned Classroom grades back into the SIS gradebook. Every change is shown as a plan that a person reviews before anything is written.
For IT directors, registrars.
All 26 features
11 of them can be tried in the demo.
Rosters: SIS to Google Classroom
- One course per class
- Creates a Classroom course for each class in the student information system, with the right teacher, co-teachers and students. Try it: One course per class
- Kept in sync all year
- Adds and removes students and teachers as schedules change, and archives courses at the end of the term. Try it: Kept in sync all year
- Your naming rule
- Course names follow a pattern you choose, such as "Art 1 (1GL-Art)".
- Finds existing courses
- Matches courses teachers already made by name and owner, instead of creating duplicates. Those courses are only ever roster-updated.
- Skips non-classes
- Lunch, recess, assemblies and other periods without a teacher are left out.
Grades: Google Classroom to SIS
- Returned grades flow back
- Proposes copying grades teachers return in Classroom into the SIS gradebook, only where the SIS is missing or different.
- Right term
- Each assignment is matched to the correct grading period by its due date.
- Creates and updates assignments
- Proposes new SIS assignments for Classroom work that has none, with the type taken from the Classroom grade category. Each one needs its own tick.
- Missing-work marker
- A grade of exactly 55% marks work as not turned in, because Classroom's own "missing" flag isn't visible to other systems.
- Teacher edits respected
- A status a teacher set by hand in the SIS is never overwritten.
- Show assignments to families
- Every two hours, assignments whose date has arrived are switched to visible. Each run is listed on its own page.
Review before anything changes
- Plan first
- Every sync is built as a plan you can read before anything is written. Try it: Plan first
- Plain-English preview
- A summary at the top says exactly what applying the plan will do. Try it: Plain-English preview
- Pick what to apply
- Tick whole classes or single changes, then apply only those. Try it: Pick what to apply
- Destructive changes gated
- Removals and archives are called out and need an extra confirmation. Try it: Destructive changes gated
- Safety limits
- Plans that would change an unusually large number of courses are held for review. Try it: Safety limits
- Stale-plan check
- A plan won't apply if the data changed since it was made.
- Resume after errors
- If an apply stops partway, rerunning it picks up only what didn't finish.
- Blocked items
- Anything that can't be synced safely, like a teacher with no email, is listed with the reason. Try it: Blocked items
Day to day
- Dashboard
- What needs attention, the last refresh and quick links. Try it: Dashboard
- Scheduled refresh
- Reads both systems every four hours and builds new plans. It never writes on its own.
- Changes page
- Each refresh lists what changed, grouped by system, with a "Mark reviewed" button and a badge for unreviewed changes.
- Classes page
- Every class with its Classroom status: created here, matched, needs a decision or not created yet. Try it: Classes page
- Event log
- Who applied what, and when. Try it: Event log
- Roles
- Viewers can look, operators can apply plans, and admins manage users. The last admin can't be removed.
- Google sign-in
- Staff sign in with their school Google account, with protection against cross-site requests.
Works with
- Google Classroom
- Your student information system, through its API (built first for Veracross; others on request)
How student data is handled
- Reads both systems every four hours and keeps snapshots in its own database. Old snapshots are pruned.
- Roster and grade changes are written only after a person approves them. Removals and archives need an extra confirmation.
- Staff sign in with their school Google account. Viewers can look, operators can apply plans, admins manage users.
- An event log records who applied what, and when.
Common questions
Will it change courses teachers made themselves?
It matches courses teachers already made by name and owner instead of creating duplicates. Those courses only ever get roster updates. They are never renamed or archived.
Does it change anything on its own?
Rosters and grades are never written without a person's approval. The one automatic job switches assignments to visible for families once their date arrives, every two hours, and each run is listed on its own page.
Which student information systems does it support?
It was built first for Veracross. Other systems with an API can be added. Ask us about yours.
What happens to things it can't sync?
They're listed as blocked items with the reason, such as a teacher with no email, so someone can fix them at the source.
More it and administration apps
Need it to work differently?
Every RosterSync feature can be adjusted to how your school works, and we can add the ones you need.
Describe what you need