MEMO 04 · RUNS WITHOUT YOU
NEEDS: the router file (Memo 01) · the morning stack (Memo 02) · the decision queue, with shared documents connected (Memo 03) · scheduled runs (Spec Sheet 04)
A check-in should open on the calls the other person has to make. On Ambervale’s* desk this Thursday there are five, and the draft that lists them is built at 8:30 by a run that nobody starts. Before then I read the morning brief and overrule the queue on the lease, and the check-in that comes back puts the five calls on top, in the executive director’s order.
RUNS WITHOUT YOU
A check-in is assembled from a week of messages your AI already reads, so it can be built on a timer, and the draft waits for you.
Three runs on a schedule, a check-in built at 8:30, one pushback line rewritten before it goes anywhere.
The setup
The sections always run in this order.
DECISIONS I NEED FROM YOU
Every call on their list, in their order, each with your recommendation, a needed-by date, and the pushback you expect, with your answer.
DECISIONS I MADE
Your own calls from the week, each with the date it can still be reversed.
MOVED
Deliverables and deadlines, three lines at most.
WAITING
Who, what and since when, leaving out anything above.
WATCHING
One risk that isn’t a decision yet.
The first line names the meeting and its date, so you can check the week. If the first section is empty, it offers to cancel.
A scheduled run has nobody there to attach files, so the router file and saved files need a home it can read: here, a shared folder, through Memo 03’s documents connection. Save them as Google Docs or Word files. Each scheduled task is one line pointing at its file: the brief at 7:00, the check-in at 8:30. Each run is its own session, so the queue’s override reaches the check-in through the dated line in the router file. A run that stops to ask permission waits for an answer, so before the first run, allow its reads and set anything that writes to ask first.
A scheduled brief of mine once made the same formatting bug four mornings in a row, and I fixed the output by hand each time. That was a setup gap: on a schedule the fix goes in the saved file, and the next run gets checked once by hand.
HUMAN LOCK
The run’s pushback line on the instructor offer is about cost. The question I know the executive director will ask is who tells Beatriz, the lead instructor whose raise comes with the offer, and when. I strike the run’s line and write his question, with my answer, before the check-in goes to him. A scheduled run reads and drafts, and nothing it makes leaves my desk until I’ve read it.
The close
The three runs finish early, and the time before the meeting goes to the part only I can write: the answers to the pushback, and whether each recommendation is one I’d defend in the first five minutes. That’s the desk running without you, and the meeting it feeds opens on decisions.
Which recurring meeting on your calendar opens with updates, and what decision is sitting at the bottom of it?
* Ambervale is a fictional nonprofit I use in these memos so I can show real workflows without showing anyone’s real inbox.
Ops Bureau · Memo 04 · 2026-10-22