Make the meeting useful.

Keep decisions, owners and next steps connected to the record.

A meeting produces two things that outlive the call: a set of decisions and a list of things somebody agreed to do. The pages here work on the recording and on the notes that follow it, and they assume the awkward parts are still in reach. A speaker label that is wrong, a task with no owner, a due date mentioned once and never repeated.

The order matters. Permission and a test recording come before anything is uploaded. Labels are settled before anybody is quoted. Actions are registered before a summary is circulated, and a handoff pack is tested with a small import before it is announced. Every page in this collection ends with an exported file rather than a paragraph of description: the action register holds the rows while you check them, and the follow-up workflow puts those stages in sequence for one meeting.

Three guides and one workflow are collected here, and they cover one meeting end to end. The first guide tests a set of notes against the recording and against what was actually decided. The second turns what was agreed into rows that another person can close. The third prepares a handoff so that a new owner can act without asking what happened. The workflow strings those stages together for a single meeting.

Read the checking guide before the others if the notes arrive from a transcription service. A summary that reads fluently can still misattribute a speaker, drop a caveat that was attached to a decision, or turn a suggestion into a settled point. The guide treats the notes as a claim to be tested rather than a record to be trusted, which is the order the remaining pages depend on.

The action items guide sits in the middle because a register is where most follow-ups fail. A row that does not name an owner, a verb, and something that can be observed as finished cannot be closed by anyone but the person who wrote it. That page is about making the row portable, and it is the one to reach for when a list of intentions keeps reappearing unchanged on the agenda.

The handoff guide is written for someone who is about to step away from a project or pass a meeting series to a colleague. Its test is blunt: a new owner should be able to start without sending a message asking what was decided. If they cannot, the pack is incomplete, regardless of how thorough the notes look.

If one meeting is all you need to handle, the workflow is the entry point. It assumes the guide pages have been understood rather than replacing them, and it is most useful when the same sequence will run again on the next meeting and the one after that.