Consulting Meeting Minutes Template: 4 Formats + Examples

Consulting meeting minutes need one fixed core for every client meeting: decisions, actions with an owner and a due date, risks and issues, and open questions. Each meeting type then adds one block: scope and roles at a kickoff, progress against plan at a weekly status, the decisions asked for at a steering committee, and outputs at a workshop.

Whatever the meeting, the person reading your minutes wants to know three things: what was decided, who does what by when, and what could go wrong. The structure below answers those in the same order every time, so a sponsor who skims ten sets of minutes finds the same thing in the same place.

The "side" column is the one generic templates leave out. On a consulting engagement, many actions sit with the client: sending data, granting access, booking interviews, signing off a deliverable. If those actions are missing from the minutes, a slipped date reads as your delay. Written down with a name and a date, it reads as what it is.

The kickoff sets the terms the whole engagement is judged against, so its minutes carry more detail than any other. Add this block above the core sections:

• Header: grocery chain, store operations review · Kickoff · 2 November 2026 · Client: Priya (COO, sponsor), Tom (operations lead) · Firm: Ana (lead), Ben · Author: Ben
• Objective: fewer empty shelves in the pilot stores; success = the stock-out rate the client already tracks, at week 8, against the September baseline.
• Scope: in: 12 pilot stores and the replenishment process. Out: suppliers, pricing, changes to IT systems.
• Deliverables: current-state report, 20 November, approved by Tom; recommendations, 18 December, approved by Priya.
• Decisions: weekly status every Monday at 09:00; steering committee every four weeks, chaired by Priya.
• Actions: share six months of store sales data, Tom (client), 6 November; book eight store manager interviews, Tom (client), 9 November; send the interview guide, Ana (firm), 5 November.
• Risks and issues: risk: the data export depends on the client IT team, owner Tom, next step: ask IT this week.
• Open questions: are the two newest stores part of the pilot? Priya to answer by 6 November.

Status minutes are short and repetitive on purpose. The block on top answers "are we on track?" in one line, then shows what moved since last week. Anything that needs the sponsor goes to the steering committee, not here.

• Header: grocery chain, store operations review · Weekly status · 16 November 2026 · Client: Tom · Firm: Ana, Ben · Author: Ben
• Status: at risk. Store sales data arrived on 10 November, four days late, so the current-state report needs two more days.
• Since last meeting: seven of eight store manager interviews done; data cleaning finished.
• Next period: last interview; draft current-state report.
• Decisions: the report moves from 20 to 24 November; Tom confirmed.
• Actions: book the last interview, Tom (client), 18 November; draft the report, Ana (firm), 23 November.
• Changes to scope: Tom asked to add online orders. Not decided here; it goes to the steering committee on 30 November.
• Risks and issues: issue: one pilot store has no reliable stock counts, owner Tom, next step: a manual count on 19 November.

Steering committee minutes are the most formal set an engagement produces. The sponsor and senior client staff use them to show what was approved, so record each decision exactly as it was taken, and note any disagreement in one neutral line. Add this block:

Ask at the kickoff how the client treats these minutes. Some sponsors want to review the draft before it goes to the committee, and some committees approve the previous minutes at the start of the next meeting. Either way, send the draft to the chair first.

A workshop produces something: a list of options, a ranked set of problems, a process map. Its minutes record that output and the agreements behind it, not the conversation. Add this block:

• Header: grocery chain, store operations review · Workshop: replenishment problems · 10 November 2026 · Client: Tom and five store managers · Firm: Ana (facilitator), Ben · Author: Ben
• Objective: rank the causes of stock-outs in the pilot stores.
• Exercises: list causes on sticky notes; group them; vote with three dots each.
• Outputs: top three causes: late deliveries on Mondays, shelf counts done at the wrong time, order quantities fixed for a year. Whiteboard photos attached.
• Agreements: Monday deliveries are the first cause to test. Disagreement: two managers see order quantities as the bigger cause.
• Parking lot: staff rotas; Tom to raise them with HR.
• Actions: pull delivery times for the last 8 weeks, Ben (firm), 13 November.

Not every client meeting needs full minutes. After a short check-in, send a summary instead: the same core, cut down to what fits on one screen.

The last line matters. Asking for corrections by a date turns silence into agreement, and catches a misheard number before it becomes the basis of next week's work.

The minutes you send are a client deliverable. Your own read of the meeting is not: who seemed unconvinced, a scope worry you have not raised yet, a commercial thought about a follow-on project. Keep that in a separate private note in the same client folder, and never paste it into the minutes.

Keeping one client's notes away from another's is a separate habit, with its own folder structure and end-of-engagement cleanup. We cover it in a dedicated guide.

1. Before: copy the template for the meeting type, fill in the header, and carry over every open action, risk and question from the last minutes.
2. During: write decisions and actions the moment they land, with the side, the owner and the date.
3. Close: in the last two minutes, read the decisions and actions back to the room and fix them there.
4. After: clean up the wording, check every name, number and date, and send within one working day to everyone invited.
5. Ask for corrections by a set date, then file the minutes in the client's folder next to your notes.

Running a meeting outside an engagement? The general five-section minutes template, with a prompt you can paste into any AI assistant, is in our guide.

A recording helps you check a number or the client's exact wording before it goes into the minutes. Reline's desktop app records your microphone and the system audio on your computer, with no bot joining the call, and transcribes the meeting live while it records. Capture is local; transcription, AI and storage run in the cloud. Transcription covers 60+ languages.

After the meeting, run a Lens on it: type its command in the note's chat. Key Decisions Log and Action Items with Owners draft the decisions and the action table, Stakeholder Update drafts a status write-up, and Draft Follow-Up Email drafts the summary email. Before a steering committee, the Project Status Lens in the client's folder drafts a status from across that folder's notes. You can also create your own Lens with the four core sections, so every meeting comes back in the same shape.

Every draft is a starting point. Check each decision, owner and date against the transcript, where you can press play on any line to hear it again.

• On a call, transcript lines are labeled as you or the other side, not person by person, and in a workshop room everyone reaches the laptop through one microphone. Write the owners' names yourself.
• Reline transcribes live only. It cannot transcribe a recording you already have or an uploaded file; for a past meeting, use the meeting platform's own transcript.
• It records audio and the transcript, not video or the screen. Photograph the whiteboards.
• There is no SOC 2 report. A DPA is available. If a client contract asks for a certification from your tools, check before you record.
• The free plan includes 10 hours of transcription and up to 1 hour of recording per note, so a half-day workshop runs past what one note can hold. Professional ($15 a month) removes both limits.

Often, you need their agreement. Recording a conversation can require the consent of everyone on it, and the rules differ between countries, regions and employers. Reline puts no notice in the meeting, so telling people is your job: say at the start that you are recording and why, offer to stop if anyone objects, and check the rules where everyone on the call is. Check your client contract too: some say whether meetings may be recorded. This is general information, not legal advice.

Four meetings, one core: decisions, actions with a side, an owner and a date, risks and issues, open questions. Copy the format for the meeting you have next, and send the minutes while it is still fresh.