Set a meeting-notes standard for assistant-led client calls

Decide what the notes are for

A meeting note can serve several purposes, and mixing them produces a document that does none well. Decide whether the note is a decision record, a task list, a client update, or a memory aid for the assistant. Write the purpose at the top of the template. The purpose tells the writer what to include and what to leave out.

For most client calls, the decision record matters most because it answers what changed and who owns the next step. A task list without decisions loses the reason for the work. A narrative summary without owners is pleasant to read but hard to act on. Choose the primary purpose and let the other uses follow.

Use a fixed format

Use the same five fields for every call: attendees, decisions, actions, open questions, and the next meeting date. Keep the fields in that order so a reader can scan for the part they need. Add the call date, the client, and the note owner at the top. A fixed format makes notes comparable across weeks and writers.

Write the decisions as complete sentences in the past tense, such as the client approved the revised scope for the next sprint. Avoid labels that only the attendees understand. If a decision has a condition, put the condition in the same sentence. A future reader should not need the recording to understand what was agreed.

Separate discussion from decision

Most calls contain more discussion than decision, and mixing the two creates false commitments. Put the discussion in a short background line only when it explains a decision. Move every proposal that was not accepted to the open questions field. A reader should be able to tell what is settled from what is still being considered.

When the call ends without a decision, say so explicitly and name the person who will decide. Silence in the notes often gets read as agreement. Record the date by which the decision is expected and the next step if it slips. An honest note protects the assistant from being blamed for a choice that was never made.

Ask for consent before recording a client call and note the answer at the top of the notes. Some clients require a specific notice or forbid recording altogether. The assistant should know the rule before the call starts. Consent belongs in the record rather than in a separate memory.

Assign owners and dates inside the call

Read each action back during the call and confirm the owner and the date before moving on. An action assigned after the call is often assigned to the wrong person. Use the attendee's name rather than a team label. The note should show one accountable person for every action.

Set dates that the owner has agreed to rather than dates the assistant assumes. If the owner cannot commit, record the action as pending with a review date. Distinguish a due date from a follow-up date. The difference matters when the team reviews the list a week later.

Send a same-day summary

Send a short summary to the attendees on the same day while the call is still fresh. Include the decisions, the actions, and one line on the next meeting. Ask recipients to correct anything that is wrong within one business day. The summary becomes the agreed record after that window.

Keep the summary shorter than the full note and link to the detailed version where one exists. Use plain language and avoid internal shorthand that the client will not recognize. Put the client's requested changes in their own words where possible. A clear summary reduces the follow-up calls that the assistant must handle later.

Handle sensitive and informal calls

Some calls cover personnel, legal, or commercial matters that should not be circulated widely. Mark the note as restricted and store it in the approved location for that client. Remove the sensitive detail from the general summary. The assistant should know who may read the full note before the call begins.

For an informal call that produces no decision, send a brief note that confirms nothing changed. That note prevents a later claim that an agreement was reached. If the call did produce a decision, treat it like any other call and send the standard summary. Informality is not a reason to skip the record.

Store the notes in the client's approved system rather than in a personal drive or a chat thread. Set a retention period that matches the client's recordkeeping duty. Give the assistant a way to search the archive by client, date, and decision. A note that cannot be found later provides little value as a record.

Audit a sample each month

Read a sample of notes from the month and check whether a reader can identify the decision, the owner, and the date without asking. Mark the notes that require the recording or a follow-up to understand. The count is a measure of the template, not the writer. Fix the format before coaching the person.

Ask one client whether the summaries match their understanding of the calls. A mismatch reveals a gap in how decisions are confirmed, not just how they are written. Update the template and the call script with the correction. A monthly sample keeps the standard from drifting as the team changes.