Board Packet & Decision Memory

Agendas, decision logs, policies, and review reminders in one light system — so the board stops re-deciding the same thing every fourteen months.

Category	Governance
Church-health domain	Operations & Governance
Data-privacy tier	High — board minutes touch personnel, financial, and legal matters
Mastery-ladder target	Level 3 · Skills
Build stack	Airtable or Notion + built-in automations + Slack; quarterly AI-drafted brief (human-reviewed)

---

The problem

Boards genuinely lose their own history. Governance bodies acknowledge that "board members change and memories fade," and that written records are the institutional memory that endures across leadership changes — helping future boards "avoid reinventing the wheel." Minutes are also legal documents. The recurring failure mode is exactly that: a board re-deciding something it already settled, because nobody can find the prior decision or the reasoning behind it.

What good looks like

A structured Decisions table where every decision has a searchable rationale, an owner, a status, and a review-by date. The next agenda auto-generates from open items. New decisions post to a board Slack channel after each meeting. Fourteen days before any decision's review date, the owner gets an email. Quarterly, an AI drafts a one-page "what we've decided this quarter" brief — which a human reviews before it goes out.

Market scan

Tool	Fit	Pricing (verify)
Boardable	Meetings/agendas/minutes	~$20.99/user/mo Essentials; Pro $99/mo
BoardEffect / OnBoard / Govenda	Enterprise board portals	Quote-only; up to $50,000+/yr
Aplos	Nonprofit/church accounting (not decision memory)	~$79–189/mo
Notion / Airtable	General databases — build it yourself	Low double-digit $/mo

The gap: decision memory is predominantly a discipline-plus-light-tooling problem, not an engineering one. A relational base (Airtable/Notion) with built-in automations covers the mechanics; enterprise portals buy polish and access controls a mid-size church may not need. AI's role is deliberately narrow and low-risk: drafting the quarterly brief and the next agenda from open items — both human-reviewed, so hallucination exposure is minimal.

Data privacy & security

• High sensitivity. Board minutes routinely touch confidential personnel, financial, and legal matters and are legal records.
• Restrict the base to board members; keep executive-session material in a separate, tightly-permissioned table.
• Do not feed sensitive minutes into any AI feature whose data-handling terms you haven't vetted.
• Use SSO / least-privilege on the workspace and turn on audit logging.

How to build it

1. Build four linked tables — Meetings, Decisions, Policies, Owners — in Airtable or Notion.
2. On the Decisions table add fields: rationale, owner (link), status, review-by date.
3. Use the no-code automation builder: open items → generate next agenda into a Google Doc; new decision → post to Slack; 14 days before review-by → email the owner.
4. Quarterly, paste the quarter's decisions into a reviewed AI prompt for the brief.

Rollout plan

• Q1: Stand up the tables and start logging decisions with rationale + owner + review date. The discipline is most of the value.
• Q2: Add the agenda-generation and Slack automations.
• Q3: Add the review-date reminders and the quarterly AI brief.

Effort & cost

• Build: a weekend to a few evenings.
• Run: the Airtable/Notion plan + optional automation tier (low double-digit dollars/month) — versus thousands per year for a dedicated board portal.

Sources

• Best practices for board minutes — https://www.churchlawcenter.com/nonprofit/best-practices-for-keeping-board-minutes/
• Effective board meetings / governance — https://www.councilofnonprofits.org/running-nonprofit/governance-leadership/effective-board-meetings-good-governance
• Board management software pricing — https://www.imboard.ai/blog/board-management-software-pricing
• Aplos pricing — https://www.aplos.com/pricing