Playbook No. 07 — Published Friday Oct 23, 2026
Board reports in an afternoon. One repeatable afternoon that turns the pile you already have — bank numbers, program counts, your own notes — into a board packet every number in which can be traced back to its source.
Most board reports are late for the same reason: they are treated as a writing project that starts from a blank page. They are not. A board report is an assembly job. The facts already exist in your accounting system, your program records, and your calendar. What is missing is a fixed order of assembly, a rule that no number travels without its source, and one page — the decisions page — that tells the board what you actually need from them. Build the assembly line once and the report stops being a monthly emergency.
Time to run it: about 3 hours the first time, about 90 minutes once the template and source pile exist — our editorial estimate, not a measured result. Cost: $0 with tools you already have. Cadence: once per board cycle.
One folder for this cycle, five things in it, nothing else: (1) the latest financials exported from your accounting system, (2) the program numbers exported from wherever you actually track them, (3) last cycle's board report, (4) your own running notes since the last meeting, and (5) the list of decisions you need from this board. Rule for the whole playbook: if a number is not in the source pile, it does not go in the report — not from memory, not from an AI's memory, not from last quarter's packet. This is the step that prevents the classic board embarrassment: a confident figure nobody can produce the source for when a director asks.
Before any narrative, fill a single page with the handful of numbers your board watches every cycle — cash on hand, revenue against budget, people served against target, and whatever two or three measures your own board has chosen to track. Same page, same order, every cycle. Directors read by comparison; a dashboard that changes shape each quarter forces them to re-learn the report instead of reading the organization. If a measure has no source-pile number this cycle, print "not yet available" rather than an estimate — a visible gap builds more trust than a smooth guess.
Now, and only now, bring in an AI assistant. Give it the source pile and a plain instruction in your own words: draft the narrative sections from these documents only; attach the name of the source document to every number you use; where the documents don't answer something, write "not in source material" instead of filling the gap. Draft the three standard sections: what happened in programs, what the money did, and what changed since last cycle. What the AI is good at here is turning exports and notes into readable prose in your structure. What it must never do is supply a fact. Keep the instruction in writing with the template — it is part of the control, not a tip.
Read the draft with the source pile open beside it and check only two things: every number against its named source, and every sentence that claims something happened against your notes. Delete — do not soften, delete — any number whose source you cannot find in under a minute. The executive director signs this report; the signature means the numbers, and the numbers are the part a board, a funder, or an auditor will test. Prose can be imperfect. A wrong figure in a signed board packet cannot.
The last page, and the one that makes boards feel briefed instead of buried: three short lists. Decisions we need — each with the recommendation and the date it is needed by. Risks we are watching — each with what you are doing about it. What we need from you — introductions, expertise, a vote, in plain terms. Write this page by hand, without the AI draft. It is the judgment page, and judgment is the one part of the packet that is definitionally yours. Include one standing line while you are here, if it is true for your organization: what AI tools staff are using on mission work, and who would stop them and how if one misbehaved. This week's Frontier section is why that line now belongs in a board packet — see below.
Send the dashboard and decisions page at the front of the packet, the narrative behind them, and archive the source pile with the packet. Next cycle, Step 1 is mostly done: refresh the exports, add new notes, reuse the template. That is where the afternoon shrinks to 90 minutes — not from writing faster, but from never starting from a blank page again.
The one action: this week, before your next report is due, build the empty template — dashboard page, three narrative headings, decisions page — and start the source pile with this month's financial export. The template built calmly is the entire playbook; everything else is filling it in.
The steelman for the skeptics: "My board does not want an AI-written report, and neither do I." Fair — and this playbook agrees with the underlying point. The board is not getting an AI's report; it is getting yours, assembled faster, with a stricter source rule than most hand-written reports ever face. The AI drafts prose from documents you chose, every number is checked by you against its source, and the judgment page is written by hand. If your board has a policy against AI drafting at all, run the same six steps without Step 3's tool — the source pile, the fixed dashboard, and the decisions page are the discipline; the drafting help is only the speed.
Published Friday, October 23, 2026. The Issue #7 newsletter edition wraps this playbook and lands in inboxes separately — browse the newsletter archive. This page is the playbook itself, frozen as published: playbooks never change after they go up. If a better way appears, it gets a new number, not a rewrite.
Free forever. One playbook every Friday.
Back to the shelf · ← Playbook No. 06 — Jobs & dignity · Playbook No. 08 — Never miss a caller →
One tested AI playbook per issue — for grant writing, donor thank-yous, volunteer scheduling, board reports — you can put to work the same day you read it. Free. One email per issue. Unsubscribe anytime.