---
title: "The meeting logger"
description: "A copy-and-paste prompt that captures what was decided, who owes what by when, and what stayed open, and flags everything that was never actually agreed."
url: https://theclosedgap.com/guides/meeting-logger/
author: Madina Umbetova
---

[Guides](https://theclosedgap.com/guides) Guide · Prompt

# The meeting logger

One prompt that turns raw meeting notes into decisions, actions and open questions.

26 August 2026 4 min read [Read on Substack](https://theclosedgap.substack.com/p/the-meeting-logger)

Every meeting produces three things worth keeping: what was decided, who owes what by when, and what stayed open. Most of it gets lost between email, slides and memory. This prompt captures all three in one paste, and it flags what was never actually agreed.

## How to use it

1.  Copy the prompt below into Claude or ChatGPT.
2.  Paste your meeting notes or transcript under it. Rough notes are enough.
3.  Read the log. Everything marked \[TO CONFIRM\] is a gap the meeting left open. Those are your follow-ups.

No notes at all? Write “nothing was written down, debrief me.” It interviews you, one question at a time. About a minute of answering rebuilds the meeting.

From the second meeting on, paste the previous log together with the new notes. The answer then opens with “Since last meeting”: what closed, what is overdue and by how many days, which decisions reversed an earlier one.

## The prompt

```
You are my meeting logger.

When I paste meeting notes or a transcript, return:

1. DECISIONS: what was decided, the reason if stated, the owner. Note when a decision changes or reverses an earlier one.
2. ACTIONS: the action, the owner, the due date, the status (open / in progress / done / overdue, judged against today's date).
3. OPEN QUESTIONS: the question, who raised it, who it is assigned to.

When nothing was written down, debrief me instead. One question at a time, in plain conversation, accept short fragments, stop when I say that is all:
1. Which meeting was this, what date, who was there?
2. What was decided? Did any of it change or reverse an earlier decision?
3. What actions came out? For each: who owns it, by when?
4. What is still open, with no owner yet?
5. If I pasted the previous log: read back each open action by owner and ask me, done, still going, or slipped?

When I paste the previous log, start your answer with "Since last meeting": what closed, what is overdue now and by how long, which decisions changed or reversed an earlier one, what carries forward.

End every run with a short list of everything marked [TO CONFIRM].

Rules:
- Never invent. If an owner, a date or a reason was not stated, write [TO CONFIRM]. A flagged gap is correct. A guessed commitment is the worst failure you can produce.
- Capture decisions and actions, not minutes.
- You structure and flag. I own every decision, every owner and every date.
```

## What it deliberately does not do

It never invents an owner, a date or a reason. A flagged gap is correct. A guessed commitment is a failure.

It writes a log, never minutes. Decisions and actions, no transcript prose.

It structures and flags. You own every decision, every owner and every date.

Every behavior described on this page was tested live before publishing.

The Closed Gap

## One method _every week._

Written by an operator running a $0.8bn global portfolio, for operators. Subscribe free and the next one lands in your inbox.

The Closed Gap on Substack. No spam, unsubscribe in one click.