What OneRoster is
A shared language for rostering data.
Before OneRoster, every SIS and every app had its own way of representing student, class, and enrollment data. Integrations required custom mapping for every combination. OneRoster (developed by the nonprofit 1EdTech Consortium) defines a common structure that all compliant systems use, which makes integrations cleaner and more portable.
What OneRoster defines:
- How student records should be structured for integration
- How teacher and staff records should be structured
- How courses, sections, and enrollments should be represented
- How rosters should be shared via CSV files or REST APIs
- Standard fields for demographics, contact information, and identifiers
What OneRoster enables:
- Plug-and-play integrations between the SIS and ed-tech apps
- Cleaner data flow to LMS platforms like Google Classroom and Canvas
- Reduced vendor lock-in because your data is in a portable format
- Simpler district onboarding for new tools
- More reliable, standards-based rostering pipelines