For elected school board members, trustees, and board secretaries
A principal runs the building. Your board sets the policy the building runs on, votes on the record, adopts the minutes the public has a right to read, and answers for all of it at the next open meeting. SchoolBoard.Network is that front door: a policy manual with an immutable version history and a staff acknowledgment ledger, a model-policy shelf you can adopt from, an agenda-to-roll-call meeting workspace, and a public sunshine-law page that is honest about what is built and what is still honest-off.
Distinct from schooladministrator.network, the day-to-day operating picture for principals, superintendents, and district administrators -- see how the two relate below, rather than two copies of the same page.
Open meetings, on the public record
Sunshine-law transparency should not be a PDF someone remembers to post. The public board page is built to read directly off the SAME governance lock your board secretary uses to close out a meeting: the moment a governance officer moves a meeting's minutes from draft to adopted, that meeting's agenda, minutes, and named roll-call votes become the public record, no sign-in required. Until that adoption step happens, the page is honestly empty -- never a draft, never a preview, never invented.
There is one lock: a governance officer moves a meeting from draft to adopted. That lock is what the public page reads -- not a separate publishing step someone can forget, and not a second copy of the minutes that can drift from the record.
Built -- honest-off until adopted
Every adopted motion carries its tally and the named vote of each public official who cast one -- who voted yea, who voted nay, who abstained. No internal ids, no meeting number, no email or address -- just the public official's name of record and their vote.
A draft, tabled, or in-progress meeting is never returned by the public page -- the read is scoped to adopted meetings only, at the source. An empty page for a board that has not yet adopted anything is the honest, correct result, not a bug to fix later.
This public record is your board's business: agendas, minutes, motions, and named votes of adult public officials. It carries no student. Anywhere else on the platform a student's data lives, it stays behind the consent gate -- a minor without recorded consent is never public, indexed, or searchable.
This page names no district and shows no sample vote. We would rather describe the mechanism honestly than fabricate an example.
Board policy, on a closed law
A policy binder anyone can quietly edit is not a real record. The manual here runs on a closed lifecycle law: a policy starts in draft, only a governance officer can move it to active, and only when it already points at a real published version -- never an empty 'active' policy. Every published text is a new, numbered version; there is no silent edit, ever.
A policy's status can only move where the law allows: draft can become active or retired, active can become retired, retired is final. Any other move is refused outright, and a governance officer is the only role who can move it at all.
Built -- module-gated
Publishing new policy text creates the next numbered version -- it does not overwrite the last one. The manual always resolves to the current version's exact text, and a version number, once published, never changes.
Only active policies appear, grouped into the manual's categories -- governance, students, personnel, finance, facilities, instruction, community relations, bylaws, and other -- sorted by policy code inside each category, the way a printed board policy manual is organized.
Assign a policy that requires staff sign-off and the ledger tracks who has acknowledged the CURRENT required version, who is still outstanding, and who is past a due date -- an acknowledgment against an older, superseded version leaves a staffer outstanding until they re-acknowledge.
The manual and the ledger are each an add-on module a district turns on for its board -- neither lights up automatically. A clickwrap self-attestation or a wet signature a governance officer keeps on file are the two acknowledgment methods behind the ledger today; a fully sealed cryptographic e-signature is captured and bound to the exact policy text but not yet cryptographically sealed by a live signing provider -- honest-off until that seal is provisioned.
A shelf to adopt from, not a blank page
Most boards do not write policy from a blank page; they adapt a model a state association maintains. This shelf holds that shape: a structured, numbered catalog of model policies, each with its own edition history, that a governance officer can adopt directly into the district's own manual as its next draft version -- through the exact same lifecycle law the manual itself runs on, never a separate, forked path.
Each model policy carries a structured code -- one to four leading letters for its manual section, then optional dash-joined groups, the shape a real board policy code takes (a code like BDDF, JFC, or KCD-R). Codes are collision-checked and sorted by section, the way a printed policy manual is organized.
A model policy's editions are numbered the same immutable way the manual's own versions are -- the next edition is always the highest existing number plus one, never a silent overwrite of the last one.
Adopting a model edition builds the next DRAFT version of your own board policy directly from its text -- routed through the exact same version-numbering, authorization, and empty-content law the manual's own versions use. There is no forked, second rulebook for an adopted policy.
The connector that would automatically pull editions from a real state association's live feed is not wired. Until it is, a governance officer authors and edits the shelf's entries directly; we do not claim a live sync to any specific association that does not exist.
Honest-off -- no external feed yet
A model policy's maintaining association is stored as a plain, generic label your district sets -- never a brand name we assert on your behalf.
The meeting itself, agenda to adopted minutes
Everything that eventually becomes the public record starts here: open a meeting as a draft working record, build its agenda, take an aggregate motion under a quorum floor, or take a named, on-the-record roll call -- then lock the minutes when your board is ready. The tally and the result are computed by one governance engine every time; the workspace never re-derives them by hand.
A governance officer opens a meeting as a draft working record and adds agenda items to it one at a time -- the working copy every later step builds on.
Built -- module-gated
Record a motion's yea/nay/abstain tally against a quorum floor and the result -- passed, failed, or tabled -- is computed by the governance engine, not typed in by hand.
For a motion that calls for it, record each member's name and choice individually -- one member, one vote, enforced at the database so the same member cannot be recorded twice on one motion.
When your board is ready, a governance officer locks the minutes from draft to adopted -- a one-way, audited move. A second attempt to adopt an already-adopted meeting is refused outright, never re-locked. This is the exact lock that feeds the public transparency page.
Meeting and motion management is a governance-officer action; any staff session can read a meeting's draft minutes once the module is on -- board minutes are a public record of public officials even before the formal adoption step.
A different front door for a different role -- not a rebuild
schooladministrator.network is the day-to-day operating picture for the people who run a school or district -- principals, superintendents, district administrators -- and it already carries an honest board-governance card of its own. SchoolBoard.Network does not duplicate that card; it is the distinct front door for the board itself: the elected or appointed members who set the policy, the board secretary who keeps the manual and the minutes, and the public who has a right to read what was adopted. Same governance engine underneath, a genuinely different audience and voice on top.
The operating picture for principals, superintendents, and district administrators: every student publication, the picture-day pipeline, a free records tier, and its own board-governance card describing these same finalizers as built and held.
This site: the policy manual and its version history, the model-policy shelf, the meeting workspace, and the public sunshine-law page -- built for a board member, a board secretary, and the public they answer to, not for the person running the building day to day.
We extend the existing card rather than rebuild it -- if you already run schooladministrator.network, this is the same governance engine wearing the board's own front door.
The network -- launching
The best answer to a governance question is usually another board member or secretary who has already answered it. We are building a peer network for elected and appointed board members, trustees, and board secretaries to compare policy language, meeting procedure, and how other boards handle a sunshine-law request. It is being built now. It is not live yet, and this page will never pretend it is.
Honest status: the network is not live. There is no live posting, no member feed, and no public directory today, and nothing on this page claims otherwise. When it opens it will be limited to verified board members, trustees, and board secretaries, who are adults; no student information is ever part of it, and anywhere a student's data lives on the platform it stays behind the consent gate -- never public, indexed, or searchable. Joining the waitlist reaches a person -- and this site sets no cookies and runs no tracker.
Frequently asked questions
schooladministrator.network is the day-to-day operating picture for the people who run a school or district -- principals, superintendents, district administrators. It already carries an honest board-governance card of its own. SchoolBoard.Network is a distinct front door for the board itself -- the elected or appointed members who set policy and vote on the record, the board secretary who keeps the manual and the minutes, and the public who has a right to read what was adopted. Same governance engine underneath; a different audience, a different voice, and this page cross-links the operations hub rather than duplicate it.
The mechanism is built: once a governance officer locks a meeting's minutes from draft to adopted, that meeting's agenda, minutes, and named roll-call votes become the public, no-login record. Until a board takes that adoption step, the public page for that board is honestly empty -- never a draft, never a placeholder, never invented. We are not claiming any district's page is populated today; we are describing what the platform does the moment a board adopts a meeting.
No. The policy manual and the board-meeting workspace are each an add-on module a district enables for its board -- neither is on by default. A district that has not turned a module on sees nothing different; the surfaces stay dark until a governance officer's school or district administrator switches them on.
Two ways today: a staffer's own clickwrap 'I acknowledge,' or a wet signature a governance officer keeps on file and records on the staffer's behalf. A compliance ledger tracks who is outstanding against the CURRENT required version and who is overdue -- an acknowledgment against an older, superseded version does not count. A fully sealed cryptographic e-signature is captured and bound to the exact policy text but not yet cryptographically sealed by a live signing provider -- honest-off until that seal is provisioned.
You author them directly today. The shelf is built to hold a state association's maintained, numbered model policies and let you adopt an edition straight into your own manual -- but the connector that would automatically pull editions from a real external association's feed is not wired yet. Until it is, a governance officer authors and edits the shelf's entries by hand; we never claim a live feed that does not exist.
No. The public record is your board's agenda, minutes, motions, and named roll-call votes -- adult public officials answering on the record, not students. It carries no internal ids and no student reference of any kind. Anywhere else a student's data lives on the platform, it stays behind the platform's consent gate: a minor without recorded consent is never public, indexed, or searchable.
No, by design. A roll-call vote is named and on the record -- one member, one vote, backed by a database rule that refuses a second vote from the same member on the same motion. An elected or appointed official answers to the public for how they voted; there is no unnamed or hidden ballot on this surface.
No. It is launching. Today this is a waitlist only -- there is no live posting, no member feed, and no public directory. When it opens it will be limited to verified board members, trustees, and board secretaries, who are adults; no student information is ever part of it.
Money is honest-off on this front door: no price, no checkout, no plan comparison lives here. Pricing lives on the pricing page, and a governance walkthrough is the way to talk through what your board specifically needs.
Sign in the same way your district already does -- single sign-on -- and a governance officer opens a meeting, defines a policy, or records a motion directly inside the workspace. There is no separate spreadsheet import for board records today; the workspace is where the record is made.
A walkthrough, not a funnel
Book a governance walkthrough and we will show you the policy manual and its immutable version history, the model-policy shelf and its one-step adopt into your own manual, and the agenda-to-roll-call meeting workspace -- each an add-on module your district turns on, not something already running everywhere. We will also show you the public sunshine-law page honestly: built, fail-closed, and empty until your board actually adopts a meeting. No stock testimonial, no invented district, no fabricated adoption count.
Your board answers to the public. The record of how it voted should be exactly what it says it is -- named, on the record, and never shown before your board says it is final. That is the law this platform enforces, not a policy binder that only holds if everyone remembers to follow it.
Already running Homeroom? Sign in -- a governance officer lands wherever their board workspace is enabled.