How to Turn Meeting Notes into a Heptabase Knowledge Base
A Heptabase knowledge base built from meeting notes fails for one reason: the notes are written for the meeting, not for retrieval. Someone searches six months later for why a decision was made and finds three paragraphs about who was on the call.
Heptabase handles this better than a folder system, because you can separate the decision from the discussion physically. The format below keeps a board useful after 100 meetings.
What should one meeting note look like?
One card per decision, not one card per meeting. A 45-minute call usually produces two to four decisions and a pile of noise.
Card template that works:
- Title: a decision, phrased as a sentence. “Billing moves to Stripe in Q1” not “Billing sync 11/12”.
- Body: two sentences of context, one line of the owner, one line of the deadline.
- Source: the link to the full meeting notes, stored separately.
Heptabase cards are meant to be atomic. If a card needs sub-headings, it is holding too much.
How do you structure the board?
Three zones, arranged left to right.
- Inbox — new cards land here after every meeting. Nothing gets organised during the call.
- Projects — cards grouped by active workstream. Each group gets a Section with the project name.
- Decisions — a chronological column of decisions that cut across projects: pricing changes, hiring, tooling.
Once a week, spend 15 minutes moving inbox cards into their zones. That is the entire maintenance cost.
How do you connect decisions to projects?
Use links, not duplicate cards. If a pricing decision affects two projects, drop the card in Decisions and add a linked card reference in each project zone.
Duplicating creates two versions that drift. Linking keeps one source of truth and shows up visually when you hover the connection.
What does the AI chat add here?
Attach the Decisions column and ask questions that would otherwise take ten minutes of scrolling: “what did we decide about vendor X and when?” or “which projects are blocked on the design system?”
The chat answers from attached cards, so accuracy equals card quality. If your cards say “discussed pricing”, the answer is useless. If they say “moved Pro tier to $19, effective March 1, owner Dana”, it is precise.
What breaks this system?
Two things, both common.
Too many inbox cards. If you never do the weekly 15 minutes, the inbox becomes the folder system you were escaping. Set a recurring reminder.
Cards without owners. A decision card without a named owner is a discussion, not a decision. Skip those cards entirely; the full meeting notes still exist if someone needs them.
A third failure is board sprawl. If you have 15 whiteboards after six months, you have no system. Cap it at three: current quarter, archive, and one sandbox.
Who should not copy this setup?
Teams that need shared notes. Heptabase is a single-user tool, so this works for an individual building their own memory, not for a team wiki.
Anyone who never rereads notes. If you have never once searched for an old meeting, this is elaborate filing for nothing.
Quick Summary
- Write one card per decision, titled as a sentence, with owner and deadline on separate lines.
- Keep three board zones: Inbox, Projects, and a cross-cutting Decisions column.
- Spend 15 minutes a week moving inbox cards; that is the whole maintenance load.
- Link cards across zones instead of duplicating, so there is one source of truth.
- Cap yourself at three whiteboards total or the system stops being a system.
