OneRoster 1.1 connector

Use your OneRoster 1.1 feeds for reporting, automation and AI.

Data Panda lands the OneRoster 1.1 rostering, gradebook and resources feeds your district publishes from the SIS, and joins them to the LMS, assessment, finance and HR data already in your warehouse. From one place we turn it into dashboards, automations, AI workflows and apps that registrars, principals, IT and curriculum teams use during the term, not in the August clean-up week.

About OneRoster 1.1

The K-12 standard that moves rosters, enrollments and grades between SIS and ed-tech.

OneRoster is a specification published by 1EdTech (formerly IMS Global) for securely exchanging rostering data between a student information system and the rest of the K-12 stack. Version 1.1, released as a final standard in April 2017, is the version most school districts still run in production. It defines three services: Rostering, which carries users, classes, courses, enrollments, organizations, academic sessions, grading periods and demographics; Gradebook, which carries line items, results and categories; and Resources, which carries learning content links attached to courses and classes.

The spec offers two bindings. The CSV binding ships a fixed set of files (academicSessions.csv, classes.csv, courses.csv, enrollments.csv, orgs.csv, users.csv, plus optional demographics and gradebook files) and is the path most SIS vendors use for nightly batch handoffs. The REST binding speaks JSON over HTTPS at the /ims/oneroster/v1p1 root, requires OAuth 2.0 Bearer tokens with TLS 1.2 or 1.3, and supports pagination, filtering and sorting on every collection endpoint. Certified providers and consumers include PowerSchool SIS, Infinite Campus, ClassLink, Itslearning, McGraw-Hill, Pearson and Studies Weekly, with Schoology and PowerSchool's Schoology Learning landing on the newer 1.2 version. Pulled into a warehouse next to the LMS, the assessment platform, the finance system and the HR record, the same OneRoster feed answers questions that span enrollment, attendance, achievement, ed-tech spend and staffing without three reports that disagree on which students are in which class.

What your OneRoster 1.1 data is for

What you get once OneRoster 1.1 is connected.

Rostering and achievement reporting

Enrollments, class memberships, gradebook results and demographic cohorts on one page across every school and term.

Enrollment counts and class loads per school, grade and homeroom
Gradebook results joined to demographics for cohort and equity reporting
Roster freshness audit on the OneRoster feed itself, per SIS publish run

Process automation

Turn OneRoster events into the downstream work the rest of the district expects, without a manual reconcile.

Provision LMS, library and assessment seats the day a new enrollment lands
Trigger a counsellor outreach when a student moves school mid-year
Reconcile ed-tech vendor licence counts against active OneRoster enrollments

AI workflows

Put rosters, gradebook history, attendance and ed-tech usage behind AI that sees the whole student record, not one vendor at a time.

At-risk scoring on grade slippage, attendance drift and missed assessments
Natural-language Q&A across district enrollment, gradebook and demographic data
Cohort-level summaries of which courses are dragging pass-rates down per school

Custom apps on your data

Lightweight tools on OneRoster data for principals, counsellors and curriculum teams who should not need an SIS adminseat to read their own building.

Principal cockpit with enrollment, attendance and grade trend per grade level
Counsellor worklist of students slipping behind their cohort this week
Ed-tech licence view per vendor, with active-versus-licensed gap per school

Use cases

Use cases we deliver with OneRoster 1.1 data.

A list of concrete reports, automations and AI features we have built on OneRoster 1.1 data. Pick the one that matches your situation.

Roster freshness auditDaily check on the OneRoster publish: row counts per file, schema diffs, primary-key gaps and orphan enrollments versus the previous run.

Enrollment-to-active-user gapActive OneRoster enrollments versus actual user activity in each ed-tech vendor, per school and licence agreement.

Class membership reconciliationOneRoster class memberships versus what the LMS, the assessment tool and the library show, with the deltas surfaced for the registrar.

Gradebook results per cohortGradebook results from the OneRoster feed joined to demographics, attendance and prior achievement per cohort and school.

Course-completion rate per LMSCompletion and pass-rate from the LMS gradebook feed, broken down by district course code and school.

Demographic cohort reportingAchievement and engagement segmented by the demographics file, used for state, ESSA and equity reporting.

Mid-year transfer trackingStudents moving between schools or districts mid-year, with the first day in the new roster and the gap to active LMS access.

Teacher load and section countSections taught, students assigned and grading volume per teacher and term, drawn from the rostering feed.

Ed-tech licence usagePer vendor: licensed seats, OneRoster enrollments, active users last 30 days, and the gap each carries against the contract.

Master-schedule change impactHow a master-schedule shift propagates through the OneRoster feed, with the affected classes, sections and teacher assignments listed.

OneRoster vs SFTP CSV reconcileFor districts running both REST and CSV bindings: a daily diff to confirm the two sources agree on counts before downstream consumers fan it out.

Academic session rollover checkEnd-of-year rollover audit: which classes, courses and enrollments carried over cleanly to the new academic session, which need an SIS-side fix.

Real business questions

Answers you will finally get.

Which schools are losing the most class memberships in the LMS within a week of a master-schedule change?

OneRoster class memberships from the SIS publish run, joined to the actual class membership the LMS reports per school and per day. The chief academic officer sees which building lost nine percent of its class memberships out of sync the week the master schedule shifted, and which feed (the OneRoster publish, the LMS sync, or a manual override in the LMS) carried the drift, before the next progress-report window opens.

Are we paying for ed-tech licences that no student is using?

