Whoever Ran the Meeting Should Not Own Its Record

Published12 min read

An old rule said the person running a meeting should not be the one keeping its notes. Automatic capture retired the rule for the wrong reason and left the part that mattered untouched, which is who gets to author the record afterward.

The rule nobody repeats anymore

You called the meeting, you ran it, and afterward you write the two lines that say what was decided and who owns the follow-up. It feels efficient. One person who was close to the discussion, no handoff, no waiting on someone else to circulate a summary. There used to be a piece of advice pointed straight at this, that the person running a meeting should not also be the one keeping the notes, and you almost never hear it now.

The reason you never hear it is easy to name. The tool takes the notes. Nobody has to choose between running the room and writing it down, so the choice looks settled and the old advice looks like something from the era of a legal pad. Before agreeing that it is obsolete, it is worth pulling the rule apart, because it was quietly doing two jobs and only one of them has actually been retired.

The half of the rule everyone remembers

The obvious reason not to run a meeting and record it at the same time is attention. Both are full jobs. Running the meeting means watching who has not spoken, noticing whether the conversation is still on the thing that matters, and deciding when to move on. Keeping the notes is its own load, and it does not pause while you facilitate.

Annie Piolat, Thierry Olive and Ronald Kellogg reviewed the cognitive effort of note taking in Applied Cognitive Psychology in 2005, using dual and triple task methods to measure how much executive attention the activity actually consumes. Their comparison put note taking above reading and above learning in the effort it demands, and below only the creative composition of an original text. The reason they give is the time urgency of it: selecting the key points and writing them down while still comprehending new information as it arrives places heavy demand on the central executive and the rest of working memory.

Now stack running the meeting on top of that. Something gives. Usually the notes go thin because the person is spending their attention on the room. Sometimes the room drifts because the person is spending their attention on the notes. This is the half of the old rule that automatic capture genuinely fixes, and it is a real fix worth having. If it were the whole rule, the story would end here and the advice really would be obsolete.

The half almost nobody remembers

There was a second reason, older than any software, built into how formal meetings have been run for more than a century. Parliamentary procedure keeps the person who runs the meeting and the person who keeps the record in two different chairs, on purpose.

Henry Robert's Rules of Order describes a presiding officer who is expected to stay impartial. Robert warns that a chairman who has even the appearance of being a partisan loses much of his ability to control the people on the other side of the question, and that anyone who expects to take an active part in the debate should never accept the chair. The record is kept by a different person entirely, the recording officer, usually called the clerk or secretary, whose minutes are defined as a record of what was done and not what was said.

Read those two rules together and the design is clear. The person steering the outcome and the person authoring the record are deliberately not the same person. It was never mainly about having a spare pair of hands. It was that the record was not supposed to be written by the one participant with the most stake in how it reads.

Automatic capture fixed the first half and hid the second

Capture tools remove the attention cost completely. No one has to trade running the meeting against writing it down, because the writing is no longer a human task during the meeting. The surface reason for the old split is gone, and it is a short step from there to deciding the whole question went with it.

But the transcript is not the record. Nobody acts on a raw capture. Someone turns it into the version people actually use, the one that says here is what we decided, here is who owns what, here is the thing we are not doing. That step is authorship, and it quietly defaults to the person who ran the meeting, because they called it and they are the one who will send the recap.

So the tool did not remove the thing the second half of the rule guarded against. It moved it. The authorship that used to happen live, in the notes, now happens afterward, in the summary. Same person, same stake in the outcome, later timestamp. The neutral transcript sitting underneath does not change who wrote the sentence everyone reads.

Why the runner is the worst-placed author, even in good faith

This is not a claim that meeting leads shade the record on purpose. The problem is more stubborn than that, because it shows up in honest people who are trying to be fair.

Michael Ross and Fiore Sicoly documented the mechanism in the Journal of Personality and Social Psychology in 1979. Across several settings, including married couples and members of working groups, people recalled their own contributions to a joint effort more readily than their partners' contributions, and claimed a larger share of responsibility for the shared result than the other participants were willing to grant them. Your own input is simply more available to you when you try to remember what happened.

The person who ran the meeting is the most central contributor in the room. Their recollection of what we decided is therefore the most tilted account available, not because they are dishonest but because their own framing is the part they remember most clearly. The objection someone raised and they answered past is the least available piece to them, and the least likely to survive into a recap written from memory. The record ends up authored by the single participant whose memory of the meeting leans hardest toward their own version, and it is handed to everyone else as the neutral account. The lean is hard to see precisely because it is sincere.

The fix is not making the runner stop typing

The instinct is to reach back for the original rule and have a second person take the notes. That aims at the wrong half. A dedicated human scribe buys neutral notes by paying the attention cost the tool already removed, which is a strange trade to make in 2026.

The better move is to separate two things the word notes hides inside itself. Capture is producing the raw account of what was said. Ratification is deciding what that account officially means. Capture can belong to anyone, the tool included, and the person who ran the meeting triggering it is completely fine. Ratification is the part that should not rest with the runner alone, because ratification is where one person's memory becomes everyone's record.

