Outsourced EmploymentPowered by StealthAgents

Practical guide

Write a meeting minutes correction record with a dated change note

A minutes correction record that preserves the original text, names the change, and records who approved it and when.

Published

Practical guide illustration for Write a meeting minutes correction record with a dated change note
Table of contents

Keep the original minutes intact

Store the approved minutes as a read-only file and make corrections in a separate record. Record the file name, the meeting date, and the version that is being corrected. A correction that overwrites the original erases the trail. The reader should be able to compare the two.

Number each correction and tie it to a line, an agenda item, or a paragraph in the original. Record the exact words that changed and the exact replacement. A general note that something was fixed gives a later reader nothing to verify. The pair of texts is the evidence.

State the reason for the correction in one sentence. A typo, a missed name, and a misstated decision are different kinds of change. Record the reason so the correction is not mistaken for a revision of the outcome. The distinction matters when the minutes support a commitment.

Name the change and the approver

Record who requested the correction and who approved it. The requester may be the note taker, a participant, or a person who reviewed the record later. The approver should be the chair or the owner of the meeting record. Record both names and the date.

Check whether the change alters a decision, an action, or only the wording. A change to a decision may need the group to confirm it again. Record the confirmation and the date. A wording fix can follow a lighter path, but it still needs a named approver.

Tell the people who received the original minutes that a correction exists. Record the channel and the date of the notice. A correction that stays in a folder leaves readers working from the old version. The notice should point to the corrected record, not repeat the whole text.

Keep the change note short and dated

Write the change note in a fixed format so every correction looks the same. Include the meeting date, the item, the original text, the corrected text, the reason, the requester, the approver, and the date. Record the version number and the status. A reader should not need to open five files to understand one fix.

Use the date the correction was approved, not the date the meeting happened. Record both dates when they differ. A correction made weeks later should not look as if it was part of the original record. The timeline is part of the evidence.

Attach any source that supports the correction, such as a recording note, a written message, or an agenda. Record the attachment name and where it is stored. A correction without support is only a second opinion. The attachment lets a reader check the reason.

Review corrections for patterns

Read the correction record at the end of each quarter and look for repeated mistakes. A name that is wrong every week may point to a bad template or a rushed process. Record the pattern and the change it suggests. The review should improve the minutes, not blame the note taker.

Check that the corrected minutes and the action list agree. A decision can be fixed in the minutes while the task list still shows the old owner. Record the cross-check and the date. The team should work from one version of the outcome.

Close the record when the correction is distributed and the original is marked as superseded. Record the closing date and the location of both files. Keep the correction for the same retention period as the minutes. A closed record shows what changed and why.

Sources

References supplied with this guide.

Article source directory
SourcePublisherContext
U.S. Department of Labor, Recordkeepingdol.govPrimary reference supplied with this article.
National Institute of Standards and Technology, Privacy Frameworknist.govPrimary reference supplied with this article.
U.S. Equal Employment Opportunity Commission, Recordkeeping Requirementseeoc.govPrimary reference supplied with this article.