End the meeting with a read-back

End the meeting with a read-back: say the decisions, commitments, owners, dates and unresolved points aloud, then let the room correct them before anyone leaves.

This is not a performance of the minutes. It is a final accuracy check. A conversation can feel aligned while three participants leave with three different versions of what “we will move ahead” means. The disagreement appears later, when the work has already diverged.

Reserve the final minutes before the discussion begins

A read-back fails when it is treated as optional work after the scheduled end. People have already closed laptops, joined another call or started moving toward the door.

Put the close in the agenda. For a 45-minute meeting, stop the main discussion at minute 42. The facilitator should warn the room when the final decision point is approaching, then protect the remaining time.

If the discussion runs long, do not borrow from the read-back. Narrow the decision or record a deliberate return point. A meeting that uses every second for discussion and none for confirming the outcome has optimised the least durable part of the work.

This is the in-room companion to the twenty minutes after the meeting. The read-back makes the raw outcome accurate; the work afterwards turns it into a useful record.

Read back outcomes, not the conversation

Do not summarise every argument. Read only the items that must survive the room:

1. Decisions: what the team will do, including the option chosen.
2. Commitments: the specific result someone agreed to produce.
3. Owners and dates: one accountable person and a real due date for each commitment.
4. Open points: questions that remain unresolved, plus who will move each one forward.
5. Changed assumptions: a fact or constraint that materially shaped the outcome.

A useful read-back sounds like this:

We chose the smaller pilot with the support team included. Leon owns the revised rollout plan by Tuesday. Priya will confirm the support capacity by Monday afternoon. The pricing question is still open; Mira will bring two options to Thursday's product review.

That is short enough to hear and precise enough to challenge. “We agreed to move ahead and follow up on the details” is neither.

Ask for confirmation item by item

“Any questions?” is a weak close. Silence may mean agreement, distraction, reluctance to slow the room down or simple uncertainty about what needs confirmation.

Direct the check to the people named in the outcome:

• “Leon, is that the result you are taking on?”
• “Priya, is Monday afternoon a date you can accept?”
• “Mira, do you own the open pricing question?”
• “Decision owner, is this the decision you are making?”

Confirmation is not ceremony. An owner may reveal that they heard “draft” where everyone else heard “final,” or that the date depends on input nobody has assigned. Fixing that sentence now is cheaper than correcting a missed handoff next week.

Do not assign work to someone who is absent and call the read-back complete. Use an explicit proposed handoff instead; an absent colleague must accept the action item before it becomes theirs.

Distinguish a decision from an intention

Read-backs often expose that a confident sentence was not actually a decision.

“We should launch the pilot next month” may be:

• a decision to launch;
• a recommendation awaiting approval;
• a preference subject to one missing estimate;
• an idea the room liked but nobody owns.

Name the state accurately. If authority is missing, record the recommendation and the person who will seek approval. If evidence is missing, record the open question, its owner and the point when it returns. A meeting with no decision still needs a record, but the record must not manufacture closure.

The same test applies to action language. “Marketing to look at the announcement” does not identify a person, result or date. The read-back should turn it into an explicit commitment or remove it from the action list.

Correct the record in the room

When someone challenges the read-back, pause and edit the wording. Do not debate from memory after the call if the people who can resolve it are still present.

There are three common corrections:

• scope: “I agreed to draft the outline, not the final plan”;
• ownership: “I can advise, but Leon is accountable for the release”;
• timing: “Tuesday depends on receiving the estimate by Monday.”

Say the revised item again after changing it. This prevents the correction itself from producing two interpretations.

Material disagreement may need more than a wording fix. If a participant believes the stated decision was never made, the decision owner must either make the call clearly or mark it unresolved. If the outcome is correct but a serious objection remains, record the disagreement without reopening the decision.

Send the same words the room confirmed

The written record should begin with the read-back, not a fresh interpretation written hours later. Clean the language, attach necessary context and separate decisions from tasks, but do not silently change the substance.

In Scripta, you can bring notes or a transcript into the meeting workspace, review proposed decisions and action items, edit them, and finalise the minutes. The human check still matters: generated structure cannot know that “Tuesday” was conditional unless the source makes the condition clear and someone verifies it.

If later review finds a factual error, use a bounded correction process rather than overwriting history. The guidance on correcting meeting minutes before they become the record explains that distinction.

Use a five-line closing script

The facilitator can keep the habit simple:

Decision: What exactly did we choose?

Actions: What result will each person produce?

Dates: When is each result due?

Open: What remains unresolved, and who moves it?

Confirm: Does each named owner accept this wording?

The purpose is not to make every meeting sound formal. It is to make ambiguity visible while the people who can resolve it are still together. A good meeting close gives the room one shared starting point for the work that follows.