middleschool.technology · For middle schools · Built for a roster that churns
A middle-grades roster does not sit still: new students enroll every term, kids switch electives at the quarter, and team and club membership turns over between seasons. The technology here keeps up. A roster syncs from your student system, and the directory, ID cards, the branded school page, and every activity, club, and team page read the current list — who is really enrolled this quarter, not last term’s. This page is about the technology that tracks the churn, not the program you teach on top of it.
Roster sync, ID cards, and the branded school page are live today. The picture-day store and texted alerts are in early access, and money is honest-off — middleschool.technology does not process payments yet.
Why the middle grades churn
This is not a data-hygiene problem to nag a school about; it is the shape of the middle grades. Three things move the roster all year, and the technology has to expect all three rather than assume a list built in August holds.
The middle grades are a churn point in a family’s life: a move across town, a transfer between schools, an enrollment that lands weeks after the year began. A roster built once in August is wrong by October if nothing keeps it current, and every downstream page inherits that error.
Middle school is where a student first picks classes — band, art, a world language, a maker elective — and where those picks change at the quarter or the semester. An elective roster that is not re-read after a schedule change points at a class a kid left in December.
Fall cross country becomes winter basketball becomes spring track, and the club that met in the fall is a different group by spring. A team or club page frozen at its first roster credits the wrong students and misses the ones who actually showed up.
The most expensive thing a school does with its data is enter it more than once. A student typed into the yearbook tool, again into the directory, again into the ID printer, and again into a team page is four copies that drift apart the first time a name is corrected in one and not the others — and in a middle school, where the roster changes every quarter, they drift apart constantly.
Here the roster syncs from your student system. A school signs in the standard ways it already logs in, or imports the list once and lets it update, and that single roster becomes the shared spine every downstream page reads. A mid-year transfer who enrolls in October appears in the directory, gets an ID card, and lands on the right school page without anyone re-keying the name. A student who switches electives at the quarter, or changes teams between seasons, moves on the pages that read the roster — because they all read the same one.
The roster is owned by the school, not by us, and it is never sold to or shared with an outside company. The technology’s whole job here is to make one current list, and to make every other surface trust it instead of keeping a private copy that goes stale.
Coverage in a middle school lives in the activities: the clubs, the first electives, the first interscholastic teams. And the coverage is only as good as the roster behind it. A club, elective, or team page that pulls the actual participant list — the current one — credits the students who were really there this quarter. A page frozen at its opening-week sheet credits the wrong kids and quietly drops the ones who joined in the winter.
So the participant list is participant-accurate by construction: every activity, club, and team page reads the roster the school keeps current, not a photocopied sheet from a coach’s clipboard. When the yearbook adviser builds a spread, the coverage tools show who is on the roster now, so a fall team’s page and a spring team’s page are two different, correct groups instead of one guessed-at blend. The book matches the year that actually happened.
ID cards for the building and a branded school page come off the same roster the directory and the activity pages read. A card design, the roster photo, and a student number print as a batch, and the page carries the school’s own name, colors, and contact. When a new student enrolls mid-quarter, they get a card and appear on the page from that one roster — nobody keeps a parallel badge spreadsheet or a hand-updated web list that lags the real enrollment.
Be plain about scope: this is a records daily-driver that complements your district’s student information system. It is not a certified state system of record, and it does not pretend to be one or try to replace the SIS. It reads from the roster and holds what the school’s own office owns — the directory, the ID cards, and the page — and leaves the certified record-of-record to the system certified for it.
A student’s records and photos run on our own private systems. They are owned by the school and are never sold to or shared with advertisers, data brokers, or any outside company. A minor’s photos are never made public, never handed to an outside search engine to index, and never sold.
Find-my-photo is a permission-checked roster lookup, not a face match. It finds a student’s pictures by the roster tag a person with permission applied — the same lookup that keeps the activity pages current — not by scanning a crowd for a face. Face matching is a capability we are building and is not turned on today — the recognizer is not yet wired: it holds no face-recognition model weights, and no face template is computed from a photo. Photo finding uses a permission-checked roster lookup instead. Withdrawing the opt-in stops the matching, on the spot.
What does already work, end to end, is the part most families are really asking about: mark a student do-not-publish and their pictures and their name drop out of the digital edition, the online reader, and the print run.
This page is careful about two things it does not claim. It does not promise a picture can never leave the building — a picture-day order routed to an outside print lab does leave it, and we say so. Face matching is a capability we are building and is not turned on today — the recognizer is not yet wired: it holds no face-recognition model weights, and no face template is computed from a photo. Photo finding uses a permission-checked roster lookup instead. The claims we make are the narrower, keepable ones: private systems, never sold, face-matching not turned on in the software we run, templates walled and never handed back, a withdrawal that stops the matching, and a minor’s photos never made public, indexed, or sold.
Live today: roster sync from the student system, the directory, ID cards, the branded school page, and participant-accurate activity, club, and team pages. These are built and run today.
Early access: the picture-day store and texted family alerts. These are named early access on purpose, and nothing else on this page is dressed up as more finished than it is.
Money is honest-off. middleschool.technology does not process payments yet. When the picture-day store opens, it is the surface where a school earns and a family buys prints — that is a description of a future product, not a live charge. The store assembles an order and settles no money on this site today; no card is charged here.
What this is: middleschool.technology is a for-profit software platform for middle schools. It is not a school, not a district, and not a nonprofit. Middle schools are (mostly) public; the platform that serves them is a for-profit vendor. There is no charity or donation framing here, and none would be honest. There are no invented adoption numbers, testimonials, or named schools on this page; the anchors are what the roster technology actually does. A demo shows the current state honestly — what is built, what is early access, and what is honest-off.
FAQ
They are two views of the same platform. middleschool.software is the program front door — the pedagogy a middle school runs: first electives, teams and clubs, standards-based report cards, counselor and MTSS supports, and the move up to high school. middleschool.technology is the technology that tracks the roster underneath that program — the sync, the ID cards, the school page, and the participant-accurate pages that keep up as the roster changes every quarter. If you are choosing what your school will teach on, start with the program page; if you are asking how the roster stays current and where the data lives, this is the page for you.
It means the middle-grades roster moves all year: students enroll every term, electives switch at the quarter, and teams and clubs turn over by season. A list built once in August is wrong by October if nothing keeps it current. The technology here expects that churn — it syncs the roster from your student system so a mid-year transfer or an elective switch shows up on the directory, the ID cards, the school page, and the activity pages without anyone re-keying a name.
No — that is the point. You sign in the standard ways your school already logs in, or import the roster once and let it sync, and every downstream surface reads that one list: the directory, ID cards, the school page, and the club, elective, and team pages. Correct a name in one place and it is correct everywhere, because there is only one place. The roster is owned by the school and is never sold.
Each club, elective, and team page pulls the actual participant list from the current roster, not a sheet someone photocopied in the fall. So a fall team’s page and a spring team’s page are two different, correct groups, and yearbook coverage credits the students who were really there this quarter. The book matches the year that actually happened rather than a guessed-at blend.
No. It is a records daily-driver that complements your district’s student information system; it is not a certified state system of record, and it does not try to replace your SIS. It holds the directory, the ID cards, the school page, and the participant lists the school’s own office owns, and leaves the certified record-of-record to the system certified for it.
Find-my-photo is a permission-checked roster lookup, not a face match. It finds a student’s pictures by the roster tag a person with permission applied — it does not scan a crowd for a face by default. The matching capability behind that consent is not wired and is not turned on today — we are building it, designed to be studio-enablable with a parent's consent. Where the optional lane is exercised at all, the template is held only inside our own private system — never sent to an outside recognition service, and never returned to anyone. Withdrawing consent stops the matching, refused at the gate rather than honoured on a delay. It is consent-gated and school-owned; a minor’s photos are never made public, indexed, or sold.
Not yet on this site. The picture-day store and texted family alerts are in early access, and money is honest-off — middleschool.technology does not process payments yet. When the store opens it is where a school earns and a family buys prints, but today it assembles an order and settles no money; no card is charged here.
Roster sync, ID cards, and the school page are free to start and settle no money. middleschool.technology is a for-profit software vendor for middle schools — not a school, district, or nonprofit — and there are no invented adoption numbers or testimonials on this page. The honest next step is a demo that shows the current state plainly: what is built, what is early access, and what is honest-off.
One roster, synced from your student system, read by the directory, ID cards, the branded school page, and every activity, club, and team page — so nothing points at last term’s list. Roster sync, ID cards, and the school page are live and free to start; the picture-day store and texted alerts are in early access; and money is honest-off — the platform does not process payments yet. A demo walks the whole thing honestly.