Close a meeting with owners

The last five minutes are the minutes

A meeting is not closed when the conversation stops. It is closed when each open commitment has one owner, one observable result and a date that owner has agreed, and those three facts are in the record. Do that in the room, or on the call, while the people are still present. Writing it up the next morning is how owners become “the team”.

Use the meeting minutes tool for that record. Discussion notes hold context. Decisions made holds what was agreed, including conditions. Action items holds the commitments. The minutes guide explains how to keep those three apart. This guide is the last pass you run before anyone leaves.

The tool does not record audio, send mail or notify owners. You still have to say the owner’s name out loud and wait for a yes. Silence is not an owner. An absent person is not an owner unless they already agreed before the meeting, and you can say how.

Fictional meeting: Northstar launch check, 9 October 2026. Alex facilitates. Sam Lee and Jordan Taylor are present. Priya Shah was invited and is absent. The sandbox is still down. The point of the close is to leave with owners, not with a better argument.

What the action table can hold

Each action row is Action, Owner, Due date and Status. Status is one of Not started, In progress, Complete or Blocked. There is no ID column and no place for completion evidence. Those belong in the action tracker after the meeting. Do not try to squeeze an ID into the Action sentence and call that a system.

Action is a result someone can finish. “Look into the sandbox” fails because nobody can tell when it is done. “Restore sandbox access and send the six payment results to Alex” can be finished. Owner is one person. If two people must contribute, the row still names the person accountable for the result. Due date is a date the owner agreed. If the room did not agree a date, leave Due date empty. An invented date becomes a false commitment the next time someone pastes the row.

Decisions are not actions. “Keep the launch date provisional” is a decision. It does not need an owner in the action table unless someone must do a further thing. Put it in Decisions made, with the condition: until the six payment tests have passed.

Paste, if you bring rows in from the tracker, uses the order Action, Owner, Due date, Status. Do not paste the tracker’s ID or Completion evidence. Extra columns fail the whole batch. Dates are YYYY-MM-DD. Preview tells you whether empty starter rows will be replaced or your typed rows will be kept.

Run the close before people leave

1. Stop discussion a few minutes early. Say you are recording owners, not reopening the debate.
2. Read each decision once. Ask: is this agreed, conditional, or still open? Move open questions out of Decisions made. The minutes tool will store whatever you type; it will not detect a hedge.
3. For each commitment, ask who will do it. Type that person’s name in Owner while they are listening. If they correct the wording, change the Action cell before you move on.
4. Ask for the date. Type only a date they accept. Leave the cell empty when the answer is “sometime next week”.
5. Set Status to Not started for new work, In progress when it has already begun, or Blocked when a named dependency stops it. Do not set Complete in the meeting unless the result is already in hand.
6. Read the row back. One sentence, one name, one date or an honest blank. Then the next row. Stop at the work this meeting created. Do not import the whole backlog into the minutes.
7. Name the absentee. “Priya Shah, absent, no actions assigned” belongs in Attendees or Discussion notes. Do not give Priya an action she has not heard.
8. On Review & export, download Word or Excel if the record must leave this browser, or save a JSON backup. Print / save PDF uses the browser dialog. Ask owners to check their rows before you circulate the file on your normal channel.

After the meeting, copy durable rows into the action tracker and give them a stable ID plus an empty evidence cell. Complete the tracker row only when the evidence exists. Then, if the minutes still show the action, set Status to Complete there too.

Fictional Northstar close

Sam’s row later becomes tracker ID A-04 with the same meaning and a blank evidence cell. Jordan’s row becomes A-05. When the results exist, evidence is written in the tracker first. The minutes file from 9 October can stay as the record of what was agreed that day; you do not rewrite history to look tidy.

If the same blocker is still open at the next meeting, paste the four columns back. Do not mint a new action that hides how long the sandbox has been down. The draft and paste guide shows the preview text to read before you add rows.

Common mistakes, and the correction

The tool will accept a vague action and a guessed date. The close is a habit you run yourself. Use the four columns as the checklist, not as a guarantee.

What the close will not do

• It will not chase owners when a date passes, and it will not read a calendar.
• It will not prove attendance. A name in Attendees is a name you typed.
• It will not turn a decision into an approval under your organisation’s process. Record sign-off where that process requires it.
• It will not store more than one browser draft of the minutes, and it will not recover that draft after site data is cleared.
• It will not hold more than 50 action rows, 2,000 characters in a main field, or 600 in a cell. Bring the backlog in the tracker, not in this table.
• It will not copy rows into the tracker for you. The blank workbook is a separate file.

Fictional close: Alex reads two actions back, Sam and Jordan each say yes, and Priya is recorded as absent. The file is exported before the call ends. Nobody needs a follow-up meeting to discover who owned the sandbox. If the next conversation is a daily standup, keep it short with standup minutes that travel, and do not reopen every decision.