Most meetings end with conversation, not closure. Everything got discussed, everyone agreed to "move forward" — and a week later the same meeting repeats, because nobody knew who was doing what or by when. Closure isn't a formality: it's the difference between a meeting that moves an indicator and one that just consumes an hour.
The three-minute ritual
Three minutes before the end — not after, when everyone is already closing their laptop — answer out loud:
- What did we decide? The decisions made, each said in one sentence.
- Who owns each next step? One person per step. "Everyone" is no one.
- By when? A concrete date, not "soon".
The rule is simple: if an item has no owner and no date, it's not closed — it's pending. And pending items get said out loud, not left implicit.
The 1:1 script
The 1:1 is the meeting where the most closure gets lost, because it feels informal. The script that saves it has four lines: blocker, next step, owner, date. What's stuck, what unblocks it, who does it, by when. It's the same script Clio hands the manager on Tuesdays — with the right person already identified.
The message afterwards
Closure lives or dies in the follow-up. A good closing message isn't meeting minutes: it's the decisions, the owners and the dates, in five lines. And it works better when it adapts to how the person receiving it works: if they need the full picture to move, open with the context; if they already have plenty of context, put the decision and the next step in the first line.
What to measure
Not how many meetings you had — how many ended closed. That share is the indicator's early signal: a team whose meetings close with an owner and a date executes what it talks about, and the KPI registers it weeks before any traditional dashboard shows it.
Where Clio fits
Clio prepares every 1:1 beforehand (agenda and script for that person) and captures it afterwards (the agreement with an owner and a date). And in the chat, it helps you draft the closing message according to how the person receiving it works.
In short
Three minutes at the end, a four-line script for the 1:1, and a closing message adapted to whoever receives it. What leaves a meeting with an owner and a date gets executed; the rest gets discussed again. Your KPI registers the difference.