Waiting On

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

• Waiting sweep runs daily · 8am and keeps the Waiting On dashboard fresh. Daily — finds what your sent mail is still waiting on.
• What is captured lands in the Waiting register dataset, which lives at Data/Waiting Register in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the What you owe dataset, which lives at Data/What You Owe in your vault — yours to open, search, and edit like any other file.
• The Waiting On dashboard reads from the dataset and shows, at a glance: waiting by person · waiting vs resolved · chases drafted · waiting longest · what you owe · how this board works · resolved this week.

The wiring, in one breath: Waiting capture writes to Waiting register · Waiting sweep writes to Waiting register · Waiting register shown by Waiting On · Waiting On kept fresh by Waiting sweep · Chase drafts reads Waiting register · Asks from a chat or call writes to Waiting register · Asks from a chat or call hands over to Keep what you owe · Keep what you owe writes to What you owe · What you owe shown by Waiting On · When a chase fails writes to Waiting register · When a chase fails hands over to Chase drafts.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

• Say what you are owed the moment you ask for it — "asked Northwind for the contract" — and Waiting capture registers it. The daily sweep also finds what your sent mail is still waiting on.
• Read Waiting longest first. The oldest open items are where a chase pays.
• When something arrives, say so, or let the sweep see the reply. The row closes and the list stays true.
• Ask for the chase rather than writing it. Chase drafts writes the polite nudge into your drafts, in your voice, and never sends — you decide.
• Tell Registrar what does not count as waiting — an FYI, a newsletter reply — so the register holds only the things that genuinely block you.
• Asked for something in a chat or on a call? Paste the thread, or tell Registrar which note or recorded call in your vault to read, and Asks from a chat or call files what you asked that nobody answered and what someone promised you. It cannot see your chat apps, your texts or your calls, so it finds only what you hand over.
• When a chase gets no answer, say so. When a chase fails lays out what you can do as facts (chase again, ask on another channel, ask someone else, or let it go), says how long it has been from the thread, and does only the one you pick. It does not choose for you, and nothing is sent.
• Say what you owe as you say it: "Marta asked me for the figures by Thursday". Keep what you owe puts it on What you owe, and the list on the board is the one you tick. It holds only what you tell it or hand it: it does not read your inbox, and it sets no reminder.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, datasets and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

• What ageing threshold makes something worth chasing.
• How a chase reads — brisk, or warm and apologetic.
• Whether replies mark things resolved automatically.
• Which people or threads never get chased.
• Who you would ask instead when a chase gets no answer, and how a note on another channel should sound.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

1. Installing ends on one screen with one honest ask: let it read your email, and Registrar's first sweep reads a month of your own sent mail for asks that never got an answer — building the register while you watch. It's a real run, so it uses credits like any other.
2. This kit doesn't bring its own keeper — it borrows Meetings': Registrar reads and keeps the register, and drafts the chases. Install both kits and there's still one Registrar, shared between them.
3. When the sweep finishes, Registrar leaves a note with what it found. Some asks may have been settled elsewhere — a call, a corridor — so the first conversation is striking those out together, and naming who should never be chased.
4. Say "not now" instead and Registrar builds the register by hand: tell it who owes you what, and the board ages it from there. Your email is never asked for again.
5. Chases are only ever drafts, in your voice once you've set it — nothing is sent by the kit, ever.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits