How to write meeting minutes: steps, template, examples

Updated 6 November 2026.

Meeting minutes are finished when every decision sits in a CRM field, every action item is a task with an owner, and the client has the follow-up email: the document itself is the least important part.

You have to take the minutes. It might be a discovery call, a pipeline review or a weekly team meeting.

You have read three guides already. They all say the same thing: note the date, the attendees, the decisions and the action items.

That advice gives you a clean document. It does little for next week, when nobody opens it and the action items have quietly slipped.

The problem starts after the meeting. Minutes die in a shared folder because the decisions never reach the place where people work.

By the end of this guide, you will have a template to paste into your next call, five steps to fill it in, and a clear place for each block to go once the meeting ends.

How to write meeting minutes, in short

• Meeting minutes record the decisions, the action items and the open questions of a meeting, with who owns what and by when.
• Six blocks are enough: meeting details, goal, decisions, action items, open questions and next step.
• Decisions and action items are written during the call, in the words people used, and the summary of the discussion stays short.
• Reading the action items back near the end of the call gets every owner to confirm their task and date out loud.
• Minutes go out the same day. Each decision then moves into the CRM and each action item into a task tool.
• A recording or an AI summary covers the discussion, and the decisions still need someone who puts them where the team works.

Why minutes die after the meeting

Most minutes are written well enough. They fail the day after, when the decisions stay in a document and the CRM, the task list and the client's inbox stay empty.

Recording the meeting has stopped being the gap. 95% of the buyer accounts that described their setup already recorded their calls, with a notetaker, a dialer, a conversation intelligence suite or the meeting tool itself (Claap call data, November 2025 to November 2026). These are one team's calls, so read the shares as directional.

So the record exists. The break comes next. About one account in seven, 15%, has the recording or the summary and says nothing is done with it (Claap call data, November 2025 to November 2026).

What buyers ask for points at the same fix. 27% want what was said on the call written into CRM fields, and 31% want the call scored against their own criteria (Claap call data, November 2025 to November 2026). Both requests describe minutes that land somewhere: a field a manager reads, a scorecard a coach uses.

The follow-up email comes up too. A sales leader at a solar-engineering software company described what they wanted from their own team: "That email, let's say follow-up email could be sent right after the meeting, you know, with all the information."

So treat the minutes as a routing job. Each block has a destination, and the minutes are done when every block has reached it.

Write the destination next to each block when you prepare the template, because a decision with no destination stays in the document and dies there.

What meeting minutes have to contain

Six blocks cover almost every meeting. Each one has a place to go once the call ends.

• Meeting details. Name, date, attendees and who took the minutes. This goes to the archive.
• Goal. One sentence on what the meeting had to decide or learn. This goes to the archive.
• Decisions. What was agreed, in the words used on the call. This goes to a CRM field (deal stage, close date, next step) or the team's decision log.
• Action items. One task per line, with an owner and a due date. This goes to the task tool or a CRM task.
• Open questions and risks. What nobody could answer yet, and who will find out. This goes to the agenda of the next meeting.
• Next step. The next meeting, its date and what it has to cover. This goes into the follow-up email.

Leave out side conversations, opinions about people and a replay of who said what. The recording holds all of that.

The five steps that produce usable minutes

Two steps happen before the meeting, two during it and one after.

Step 1: Prepare the template with the goal and the destinations

Open the template before the call. Fill in the meeting details and write the goal in one sentence.

Next to each block, write where it will go: which CRM field, which task board, who gets the follow-up. It takes a minute, and it decides whether the minutes get used.

Step 2: Agree on who takes the minutes

Give the minutes to someone other than the person running the meeting when more than three people attend, because nobody can steer a discussion and write decisions word for word at the same time.

On a one-to-one client call, the seller takes them. Keep the notes short and let the recording hold the detail.

Step 3: Write decisions and action items as they happen

Write a decision the moment it is made, in the words used. "We pilot with the support team first" is a decision. "Discussed pilot scope" is a topic.

Write each action item as a verb, an owner and a date. If one of the three is missing, ask for it on the spot.

Step 4: Read the action items back before the call ends

Keep the last minutes of the meeting for this. Read each action item out loud and ask the owner to confirm the date.

Do this on every client call, because a client who confirmed a task out loud remembers owning it.

Step 5: Send the minutes the same day and route every block

Send the minutes within the working day when the meeting involved a client, because the follow-up email is the moment the client checks that you heard them. Our meeting recap email template gives you the email itself.

Then move each block to its destination: decisions into the CRM, action items into the task tool, open questions into the next agenda. When every block is in place, the minutes are done.

A meeting minutes template you can paste into the call

Copy these headings into your notes before the meeting.

• Meeting: name, date, attendees, minute taker.
• Goal: one sentence on what this meeting has to decide or learn.
• Decisions: one line per decision, in the words used. Add where it goes (CRM field or decision log).
• Action items: verb, owner, due date. One task per line.
• Open questions and risks: the question, who will find the answer, by when.
• Next step: next meeting, date, what it has to cover. This line opens the follow-up email.

Here is the same template filled in after a discovery call.

• Meeting: discovery call with a logistics software company. Their Head of Operations and IT lead, our Account Executive. Minutes by the Account Executive.
• Goal: find out whether their support team's call reviews are worth fixing this quarter.
• Decisions: "We pilot with the support team first." Goes to the CRM next step field. "IT has to approve any recording tool." Goes to the CRM risks field.
• Action items: send the security documents, Account Executive, Friday. Share the current review checklist, Head of Operations, Wednesday.
• Open questions and risks: who signs the budget above the team level. The Head of Operations will ask the COO.
• Next step: demo next Tuesday with the IT lead, focused on security and the CRM sync.

Meeting minutes examples for the meetings sales teams actually run

Discovery call. The decisions are about fit: the pain, who owns it, and whether there is a next meeting. Route the pain and the budget owner into CRM fields so the deal review sees them.

Demo. The minutes record which use cases landed and which objections came up, in the buyer's words. The objections go into the CRM and the next step goes into the follow-up email.

Pipeline review. Write one line per deal: the decision (move, hold, close lost) and the action the rep owes before the next review. Update the CRM during the meeting so the minutes and the forecast stay in sync.

One-to-one. Record the commitments on both sides and one skill the rep works on next. Start the next one-to-one by reading those lines back.

How to automate the minutes without losing the decisions

Three parts of the job can be automated: capturing what was said, drafting the minutes, and writing the decisions into the CRM. Confirming the owner and the date of each action item stays a human job, and it happens on the call.

Most teams stop at the first part. The recording exists, a summary arrives, and the CRM stays empty. If you only need the discussion in short, a meeting summary is the lighter format. For minutes, the CRM write is the part worth automating.

Automate the capture and the CRM write when your team runs client calls every day, because nobody keeps typing the same fields by hand after the first busy week.

Claap is our product, so read this paragraph as our pitch. Claap records your online meetings on Zoom, Google Meet and Microsoft Teams without a bot joining the call, and you can type your own notes during the meeting and get them back cleaned up. CRM auto-complete writes typed values into the fields your reports already use: for each field you pick the type, the prompt and the property, and sync rules protect what a rep already entered.

Mistakes that make minutes useless

• Writing a transcript. A replay of the discussion buries the three decisions that matter.
• Action items with no owner. "Send the proposal" with no name and no date is a wish.
• Sending them a week later. By then the client has forgotten the call and the team has forgotten the tasks.
• Keeping them in a folder. Minutes that stay in a document never update the CRM, and the deal review works from old data.
• Paraphrasing the decision. A rewritten decision invites a second debate. Keep the words people used.

What to change in your next meeting

Pick one meeting this week and run it with the template.

• Prepare the destinations. Next to each block, write where it goes before the call starts.
• Write decisions live. Use the words people used, the moment the decision is made.
• Read the action items back. Get each owner and date confirmed out loud before anyone hangs up.
• Send and route the same day. Send the follow-up email, fill the CRM fields, create the tasks.
• Automate the capture. Let a recording and a CRM write handle what you used to type.

This fits sales calls, client meetings and internal team meetings, anywhere the minutes exist to make work happen. Do this unless your minutes are a legal record, such as a board meeting, a committee or a formal approval: there, follow the format your bylaws or regulator require, because the exact wording and the approval of the minutes carry legal weight.

The test for your next set of minutes is simple. A week later, can someone find every decision in the CRM without opening the document?