For organizers of a recurring event, before the next plan is written

Debrief LedgerWhat keeps going wrong every edition, and the one change to make next.

Paste the debrief notes from several editions. Free in your browser: every entry filed through the signal gate, names taken out of the record, the entries grouped into themes and counted by edition - one-off, candidate (two), pattern (three) - each routed to whoever owns it, the three ranked menus re-ranked for your team, the KPI shortlist, the closure pass on last cycle's changes, the audit with its one pass threshold, and a draft learning log. A run writes the trend read, or the learning log the next team inherits. The log format, the occurrence bar and the menus are the skill's own construction, not established organizer practice; every threshold is self-set.

Try a sample:

1 The event and the team free

Event

Editions run (Q1)

With written records

Records today (Q2)

Team turnover since the first record (Q3)

A handover to new people this cycle

Entries in three parts, with owner and date (Q4)

Comparable numbers across editions

A past edition changed something because of a finding

Next planning starts (Q5)

The date, or the go/no-go

Mandate (Q6)

Roughly how many more editions

Hours between editions (Q7)

Someone owns a between-edition job

Where the log lives (Q8)

The one person who opens it before planning

Community A chapter in a peer network of independent communities

2 The debrief notes free

One heading per edition ("## 2024", "Edition 3", "Code Fair 2025 debrief", or "---" between them), one finding per line or bullet - or drop several .md or .txt files here, one per edition

Open files

3 Last cycle, the KPIs, the carry optional

Last cycle's deliberate changes - one per line: what | shipped: yes/no | improved: yes/no, why

KPIs - one per line: name | owner | action | threshold | local or network

Changes to carry into the log - theme | change | check (the trend read fills this)

4 The trends, worked out free

What the page flags

The editions

Themes, counted by edition - one-off, candidate (2), pattern (3)

Hand-offs and change slots

Every entry through the signal gate

The three menus, ranked for this team

The KPI shortlist

The closure pass

The audit, Keep to Delete

5 The draft learning log free

Built only from the de-personalised entries - no name reaches it. The appended-document form, or the structured record's columns when that rung is the pick.

6 The trend read metered

Pricing as soon as the session is ready...

The reply could not be read. Here it is as it came back:

NOT RUN YET

The page's check of this reply

7 Saved ledgers

How it works - and what is sourced

Every entry passes a filing gate borrowed from printing-press-retro: it counts only when it is current, reproducible in this event's own conditions and generalizing. A failure handled at no cost is expected work, filed with its reason and never counted; a condition the event has left is closed, not deleted. Names come out before anything is persisted - "one person forgot" happens once, "no owner and no backup" recurs. Entries are grouped by what would have to change to prevent them, and a theme is counted by the editions it appears in, never by entries: two make a candidate, three a pattern, always out of the editions you hold.

Published organizer practice reaches only the first handover: MLH's keeping-records guide (a running document, a reflection meeting, one handover to next year's team), DevOpsDays' organizing.md (a shared document that survived complete turnover - not a template for a trend log), and Fraser and Mancl's 2023 report (a retrospective after every edition of a conference series). The log format, the occurrence bar, the three menus and the one pass threshold - zero unclassified entries after an audit pass, with the Keep/Update/Consolidate/Replace/Delete classification borrowed from ce-compound-refresh - are the skill's own construction. Every threshold is self-set.