Board packets · a roadmap page, told honestly
One packet: agenda, policies, and last meeting's minutes, put together in one place.
Preparing a board packet today means pulling the agenda from one place, the policies up for a vote from another, and the prior meeting's adopted minutes from a third. We are planning a single, assembled packet that draws from the SAME real agenda, policies, and minutes your board already keeps -- not a fourth, separate copy of any of it. This is a roadmap page: honest about what is coming, and equally honest about what is not built yet.
Coming -- waitlist, not yet built
Built from the same policy manual and meeting workspace schoolboard.network already ships -- no separate packet system to keep in sync.
The vision
What a packet would pull together
Imagine your next board meeting's agenda, the policies scheduled for a vote at that meeting, and the adopted minutes from your last meeting, gathered into one packet a board member can read before they walk into the room. No copy-and-paste between the policy manual and the meeting workspace; one packet, drawn from the same governance record your board already keeps.
The meeting agenda Policies up for a vote The prior meeting's adopted minutes
This is the plan, not a shipped feature -- see the honest breakdown below for exactly what exists today.
The honest breakdown
What is real and shipped today -- and what is not built yet
Real and shipped today (each an add-on module a board turns on, never universally on): a policy manual that moves through one closed law -- draft, active, retired -- with every published version numbered and never silently edited; and a board-meeting workspace where a governance officer opens a meeting, builds its agenda, records an aggregate motion under a quorum floor, takes a named, one-member-one-vote roll call, and locks the minutes from draft to adopted.
Not yet built: pulling those two real, separate surfaces into one assembled packet document. There is no packet table, no packet-assembly engine, and no packet API in the product today. This page is the honest, plain statement of that gap and the roadmap to close it -- not a preview of a feature that already works.
Why it matters
A board secretary's real, ordinary work today
Before an open meeting, a board secretary already gathers the agenda, checks which policies are scheduled for a vote, and pulls the prior meeting's adopted minutes for the record -- three real things, kept in two real, separate places (the policy manual and the meeting workspace) today. We are not claiming that gathering step is automated yet. We are describing why a single, assembled packet -- built from those same two real surfaces, not a third copy of them -- is the roadmap item worth building next.
Get notified
Join the waitlist for board packets
There is no live posting, beta build, or committed ship date today. Joining the waitlist reaches a person. This page sets no cookies, uses no third-party advertising or tracking scripts, and builds no behavioral profile; basic short-lived operational logs may record page requests.
FAQ
Common questions
Is board packet assembly live today?
No. Today the policy manual and the meeting workspace are two separate, real, shipped surfaces. Pulling an agenda, the policies up for a vote, and the prior meeting's adopted minutes into one assembled packet is not yet built. This page describes what we are planning, not what ships today.
What already works today, if packets are not built yet?
Two real things: a policy manual that moves through one law -- draft, active, retired -- with every version numbered and never edited in place, and a board-meeting workspace where a governance officer opens a meeting, builds its agenda, records a motion under a quorum floor, takes a named roll call, and locks the minutes from draft to adopted. A packet would sit on top of both, not replace either.
How would a packet actually get assembled, once this ships?
We have not built that mechanism yet, so we are not going to describe one that does not exist. What we can say honestly: it would draw from the SAME agenda, the SAME policies, and the SAME adopted minutes your board already keeps in the meeting workspace and the policy manual -- not a second, separate copy of any of it, and not a generator that does not exist yet.
Can I sign up to be notified when packets ship?
Yes -- join the waitlist and we will reach out. There is no live posting, no beta build, and no committed ship date today.
Does a packet include any student information?
No. A board packet, once built, would carry the same adult public-official governance content the policy manual and meeting workspace already carry -- an agenda, policies, motions, and named board-member votes. It would never carry a student record.
Is this the same as the public sunshine-law page?
No. The public sunshine-law page reads your board's adopted meetings once your board adopts them -- that is a separate, already-built surface. A packet, once built, would be an internal assembly of the same kinds of material -- agenda, policies, minutes -- as one document for board members to prepare from, not a public page.