The questions to ask after a meeting

Go through what was said, find the places where a wrong assumption would cost the most, and ask about those — in writing, the same day, three or four at a time.

This guide groups the questions worth asking by what is at risk, shows how to find them in your notes or a transcript, and covers how to ask them without sounding like an audit.

Why ask after, not only during

Meetings move fast. Someone says "we'll need it by the end of the quarter" and the conversation moves on before anyone asks which quarter, or whether "it" means the whole thing or the first part. Nobody is being careless; there is simply no gap to ask in.

Afterwards, with the notes in front of you, the gaps are visible. A short list of questions sent the same day does three things: it catches misunderstandings while they are cheap, it shows the other side you were listening, and it puts the answers in writing.

The questions, grouped by what is at risk

Scope

The most common source of disputes later.

• "When you said you'd like it simpler, which parts did you have in mind?"
• "Is the reporting piece part of this phase, or the next?"
• "What would you expect to see at the end of this, so we know it's done?"
• "Is there anything you assumed we'd do that we didn't mention?"

Money

• "Who approves the budget for this, and is it already set aside?"
• "Is the figure we discussed inclusive of the extra reports, or on top?"
• "Does anything need to happen before a purchase order can be raised?"

Dates

• "When you said end of the quarter, is that a hard date? What happens if it slips?"
• "Is anything on your side needed before we can start — access, data, sign-off?"
• "Are there dates we should avoid, like a freeze or a holiday period?"

People

• "Who else needs to agree before this goes ahead?"
• "Who should we send questions to while you're away?"
• "Is there anyone who'd be surprised to hear about this decision?"

Assumptions

• "We assumed the data would come from the current system — is that right?"
• "Is the approach we discussed consistent with your security policy?"
• "What would make you change your mind about this?"

Disagreement

Where the two sides differed and the meeting moved on without settling it.

• "We didn't fully settle the question of monthly or annual pricing — shall we go with yours for now and review after launch?"
• "You mentioned concerns about the timeline. Is there something specific we should plan around?"

For sales and technical discovery, the same groups apply with an emphasis on requirements and objections — see meeting notes for sales engineers.

Finding the questions in your notes

Go through your notes, or the transcript if you have one, and mark each of these:

1. Vague commitments. "We'll sort that out", "someone will look into it". No owner, no date.
2. Unconfirmed numbers. A price, a date or a quantity mentioned once, not repeated back.
3. Missing people. Any time someone said "I'll need to check with…".
4. Unspoken assumptions. Statements that only hold if something else is true.
5. Unsettled disagreements. A point where both sides spoke and nobody said "agreed".
6. Things that were not said. No mention of budget, approval or deadline in a meeting about buying something is itself a gap.

For each mark, ask: if we are wrong about this, what does it cost? Rank by that, and keep the top three or four.

If you keep client meeting notes in a structured way — decisions, scope changes, where you differed, open questions — most of this work is done already: the open questions section is your list. The general meeting notes template has the same section.

Asking without sounding like an audit

Questions after a meeting can read as distrust if they are phrased badly. A few habits help:

• Lead with what was agreed. Confirm the decisions first, then ask. The questions then read as finishing the job, not questioning it.
• Say why each question matters. "So we can schedule the data work" makes a question easy to answer.
• Offer a default. "Unless you tell us otherwise, we'll assume the reporting is phase 2." It turns an open question into a yes-or-no one, and silence into a reasonable record.
• Keep it short. Three or four questions. Save the rest for the next meeting.
• Put them in the follow-up email, not a separate message. How to write a follow-up email after a meeting shows where they go.

A fictional example

Northwind is an invented customer; the people are invented too.

Subject: Pricing page — what we agreed, and three questions

Hi Marc,

Thanks for today. To confirm what we agreed:

- The launch price holds for the first quarter.
- The pricing page will list what the free tier includes.
- Prices are shown monthly first.

Three questions, so we can plan the next two weeks:

1. Is the competitor comparison table part of this phase? We've assumed not,
   and will send a quote separately — let us know if you'd expected it included.
2. Does Priya need to approve the page before launch, or only the price?
   It changes when we'd need to send her the draft.
3. You mentioned a freeze "around the end of the month". Which dates exactly?
   We'd like to avoid a release landing inside it.

Best,
Ana

Finding the questions with Notey

Notey's Tough questions note does this step from a recorded meeting's transcript: it lists the questions worth going back and asking, grouped by what is at risk, each one saying why it matters. It is written only when you ask for it, it sends the transcript's text and never the audio, and it is labelled as AI-generated. Treat it as a first draft of the list: check each question against the transcript — click a line's timestamp to hear the moment — and keep the few that matter most.

The Where you differed note covers the disagreement group above, and Follow-up email drafts the message that carries the questions.

Checklist

1. Go through notes or the transcript the same day.
2. Mark vague commitments, unconfirmed numbers, missing people, assumptions and unsettled disagreements.
3. Rank by what a wrong assumption would cost.
4. Keep three or four; say why each matters; offer a default.
5. Send them in the follow-up email, after what was agreed.
6. Put the answers in your notes when they come back.

Frequently asked questions

What questions should I ask after a client meeting?

Questions that close gaps where something is at risk — what exactly is in scope, who approves the spend, what the real deadline is, who else needs to agree, and what the client assumed that you did not.

How soon should I send follow-up questions?

The same day or the next morning, while the meeting is fresh for everyone. Put them in the follow-up email, after the summary of what was agreed.

How many follow-up questions is too many?

More than three or four in one email usually means some will go unanswered. Ask the ones where a wrong assumption would cost the most, and save the rest for the next meeting.

How do I find the questions I should have asked?

Go through your notes or the transcript looking for vague commitments, unnamed owners, numbers nobody confirmed, and statements that start with an assumption. Each one is a candidate question.