Set meeting notes ownership before you delegate scheduling

Scheduling is not the same job as minutes

Calendar work is mostly coordination: finding a time, sending an invitation, and handling a change. Minutes are a record of what was decided and who owes the next step. Combining them into one vague assistant role usually produces good scheduling and weak notes.

Split the two jobs before you write the task list, even if the same person does both. Each output needs its own definition of done.

Decide which job you are delegating before you write the task list. If you need both, name two outputs with separate quality checks. A calendar with no conflicts is easy to verify, while a note that captures a decision needs a reviewer who understands the meeting.

Tell the coordinator which output has priority when the calendar is busy. Otherwise the visible task will always win over the quiet one.

Choose the note format the team will read

A note format should fit the way the team works, not the way a template looks. A short format with attendees, decisions, open questions, and actions covers most operating meetings. Add a section only when someone will read it before the next meeting.

Test the format on one real meeting and remove any section that stays empty. A shorter note that gets read beats a complete note that gets archived.

Put the decision in plain language and name the person who made it. Record the alternatives only when they explain why the decision was made. A transcript is not minutes, and a recording is not a decision log.

The note should let an absent colleague act without asking what happened. Write the action as a verb and a result so the next reader knows what finished looks like.

Define decisions, owners, and due dates

Every action needs one owner, one verb, and one date. Split actions that need two people so the follow-up is visible. Use the owner's name rather than a team label, because a team cannot be asked for status.

Add the date the action was agreed so a later reader can see how long it has been open. An action without a date is a wish with a meeting attached.

Separate a decision from a discussion point. A discussion point belongs in the note only if it changes the next action. Otherwise it adds length without adding accountability.

Review the action list at the start of the next meeting and close or re-date each item. If an item rolls forward three times, decide whether to drop it or give it a real owner.

Write the note during or immediately after the meeting, not the next morning. Context fades quickly, and a delayed note tends to summarize the discussion instead of the decision. Set a same-day deadline for the draft and a short window for the chair to correct it.

If the note cannot be written the same day, record the decisions in the queue first. The full note can follow.

Protect sensitive meetings from blanket delegation

Not every meeting should be documented by an outside coordinator. Personnel issues, legal advice, pricing strategy, and security incidents need a narrower list. Name those meeting types in the role brief and keep the notes with the appropriate internal owner.

Tell the coordinator what to do if a meeting drifts into a sensitive topic. The safe default is to stop taking notes and ask the chair.

If a coordinator must attend, limit the record to logistics and agreed actions. Remove personal details and anything under investigation. Confirm the retention rule before the first meeting, because a note that should not exist is a liability rather than a record.

Store sensitive notes in a restricted location and check who can open the folder. Access should be reviewed when the role changes.

Check the first ten sets of notes

Review the first ten notes against the source meeting. Check whether the decision is stated accurately, the owner is named, and the date is realistic. Look for actions that describe an intention rather than a task.

Compare the note with what the chair remembers, and resolve the difference in the note rather than in a side conversation. Record the correction so the next review can see the pattern.

Give the coordinator the corrected version and explain the change. After ten notes, move to a weekly sample that includes at least one difficult meeting. If accuracy stays weak, simplify the format before adding more meetings.

Ask whether the problem is hearing, understanding, or writing, because each needs a different fix. Do not add a second reviewer until the first review is consistent.

Keep a searchable archive

Store notes in one place with a consistent name and date. Use a short title that matches the meeting series so a later search finds the right record. Keep the action list linked to the meeting note rather than in a separate personal file.

Test the search with a phrase a new colleague would use. If the archive cannot answer a simple question, the format is not finished.

Set a retention period with the internal owner and remove notes when it ends. Restrict access to the people who need the record. A tidy archive is useful only when the right people can find it and the wrong people cannot.

Review the folder permissions at the same time as the notes, because an open folder defeats a careful format. Write the retention rule where the coordinator can see it.