Turn meeting notes into an action register

Meeting notes mix decisions, questions and suggestions. An action register should only assign work that the notes actually support.

Prepare the source material

Choose a document role and attach only the approved source material. Specify the audience, desired sections and output format before starting. A local task needs compatible document tooling; the sandbox includes document-generation libraries. Open the original DOCX in a document application to inspect page breaks, tables and headings, because an extracted text preview cannot establish layout quality.

Inputs for this workflow: notes.md with speaker labels and any approved decisions.

Work through the task

1. Separate decisions from proposals.
2. Extract explicit owners and due dates without filling gaps.

A brief you can adapt

Create actions.docx with Action, Owner, Due date and Source note columns. Use Unassigned and Not stated when details are absent. Add a separate open-questions section.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Trace each action to the source and confirm that a suggestion was not promoted into an agreed commitment.

Where this approach can fail

Do not infer an owner from who spoke most often.

For the related desktop setup, see review results.