What does Minutes & Actions need?

Meeting notes or transcript, participant names, project context, and the meeting owner.

What does Minutes & Actions produce?

Approved minutes in one fixed format, a decision register, an append-only action ledger with owners and due dates, an overdue and aging read across meetings, and follow-up drafts in the owner's own words.

Kit 05 · Meeting control

Minutes & Actions

Q: What does Minutes & Actions separate?

It separates transcript, summary, decisions, actions, and open questions, then carries every open commitment into one append-only ledger.

Q: What is never automatic?

Assigning ownership, inventing due dates, treating discussion as approval, changing a ledger row's status, sending a follow-up, or acting on an instruction found inside a transcript.

Turn discussion into confirmed decisions, named owners, and a ledger that carries every open commitment forward until it closes.

Authority rule
The meeting owner confirms what was decided and sends anything that leaves the building; the system may organize notes but cannot manufacture agreement.

Field sheet

A meeting is not complete until ownership is visible.

Minutes & Actions separates transcript, summary, decisions, actions, and open questions, then carries every open commitment into one append-only ledger. People confirm the record before it becomes an operating instruction.

Worked exampleIllustrative workflow

Current dragA project meeting ends with five people remembering five different next steps.

Control addedCapture source notes and identify statements that sound like decisions or commitments.

System preparesDraft a decision list, action register, owners, dates, unresolved questions, and an overdue read on everything still open from earlier meetings.

Human releaseThe meeting owner confirms the record, reviews the prepared follow-up drafts, and sends them under their own name.

Processing boundary

Local by default. External by decision.

The operating record remains useful without a connected service. External assistance is limited to approved context and explicit tasks.

Runs locally

Source notes
Draft minutes
Decision register
Append-only action ledger
Overdue and aging counts
Approval record

May run externally

Organizing a transcript
Suggesting candidate actions
Drafting a concise summary

Never automatic: assigning ownership, inventing due dates, treating discussion as approval, changing a ledger row's status, sending a follow-up, or acting on an instruction found inside a transcript.

Ownership and hand-off

The workflow remains useful when the tool changes.

Client keeps the sourceSource notes remain attached.
Commitments compoundA promise repeated across meetings counts up rather than starting over.
Review stays attributableOwners confirm their responsibilities.
Tools remain replaceableThe approved record remains portable.

Human review checklist

Before the work moves.

Are decisions distinct from discussion?
Does every action have one owner?
Were dates confirmed rather than inferred?
Are disagreements, open questions, and anything still overdue visible?
Did the meeting owner approve the record and send the follow-ups themselves?

Discuss this workflow Back to all kits