The problem: meetings that evaporate
Every organization runs the same loop: a sharp steering call, clear decisions, assigned owners — and forty-eight hours later nobody can find the record. Notes live in a personal doc, a chat thread, or a slide labeled FINAL_v4. New joiners re-ask questions that were already settled. AI assistants guess because the authoritative text never entered the project system.
Auto meeting minutes sound like magic transcription. The harder problem is durable publication: turning discussion into structured decisions, action items, and wiki pages your team — and grounded AI — can retrieve later.
Why copy-paste summaries fail
Typical failure modes:
Stale or incomplete capture — Someone types from memory; blockers and nuance drop off.
No single source of truth — Three versions circulate; tasks get created without the why.
Search dead ends — Drive folders and chat pins do not connect to Kanban, approvals, or finance.
AI without grounding — Pasting a transcript into a generic chat produces fluent prose with invented action owners.
Minutes need a workflow, not just a recorder.
Framework: capture → structure → approve → publish
Think in four layers before opening any tool:
1. Capture — Agenda, attendees, context. Raw notes or transcript as input — not the final artifact.
2. Structure — Separate decisions, open questions, action items (owner + due hint), and references to prior wiki pages.
3. Approve — Facilitator confirms decisions are stated clearly; sensitive items redacted or restricted.
4. Publish — Promote the approved summary to project wiki so search_docs, permissions, and task links work.
AI belongs in layers 1–2 (drafting, formatting, linking suggestions). Humans own layer 3. The system owns layer 4.
| Section | What good looks like |
|---|---|
| Context & goal | Why we met; success criteria |
| Decisions | Explicit choices — not "we'll look into it" |
| Action items | Owner, due hint, task link when created |
| Open questions | Named owner for follow-up |
| References | Prior wiki, release, or finance entries |
Where WKFGo fits: meetings → publish_meeting_wiki
WKFGo supports structured meetings with decision items, todos, and dependencies that can flow into tasks without retyping. When the meeting closes:
- Review draft — facilitator confirms accuracy
- Publish —
publish_meeting_wikicreates or updates a wiki page scoped to the project - Link tasks — action items tied to owners appear on the board
- Notify — stakeholders who missed the call find the page in search
For AI-assisted teams, assistants can draft from meeting structure or transcript, then invoke publish_meeting_wiki after human approval — automation with accountability, not silent edits.
MCP and chatbot paths
- MCP —
get_meeting,publish_meeting_wiki,search_docsfor cross-referencing prior decisions - In-app chatbot — answers "what did we decide about auth?" against wiki vector search after publish
- Permissions — same feature access as the web app; contractors do not see restricted leadership notes
Rituals that make auto-minutes stick
Rotate scribe — not always the PM; juniors learn context by writing decisions.
End recurring meetings with "publish or defer" — if it is not wiki-worthy, cancel the recurring invite.
Link wiki from tasks — when a task implements a meeting decision, reference the page in description.
Quarterly prune — archive superseded pages; mark reversed decisions in a new entry.
Getting started this week
Pick your next recurring meeting — sprint planning, steering, or retro. Assign a scribe rotation. Before the call ends, confirm which decisions are wiki-worthy. Draft minutes from the meeting object or transcript using chatbot or MCP. Facilitator reviews in five minutes. Publish with publish_meeting_wiki. Link one action item on the board back to the new wiki page. Repeat for three cycles; search adoption usually follows once people trust findability.
For MCP users, add a team prompt template: "Draft meeting summary from meeting ID X — decisions, action items with owners, open questions — do not publish until I approve." Keep publish as an explicit second step.
Anti-patterns
- Publishing raw transcript without decision extraction
- Letting AI publish without facilitator sign-off
- Minutes in email only — no wiki, no task links
- Over-automation on sensitive HR or legal topics
FAQ
Does WKFGo replace Zoom transcription?
No — capture can come from any source. WKFGo structures and publishes approved minutes to project wiki.
Can AI write the first draft?
Yes — via MCP or chatbot on meeting data; a human must approve before publish_meeting_wiki.
What about confidential leadership meetings?
Restrict wiki pages to admin roles or publish redacted public summaries with full notes in the document module.
Does publish overwrite prior wiki pages?
Typically creates a dated page or updates a designated meeting log — set team convention once.
Turn meetings into searchable knowledge
Stop re-deciding what you already decided in a Zoom room. Draft with AI; approve as a team; publish where delivery lives.
Try it now
Put these patterns on live project data—not slide decks.