01 · Compliance
Understanding the Open Meetings Act
Every U.S. state has a law requiring public bodies to do their business in public — Open Meetings Act in most states, Sunshine Law in others. The shape of the rule is similar everywhere: the public must be told where a meeting will happen, when it will happen, and what will be discussed, with enough notice that residents can plan to attend.
The notice clock varies by state. Most states require 24, 48, or 72 hours of advance notice for a regular meeting. A few outliers:
- Michigan — 18 hours (MCL §15.265). Posted publicly at the principal office of the public body.
- California — 72 hours for the Brown Act (Cal. Gov. Code §54954.2).
- Illinois — 48 hours for ordinary meetings (5 ILCS 120/2.02).
- Hawaii — 6 days (HRS §92-7).
For regular meetings, most states accept an annual schedule posted at the start of the year as satisfying notice for the whole year. Only special meetings require fresh per-meeting posting under the state's hour rule.
Emergency meeting exception — narrow. Almost every state's OMA carves out an exception for genuine emergencies (e.g. severe and imminent threats to public health, safety, or welfare). Notice must still be given as soon as reasonably possible. The exception is genuinely narrow — fiscal deadlines, contract pressures, and personnel issues typically don't qualify.
The penalty for getting this wrong isn't theoretical. In most states, decisions made at a meeting that violated OMA can be voided in court, and individual board members can be personally fined.
Citations vary by state. BoardVoice's Audit & Compliance dashboard grades every meeting against your state's specific rule with the statute number attached.
02 · Compliance
Public records & FOIA, in plain English
Every public board produces records — agendas, minutes, contracts, payroll, correspondence, calendars, emails. State public-records laws (often called FOIA, after the federal model) say residents have the right to ask for those records. Same idea everywhere; deadlines differ.
There are two clocks every clerk needs to track:
- Acknowledge — most states: 5 business days from receipt. The clerk has to tell the requester "yes, we got it" within that window, even if the actual records take longer to produce.
- Respond — most states: 15 business days. By then, the records have to be produced, denied with a written explanation, or the deadline has to be extended in writing.
The federal FOIA gives 20 business days; many state laws are tighter. Always operate to your state's deadline, not the federal one.
What makes a request valid. Most states require the request to:
- Be in writing (email counts in nearly every state).
- Identify the requester (name + contact).
- Describe the records with enough detail that the agency can find them — but it doesn't have to use exact filenames or be technically precise.
What can be withheld. Common exemptions across states: personnel records, attorney-client communications, security-sensitive infrastructure, records that would identify minors, draft documents not yet finalized. Specific exemptions vary — check your state's code.
Don't lose the request in email. The most common FOIA failure isn't denial — it's a request that disappeared in someone's inbox until the deadline already passed. A central queue with deadline tracking is the single biggest reduction in compliance risk.
03 · Workflow
The four-stage minutes workflow
Minutes aren't notes. They're the legal record of what a public body decided. Most state OMA statutes require minutes to be available for public inspection, often within a defined window after the meeting (Michigan: 8 business days for proposed minutes, 5 business days after the next meeting for approved minutes).
A clean minutes workflow has four stages — and an audit trail at each step:
- Draft. The clerk (or the secretary running the meeting) types up what happened. Motions made, who moved, who seconded, the tally, and any tabled items. This is a draft — not yet binding.
- Awaiting Approval. The draft is finalized and queued for the next meeting. Most boards include "Approval of Previous Minutes" as a standing agenda item.
- Board-Approved. The board votes to approve the minutes — usually with corrections noted in the new meeting's minutes. Once approved, they become the official record.
- Published. The approved minutes are posted publicly, typically with subscriber notification, and archived permanently as the legal record of the meeting.
The reason this matters: if a decision is ever challenged in court, the approved-and-published minutes are the evidence. If a clerk skipped the approval step or never published, the board's defense gets harder.
The most common breakdown is between Stage 2 and Stage 3. A clerk drafts the minutes, queues them, and then nobody actually moves to approve them at the next meeting — so the record stays in limbo. A workflow that surfaces "you have minutes awaiting approval" prevents that drift.
On BoardVoice today
When a clerk builds the next meeting's agenda, a one-click
📎 Attach prior minutes button on the "Approval of Previous Minutes" item pulls the last meeting's approved minutes onto the new agenda automatically — no cross-page lookup, no manual URL copying.
04 · Workflow
Two-click meeting scheduling
The thing that eats a clerk's day isn't writing minutes — it's building the next agenda. Every meeting of the same type uses the same skeleton (Call to Order, Roll Call, Approval of Minutes, Public Comment, Old Business, New Business, Adjournment) and the same handful of recurring sub-items. A clerk who rebuilds that from scratch every two weeks is doing the same setup work fifty times a year.
BoardVoice collapses the scheduling and agenda-drafting steps into the calendar itself:
- Click an empty date on the admin calendar.
- Pick the meeting type (Regular, Special, Workshop, etc.) and time. Hit "Schedule meeting."
- You land on the new meeting's agenda editor with every item from the last meeting of that same type already in place — exactly as you published it last time. Edit what's different, leave the rest.
For a township that runs a Regular Township Board meeting, a Planning Commission meeting, and a Board of Review meeting on three separate calendars, the system does the right thing automatically: each board's "copy previous" pulls from that board's most recent meeting of the matching type, not a mix.
The clerk-time math. A standard township board agenda runs 8–12 items with sub-items. Building from a blank form takes 10–15 minutes per meeting. With pre-fill from the last meeting, you're editing the 2–3 items that actually differ — about 60 seconds. Over a year of bi-weekly meetings that's roughly six full workdays back in the clerk's calendar.
On BoardVoice today
The same calendar that residents see at
/your-board/calendar is what clerks use to schedule. The public view is read-only and shows only published meetings; the admin view shows drafts too, has an "Add meeting" affordance on every empty cell, and surfaces the "Use previous agenda" picker on the meeting editor for one-off cases where you want to copy from a specific past meeting instead of the most recent.
05 · Governance
Multi-board organizations
Most public agencies don't operate just one board. A township typically runs:
- Township Board — the main elected body
- Planning & Zoning Commission — appointed, usually monthly
- Zoning Board of Appeals (ZBA) — appointed, meets as needed
- Board of Review — meets in March on assessment appeals
- Plus committees: Parks, Water & Sewer, Election Commission, etc.
A school district might run a main School Board, a Foundation board, a curriculum committee, a finance committee, and a facilities committee. Each is its own public body for OMA and FOIA purposes — separate agendas, separate minutes, separate vote records, separate notice rules.
The procurement question that follows: do we pay per board, per organization, or per "public body"? The honest answer is that the marginal cost of supporting another board on a software platform is essentially zero — a separate folder of meetings, a separate page on the public site, a separate roster. Pricing per board pretends otherwise to extract more revenue.
Operationally, what matters most is that each board can run autonomously — its own chair, its own agenda template, its own document library — while still rolling up to one organization-wide audit log and one transparency dashboard. Anything less and the clerk is operating four separate tools.
On BoardVoice today
Bringing existing records in is a one-step service: the
Migration Pack add-on (
$149 one-time) imports up to 5 years of past agendas, minutes, and packets as searchable public meeting records — bulk-uploaded, tagged by date and meeting type, run through Claude so a query like
"every motion mentioning the road millage" works on day one. Self-serve bulk upload is included free with every plan.
On BoardVoice:
Unlimited boards under one $190/year subscription. See pricing →
06 · Trust
What "audit-proof" actually means
"Transparent" is a word every meeting platform uses. "Audit-proof" is a higher bar. It means an outside auditor — a state association reviewer, a transparency journalist, an attorney representing a resident — can verify everything a board has done in one sitting, without filing a records request to do it.
Four guardrails get you there:
1. Per-meeting OMA grading
Every meeting on the calendar should be graded against the state's notice rule. "Posted at 2:14 PM the day before the 7:00 PM meeting — 28 hours, compliant under MCL §15.265." Or, if it wasn't: "Posted 12 hours before — late notice." The verdict, the timestamp, and the citation, all on one screen.
2. FOIA deadline tracking
Open requests show two clocks — acknowledged-by and respond-by — counting down in real time. A request that's been sitting for 12 business days isn't a forgotten email; it's a red number on the dashboard.
3. Tamper-evident activity log
Every meeting published, document uploaded, vote recorded, FOIA status change, and role assignment is appended to an immutable log — read-only after write, even for admins. If a future board chair tries to edit history, the audit trail catches it.
4. Minutes lifecycle hub
One page that shows every meeting bucketed by where its minutes live: drafts needed, awaiting board approval, ready to publish, or published. No meeting falls through the cracks because no clerk has to remember which ones still need work.
Together, these turn "trust the clerk" into "verify the system." That's the difference between transparent and audit-proof.
On BoardVoice today
Every published meeting — current or migrated from years past — lives on the org's public site, browsable by year via a dropdown filter at the top of the meetings list. No portal login, no records request. An auditor opens the page, picks the year, and the record is right there.
For the deeper audit dive, every meeting has a one-click
Export Record button on the admin side that downloads a complete JSON bundle — full agenda, every vote and outcome, every attachment URL, minutes, related public comments, and the audit log entries for that meeting. Re-runnable at any time, so the bundle reflects the meeting's current state.
07 · For Residents
Staying informed without an account
A public board's website only matters if residents can actually use it. Every BoardVoice board page ships with a set of resident-side tools — no signup, no app install, no waiting on the clerk — that meet people where their attention already lives.
Calendar subscriptions (iCal)
Every board has a live calendar feed at /<org>/<board>/calendar.ics. One tap on the Subscribe in your calendar button on the public Calendar page hands the feed off to Google Calendar, Apple Calendar, or Outlook — and from then on the resident's calendar stays in sync with whatever the clerk publishes. Cancelled meetings show as a strikethrough automatically.
RSS / Atom feeds for press and watchdogs
Each board publishes an Atom feed at /<org>/<board>/feed.xml with a separate entry for every agenda-published and every minutes-published event. Reporters, league-of-women-voters chapters, and accountability journalists can subscribe in Feedly / Inoreader / NetNewsWire and never miss a posting. Discovery links on every page mean modern feed readers find the feed automatically.
Email subscribers, with a choice of cadence
Residents who prefer email can subscribe with their name + address in 5 seconds. The default is one email per publication, but the signup form offers a weekly digest option that aggregates the whole week's agendas and minutes into one Monday morning summary. Either way, every subscriber gets an automatic 24-hour reminder the day before each meeting.
Full-text search of the historical record
Every published agenda item, motion, and secretary's notes block is indexed at /<org>/<board>/search. Residents can type any keyword — "zoning variance," "fund balance," a board member's name — and pull up every meeting where it came up. Match terms are highlighted in the snippet; each result links directly to the minutes.
Per-member voting record
Each board member's roster card links to a dedicated voting-record page that aggregates every roll-call vote they've cast: Yes / No / Abstain / Recuse counts, participation percentage, and a chronological detail table. Recusals carry the reason inline ("Jane Doe — conflict with applicant"), making conflict-of-interest disclosures visible without having to read every set of minutes.
Public action-items tracker
The /<org>/<board>/tracker page surfaces every commitment the board has made and where each one stands today: open, overdue, or completed. Residents can filter by status, search by description or assignee, and click through to the originating meeting. Promises made publicly are tracked publicly.
Closed-session record on the public minutes
When a board recesses into a closed (executive) session, BoardVoice keeps the deliberations confidential but publishes a Closed Session Record block at the bottom of the public minutes: the legal citation that authorized closing the session and a brief public summary of any action taken. Residents see exactly what was decided behind the closed door, even when the discussion itself is sealed by statute.
On BoardVoice: every public board page surfaces these tools by default — no admin work required after the board signs up.