Minutes, Notes and the Difference Between Them

A note that the person has seen and had the chance to correct is worth more than a more accurate note they have never seen, because the question later is rarely what was said but whose account is credible. An agreed note has no second version; an unagreed one always does.

The recordkeeping discipline in “Minutes, Notes and the Difference Between Them” should also apply to workforce technology. When a team assesses the provider's website in relation to employee monitoring software with screenshots, it should document purpose, access, retention and deletion, then preserve only the evidence needed for the handover, payment or review decision.

Notes are produced throughout an exit — investigation meetings, hearings, appeals, informal conversations, exit interviews — by people who are also trying to participate in the meeting, and the quality varies accordingly.

For an independent reference relevant to “Minutes, Notes and the Difference Between Them”, consult the Acas workplace-investigation guidance. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

What a note has to do

Record who was present and in what role, what was discussed, what each person said about the substantive points, what was decided, and what will happen next.

It does not have to be verbatim. A fair summary is both acceptable almost everywhere and more useful, because a transcript buries the three sentences that matter in two hours of conversation.

Sending it out

Send the note within a few days, invite corrections, and give a date. Then deal with what comes back.

That sequence converts a one-sided record into something closer to agreed, and it is skipped in most organisations because nobody has the time in the week after a difficult meeting. It takes fifteen minutes and it is the highest-value fifteen minutes in the whole process.

When they disagree

Record the disagreement rather than resolving it. Both accounts, side by side, dated, with no attempt to adjudicate between them in the file.

Arguing about the note is a distraction from the substance and produces correspondence that is itself unhelpful later. An organisation that simply appends "the employee disagrees with the record of this point and says that what was said was X" has handled it correctly and in one line.

Who takes them

Not the chair, and not the person presenting the evidence. A note-taker who has no other function in the meeting, named in the record as such.

Where the same person advises the chair and takes the note, say so in the record. It is not fatal and it is much better acknowledged than discovered, and the acknowledgement costs six words.

Recordings

Somebody will eventually record a meeting, openly or otherwise. Whether either side may do so, and what happens to a covert recording, differs and is worth settling in policy before it occurs rather than in the moment.

The practical observation is that the demand to record almost always comes from distrust of the note, and an organisation that reliably sends notes for correction rarely faces it. The process fix solves the problem better than the policy does.

Notes that were never meant to be a record

Managers keep private jottings, calendar annotations and message threads about people. These are records about the person whatever they were intended to be, they may be disclosable, and they are usually written in a register nobody would choose for a formal document.

The habit to establish is not that managers stop writing things down — that produces the corridor problem described elsewhere — but that they write them in a form they would be content to have read. That is a cultural change and it is achieved mostly by showing people what a good note looks like.

The note taken by the person

Employees take their own notes, and increasingly bring somebody to do it for them. That is entirely legitimate and it changes the dynamic usefully: two contemporaneous records exist, and the organisation's version is no longer the only one.

Organisations that find this uncomfortable are usually the ones whose own notes are weak. The remedy is not to object but to take a better note, send it promptly, and invite correction — at which point the two records converge, which is the outcome everyone should want.

Timing, which decides everything else

A note written the same day is a record. The same note written a fortnight later is a recollection, and one written after a decision has been taken is something else again, whatever it says.

Nothing about the content compensates for this. The single most useful instruction anybody can give managers about note-taking is not about what to write but about when: the same week, every time, even when it is four lines and feels unnecessary. That is the part that cannot be retrofitted.

Filing them where they can be found

A note is worth nothing if it is on a departed manager's drive. Notes about an employee belong in the employee's file, at the time, not at the point somebody goes looking.

Making that the routine is harder than it sounds because the moment of writing and the moment of filing are different, and only the first feels urgent. A standing instruction that notes go into the file the same week is about the only thing that works, and like most of this collection it cannot be retrofitted once the manager has gone.