What that looks like in practice

Keep the raw capture as the source of record, not only the tidy summary. The neutral account of what was said is the modern version of what was done and not what was said: it is the thing a contested recap can be checked against, so the summary is verified rather than taken on the author's word.

Put the decisions and action items back in front of the room for a short correction window before they harden. The argument about what we actually agreed is cheap in the hour after the meeting and expensive three weeks later, when someone is being held to a wording they never registered as the decision.

Where the runner's framing and a participant's differ on what was decided, keep the decision in the participant's words rather than smoothing it into the runner's. A disagreement preserved in the record is worth more than a clean sentence that only one person would have written.

For a meeting with real stakes or real disagreement, hand the recap to someone who did not run it. The person who argued hardest for an outcome is the one person who should not also write the sentence that records it, and having a different author is a lighter fix than it sounds once capture is already handled.

Where this matters and where it does not

Most meetings need none of this. A standup, a working session, a routine sync between two people who trust each other: the runner's recap is fine, and adding a ratification step would be procedure for its own sake. Do not put a correction window on a fifteen minute check-in. The overhead would outweigh anything it caught.

The rule earns its keep exactly where the chair and secretary split earned it. Meetings where the outcome is contested. Meetings where a trade between two people or two teams was made. Meetings where someone will later be held to what we decided. In those rooms the authorship of the record is worth keeping separate from the person who steered the result, for the same reason parliamentary procedure kept it separate long before anyone had a transcript.

What changed is the price of doing it. Separating those roles used to cost a second person's full attention for the entire meeting, which is why teams skipped it and let the runner keep the notes. Now capture is free and neutral by default, so the only thing left to distribute is the editing, and that is a few minutes of one other person reading a summary, not an hour of someone typing.

How Driffle fits

Driffle captures a meeting from your own computer, with no bot joining the call and nothing for the other side to install. It never auto-joins, auto-records, or runs in the background. You start it and it works, you close it and it stops. Audio is transcribed in real time and discarded, so what is left afterward is the text and the notes you wrote.

That neutral capture is the useful part here. Because the account of what was said exists independently of whoever writes the recap, a summary can be checked against it instead of trusted, and you can ask the record what was actually decided rather than relying on one person's memory of it. Notes stay private to their author until they are shared, workspace admins see what has been shared into shared folders rather than private notes, individual notes can be removed, and full account deletion clears the data within 30 days including backups.

Driffle does not decide who ratifies a meeting for you, and it should not. What it does is make the capture cheap and neutral, so the only judgement left is the one worth keeping human, which is who gets to say, officially, what the meeting decided.

A question for your next meeting that matters

After the next meeting that actually carries weight, notice who writes the sentence that begins with we decided. If it is the same person who pushed hardest for that decision in the room, then the record has exactly one author and it is the most interested party present. Nothing about an automatic transcript changes that, because the transcript is not the sentence people will act on.

You do not need a scribe and you do not need to distrust anyone. You need the raw capture to survive as the check, and you need one other person to read the recap before it becomes the thing everyone is measured against. Capture is the cheap part now. Deciding what the capture means is the part still worth sharing out.

Sources

FAQ

Isn't this already solved now that the tool takes the notes automatically?

The tool solved the attention problem, which was only half of why the old rule existed. It did not solve authorship. Someone still turns the raw capture into the official version of what was decided and who owns what, and that summary is where one person's framing enters. The transcript underneath is neutral, but a recap written from it is not automatically neutral just because a tool produced the transcript.

Are you saying the person who ran the meeting should never write the recap?

No. For most meetings it is fine, and anything else is overhead. The narrower claim is about meetings with contested outcomes or real trades, where the person who steered the result is the worst-placed person to also be the sole author of the record. Even there, the fix is usually a short correction window or a second reader, not banning the runner from writing anything.

We don't have a spare person to take notes. Does this fall apart?

It does not, because the fix is not a dedicated note-taker. Automatic capture already gives you a neutral account of what was said without a second person in the room. What is left is a few minutes of ratification: send the decisions back to the room to correct before they harden, and keep the raw capture so the summary can be checked against it. That does not need extra headcount.

Won't sending every recap back for correction slow the team down?

It would, if you did it for every meeting, which is why you should not. Reserve it for meetings where being wrong about what we decided is expensive. For a routine sync the runner's recap stands as written. The point is to spend the correction step where the stakes justify it, not to add a ceremony everywhere.

Isn't the transcript itself the neutral record, so why worry about the summary?

The transcript is neutral, but nobody acts on a transcript. People act on the short version: the decisions, the owners, the next steps. That short version is a selection from the transcript, and selection is where a point of view enters, including which objection made the cut and how a decision gets worded. Keeping the transcript matters because it lets you check the selection, but the selection still has an author, and it is worth thinking about who that is.

Never lose the thread of a meeting again.

Driffle keeps the decisions, owners, and context from every conversation searchable when work resumes.

Request access

Similar articles