middleschool.center · For middle-school staff · Grades 6-8
Middle school is more departmentalized than elementary: a student moves between five, six, or seven different teachers in a single day, often for the first time. That is a genuine gain -- students first run their own schedule, pick electives, and start to speak up for themselves with a teacher directly -- but it means no single adult has the whole-day view an elementary teacher has by default. middleschool.center gathers that view by the one anchor that still holds the day together: the advisory or grade-level team. Attendance triage, the counselor and MTSS caseload, standards-based grades, each teacher’s daily surfaces, and family messages -- read by GROUP, not scattered across five separate systems.
This hub is in active development. No school is running it live yet, and money is honest-off -- there is no live charge on this page. The picture-day store and texted alerts are early access.
Why a hub, not another single-purpose tool
Three things about grades 6-8 make a gathered, by-group view the right shape -- not a nice-to-have layered on top of the program, publications, and roster tools the platform already runs.
An elementary student has one teacher who sees the whole day; a middle schooler has a different teacher for math, science, English, a world language, and an elective, often on a rotating block. Each of those teachers sees a slice. Nobody sees the whole day by default -- unless a hub is built for the one group that DOES span it: the advisory or team.
This is the age a student starts handling things directly with a teacher -- asking for help, requesting a schedule change, speaking up in an elective -- instead of routing everything through a parent. That is growth, not a gap to close. But it means the family channel has to work as a BACKSTOP the student does not always trigger themselves, not the only channel a family hears anything through.
The activities a student is actually in -- a first elective, a club, a team -- turn over by the term, and the people responsible for that student's day change with them. A hub view is only honest if it reads the CURRENT group a student is in, not a roster frozen from the first week of school.
What the hub gathers
Every capability below already exists on the platform; this page describes how the hub reads it from the GROUP angle rather than describing it as a new engine.
A chronic-absence band rolls up from a supplied attendance summary and recommends a tiered intervention -- but the recommendation is ADVISORY ONLY: it never files a truancy petition and never refers a family to court on its own. Where the enrolled-days count is missing or zero, the rate is reported as UNKNOWN, never a misleading 0%, and an unknown band routes to needs-review for a human, never silently to “on track.” A student is referenced only by an opaque roster handle.
Built · advisory-only · fail-soft
A departmentalized day only has one thing that spans it: the advisory, homeroom, or team group. The scheduling engine treats that grouping as a first-class structural constraint, so the cohort holds together across five or more separate subject sections rather than dissolving into a pile of unrelated class rosters. The hub reads that SAME structural anchor to organize its view -- opaque cohort keys, never a student identity.
Built · structural anchor for the group view
A counselor's caseload and a composed student-360 read pull together the on-track picture for the students assigned to them, and a tiered MTSS support level is a data-trend FLAG a team reviews -- never a tier the system moves on its own. A sole-possession note is visible ONLY to the counselor who wrote it. Every read is fail-closed: an unauthorized viewer -- a general teacher without the capability, a parent, a rep -- gets nothing, never a leak.
Built · fail-closed · privacy-walled
The canonical gradebook's standards-aligned evidence rolls up to mastery PER standard, deterministically, as a report model over the existing gradebook -- not a second gradebook and not a new student table. A grade-level team reading the hub sees mastery banded by skill for the group it is responsible for, rather than opening each subject teacher's gradebook in turn. Surfaced through a consent gate; complements a school's system of record rather than replacing it.
Built · consent-gated · complements the SIS
Every subject teacher already has a section-scoped daily view: a seating chart, a sub plan, a parent-contact log, and an assignment roster. The seating chart and sub plan are section/room config; the parent-contact log and the assignment roster are student-coupled PII and are HONEST-OFF by design wherever no authorized store is connected -- nothing here is fabricated. The hub's job is reading those same per-teacher surfaces from the advisory/team angle, authorized-only, rather than inventing a new place to store them.
Built · honest-off where unconnected · authorized-only
A message to a family rides the same consent-gated `family_comms` lane used across the platform: email and text are sent only where a family has opted in, and a non-urgent send defers during a family's quiet hours. A genuine alert overrides quiet hours, because that is the life-safety lane, not the routine-update lane. Deliveries are de-duplicated, and an invalid event produces no send at all -- fail-closed, not a best-effort guess.
Built · consent-gated · fail-closed
Middle School Center is a staff-facing hub: the view an advisory teacher, a grade-level team lead, or a counselor opens to see the students they are responsible for, gathered by that ONE group rather than scattered across the platform. It is not itself the program a middle school runs, not the publications editor a student staff uses, and not the roster-sync plumbing underneath -- those are three separate, already-bespoke surfaces, and this page cross-links each rather than re-describing it.
Concretely: middleschool.software is the program front door a student and family use directly -- picking electives, running the schedule, joining a club or a first team. middleschool.press is the publications editor a student staff runs the yearbook and newspaper in. middleschool.technology is the roster-sync technology that keeps every downstream page current as the roster turns over by the quarter. middleschool.center is none of those -- it is the staff-side read of the SAME underlying records, organized around the advisory or team group, so a middle-school staff member is not opening five systems to understand how one group of students is doing.
An advisory teacher or grade-level team lead opens the hub for their group -- one advisory, one team, one house -- and sees, in place: which students crossed a chronic-absence band overnight (flagged for a human, never auto-referred), which students are on an active MTSS tier or a counselor’s caseload (visible only to the people authorized to see them), how the group’s standards-based grades are trending this term, and which of the group’s several subject teachers logged a parent contact or flagged a seating change this week. It is the SAME records every subject teacher and the counselor already work in; the hub’s only job is presenting them by group instead of by system.
When a family needs to hear something, the message goes out on the consent-gated channel the family actually opted into, deferred outside quiet hours unless it is a genuine alert. Nothing here replaces the subject teacher’s own gradebook, the counselor’s own notes, or the family’s own preferred channel -- it reads all three, by group, in fail-closed authorized view.
Gathering a group’s attendance, counselor, grade, and family-message picture into one screen raises the stakes on who can see it, not lowers them. Every read is authorized-only and fail-closed: a viewer without the counselor capability, the MTSS-team capability, or the records-office role sees an empty result, never a partial leak. A counselor’s sole-possession note stays visible only to the counselor who wrote it, even to another counselor on the same team.
Facial recognition is off by default, and family communication rides a consent-gated channel a family can withdraw at any time. Who can see a student’s roster entry and photos follows the access permissions a school sets, and families control their own consent. A picture-day order routed to an outside print lab is fulfilled by that vetted partner, so not every step is kept fully in-house -- and we never sell your data. The honest, keepable posture is the narrower one: consent-gated, off by default, and under the school’s own access controls.
What is built and what is honest-off — plainly
Built and wired today, on the same platform this hub reads: chronic-absence triage that recommends but never refers to court or files a petition; the advisory/team scheduling constraint that holds a cohort together across a departmentalized day; the counselor caseload and student-360 read, fail-closed; the MTSS tiered-support flag, advisory only; the standards-based grade roll-up over the canonical gradebook; each subject teacher's section-scoped daily surfaces; and consent-gated, quiet-hours-aware family messaging.
Honest-off: the parent-contact log and a section's assignment roster are HONEST-OFF wherever no authorized store is connected -- this hub reads them, it does not fabricate them. Money is honest-off across this page: no live billing, no subscription, no live payment; the picture-day store and texted alerts are EARLY ACCESS, matching the standing platform posture. No school is running Middle School Center live yet -- a conversation is the honest next step. Middle School Center is FOR-PROFIT software for middle schools; it is not itself a school, a district, or a nonprofit. Nothing here is legal or medical advice.
FAQ
Each is a distinct surface on the same platform. middleschool.software is the program front door a student and family use directly (electives, scheduling, clubs). middleschool.press is the publications editor a student staff runs the yearbook and newspaper in. middleschool.technology is the roster-sync technology underneath all of it. middleschool.center is the staff-side HUB: the view a advisory teacher, team lead, or counselor uses to see their group -- attendance, counselor/MTSS flags, grades, and family messages -- gathered by group rather than opened one system at a time.
No. Attendance triage is advisory only: the recommendation's refersToCourt value is always false, and the highest concern band always routes to needs-review for a human, never to a court referral. The MTSS tier is the same shape -- a data-trend flag the team reviews; the persisted tier is always the team's own decision, never one the system applies by itself.
Only an authorized viewer: the counselor-role capability, or a school/district admin for the aggregate view. A general subject teacher without that capability, a parent, or a sales/support role gets an empty result, not a redacted one -- there is no partial leak. A sole-possession counselor note is visible only to the counselor who authored it, even from another counselor on the same team.
No. The standards-based grade roll-up is a report model over the school's existing gradebook -- it consumes the standards-aligned evidence the gradebook already produces and does not introduce a second gradebook or a new student table. This complements a school's system of record; it is not a certified, full academic system-of-record.
They stay honest-off. The per-teacher daily surfaces that hold a parent-contact log and an assignment roster never persist or fabricate either on their own -- both defer to an authorized, injected store, and when that store is absent the hub simply shows nothing for that surface rather than inventing data.
A message rides the same family_comms consent lane used across the platform: in-app delivery is always available, while email and text are sent only where a family has opted in. A routine update deferred during a family's quiet hours; a genuine alert overrides quiet hours because that is the life-safety lane. Deliveries are de-duplicated, and an event that fails validation produces no send at all.
Because the audience is different. middleschool.software is built for the student and family driving their own schedule and electives. This hub is built for the STAFF member responsible for a group -- an advisory teacher, a team lead, a counselor -- who needs the group view, not the individual student-facing flow. Keeping them separate keeps each page honest about who it is for.
The hub view over records, attendance, and grades settles no money; money is honest-off across the platform today, including the picture-day store, which is early access alongside texted alerts. Middle School Center is in active development and no school is running it live yet. The honest next step is a conversation that shows the current state plainly -- what is built, what is honest-off, and what is early access. Email [email protected].
Attendance triage, the counselor and MTSS caseload, standards-based grades, each teacher’s daily surfaces, and consent-gated family messages -- read by advisory or team, not scattered across five systems. The hub is in active development, and a conversation walks through what is built, what is honest-off, and what is early access, honestly. Money is honest-off; there is no live charge on this page.