What to Do When Your Manager Asks "What Did We Decide?" and You Can't Remember

When your manager asks what was decided and you can't remember, don't guess. Say you'll check and reply within a set time, search the notes, chat threads, calendar and transcript, ask a peer who was there, write the answer down, and say so if nothing was actually decided.

  1. Don't bluff; promise a quick, specific answer.
  2. Search notes, chat, calendar and transcripts.
  3. Ask a peer or the facilitator, framed as confirming.
  4. Write the recovered decision down.
  5. Say so if no decision was actually made.

Updated October 9, 2026 · By the DeftBrain team

When a manager asks what was decided in a meeting you can't recall, a short holding reply such as 'let me check the notes and get back to you in ten minutes' is safer than guessing. Most meetings leave written traces (agendas, notes, chat summaries, calendar invites, transcripts) that usually settle the question. If they don't, asking a colleague who attended and then recording the answer prevents the same gap next time.

'What did we decide on the launch date?' The meeting was three weeks ago. You remember something about Q4, but not the decision. Your fingers hover while two parts of your brain argue: bluff or admit?

How to do it
1

What should you say when you can't remember what was decided?

The first move is the one that's easiest to skip: don't answer immediately if you're not sure. The cost of a confident wrong answer is much higher than the cost of a brief delay, and a manager asking 'what did we decide' usually isn't on a thirty-second clock — they're asking because they need it for something coming up, and a five-minute or twenty-minute delay is fine. The reply that earns the window is short and direct: 'Let me check the notes — back to you in ten minutes.' Or: 'I want to make sure I give you the right answer — checking now.' Both tend to read as conscientious rather than uncertain. The bluff, if discovered, gets read as both wrong and unaccountable. The window is free; the bluff is expensive. Always pick the window.

What to say

"Let me check the notes — I want to give you the exact wording we landed on. Back to you in ten minutes."

This response does the three most important things in a single sentence: it doesn't bluff, it commits to a specific quick turnaround, and it frames the work as wanting to give the precise answer rather than as recovery from a memory failure. Managers read this as conscientious, not uncertain. It also bought you a real window — ten minutes is enough time to do an artifact sweep and ask one or two people if needed. The contrast with the wrong-confident bluff is enormous: the bluff costs trust if discovered, while this response builds it.

2

Where can you find what was decided in a meeting?

Most meetings leave more written traces than people remember. The agenda you sent or received. The Slack channel where someone summarized afterward. The calendar event invite that includes the topic. The recording or transcript if Zoom or Teams was running. The notes someone took, even if you weren't the one taking them. Before you ask anyone what was decided, do a five-minute sweep through the artifacts that already exist. Search Slack for the topic name across the relevant channels. Check the calendar for the meeting and any follow-up calendar entries. Open the meeting transcript if there is one. Often the decision is recorded somewhere in writing; you just didn't remember where. The sweep takes a few minutes and frequently recovers the decision without involving anyone else.

3

Who should you ask about a past meeting decision?

If the artifacts don't surface the decision, you have to ask someone — and how you ask matters. Asking the most senior person who was in the room ('hey, can you remind me what we decided?') puts you in a worse position than asking a peer who was also there. Asking a peer with 'do you remember what we decided about X?' is normal collaboration. Asking the meeting facilitator with 'I'm pulling together a summary for [manager], can you confirm what we landed on for X?' frames it as documentation work rather than memory failure. The phrasing changes how the request lands. The general rule: ask the person closest to the source of truth, frame the ask as documentation rather than recovery, and don't apologize for asking. People are happy to confirm what they themselves know; they're less happy to feel like they're filling in for someone else's missed attention.

4

How do you make sure a decision doesn't get forgotten again?

Once you've recovered what was decided, the most valuable thing you can do is write it down somewhere durable, immediately. A short Slack message to the relevant channel ('Confirming we decided X on the launch question — flagged for the record'). A note appended to the original meeting notes if you have access to them. A calendar entry with the decision in the description. The medium matters less than the act. Decisions that get recovered orally and then re-forgotten produce the same problem in three more weeks. Decisions that get written down once stay written down. This step takes ninety seconds and pays itself back the next time the same question comes up — which it often does. The recovered decision becomes a small permanent asset rather than a recovery you have to repeat.

5

What if no decision was actually made?

There's a category of 'what did we decide' questions where the honest answer isn't recoverable from notes or peers — because no decision was made. The meeting discussed the topic. Several people had opinions. The room moved on without explicitly settling on a direction, and the absence of a decision wasn't named at the time. Three weeks later, someone treats the topic as if it had been decided, and you're being asked to recall something that doesn't exist. The signal you've reached this category: have you checked notes, Slack, and asked one or two attendees, and the answer is consistently fuzzy? If yes, what you have isn't a memory problem; it's an unmade decision. The right response is to name that directly: 'I checked notes and asked Tom — I don't think we actually landed on a decision in that meeting. We discussed it but didn't settle. I think we need a quick decision call.' This is harder to say than 'we decided X' but much more useful, because it surfaces the underlying problem (unmade decision) instead of perpetuating the assumption (decision that was made and forgotten). Managers will remember the surface much better than the cover.

Try it now — free

Never lose a decision again — paste the transcript when it happens

The Debrief takes the original meeting transcript and produces the structured decision record you wish you'd had at the time: decisions with owners, action items with deadlines, UNASSIGNED items flagged, and tensions captured. Run it on the original meeting and the artifact you needed for the recovery question is already there.

Structured decision records — what was decided, who drove it, what's pending Distinguishes real decisions ('we agreed to') from soft ones ('someone said we should') Boss Update mode: 3–5 sentence upward summary you can forward as-is Series mode: paste recurring meetings to spot decisions that keep getting revisited Works retroactively — paste a transcript from three weeks ago and recover the decisions
Open The Debrief → No account required to get started.

Found this useful? Link to it.

https://deftbrain.com/guides/meetings/what-to-do-when-your-manager-asks-what-did-we-decide

Free to read, no account, no paywall — link away.

Related situations

💡 Missing something?

Didn’t find what you need? Suggest a tool. We read every suggestion, and the best become new tools.

📮 Newsletter

One useful tool a month — the one worth knowing about before life demands it.