For school board members and board secretaries
A school board posts notice, adopts an agenda, distributes a packet, moves and votes, adopts minutes, and maintains a policy manual that is the district's law. This is the workroom for those six acts — and for the secretary who carries most of them.
Some of what follows is running inside the platform today and some is still being built. Every section below is labelled with which it is. Nothing on this page can take a payment, and nothing here is sold by the seat.
The governance cycle
Most board software models a meeting as a document. A meeting is really a sequence of acts, each producing a record that a later act depends on. Model the acts and the documents fall out; model the documents and the acts have to be reconstructed from prose.
Board secretary
The meeting is called and posted. Open-meetings statutes set a minimum notice period and a posting location, and both vary by state -- the system holds the posting timestamp and the notice text as a record, so the board can show what was posted and when.
Produces: A timestamped notice record
Board president + secretary
Items are placed, ordered, and split between the consent agenda and items called for separate action. An item carries the person who placed it and the action being requested, so the agenda reads as a list of decisions rather than a list of topics.
Produces: An adopted agenda, versioned
Board secretary
Each agenda item gathers its supporting material into one packet. The packet has two faces -- the members' copy and the public copy -- and the difference between them is a redaction decision that is recorded, not a second document someone maintains by hand.
Produces: A member packet and a public packet
The board
Quorum, motions, seconds, amendments, and the vote. A motion carries its exact text; a roll-call vote carries each member's name and how they voted. Abstentions and recusals are distinct from absences and are stored that way.
Produces: Motions with recorded votes
Board secretary
Draft minutes are prepared from the motions and votes already captured, then go back to the board to be adopted. Minutes are not the record until the board adopts them, and the system does not let a draft masquerade as an adopted minute.
Produces: Adopted minutes, with the adopting motion
The board
Where the meeting adopted or amended policy, the manual moves. The prior text is superseded, not deleted, and the adopting motion is attached -- so any clause can be traced to the meeting that put it there.
Produces: A policy version with its provenance
The packet
The member packet and the public packet differ by a set of recorded decisions, not by a second file someone maintains by hand. That is the whole design: when the two are separate documents, the public one drifts, and the drift is discovered by a reporter.
Seated board members and the secretary
Holds
Never holds
Anyone, no login
Holds
Never holds
The minors wall
This is the most load-bearing claim on this page, so it is stated as mechanism rather than as posture. Each row below says what the rule is and what enforces it.
Never enters the public packet
Items that reference an individual student carry a student reference, not a name; the public rendering resolves that reference to nothing at all rather than to a redaction box that advertises a name is missing.
Consent-gated, and never on a public governance surface
Board surfaces do not read the photo store. There is no code path from an agenda item to a student image, which is a stronger statement than a permission check on one.
Closed session only, and segregated in storage
These items are stored against the closed-session label from creation. An item cannot be moved into open session without an explicit action that is itself recorded.
Recorded as participation, not as a student record
Public comment captures that comment occurred and on what item. Where a minor speaks, the identity handling follows the district's consent posture rather than defaulting to publication.
Published only above a suppression threshold
Small-cell suppression is applied before a figure reaches a public packet, because a count of one in a subgroup is an identity.
This architecture is FERPA-aware. It is not certified, and there is no certification for a school-board records product to hold — a product displaying one is displaying something else.
The policy manual
A policy manual exists to answer one question: what rule was in force on a given date. That question is unanswerable if history can be edited, so superseded text is retained with the range it governed and the motion that ended it.
| State | What it means | Public visibility |
|---|---|---|
| Draft | Text exists; no board action has been taken on it. | Not published |
| First reading | Introduced to the board. Discussion permitted; adoption not yet in order. | Published with the reading date |
| Second reading | Returned to the board, usually with amendments from the first reading. | Published, with the changes since first reading marked |
| Adopted | Carried by motion. This is the policy of record from its effective date. | Published as current, with the adopting motion attached |
| Superseded | A later adoption replaced it. The text is retained, never deleted. | Published as historical, with the date range it governed |
| Rescinded | Withdrawn by motion with no replacement. | Published as rescinded, with the rescinding motion |
Seats, officers, and disclosure
A seat has a term with a start and an end, and a member occupies a seat rather than the board as a whole. Vacancies, appointments, and mid-term resignations are seat events, which is what makes a historical roster answerable.
President, vice-president, and clerk are roles held for a term, recorded with the motion that elected them. The presiding officer of a meeting is recorded per meeting, not assumed.
A disclosure is attached to a member and surfaces against agenda items it touches. The system records the disclosure and the recusal separately, because disclosing an interest and declining to vote are two different acts.
Many states require newly seated members to complete open-meetings or ethics training within a window. The record holds completion dates. It does not assert what any given state requires.
Meeting mechanics
Minutes narrate. A record answers. Storing quorum, the motion text, the second, each amendment, and each member's vote as discrete events is what lets a board answer “who voted for this, and under what threshold” without re-reading a transcript.
| Step | What happens | What is stored |
|---|---|---|
| Quorum | The meeting cannot act without a quorum, and quorum is computed against seats filled, not seats that exist. A vacancy changes the threshold. | Members present, seats filled, threshold at gavel |
| Motion | A member moves. The motion carries its exact text, because the text is the thing being voted on and a tidier restatement is a different sentence. | Verbatim motion text and the moving member |
| Second | Without a second the motion dies, and dying for want of a second is itself a recorded outcome. | Seconding member, or the absence of one |
| Amendment | An amendment is its own motion against the parent. The parent's original text survives the amendment rather than being overwritten by it. | The amendment, its vote, and the resulting text |
| Vote | Voice vote or roll-call. A roll-call vote records each member by name. Abstention and recusal are stored distinctly from absence, because they mean different things about the member. | One row per member per motion |
| Outcome | Carried, failed, tabled, or withdrawn, against the threshold that applied. Some actions need more than a simple majority, and the threshold is recorded with the result. | Outcome, threshold applied, and tally |
Grounds for closing a meeting are set by state statute and vary materially. These are the categories the record supports — the page does not assert any state's rules, and none of this is legal advice.
An individual employee's appointment, evaluation, discipline, or dismissal.
Discipline, placement, and special-education matters concerning an identified student.
Pending or threatened litigation, and consultation with counsel.
Collective bargaining strategy and the negotiation of real property terms.
Safety plans and security arrangements whose disclosure would weaken them.
Speakers sign up against a meeting and, where the board requires it, against an item. Time limits are the board's policy; the record holds who spoke, on what, and for how long.
That comment occurred, on which item, and any written material a speaker submitted for the record. The board's response, if it makes one, attaches to the item rather than to the person.
Identity handling follows the district's consent posture rather than defaulting to publication. A child addressing the board does not thereby become a public record entry.
Public comment is not a complaint channel with a service level, and the product does not pretend otherwise. Where a district runs a formal complaint process, that lives elsewhere.
The record
Retention schedules are set by state law and by the board's own policy. The product's posture is to retain rather than to prune, and to never silently edit an adopted record.
| Record | Posture |
|---|---|
| Meeting notice | Retained with its posting timestamp |
| Adopted agenda | Retained, versioned; superseded versions kept |
| Member packet | Retained; closed-session portions segregated |
| Public packet | Retained and publicly readable |
| Motions and votes | Retained permanently; never edited after adoption |
| Adopted minutes | Retained permanently, with the adopting motion |
| Policy versions | Retained permanently, including superseded text |
| Closed-session material | Retained under the closed label; not publicly readable |
Honest status
This table is the reason this page can be trusted about anything else. Rows marked not built are not roadmap language — they do not exist.
| Capability | Status | Detail |
|---|---|---|
| Public board portal (agenda, minutes, motions, roll-call votes) | Built | A public, no-login read of one board's adopted record is live in the platform and is the outward half of this product. It is served under schoolboard.network, not here. |
| Motion and vote capture, including abstention and recusal | Built | Votes are stored per member per motion, with abstention and recusal distinct from absence. |
| Policy manual with reading states and supersession | Built | The state machine above is implemented; superseded text is retained. |
| Packet assembly with a member face and a public face | Partly built | Assembly and the two faces exist. The redaction-decision record -- who withheld what and why -- is specified and not yet fully wired. |
| Notice posting with statutory timing checks per state | Partly built | The posting record exists. Per-state notice-period rules are encoded for a subset of states, not all fifty, and the page does not pretend otherwise. |
| Public-records request intake and response tracking | Not built | Specified, not started. There is no request queue in the product today. |
| Live-meeting streaming or captioning | Not built | No streaming stack, no captioner, no integration. If a board needs a stream today it runs one outside this product and links it from the agenda. |
| Electronic signature on adopted instruments | Not built | No signature rail is wired. Adopted instruments are recorded, not signed, in the product. |
| Payment, dues, or per-seat billing | Not built | Deliberately absent. This site has no payment rail at all -- see the honest-money note under the refusals below. |
| Machine-drafted minutes or agenda summarization | Not built | Deliberately absent, and it is a refusal rather than a gap. See the refusals section for why a paraphrase of a motion is not a record of it. |
Posture
No vendor is named here. The comparison that matters is against the common posture, which is what most boards actually live with regardless of whose software they run.
| Dimension | The common posture | Here |
|---|---|---|
| The public copy | A second document, exported and uploaded by hand after the meeting | A second face of the same packet, derived from recorded redaction decisions |
| A member's vote | Recorded in the minutes narrative as prose | A stored row per member per motion, with abstention and recusal distinct from absence |
| Policy history | The current manual, with prior versions kept in a separate archive if at all | One manual whose clauses carry their adopting motion and the dates they governed |
| Student material in a packet | Handled by the secretary remembering to redact it | Structurally absent from the public face; there is no path from an item to a student record |
| Pricing posture | Per-seat, per-board-member, renewed annually | Not sold on this site at all today; no payment rail exists here |
Refusals
A governance record is one of the few products where the refusals are the feature list. Each of these is a decision, not a gap.
The text of a motion is the thing that was voted on. A generated paraphrase that reads more smoothly is a different sentence, and a board that adopts it has adopted the paraphrase. Motions are stored verbatim and rendered verbatim. There is no summarizer in this product.
Minutes become the record when the board adopts them. Until then they render as a draft everywhere they appear, including in the packet and in any export. There is no setting that removes the draft label.
Open-meetings law makes the board's business public. It does not make a child public. Where the two pull against each other the minors wall wins, and the item moves to closed session rather than the student moving into the public packet.
A policy manual whose history can be edited cannot answer the question it exists to answer: what rule was in force on a given date. Superseded text is retained with the range it governed.
There is no cart, no plan table, no card field, and no payment processor on this property. A governance record and a transaction have no business sharing a surface, and this site does not ask a board member for money.
The architecture is FERPA-aware and the page describes exactly what the data model does and does not hold. There is no federal certification for a school-board records product, so this page does not display one.
The governance family
Naming these here is not a claim that any is live. Each is its own brand with its own status, stated on its own page — and the two that are still being built are not linked, because a link asserts a reachable product.
The board
boardofeducation.software
The governing body's own workroom: notice, agenda, packet, motions, minutes, policy.
You are here
The district
The administrative tier the board governs.
The state
doe.software
The state-agency tier the district reports into. Being built.
Being built
The public record
The board member's network and the no-login public read of an adopted record.
Questions
schoolboard.network is the public and role-facing half -- the board member's network and the no-login public read of an adopted record. This property is the workroom where that record is assembled: notice, agenda, packet, motions, minutes, and the policy manual. One board, two surfaces, and they are deliberately not the same site.
No. The meeting cycle and the policy manual are separate; a board can run agendas and packets while its manual stays where it is. Moving the manual is worth doing for the provenance, but it is not a precondition.
No, and nothing is. There is no federal certification programme for a school-board records product to hold, so any product displaying one is displaying something else. What this architecture does is described plainly in the minors wall above: student-identifying material is consent-gated, is structurally absent from public governance surfaces, and closed-session material is segregated from creation.
Not on this site. There is no payment rail here and no per-seat plan. Boards that want to try it are onboarded by hand, one at a time, by email.
No, and that is a refusal rather than a missing feature. Motions and votes are captured as they happen, so the draft minute is assembled from records that already exist -- but the prose is the secretary's, and no machine paraphrases a motion.
Notice periods and posting rules are encoded for a subset of states and are being extended. Where a state is not yet encoded the system still records what was posted and when, which is the evidence a board needs; it simply does not check the timing for you.
Seated members and the board secretary. A member who has recorded a recusal on an item stops seeing that item's material. Nobody outside the board sees the member face at all.
It exports. Agendas, packets, motions, votes, minutes, and the full policy history including superseded text come out in a documented format. A governance record that can only be read inside one product is not a record.