Attendance
BuiltEveryone starts present and the teacher marks the exceptions, with five days of history on every row. A period takes about thirty seconds.
RoundUp K12 is a web-first records platform for K-12 districts — attendance, grades, students and schedules in one place, built for the staff who keep them accurate rather than for the demo that sells them.
Attendance is the module that exists today. The rest is in design, and this page marks which is which.
The product
A student information system is judged on the unglamorous half — the August schedule conflicts, the state submission window, the record a registrar corrects at 4pm. We are building toward that, and we are not going to describe it in the present tense before it arrives.
Everyone starts present and the teacher marks the exceptions, with five days of history on every row. A period takes about thirty seconds.
Assignments, weighting and posting, built so a teacher can enter a stack of papers without leaving the keyboard.
The record a registrar actually works from: enrolment, contacts, programme flags and the history behind each of them.
Courses, sections and the master schedule, including the part nobody demos — the fifty conflicts you resolve in August.
The extracts your state asks for, generated from the same records staff maintain daily rather than reassembled each submission window.
Grades and absences for parents. A responsive route first; a phone app when push notifications are worth the store review.
How it is shaped
A registrar, an attendance clerk, a counsellor and a SIS admin all sit in front of a large monitor, and the work in front of them — schedules, transcripts, reporting — is spreadsheet-shaped. So the staff product is a web app with the density that implies, not a phone screen stretched sideways. Teachers use the same app; it is deliberately not scoped as a “teacher app”, because teachers touch two of the six modules and none of the reporting the district is liable for.
Family access is the part that belongs on a phone, and it earns a real app the day push notifications matter — a grade posted, an absence in second period. Until then a responsive route serves a parent perfectly well, and we would rather ship that than an app shell with nothing behind it.
Security and privacy
These are architecture decisions made before there was anything to protect, which is the only time they are cheap.
Every district is its own subdomain, so districts are separated by the browser's own origin boundary and not only by our code. Nothing is shared between them in a browser — that is the point of paying for subdomains.
The hostname decides what a heading says. The API resolves the district from the signed-in session and authorizes every request on its own, so a wrong hostname costs a mislabelled screen, never another district's records.
Those two identity providers, pinned deliberately. Districts already run one of them, and a narrow list is a smaller thing to get right than an open one.
Built around the FERPA obligations a district already carries, with data residency in the United States. We hold no third-party audit yet, and we will tell you exactly what we can and cannot show you.
For districts
Half an hour on what your registrar and attendance clerk do today, and an honest answer about which parts of that we can carry now.
Onboarding a district is a database row, not a DNS change. You get district.roundupk12.com and sign in with the accounts staff already have.
Pilots start narrow — a single school, a single module — because that is the size at which we can fix what you find while you are still watching.
Questions
No. Attendance is the only module built, and we are not selling a student information system on the strength of a roadmap. What we are doing now is pilot conversations with districts willing to shape the rest.
That is the destination, and it is not where we are. Scheduling, transcripts and state reporting are what an SIS is actually judged on, and those are scoped rather than shipped.
Because the people who live in this system — a registrar, an attendance clerk, a counsellor, a SIS admin — are at a desk with a large monitor, and the work is spreadsheet-shaped. Teachers use the same web app. Parents get the phone companion, because a parent genuinely has no desk.
The district does. Export is a requirement of the record layer rather than a feature on a price sheet, and an exit should be as unremarkable as an import.
Yes — same team, separate product. K-12 is organised around grade, course and section, with its own schema and its own backend, because an early-childhood system organised around age in months and licensing ratios is the wrong shape for a high school.
We are choosing a small number of districts to build the next modules alongside. If yours is coming up on a renewal, or you have simply had enough of the one you have, that is a good conversation for us to have.