Overview
On a visit to a client in Western Maryland, I learned that their board document platform, BoardDocs, had been acquired by another vendor. That acquisition gave Allegany County Public Schools something districts rarely get: a genuine opening to look at what else was out there.
They looked. What they found was dated, awkward to use, and built around someone else's idea of how a board meeting works. So instead of forcing the district into another platform's shape, we built one around theirs. Agenda Beacon now runs their public meeting record at agendabeacon.com/org/acps.
The problem
Board software is unusual: it has to serve two audiences at once, with a legal line between them. The options the district evaluated struggled on both sides of that line.
- Interfaces that looked and behaved like software from a decade ago.
- Workflows that fought the clerk instead of helping — steps in the wrong order, fields nobody used, nothing that matched how the packet actually gets assembled.
- No clean, trustworthy split between what the public sees and what the board sees, which is exactly where mistakes become public records problems.
- Pricing built for a captive market: districts commonly pay in the neighborhood of $10,000 a year for a legacy platform.
“Give the public what the public should see. Give the board the whole packet. Don’t make it complicated.”
The approach
I sat with the executive assistant to the superintendent — the person who builds every agenda, assembles every packet, and publishes every set of minutes — and mapped the real cycle end to end: draft the agenda, attach the material, distribute the packet, run the meeting, record the votes, produce the minutes, keep the archive searchable.
Start from the clerk's day, not a feature list
Every screen exists because a step in that cycle needed it. Nothing was added because a competitor had it.
One system, two audiences
The public portal and the board workspace are the same data with a visibility line down the middle, not two products to keep in sync.
Build in days with AI, decide like an engineer
AI-assisted development compressed the build loop so the district reviewed working software instead of mockups — while architecture, permissions, and the audit trail got real engineering attention.
Bring the history along
Years of prior agendas and minutes were imported so the archive didn't restart at day one.
What the public sees
Each organization gets an outward-facing portal at its own address. It is the transparency face of the board, and it is readable by a parent on a phone.
Meetings, organized the way people look for them
Upcoming, recent, and an archive broken out by calendar year, filterable by year and by board.
Public agendas and approved minutes
The agenda as the board will run it, plus minutes once the board has approved them — never before.
Board roster
Members in the order the board expects, with optional photos, biographies, and contact details.
Policy library and full-text search
A searchable policy shelf and search across everything published to the public side.
What the public can never see: internal board-only notes, anything not marked public, draft minutes, and the administrative screens. Visibility is layered — organization, then board, then meeting, then each item, document, and set of minutes.
What board members and staff get
Behind the sign-in is the working half of the product: the board workspace, where the packet gets built and the record gets kept.
Structured agendas
Numbered sections with lettered items that renumber themselves when you reorder. No hand-numbering, ever.
Item types that mean something
Information, discussion, procedural, action, action-vote, and consent — with vote requirements set automatically from the type.
Responsible person and titles
Pick from the directory or type a guest presenter; titles can be appended automatically on printed agendas.
Board-only notes and attachments
Internal context stays internal. Non-public files are served through short-lived secure links and every download is logged.
Agenda templates
The standing skeleton — call to order, roll call, consent, new business — saved once and reused every meeting.
Imported history
Past meetings from the previous system are filed on their original dates and flagged as imported, so the archive is complete.
Printed and downloaded agendas carry the district's letterhead, and admins control exactly which organization details appear on them.
Running the meeting
Authoring an agenda and running a meeting are deliberately separate modes. On meeting day, the moderator opens Run Meeting and walks the agenda one item at a time.
Motions with mover and second
Open a vote on any item that requires one; motion text defaults to the item subject and is editable in the moment.
Roll call from any device
Members tap their own yea, nay, or abstain — or the clerk records votes on their behalf for a voice vote.
Outcomes the way boards actually close
Passed, failed, tabled, or withdrawn, with bulk all-yea and all-nay shortcuts and per-member adjustment.
Corrections with an audit trail
Votes can be reopened and mistakes fixed. Every change is written to the motion audit log — nothing is silently overwritten.
Once the meeting is complete, results become read-only vote cards showing exactly how each member voted.
Minutes
Minutes are where clerks lose their evenings. Agenda Beacon records audio in the browser or accepts an uploaded file, transcribes it, and drafts minutes aligned to the agenda structure and the attendance record.
- Audio captured in the browser during the meeting, or uploaded afterward.
- An AI-assisted first draft mapped to your sections and items, using attendance to resolve who spoke.
- A human edits and the board approves — the draft is never treated as the official record.
- Draft minutes stay internal until approved, then publish to the public portal with one visibility toggle.
Access and security
Public bodies get held to their records. The access model was built for that from the start rather than bolted on.
- Invitation only. There is no public sign-up form; administrators invite people with single-use links tied to their email address.
- Two-factor is mandatory. Every account enrolls an authenticator app. It cannot be skipped.
- Four roles. Administrator, board member, moderator/secretary, and staff — changed at any time, effective immediately.
- Sign-in activity and lockouts. Administrators review successful and failed attempts; accounts lock automatically after repeated failures.
- Layered visibility. Organization, then board, then meeting, then item and document. Private-organization mode closes the public portal entirely for company and nonprofit boards.
- Preserved history. Removing someone revokes access immediately but keeps their votes, motions, and attendance in the record.
Cost
Agenda Beacon is $995 a year per organization. Districts commonly pay around $10,000 a year for a legacy board document platform like BoardDocs — for less capability and a worse day-to-day experience.
$995 a year
One organization, the full product: public portal, board workspace, voting, minutes, and archive.
~$10,000 a year
Roughly what a comparable legacy platform costs a district annually.
Call or text a real person
Need something changed? You reach us directly — not a ticket queue, and not a vendor who stopped answering after onboarding.
Current pricing lives on agendabeacon.com/pricing.
What this means for your organization
Agenda Beacon started as one district's problem and became a product. That path is available to more organizations than most people assume: if your process is well-understood by the people doing it, purpose-built software is no longer a five-figure gamble.
- Boards, councils, authorities, and committees still running the meeting cycle on email attachments and PDFs.
- Any process where the public and an internal group need the same system with different views of it.
- Replacing an aging vendor platform that your team works around instead of works with.
- Turning a workflow you understand deeply into software other organizations would pay for.