01 · Compliance
Understanding the Open Meetings Act
Every state has laws governing meetings of covered public bodies—often called an Open Meetings Act or Sunshine Law. Which bodies are covered, how much agenda detail is required, where and when notice must appear, and which exceptions apply vary by jurisdiction.
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).
Some laws distinguish an annual schedule for regular meetings from additional notice required for special, rescheduled, recessed, or emergency meetings. The distinctions and posting locations matter; configure BoardVoice to support the process your public body has verified.
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.
Consequences vary and may include court orders, invalidation proceedings, civil remedies, or other sanctions. Treat a timing flag as a prompt for review—not as a legal verdict.
BoardVoice can display a timing calculation and reference citation beside the record. It cannot evaluate every statutory exception, posting method, local rule, or factual circumstance.
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.
Start with the clock your own law creates. A useful request workflow records when a request was legally received, the initial response deadline, any permitted written extension, and the final disposition. Those events—and even the definition of “received”—vary by jurisdiction.
For example, Michigan generally requires a response within 5 business days and permits one written extension of not more than 10 business days under MCL §15.235. That example should not be applied to another state or to a body governed by a different rule.
What makes a request workable. Requirements vary by jurisdiction. A clear written request with reliable contact information and a reasonably specific description is usually easiest to track and fulfill. Verify whether your law permits oral or anonymous requests and what identifying information, if any, may be required.
What can be withheld. Exemptions are jurisdiction-specific and fact-specific. They may address privacy, privileged communications, security-sensitive information, or other protected material. Verify the governing statute and obtain counsel when needed rather than relying on a category name alone.
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 board-approved record, subject to any correction procedure required by applicable law or policy.
- Published. The approved minutes are posted publicly, typically with subscriber notification, and made available and retained according to the organization’s adopted records policy and legal duties.
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.
Less repetitive setup. Starting from a prior agenda means the clerk can focus on the items that changed instead of rebuilding the recurring structure.
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. A committee or related board may be a separate public body depending on how it was created, its authority, membership, and governing law. When separate treatment is required, BoardVoice can keep its agendas, minutes, vote records, and configured notice references scoped to that board.
BoardVoice can organize related public bodies under one organization while preserving separate board pages, schedules, rosters, and records. See the pricing page for the current plan structure.
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, processed and indexed for supported search after review. Self-serve bulk upload is included free with every plan.
On BoardVoice:
Unlimited boards under one $190/year subscription. See pricing →
06 · Trust
What "review-ready" actually means
Transparency is easier to demonstrate when meeting notices, agendas, votes, minutes, documents, and activity history remain connected. “Review-ready” is our shorthand for organizing that evidence—not a guarantee that a record is complete or legally compliant.
Four guardrails get you there:
1. Per-meeting OMA grading
Each meeting can show the posting timestamp beside a configured notice reference—for example, “Posted at 2:14 PM for a 7:00 PM meeting — 28 hours before start.” The clerk or reviewer determines what follow-up is required.
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. Append-only activity history
Administrative events can be appended to a history that ordinary client interfaces cannot rewrite or delete. It supports review and troubleshooting, but it should be used alongside adopted records policies and independent backups.
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. This helps the team see which records still need action without relying only on memory.
Together, these tools make routine review faster while keeping human judgment, records policy, and legal responsibility with the public body.
On BoardVoice today
Published meetings that the organization retains in BoardVoice live on the organization’s public site, browsable by year via a dropdown filter at the top of the meetings list. Public records are available without a portal login when the organization has published them. 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. BoardVoice board pages can provide resident-side tools without requiring a resident account or app installation. What appears depends on the organization’s configuration, published records, and enabled services.
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
Supported published meeting content 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 recorded statutory basis for entering closed session and any action lawfully taken after the body returns to open session. Confidential deliberations remain protected only to the extent permitted by applicable law.
On BoardVoice: authorized administrators choose which supported tools to enable and remain responsible for reviewing the records and settings made public.