Case file / E.01 · Concept build
Delegation Ledger
Every meeting an executive records gets read once for the asks they handed to other people. What comes back Wednesday at 8:00 is a ledger of everything still owed to them, who owes it, when it was due, and for anything late, a nudge drafted in their own voice. Two minutes to approve, and nothing they delegated goes quiet.
The Problem
Executives hand out asks all day. Get me the two options by Tuesday. Have the offer ready to sign Wednesday. Send me the pipeline numbers before my nine o'clock. Most of them land. The ones that do not are rarely forgotten by the person who owes them. They are forgotten by the person who is owed, because nobody wrote the ask down on the executive's side of the table.
What that costs is a week. An answer promised to a landlord slips. A candidate waits on an offer letter. A customer call happens without the pricing it needed. Meeting tools capture action items for the team. Almost nothing captures what the executive is waiting on.
The gap between the number of asks an executive makes in a week and the number anyone tracks back to them is where this lives.
The Solution
The read is a language model over the transcript, scoped to the asks the executive made of a named attendee, with the owner, the words and the deadline carried on each line. A keyword list cannot do this, because nobody says I delegate out loud. The same ask arrives as can you get me, have it ready, hold two dates, or bring me a venue.
Then a person reads it before the executive does. I close what a later meeting says has landed, merge the same ask made in two rooms, and write the nudge for anything late or due today, in the executive's voice, with the item, the date and why it matters. Everything else is listed so nothing goes quiet.
The executive approves. They never chase.
The Ledger
This is what arrives at 8:00 on Wednesday. Late and due-today asks carry their nudge, ready to send. Everything on track sits in a list beneath. Anything that landed since Friday, or was asked twice, is listed once at the bottom and never appears again.
How it runs
Four steps, and the executive touches the last one.
- Record. The meeting tool already in use writes the transcript it already writes. Granola, Gemini, Otter, Fireflies. The transcript is an input, never a dependency.
- Extract. Only the asks the executive made of someone else, never the promises they made themselves. Those belong on the Commitment Brief. Each one carries an owner, the executive's words and a due date.
- Filter. A human closes what landed, merges duplicates, and writes each nudge before the page is built. This is the step that makes the page worth opening.
- Deliver. One page, Wednesday at 8:00, with the messages already drafted. No new inbox, no new app, no notification stream.
The one pager
The executive summary of the system, on one page, the way it would be handed to a principal who has ninety seconds.
