The case for one shared student record per class
By The Corra team · · 2 min read · Product
A shared student record means the facts about a class — who is in it, who has accommodations, who reads below grade level, whose family speaks another language at home — are stored once and read by every part of the software. It sounds like an implementation detail. It is actually the difference between a tool that saves you typing and a tool that can do the thinking.
The retyping tax
Most teachers keep the real roster in their head and a partial copy in each tool. The gradebook has names. The seating chart has names again. The intervention log has names, initials and a spreadsheet. Every one of those copies has to be updated when a student joins in October, and in practice most of them are not.
- New students get added to some systems and not others.
- An accommodation added in one place never reaches the tool that would have used it.
- Nobody can tell which copy is current, so the teacher becomes the reconciliation engine.
What becomes possible once it is shared
The interesting part is not the saved keystrokes. It is that software with a real roster can act on it. A differentiation request can produce the version a specific student needs rather than a generic tier. A family message can default to the home language on file. A substitute packet can carry the seating and the flags a stranger needs to know without you writing them out at 6am.
The risk this creates, and how it is contained
Concentrating student information in one place makes that place worth protecting properly, and pretending otherwise would be dishonest. Corra separates the sensitive parts of a student record so a limited-permission user cannot read them, denies every database request that does not match an explicit rule naming your account, and keeps identifiers out of AI requests entirely. Concentration is a design decision that has to be paid for in access control.
Where it starts
The roster is the first thing built in Corra, before any of the modules that depend on it, because building the spine last is how tools end up with five copies of the same class list. Today you enter classes and students manually. Import from Google Classroom and other sources is on the roadmap, and when it lands it will match on the provider’s own identifiers rather than on names — matching by name is exactly how a re-link produces two of every student.
Common questions
- Do I have to enter my whole roster before Corra is useful?
- You need a class and its students before the parts that reason about students can help, but you can start with a single class and add the rest later.
- Can Corra import my roster?
- Not yet. Import is on the roadmap; today entry is manual.