homeroom.city
The school system inside one municipal boundary
A city system is close together and always moving. Here is what that costs you, and which parts of it the platform actually carries today.
A city system is not a small county system. The buildings are minutes apart, the families move between them without ever leaving town, and the same adult works in four of them in one week. This page is about that geography, and it is honest about which parts of it the platform carries today and which parts are switched off.
The premise
A city system is a geography problem
Everything that is hard about running schools inside one municipal boundary is hard because the buildings are close and the people move.
Distance is small, so movement is constant
A family that changes apartments changes schools without changing districts. The transfer is internal, which is exactly why nobody treats it as an event — and why the record work gets done twice.
Buildings are small, so staff are shared
A compact system does not have one nurse per school. It has one nurse across four schools, one photographer across all of them, and an adviser who runs two yearbooks.
The central office is two miles away, not forty
Proximity is the reason a city office ends up doing building work by hand. It is close enough to absorb the problem, which is how the problem stays invisible.
The city is standing right there
The library, the parks department and the council all want to know what the schools are doing. They are not entitled to the records. They are entitled to a page.
None of those four are claims about software. They are the conditions this page is written against, and each of the sections below answers exactly one of them.
The specific case
The family that moves in November
One child crosses town mid-year. Here is the work that actually happens, system by system, and what a shared roster changes about it.
| What has to move | Done by hand | On one shared record |
|---|---|---|
| The roster record | Re-typed at the receiving building from a printout or an email. | One record, one identifier, a building attribute that changes. |
| Photo and consent state | Re-collected, because the receiving office cannot see what was signed. | Consent travels with the record and stays withdrawable by the family. |
| Directory visibility | Two entries for one child until somebody notices the duplicate. | One entry; the old building loses access on the date it loses the student. |
| Publication placement | The child appears in both yearbooks, or in neither. | Placement follows the enrollment date, not the memory of an adviser. |
| Picture day status | Photographed twice, or missed entirely and discovered in April. | The status is a field on the record, readable from either front office. |
The concession: none of this is automatic. Somebody still changes the building on the record, and if nobody does, every row above stays wrong. What changes is that there is one place to be wrong, and one place to fix it.
The honest state
What is live today
Four platform behaviors carry every city-shaped claim on this page, and this page adds no fifth one.
One home base
A staff member reaches the year’s work from one place instead of a browser full of separate logins.
Single sign-on
One account per person, which is what makes the shared-staff cards above possible without a borrowed password.
One shared roster
The same roster underneath every tool, which is what makes an in-system transfer a change to one record rather than five.
Role-based access
Access granted per role and per building, which is what lets a person work in two buildings without seeing all of them.
Those four are quoted from the platform’s own home-base description, not invented for this page. Everything else this page describes is one of those four seen from a city’s angle. If a sentence here seems to promise a fifth capability, that sentence is a defect and should be cut.
The honest state
What is off today
Each line below is a present-tense state, not a schedule. If one of them changes, this page changes with it, because the sentence is written from the same switch that refuses the act.
- PaymentNo payment rail is switched on in this product.There is no price on this page, no checkout, and no fee a family can pay here. Money moves through the channels a system already uses.
- AINothing here is AI.No text on this page was generated for you, nothing is ranked by a model, and no assistant reads a student record.
- MailNo mailbox is provisioned and mail is not sent from this product.Where a page describes reaching a family, it means a page they can open, not a message this product delivers.
- City-agency data sharingNo student record crosses from a school system into a city department through this product.We hold no data-sharing agreement with any municipal agency. What a partner can have is a page to read, which is a publishing act rather than a data act.
- Safety reportingConfidential reporting is a module, off in a building until a named person at the system turns it on for that building.The switch belongs to the system, per building. This page states the switch; it does not speak for any building's setting.
Read the last two together. Confidential reporting is a switch a system owns, per building, and a city department reading a published page is not the same thing as a city department reading a record. Conflating those two is the mistake this section exists to prevent.
The fourth condition
The city as an audience, not as a recipient
A public library, a parks department and a council committee all want to know what the schools are doing. What they can have is a page.
The distinction is the whole section: publishing is an act this product can perform — a page exists at an address and a partner opens it. Sharing a record is an act it cannot, because no data-sharing agreement with any municipal agency exists to authorize it. A partner who asks for a roster is asking for the second thing.
What a partner can be given
The same published page a family reads: a calendar of public events, a publication that has been released, a photograph the subject consented to publish.
What a partner cannot be given
A roster, an address, an enrollment record, a schedule, a health note, or an image of a minor who did not consent to it being published. None of those leave the system through this product.
Why we say it here
City partners are physically close and ask informally. An informal ask is the one most likely to be answered with a spreadsheet, so the answer is written down in advance.
The honest limit: this section describes a policy and a set of published surfaces. It does not describe an integration with any city department, because there is not one.
Minors
Consent, and what a map may never show
A city page is a map-shaped idea, so the first rule is about what a map may never carry.
Never public
No minor’s name, face, address, schedule or building assignment is publicly browsable. There is no map on this site with children on it, and there will not be one.
Consent-gated
A photograph of a student is published only where a consent covers that use. The consent travels with the record across an in-system transfer, which is one of the rows in the transfer table above.
Withdrawable
A family can withdraw consent, and the withdrawal applies going forward across the system rather than in one building.
Directory is a permission, not a publication
Directory visibility is granted per role and per building, and a family can be unlisted. Being in the directory is not being on the internet.
Distinct, not duplicate
Why this is not the district page
Two pages describe a multi-building deployment. They answer different questions and neither one restates the other.
| Question | Page that answers it |
|---|---|
| Who may act, on which class of data, and what does the action leave behind? | The authority plane — homeroom.management. Permissions, consent policy, the record of an action. |
| What follows a family that moves three blocks, and who covers four buildings on a Tuesday? | This page. Distance and movement inside one boundary. |
| What does one building do with its own year? | homeroom.center — the inside of a single school. |
| What does the platform do, feature by feature? | homeroom.software — the product tour. |
The overlap we admit: both this page and the authority page care about a person working in two buildings. The authority page cares because it is a permission. This page cares because it is a commute.
The stake
What it costs to not have this
Stated as consequences rather than as savings, because we hold no figure for any system and will not invent one.
A child is counted twice
Two directory entries, two yearbook placements, or two picture-day records for one student. It is found late, usually by a parent.
A child is counted zero times
The worse direction. A mid-year transfer lands between two buildings’ lists and the student appears in neither publication.
A consent is re-collected or lost
The receiving office cannot see what was signed, so it either asks again or assumes. Assuming is the failure that matters.
An action becomes unattributable
Shared credentials for shared staff means that six months later nobody can say which adult made a change.
We are not claiming a dollar amount, an hours-saved number, or a percentage. No system has published one to us, and a number we made up would be worse than none.
Pushback
Objections we get, answered
- We are four buildings. Is this sized for a county?
- The shared roster and role-based access do not care how many buildings there are. A four-building system uses the same two mechanisms a forty-building one does, with fewer scopes to grant.
- Our buildings already each have something that works.
- Then the cost you are carrying is the seam between them, and it shows up on the day a family moves across town. That is the ledger in the transfer section, not a claim that your building tools are bad.
- Can the city read our data?
- No record crosses into a city department through this product, because we hold no agreement that would let it. A partner reads a published page, the same page a parent reads.
- What happens to a student who leaves the system entirely?
- The receiving system is outside this deployment, so the record does not follow. What the family keeps is what they were given: their own copies, and a consent they can withdraw.
- Who can see a child’s address?
- Directory visibility is granted per role and per building, and a family can be unlisted. No minor’s address, schedule or face is publicly browsable from this or any Homeroom host.
- Is any of this switched on for us right now?
- Not by us. A system turns modules on building by building, with a named person doing it. Nothing on this page describes a state your system is already in.
The ask
The next concrete step a city system takes
One step, and it is a reading step rather than a purchase.
- Read the product itself at homeroom.software, which is the feature-by-feature tour this page deliberately does not repeat.
- Read the authority plane at homeroom.management before any conversation with a records officer, because the permission and audit questions are answered there and not here.
- Write down your own version of the transfer table above — the five systems a mid-year move touches in your buildings. That list is the thing worth bringing to a first conversation, and it is yours whether or not you ever talk to us.
There is no form on this page, no price, and nothing to buy here. That is a statement about what this page does, not a hint that something is about to change.
What is true on this page
Homeroom is a school platform. On this host it is described from the angle of a city school system: several buildings inside one municipal boundary, families that move between them, and staff shared across them.
No payment rail is switched on in this product. Nothing here is AI. No mailbox is provisioned and mail is not sent from this product. No student record crosses into a city department through this product, because we hold no agreement that would permit it. No minor’s name, face, address or schedule is publicly browsable.
No city, school, system, count or customer is named anywhere on this page, because we hold none to name.