# Who promised what, and is it done?

Every meeting summary's decisions and action items land in one place: who promised what, by when, and whether it is done. Customer requests are grouped by how often they come up, and a weekly update writes itself from what really happened.

[Video: Life → Open loops: promises grouped by when they are due, a past-due promise, decisions and customer requests.](https://www.earlyn.app/video/clips/clip-loops)

## Promises, by when they are due

Life → Open loops lists the promises from your meetings under Past due, This week, Later and No date. An action item like “Deniz — send the changelog — Thursday” gets Deniz as the owner and the Thursday after the meeting as the due date, in English or Turkish. Tick it when it is done. Once a day, Earlyn tells you how many promises are past due.

## Decisions you can find again

“Why did we pick the yearly plan?” Every decision is kept with the meeting it came from, searchable, and Chat uses them when you ask about a week.

## The voice of the customer

Summaries also note what the other people asked for or complained about. Requests that say the same thing are grouped, the most asked first (“asked in 3 meetings”), and Send to Linear files one as an issue after you confirm.

## A weekly update that writes itself

The “Weekly update for stakeholders” agent runs on Fridays: progress per project with real hours, the decisions, the promises and their status, risks and next week, from the facts Earlyn computed. Nothing is invented.

## Questions

### Where do the promises come from?

From the action items of your meeting summaries. Summarize a meeting again and its open items are updated; the ones you marked done stay done.

### Can Claude Code or Codex read them?

Yes, through the open_loops tool of Earlyn's local MCP server.

---
Canonical: https://www.earlyn.app/features/open-loops · Updated 2026-10-05