Per vendor: licensed seats from the contract, active OneRoster enrollments mapped to that vendor, and active users in the last thirty days from the vendor's own usage feed. The director of technology sees which contract is over-provisioned per school, which is under-licensed against actual usage, and where the renewal conversation should land before the next purchasing cycle.

Which cohorts are falling behind on the gradebook results we publish through OneRoster?

Gradebook results from the OneRoster feed joined to the demographics file and the attendance record, per school, grade level and cohort. The state-reporting team sees the same numbers it submits for ESSA and equity reporting, but with the underlying student-by-student detail the assessment lead can act on this term, not at the year-end audit.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Per-pupil funding tied to live enrollment from the OneRoster feed, not to a count taken in October. The CFO of the district sees which schools are funding which, where mid-year transfers are pulling funding entitlement, and which ed-tech licence lines are running ahead of plan in the same view.

For sales leaders

For ed-tech vendors selling into districts, the OneRoster feed is the renewal evidence base. Account managers see active enrollments per district, active users in the last thirty days, and the gap each contract carries, so renewal conversations open with the same numbers the district sees.

For operations

Registrar, IT and curriculum staff work from the same enrollment, class and gradebook record. The superintendent's office sees which buildings carry the most out-of-sync class memberships, which ed-tech tools the catalogue uses, and where the at-risk worklist for counsellors is, on one page rather than five vendor reports.

Ideas

What you can automate with OneRoster 1.1.

Pair with Salesforce

Tie district admissions to live OneRoster enrollment

New OneRoster enrollments, school transfers and class memberships flow back to the Salesforce Education Cloud record of each prospect-turned-student. Recruitment, admissions and family-engagement teams see which accepted students never showed up in the roster, which transferred mid-year, and which sit active across the LMS and assessment platform, so outreach starts the week the gap shows up rather than at the year-end audit.

Pair with HubSpot

Sync OneRoster enrollment status with HubSpot for charter and private-school recruitment

For charter networks and private schools using HubSpot for family-side marketing, OneRoster enrollment events flow to the HubSpot CRM record of each family. Marketing and admissions see which inquiries became enrolled students, which dropped at registration, and which are inactive in the LMS after enrollment, so re-engagement and waitlist campaigns reach the right segment instead of the full inquiry list.

Pair with Slack

Alert IT in Slack when the nightly OneRoster publish breaks

When the nightly OneRoster publish from the SIS misses a file, drops below an expected row count, or fails schema validation, the on-call IT lead gets a Slack message with the failed file, the previous-run baseline and the affected schools. The fix happens before homeroom on the next school day, instead of when a teacher reports an empty roster in second period.

Pair with monday.com

Run state-reporting prep on a monday.com board fed by OneRoster

OneRoster enrollments, gradebook results and demographic counts land on a monday.com board structured per state-reporting submission and per school. The data lead sees which submissions are complete, which carry blank fields, and who owns the school-side fix, instead of chasing spreadsheets the week before each state deadline.

Pair with HiBob

Match HiBob teacher records to OneRoster section assignments

Teacher and staff records from HiBob match against the OneRoster users and enrollments feed, so people ops sees which teachers carry which sections, the load per teacher, and the gap between contracted FTE and actual section load. Mid-year reassignments, leave cover and overload conversations open with the same numbers the academic office uses for staffing.

Pair with Exact Online

Reconcile ed-tech vendor invoices in Exact Online with OneRoster active enrollments

For schools and training providers invoicing ed-tech licences through Exact Online, vendor invoices line up with active OneRoster enrollments and last-thirty-day usage per vendor. Finance sees the gap between billed seats and active learners per school and contract line, and the renewal-quarter purchase plan follows the cohorts that are in the platform, not the headcount the contract was signed on.

Data model

Tables we make available.

These are the 8 tables we currently pull from OneRoster 1.1 into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.

Classes
Courses
Demographics
Enrollments
Orgs
Students
Teachers
Users

Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your OneRoster 1.1 data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From OneRoster 1.1 to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

OneRoster 1.1 connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Does the connector use the OneRoster REST binding or the CSV binding?

Both, depending on what the SIS publishes. The CSV binding ships the fixed file set (academicSessions.csv, classes.csv, courses.csv, enrollments.csv, orgs.csv, users.csv, plus optional demographics.csv and the gradebook files) over SFTP or a similar drop, and is the path most districts use for the nightly batch. The REST binding speaks JSON over HTTPS at the /ims/oneroster/v1p1 root, with OAuth 2.0 Bearer tokens and TLS 1.2 or above, and is the right path for near-real-time pulls and per-resource lookups. We typically combine both: CSV for the warehouse landing, REST for the operational checks and back-pushes.

Which OneRoster services does the connector cover?

OneRoster 1.1 defines three services and the connector covers all three when the SIS publishes them. The Rostering service carries users, classes, courses, enrollments, organizations, academic sessions, grading periods and demographics. The Gradebook service carries line items, results and categories. The Resources service carries the learning content links attached to courses and classes. Most districts publish Rostering at minimum, with Gradebook and Resources following depending on the SIS and the LMS in use.

What about OneRoster 1.2? Should we upgrade?

OneRoster 1.2 is the current version on the 1EdTech catalogue and adds capabilities around assessment, attendance integration and richer authentication scopes. Version 1.1, released as a final standard in April 2017, is still the version most school districts run in production, and the path PowerSchool SIS and other certified consumers continue to support. The connector lands either version against the same warehouse model, so the upgrade conversation can move at the SIS vendor's pace rather than blocking reporting today.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your OneRoster 1.1 setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors