Do Meeting Minutes Need to Be Signed? And How Approval Works

The short answer: In most organisations, no law requires a signature — your governing document does, or it doesn’t. Where signing is required it happens after the group approves the minutes, and the signature evidences which version was approved rather than making the minutes valid. This describes common practice, not legal advice.

Writing minutes is the visible half of the job. The half that makes them count is what happens afterwards: minutes are only the record once the group has agreed they are. Here is how that process normally works, and where it goes wrong.

One caveat first, and it is important. Requirements vary by country, by organisation type, and by your own governing document — articles of association, bylaws, a constitution, standing orders. Nothing here is legal advice, and where this article and your governing document disagree, your governing document wins. If minutes matter to you because of a regulator, a court, or a dispute, take proper advice rather than relying on a web page.

Draft, approved, signed

Three distinct states, often confused:

Draft. What the minute-taker circulates after the meeting. Useful, and not yet authoritative. Circulate drafts promptly — memories decay fast, and corrections get harder to resolve as they do.

Approved. The group has considered the draft and agreed it is an accurate record. This is the moment the document becomes the official account of what happened.

Signed. Where required, the chair or secretary signs the approved version. The signature is evidence of which version was approved — a useful thing when a set of minutes is produced years later and nobody remembers whether a particular copy was final.

Do minutes have to be signed?

For most groups, no statute compels it. The requirement, where it exists, comes from your own governing document — articles of association, bylaws, a constitution, standing orders — or from a regulator that supervises your sector. Plenty of well-run boards never sign anything and rely on the approval being recorded in the following meeting’s minutes, which is itself a perfectly good audit trail.

So the useful question is not “is it required?” but “what do our rules say, and what would we want to be able to prove later?”

What a signature actually does

This is the part that is most often misunderstood. A signature does not make minutes valid, and an unsigned set of approved minutes is not void. What the signature does is fix which document the group approved, and when. It is evidence, not magic.

That matters in exactly one situation, but it is the situation that hurts: somebody, months or years later, disputes what was decided. If two versions of the minutes are in circulation and neither is signed, resolving that becomes an argument about email timestamps. A signed copy ends it.

Who signs, and when

Signing comes after approval, never before — you are attesting to the version the group agreed, so there is nothing to attest to until they have agreed it. Signing a draft is the most common procedural mistake here.

Who holds the pen varies:

• The chair of the meeting at which the minutes are approved — the most common arrangement, because that person is confirming what the group just agreed.
• The chair of the meeting being minuted — used where the emphasis is on the accuracy of the record rather than the act of approving it.
• The secretary or clerk — often as well as the chair rather than instead of them, particularly where the secretary drafted the minutes.

Your governing document decides. Where it is silent, pick one arrangement and apply it consistently; an inconsistent practice is worse than either choice.

Electronic signatures, and signing every page

Electronic signature is widely accepted for minutes, and many organisations moved to it permanently after several years of remote meetings. Whether it satisfies your rules is again a governing-document question, and a handful of regulated bodies still expect a wet signature in a bound minute book.

Two conventions worth knowing:

• Signing each page, or initialling each page and signing the last, makes it hard to substitute a page later. Formal bodies and anything likely to face scrutiny still do this.
• Recording the date of signature separately from the date of the meeting. Those are different dates and conflating them is a common source of confusion in a minute book.

If your rules are silent

Sign anything consequential anyway. It costs nothing, it takes seconds, and it removes an entire category of future argument about which version was the approved one. For a weekly team catch-up it is overkill; for anything a regulator, auditor, member or court might one day read, it is cheap insurance.

How approval usually happens

Approval is conventionally the first substantive item on the next meeting’s agenda, and it runs like this:

1. The draft is circulated in advance, so people can read it rather than skim it in the room.
2. The chair asks for corrections. This is a check on accuracy, not a reopening of the debate — a common and avoidable failure is a group re-arguing a decision instead of confirming what was decided.
3. Corrections are agreed and noted.
4. The minutes are approved, either by formal motion or by general consent where nobody objects.
5. The approval is recorded in the current meeting’s minutes, which is what creates the audit trail.

That last step matters more than it looks. The evidence that January’s minutes were approved lives in February’s minutes. Skip it and you have a record with no proof it was ever accepted.

The motion, if you use one

Formal bodies typically use wording along the lines of:

“I move that the minutes of the meeting held on 14 July 2026 be approved as circulated.”

Or “as corrected”, where changes were made. It is seconded, the chair puts it to the vote, and the outcome is minuted. Groups following Robert’s Rules of Order frequently skip the formal motion and approve by general consent — the chair asks whether there are corrections and, hearing none, declares the minutes approved. Both are normal; consistency is what matters.

Correcting an error after approval

This is the part people get wrong, usually with good intentions.

Before approval, correcting a draft is trivial — that is what the approval item is for. After approval, do not quietly edit the document. The convention is to correct it by a motion at a later meeting, recording what the error was and what it now says, so the history of the record stays intact.

The reason is straightforward: a record that can be silently changed is not a record. The value of minutes rests entirely on their being a fixed account, and an amendment trail is what preserves that.

Where the recording fits

The most common cause of a contested approval is a genuine disagreement about what was decided — two people remembering the same sentence differently, with the minute-taker caught between them.

A recording resolves that in seconds rather than by seniority. If the meeting was recorded, you can check the actual wording of the decision instead of reconstructing it, and speaker labels tell you who proposed what. It also removes the hardest part of the job: taking an accurate note of a motion’s exact wording while also taking part in the discussion.

Two practical notes. Ask the room before recording — always, and as a matter of course. And a recording is working material, not part of the record: the approved minutes are the official document, and how long you keep audio afterwards is a decision worth making deliberately rather than by default.

For the mechanics, see how to record a meeting on iPhone, and for turning the transcript into a usable record, what to include in meeting minutes and how to write meeting minutes from a recording.

Also worth reading: what meeting minutes are, which explains why the approval step is what turns one person’s account into the organisation’s record, and how to send meeting minutes for circulating the draft before that meeting — including what to do when somebody says the minutes are wrong.