Key takeaways
- →Protect the last ten minutes on the agenda before you protect anything else - the close is the part that determines whether the previous two hours mattered.
- →A decision without a named person and a date is a topic, not a decision, and it will not survive the week.
- →Read decisions back and ask for objection, not agreement; silence after 'any objections?' is worth more than nods after 'everyone happy?'.
- →The final two minutes are disproportionately remembered, so end on something concrete rather than an apology for overrunning.
- →Send the recap within an hour while the language is still the room's own, not a tidied-up version nobody recognises.
- →Capture what is still unresolved as explicitly as what was decided - naming the open loop stops it being relitigated from scratch.
To close a session so the decisions stick you need ten protected minutes, a decision list read back out loud with a name and a date against each line, and a recap sent while people can still remember the conversation. That is the whole method. The difficulty is not knowing it - it is defending those ten minutes when the discussion is still live at minute fifty.
The failure is almost always the same shape. The session runs hot, the good argument happens in the last quarter, someone says 'we're at time, I'll write this up', and everyone leaves with a slightly different version of what was agreed. Two weeks later the same discussion starts again, and nobody can point to what was decided or who was meant to do anything about it.
This guide covers the ten-minute closing sequence, how to capture a decision so it survives, the closing activities worth running and the ones that waste the room's last good attention, what belongs in a recap, and how to close a session that did not reach a decision at all.
Why the close is where sessions are won or lost
People do not remember sessions evenly. What survives is roughly the most intense moment and the ending, which is why a session that was useful for ninety minutes and then dribbled out over a chaotic finish gets remembered as a session that went nowhere. The peak-end rule is not a facilitation trick; it is a constraint on what you can expect people to carry out of the room.
There is a second, more practical reason. Everything the group produced - the sorted list, the votes, the argument that changed two minds - exists in short-term shared memory and on a screen that is about to be closed. If it is not converted into something written, owned and dated in the last few minutes, it decays quickly and unevenly. Individuals will each retain a different subset, and each will believe theirs is the record.
The close is also the only moment where you have the whole group's attention and the full context at the same time. Chasing an owner by email on Thursday costs three messages and gets a soft yes. Asking 'who owns this?' in the room, out loud, with everyone listening, costs eight seconds and produces a commitment other people heard.
The ten-minute close
Ten minutes sounds generous until you run it. Reading five decisions back with owners and dates genuinely takes six or seven minutes with a group of twelve, because two of them will turn out to need a clarifying sentence and one will turn out not to be agreed at all. That discovery is the point - finding it in the room is cheap, finding it a fortnight later is not.
Call time on the discussion (T-10)
Say it flatly: 'We have ten minutes and I want to spend them landing this rather than continuing it.' Do this even mid-sentence. Facilitators who wait for a natural break never get one.
Read the decisions back (T-9 to T-6)
Say each decision aloud in one sentence. Not a summary of the discussion - the decision. Three to five is a good session; more than seven and something on the list is not really decided.
Assign owner and date (T-6 to T-3)
For each line, ask 'who' and 'by when' and wait for a person to say their own name. Do not assign in absentia and do not accept 'the team'. If nobody volunteers, the decision is not real yet - say so.
Ask for objections, not agreement (T-3 to T-2)
'Anything on this list you think is wrong?' surfaces dissent that 'is everyone happy?' buries. Wait a full ten seconds. The person who speaks here saves you a fortnight.
Name what is still open (T-2 to T-1)
List the unresolved items explicitly and say when they get picked up. An open loop that has been named is parked; an unnamed one gets relitigated from the beginning.
End on the artefact (T-1 to T-0)
Point at what the room produced, say when the recap arrives, and stop. No apology for the overrun, no thanking people for their time twice, no drift into logistics.
What a decision has to contain to survive
A durable decision has four parts: what was decided, who owns the next step, when it happens by, and what it means the group is no longer doing. That last one is the part everyone drops, and it is why decisions quietly reverse. 'We are prioritising onboarding this quarter' is much weaker than 'we are prioritising onboarding this quarter, which means the reporting rebuild slips to Q4'.
Write it in the room's own words, not in tidy corporate paraphrase. If the group spent forty minutes saying 'the signup wall', do not write 'the registration friction workstream' in the recap. People recognise their own language and skim past someone else's, and a recap that sounds like it was written by a stranger gets filed unread.
Distinguish decisions from actions from topics. A decision closes a question. An action is a thing one named person does. A topic is something that came up and is not either of those. Keeping the three visually separate in your capture stops the list bloating to twenty items, of which four matter.
The numbers to hold yourself to
These are working guidelines rather than research findings - they are the thresholds that hold up across most session types, and they are worth treating as constraints because each one has an obvious failure on the other side. The three that matter most are the protected window, one named owner, and the send deadline; the decision count is a diagnostic rather than a target.
The single-owner rule causes the most argument and is the most useful. Two names against one action feels collaborative and reads, three weeks later, as each person assuming the other had it. If the work genuinely needs two people, name one as the owner and the other in the description of the action.
Closing activities worth the last five minutes
Pick one. Two closing activities is one too many, and running a reflection exercise and a rating and a commitment round turns the close into its own agenda item. If you are running any of these in Session Flo, keep them on the same room code people have been using all session - a fresh join at minute fifty-five loses a third of the room.
Confidence check on the decisions
A single 1-5 poll: 'How confident are you that we will actually do this?' A room that just agreed something unanimously but scores 2.4 on confidence has told you something important, and it takes forty seconds to find out. Run it anonymously or the number will be a 4.
One-word close
Everyone types one word describing how they are leaving. It takes ninety seconds, gives you a temperature reading to compare against the opening word cloud, and ends the session on the group's voice rather than yours. Best for workshops of an hour or more.
Commitment round
Each person states one thing they will do before the next session. In groups under ten this works verbally; above ten, have everyone type it and show the list. Public commitment is materially stickier than a private intention, and the list doubles as the start of the next agenda.
What would stop this happening?
Two minutes on obstacles, collected as open text rather than discussed. This is a miniature pre-mortem and it surfaces the dependency nobody mentioned while the decision was being made. You are collecting, not solving - say so, or it reopens the discussion.
The one-question session rating
A single question - 'was this a good use of your time?' - collected anonymously at the end. It costs the room fifteen seconds and gives you a trend line across sessions that is far more useful than a long feedback form nobody completes.
The recap that actually gets read
The recap is not admin, it is the artefact the session existed to produce. Session Flo builds a recap from what the room actually generated - the poll splits, the word clouds, the ranked lists - so the send is a couple of minutes of editing rather than an hour of reconstruction on Monday morning. That timing difference is most of the reason recaps do or do not get sent at all.
Top Tips
- Lead with decisions, not attendance. The first thing on screen should be the three to five things that were decided, in the room's own words. Nobody needs a chronology of the discussion.
- Put owner and date on the same line as the action. A separate 'actions' table at the bottom gets scrolled past on a phone; inline attribution does not.
- Include the raw output, not just your summary. The ranked list, the poll split, the words people typed - people trust a recap more when they can see the evidence behind the conclusions.
- Say explicitly what was not decided and when it will be. This is the single highest-value paragraph in most recaps and the one most often omitted.
- Send it within the hour. A recap that arrives on Thursday is an archive; one that arrives before people have finished their next meeting is a working document that can still be corrected.
- Keep it to one screen where you can. If the recap needs scrolling twice on a phone, the decisions are competing with detail that belongs in a linked document.
A decision with no name against it is a topic. A decision with a name but no date is a hope. Both will be back on next month's agenda.
How to close a session that did not decide anything
Sometimes the honest answer is that the group did not get there. Closing that session by pretending otherwise - inventing a soft consensus so the meeting has an ending - is worse than closing it openly, because the false agreement will be quietly ignored and you will have burned the group's trust in what your decision lists mean.
Close it like this instead. Name what the disagreement actually is, in one sentence, as neutrally as you can manage: 'We are split on whether this is a pricing problem or a positioning problem, and we did not resolve it.' Then state what would settle it - a piece of data, a customer conversation, one person's call - and who is getting that by when. That converts a failed session into a defined next step, which is a legitimate outcome.
Watch for the opposite failure too. A room that agrees quickly and unanimously to something nobody is enthusiastic about is a familiar pattern, and it is worth one direct question at the close: 'Is anyone agreeing to this because it seems easier than arguing?' Asked lightly, at the end, it occasionally saves a quarter.
Closing a hybrid or large session
The underlying rule for both hybrid and large rooms is that the close must be readable, not just audible. Everything you say in the last ten minutes should also exist as text on a shared screen, because that is what remote attendees, latecomers and the person who lost connection at minute forty will rely on.
Confirm on screen, not in the air
In a hybrid room, read decisions aloud but also show them written. Remote attendees cannot ask for a repeat as cheaply as people in the room can, and a mis-heard decision becomes a mis-remembered one.
Take objections through the device
'Any objections?' asked into a hybrid room collects objections only from the loudest space. A ten-second anonymous yes/no on the decision list collects them from everyone.
At 100-plus, do not do a round
Verbal commitment rounds break above roughly ten people. Collect commitments as text simultaneously and display the aggregate - it takes ninety seconds regardless of whether there are 30 people or 300.
Name owners before the last five minutes
In large sessions, owners are usually a small subset of attendees. Line them up during the session so the close is confirmation rather than recruitment.
End early rather than exactly on time
Finishing two minutes early is remembered as control. Finishing four minutes late, with the last item rushed, is remembered as the whole session being disorganised.
Make the close a habit the group expects
The first time you cut a live discussion at T-10 it will feel abrupt and one person will be irritated. The fourth time, the group starts self-regulating - someone else will say 'we should land this, we're near time'. That transfer is the goal, and it happens surprisingly fast when the close reliably produces something people can point at afterwards.
Reinforce it by opening the next session with the previous close. Thirty seconds of 'here is what we decided last time and where each of those got to' does two things: it proves the recap was not theatre, and it makes people take the closing commitments more seriously the second time, because they now know they will be read back.
If you change one thing about how you run sessions, make it this: put the ten minutes in the plan before you plan the content, and treat them as non-negotiable in the way you already treat the finish time. Almost every other improvement to a session compounds through the close, and without it, most of them evaporate by Wednesday.
Frequently asked questions
How long should it take to close a session?
Ten minutes for a session of an hour or more, five for a half-hour meeting, and fifteen for a full-day workshop where there is more to reconcile. Block it at the planning stage rather than hoping the discussion finishes early, because it never does. If ten minutes feels impossible, the content is over-scoped: cutting one agenda item to protect the close will produce more actual output than fitting everything in and landing none of it.
What should be in a session recap?
Decisions first, each with a named owner and a date, written in the words the room used. Then the raw output the group produced - the poll splits, the ranked list, the words people typed - so people can see the evidence rather than only your interpretation. Then an explicit list of what was not decided and when it gets picked up. Attendance, agenda and a narrative of the discussion are optional and usually noise.
Who should own the follow-up after a session?
One named individual per action, stated by that person in the room rather than assigned to them in their absence. Shared ownership between two people is the most common way an action dies, because each assumes the other is moving. If the work genuinely requires two people, name one as the owner and mention the second in the action description so the accountability stays singular while the collaboration stays visible.
How do I stop the discussion running into the closing time?
Announce the cut before it happens rather than at the moment of it - 'ten minutes left and I am going to stop the discussion at five to land this' - so the interruption is expected. Then do it even if the conversation is good. If the point being made matters, capture it as a named open loop; that respects the contribution without letting it consume the close. Doing this consistently is what trains a group to land things themselves.
Should the closing activity be anonymous?
Confidence checks and session ratings should be anonymous, because a named low score is a social act most people will not perform in front of their manager. Commitments should be named, because the visibility is the mechanism - a public commitment is stickier than a private one. So a good close often mixes both: an anonymous confidence poll on the decisions, then a named round of who is doing what by when.
What do I do when a session ends without a decision?
Close it honestly. Name the disagreement in one neutral sentence, state what would settle it - specific data, a particular conversation, or one person's call - and name who is getting that and by when. That is a legitimate outcome and a defined next step. Manufacturing a soft consensus so the meeting has a tidy ending produces an agreement nobody acts on and quietly devalues every decision list you produce afterwards.
Keep reading
- why the ending disproportionately shapes the memory — The research behind protecting the last few minutes.
- turning workshop output into decisions — What to do with a wall of sticky notes once the session ends.
- building a session recap people read — Format and timing for the follow-up document.
- opening a workshop in the first five minutes — The other end of the loop - the words you bring back at the close.
- see how Session Flo builds the recap for you — Automatic recaps from the activities the room already ran.