---
title: "Nonprofit executive board report writer"
type: "skill"
url: "https://useaiblocks.com/skills/nonprofit-executive-board-report-writer"
updated: "2026-10-28"
first_published: "2026-10-25"
job: "Lead and manage people"
tested: true
licence: "MIT"
source: "https://github.com/sector-skills/nonprofit-skills/tree/7d8a2ca9d471fc975d0e9ccd02fcdd66520fd1c8/nonprofit-skills-library/skills/executive-leadership/nonprofit-ceo-board-partnership"
instructions: "https://useaiblocks.com/skills/nonprofit-executive-board-report-writer/SKILL.md"
---

# Nonprofit executive board report writer

> Turn board goals and current results into a report with clear decisions and next steps.

Share board goals, checked results and open issues. Get a draft report with facts to review, choices to make, risks and owners for next steps.

Free skill for the job "Lead and manage people" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28

## Links

- Page: https://useaiblocks.com/skills/nonprofit-executive-board-report-writer
- Instructions (SKILL.md): https://useaiblocks.com/skills/nonprofit-executive-board-report-writer/SKILL.md
- All files (zip): https://useaiblocks.com/skills/nonprofit-executive-board-report-writer.zip
- JSON version: https://useaiblocks.com/skills/nonprofit-executive-board-report-writer.json
- In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get nonprofit-executive-board-report-writer"

## What it does

Bring the board’s goals, results and open issues. Draft the executive’s report, chair agenda or review memo with evidence and clear requests.

## What you give it

- Your board's written goals, limits and expectations
- Your last board packet and dashboard
- Your approved budget and results so far
- Decisions the board must make at the next meeting
- Open risks and past commitments (optional)

## What you get

- A board report that lists every decision requested at the top
- Results reported against your board's written limits, with problems named early
- A short narrative that does not repeat the dashboard
- A chair meeting agenda, executive-session notes or a self-evaluation memo
- A meeting debrief note with owners and follow-ups

## Example: what goes in and what comes out

### What goes in

- Your board's written goals, limits and expectations
- Your last board packet and dashboard
- Your approved budget and results so far
- Decisions the board must make at the next meeting
- Open risks and past commitments (optional)

### What comes out

- **Decisions requested**: Each decision the board is asked to make at this meeting, in one sentence each, or a clear note that there are none.
- **Generative question**: A real strategic question for the board to discuss, with why you raise it now and what input you want.
- **Exception reporting**: Where you are inside or outside the board's written limits and goals, with the worst news stated early.
- **Executive narrative**: A short story of what changed and why, tied to evidence, without repeating the dashboard in prose.
- **What was left out**: Detail cut because the board cannot act on it, plus any appendix items marked read if interested.
- **Chair 1:1 agenda or executive-session notes**: A standing call agenda or talking points for when staff and guests leave the room.
- **Board-meeting debrief**: A post-meeting note to the chair with follow-ups, owners and commitments.

## Use it when

- Your board packet is due and you need the executive narrative.
- You want talking points for the executive session.
- You need an agenda for your next call with the board chair.
- Your annual review is coming and you must write your own self-evaluation memo.

## Skip it when

- You run the board itself, or write bylaws, committee plans or board job descriptions: use a board governance adviser or your board chair.
- You need a note for all staff or for funders: write it as a plain message from the executive, not as a board report.
- You are planning a CEO handover: use a transition plan with your board chair, not a board report.

## How to use it

1. Open Claude, ChatGPT or Gemini and paste in the skill instructions. No code or paid tool is needed.
2. Paste your goals, limits, last packet, dashboard, budget and open decisions.
3. Say which item you want: board report, chair agenda, executive-session notes, self-evaluation or debrief.
4. Check that the decisions block is on page one and that every number matches your own records.
5. Fill any gap your AI marks as missing before you send the packet. Send it 5 to 7 days before the meeting.
6. Your board report becomes part of the governance record, so have a person review it first.

## What to do next

- [Nonprofit board meeting and role planner](https://useaiblocks.com/skills/nonprofit-board-meeting-and-role-planner): Lead the team
- [Nonprofit change rollout planner](https://useaiblocks.com/skills/nonprofit-change-rollout-planner): Lead the team
- [One-on-one agenda and feedback planner](https://useaiblocks.com/skills/weekly-one-on-one-prep-keeper): Lead the team
- [Work commitment and follow-up writer](https://useaiblocks.com/skills/executive-work-keeper): Work commitment and follow-up writer
- [Executive meeting brief writer](https://useaiblocks.com/skills/executive-meeting-brief): Executive meeting brief writer

## Sources and credits

- From sector-skills: https://github.com/sector-skills/nonprofit-skills/tree/7d8a2ca9d471fc975d0e9ccd02fcdd66520fd1c8/nonprofit-skills-library/skills/executive-leadership/nonprofit-ceo-board-partnership, shared under the MIT licence (original name: nonprofit-ceo-board-partnership).
- [nonprofit-ceo-board-partnership skill](https://github.com/sector-skills/nonprofit-skills/tree/7d8a2ca9d471fc975d0e9ccd02fcdd66520fd1c8/nonprofit-skills-library/skills/executive-leadership/nonprofit-ceo-board-partnership), sector-skills: Original instructions and supporting files, with attribution and the MIT licence. Display copy describes the task.
- [AI Blocks catalogue guidance](https://useaiblocks.com), AI Blocks: We added Before you start and After this sections that link to other AI Blocks steps. We refreshed those generated sections from the catalogue inputs and next-step links.

## Instructions (SKILL.md)

## Nonprofit CEO ↔ Board Partnership (Executive Side)

<!-- needs: written by tools/add-needs.mjs for AI Blocks; not part of the original skill. Edit that tool, not this section. -->
### Before you start
Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait.

**What you need** (use your own material or the linked skill):
- **A document** (yours): a finished document, such as a Word file, a PDF or a page of notes.

**Makes it better (optional):**
- **Your data** (yours): the data files, with their format and where they came from.
- **Financial statements** (yours): the income statement, balance sheet and cash flow statement, for the periods you have.
- **A plan** (yours): the goals, steps, constraints and dates for this work.

How to start:
1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name.
2. **Check what's missing.** Look for a document, your data, financial statements. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps.
3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it.
<!-- /needs -->

### When to Use This Skill

Use this skill when the user is sitting in the **CEO / executive director seat** (or staffing that
seat as chief of staff, or coaching a CEO as an advisor) and needs to produce or improve an
artifact the CEO owns toward the board: the monthly/quarterly **board report** and dashboard
narrative, **executive-session** talking points, the standing **board-chair 1:1** agenda, the
**CEO self-evaluation memo** and response to the board's written evaluation, or the framing of a
**generative-mode** conversation the CEO wants the board to have. Trigger phrases include: "help
me write my board report," "what should I put in exec session," "agenda for my 1:1 with the
chair," "we do the CEO review without written criteria," "the board got blindsided last meeting,"
"I need a good generative question," "coach my chair on consent agenda," or "draft my CEO
self-evaluation."

Boundary: this skill is the **executive's side of the table**. Board-side work — running the
board itself, designing committees, board self-assessment, board member job descriptions, bylaws
and policies, recruiting or onboarding directors, or Form 990 Part VI governance disclosure — is
`nonprofit-board-governance`, `nonprofit-board-recruitment`, `nonprofit-bylaws-policy`, or
`nonprofit-form-990`. Transition in or out of the CEO role (first-90-days plan, resignation
sequencing, interim CEO handoff) is `nonprofit-executive-transitions`. All-staff, funder, or
public-facing CEO messages are `nonprofit-executive-communications`.

### Core Frameworks

Name the model the CEO is operating under before drafting artifacts — the same board report reads
very differently against Carver-style limits vs. a traditional approval board.

- **BoardSource CEO–board partnership model**: the CEO and board share responsibility for mission,
  strategy, resources, and impact; the board holds the CEO accountable for results while the CEO
  equips the board to govern. The CEO's job is not to *report to* the board but to *partner with*
  it — supplying the information, framing, and questions the board needs to do its own governance
  work well.
- **Chait, Ryan, and Taylor — "Governance as Leadership" (three modes)**: high-functioning boards
  move fluidly between three modes of work, and the CEO's job is to signal which mode a given
  agenda item lives in.
  - **Fiduciary mode** — stewardship of assets, legal/financial oversight, compliance monitoring.
    Handled by consent agenda and exception reporting where possible.
  - **Strategic mode** — shaping strategy with the CEO, choosing among defined options, allocating
    resources. Handled by decision items with pre-read analysis.
  - **Generative mode** — sense-making about ambiguous, upstream questions ("what is the problem
    we are actually solving?"). Handled by a framed generative question, not a memo asking for a
    vote.
- **Carver "Executive Limitations" discipline as it shows up in CEO reports**: even boards that
  don't formally adopt Policy Governance benefit from the CEO reporting **against written
  limits/expectations** — "here is the boundary the board set; here is the evidence I stayed
  inside it (or didn't, and why)." This converts the CEO report from a status update into a
  monitoring instrument the board can actually act on.
- **Consent-agenda discipline**: routine items (minutes, standard financials within tolerance,
  policy renewals with no changes, committee reports with no exceptions) are bundled into one
  motion, pulled off only on request. The CEO's job is to be honest about what belongs on consent
  and to resist the temptation to bury a controversial item there.

### Standard Deliverables

Every request in scope resolves into one of these artifacts:

- **CEO board report / dashboard narrative** — the written narrative that accompanies the
  dashboard in the packet.
- **Executive-session talking points** — what the CEO says (and does not say) when staff and
  guests leave the room.
- **Board-chair 1:1 agenda template shape** — the recurring structure of the standing chair call.
- **CEO self-evaluation memo** — the CEO's written input into the annual evaluation cycle.
- **Board-meeting debrief** — the CEO's post-meeting note back to the chair (and to self) that
  turns the meeting into learning and follow-up.

### Producing the CEO Board Report — Numbered Checklist

Run this checklist every packet cycle. The failure mode is treating the report as a status log
instead of a governance instrument.

1. **Audience**: name the actual reader. It is the seated board plus (usually) the auditor and
   sometimes lead funders. Write for a director who has 20 minutes and no operational context —
   not for the program team.
2. **Decisions requested**: state, at the top, every decision the board is being asked to make at
   this meeting, in one sentence each ("Approve the FY27 operating budget of $X"; "Authorize the
   chair to sign the lease amendment"). If the answer is "none," say so explicitly.
3. **Generative question(s)**: offer at least one framed generative question tied to a real
   strategic ambiguity — not a rhetorical prompt. Say why you are bringing it now and what kind of
   input you want (sense-making, red-teaming, prioritization), not a vote.
4. **Exception reporting against limits/goals**: report against the written expectations the board
   already set — budget vs. actual with variance thresholds, strategic-plan milestones, executive-
   limitation-style boundaries (cash floor, key-person concentration, compliance obligations). Say
   where you are inside the limit; say plainly and early where you are outside it.
5. **What to leave out**: operational detail the board cannot act on, program anecdotes without a
   governance implication, restatement of the dashboard in prose, and anything already covered in
   a committee report unless it needs a full-board decision. If the reader would say "why am I
   reading this?", cut it.
6. **Packet-page-count discipline**: cap the CEO narrative at roughly 2–4 pages plus the
   dashboard; cap the full packet so a diligent director can pre-read it in under 90 minutes. Move
   deep-dive material into appendices flagged as "read if interested," not into the main flow.
   Land the packet 5–7 days before the meeting; late packets guarantee that the meeting is spent
   reading, not governing.

### Dashboard vs. Narrative

The **dashboard** shows the numbers and the trend. The **narrative** does three things the
dashboard cannot: (1) tell the board *what changed and why* since last meeting, (2) name the
exceptions and the CEO's planned response, and (3) surface the one or two things the CEO wants
the board to think about that are not yet on any metric. If the narrative just repeats the
dashboard in sentences, delete it and reclaim the packet space.

### Executive-Session Preparation

Executive session (board only, no staff — sometimes CEO in, sometimes CEO out) is where CEO
evaluation, compensation, sensitive personnel/legal matters, and candid board-to-board
conversation happen. From the CEO seat:

- **Ask for it on the agenda every meeting, even briefly**, so it is a habit rather than a signal
  that something is wrong. A standing 10-minute exec session with the CEO in, followed optionally
  by a short session with the CEO out, normalizes the practice.
- **Prepare talking points for both configurations**: what you want the board to know when you are
  in the room (typically: a candid read on 1–2 risks, one ask of the board, and any topic you'd
  rather not put in the written packet); and what you expect them to discuss when you step out
  (typically: your performance, compensation, or a board-only concern).
- **Minute discipline**: only the fact that the session occurred and its general subject go in the
  minutes; substantive discussion does not, unless legally required.
- **Never run exec session reactively** — do not let the first exec session of the year be the one
  called because something went wrong.

### Board-Chair 1:1 Agenda Shape

The standing chair 1:1 (typically 30–60 minutes, every 2–4 weeks, more often between meetings)
carries most of the real CEO-board partnership work. A reusable shape:

1. **Personal check-in** (5 min) — this is a working relationship, not a transaction.
2. **Look-back**: what happened since we last spoke that the chair needs to know (heads-up items,
   not a status dump).
3. **Look-ahead to the next board meeting**: draft agenda, decisions requested, generative
   question in development, anything the chair should socialize with directors in advance so
   nothing lands cold.
4. **Directors needing attention**: engagement issues, conflicts, contribution gaps, upcoming
   term rolls — the chair, not the CEO, owns board-to-board management, and the 1:1 is where the
   CEO hands those signals over cleanly.
5. **CEO asks**: what the CEO needs from the chair before next meeting (a call to a director, a
   framing decision, air cover on a topic).
6. **Chair asks of the CEO**: leave real time for this; a 1:1 that is 100% CEO agenda is a signal
   the partnership is one-directional.

### Annual CEO Evaluation Cycle — From the CEO's Side

The board owns the evaluation, but a CEO who lets the board improvise it will get an improvised
result. Drive the process from the executive seat without controlling the outcome.

- **Pre-set criteria (before the review period)**: at the start of each cycle, propose written
  goals and evaluation criteria to the chair/executive committee — tied to the strategic plan,
  board-approved annual priorities, and executive-limitation-style boundaries. Get them adopted
  in writing. Retroactively invented criteria are the single biggest source of unfair CEO reviews.
- **CEO self-evaluation memo**: 3–6 pages, written to the board. Structure: (1) recap of the
  criteria set at the start of the period; (2) evidence against each, with metrics and named
  outcomes, honest about misses; (3) organizational health signals the board should weigh
  (finance, staff, program, risk); (4) the CEO's own view of development areas for the coming
  year; (5) proposed goals for the next cycle. Submit it *before* the board's evaluation
  deliberation, not after.
- **360 input request**: if the process includes 360 input from direct reports, board members,
  and/or key external partners, the CEO can (and should) actively request it be run by the chair
  or an outside facilitator, with a defined instrument and confidentiality rules — not ad hoc
  phone calls. Name the respondent pool and the questions in advance.
- **Response to the written evaluation**: after receiving the board's written evaluation (usually
  from the chair on behalf of the board, in executive session), the CEO's move is a short written
  response: what you accept, what you contest and why, what you commit to, and the goals proposed
  for the next cycle. This response goes into the CEO file alongside the evaluation.
- **Compensation is a separate conversation**: it uses the IRS rebuttable-presumption-of-
  reasonableness process (independent body, comparability data, contemporaneous documentation)
  owned on the board side — do not let performance and compensation collapse into a single
  hallway conversation.

### Managing Up as a Governance Body

The CEO reports to the **board as a whole**, not to individual directors. Rogue direction from a
single director — even the chair — is a governance problem, not a CEO problem to absorb
silently. The CEO's tools:

- Channel all direction back through the chair and full-board votes; when a director tries to
  direct staff work, route the request to the chair with a note.
- Treat committee chairs as the board's delegates, not as parallel bosses; a committee's
  authority is whatever the board's written charter says it is, no more.
- Do not build private information channels to favored directors. Every director should have the
  same version of the truth as of the last packet and the last chair 1:1.

### Generative-Mode Conversations Initiated by the CEO

The generative-mode conversation is the highest-leverage thing a CEO can put on a board agenda,
and the one boards most often flinch away from. To make one land:

1. **Frame the ambiguity, not the answer**: "We are seeing three signals that suggest our theory
   of change may be shifting — I want the board's sense-making on whether we are seeing the same
   thing before we scope a strategy refresh."
2. **Say what you are asking for and what you are not**: "I am not asking for a vote or a decision
   today. I am asking for 40 minutes of structured discussion using [method]."
3. **Choose a method appropriate to the room**: silent-then-share, small-group-then-plenary, a
   pre-read with three provocations — anything that prevents the loudest director from setting
   the frame.
4. **Close the loop in the next packet**: report back what the CEO heard, what it changed, and
   what comes next. A generative conversation with no follow-up trains the board that generative
   time is optional.

### Consent-Agenda Coaching (CEO to Chair)

The chair runs the meeting, but the CEO builds the packet — so the CEO shapes what is on consent.
Coach the chair to: (1) actually call for the consent motion as a single motion, not read each
item aloud; (2) explicitly invite any director to pull any item off consent before the vote; (3)
resist expanding consent to hide controversial items (a fast way to lose trust); (4) keep
minutes, standard financials within tolerance, routine policy renewals, and non-exception
committee reports on consent; keep decisions with real dollars, real risk, or real dissent off it.

### Board-Meeting Debrief

Within 48 hours of every board meeting, send the chair a short written debrief and keep a copy in
the CEO file: what got decided, what got deferred and why, what surprised you, what the board
seemed most/least engaged by, follow-up commitments (yours and directors'), and one thing to do
differently next meeting. This is the artifact that turns a series of meetings into an actual
CEO-board partnership over time.

### Common Failure Modes

- **Surprise items in the packet** — a decision, financial variance, or personnel issue appears
  in the packet with no prior heads-up to the chair. Fix by socializing anything material in the
  chair 1:1 first; the meeting is not the moment to break news.
- **Dashboard-vs-narrative confusion** — the narrative just restates the dashboard in prose,
  wasting packet space and telling the board nothing new. Fix by making the narrative do only
  what the dashboard cannot: explain change, name exceptions, surface not-yet-metric concerns.
- **No explicit decisions requested** — the packet describes a lot and asks for nothing, so the
  board defaults to advisory-committee behavior. Fix by putting a "Decisions Requested" block on
  page one of the CEO report every cycle, even if the answer is "none this meeting."
- **No generative question offered** — the board sees only fiduciary and (rarely) strategic
  content, and never gets to do generative work, so it either drifts into micromanagement or
  disengages. Fix by putting one framed generative question on the agenda at least every other
  meeting.
- **Executive session run reactively** — the first exec session of the year is called because
  something went wrong, which makes exec session itself feel like an alarm. Fix by scheduling a
  short standing exec session every meeting so it becomes routine.
- **CEO evaluation done without pre-set criteria** — the board evaluates against whatever
  directors remember, which is unfair to the CEO and useless to the organization. Fix by getting
  written criteria adopted at the *start* of the review period and submitting a self-evaluation
  memo before the board deliberates.
- **Reporting to individual directors instead of the board** — the CEO ends up with several
  parallel bosses and no coherent direction. Fix by routing all substantive direction through the
  chair and the full board, in writing.

### Practitioner vs. Advisor Framing

- **As the CEO/ED (or chief of staff drafting for one)**: rebuild the packet before you rebuild
  the board. Most "our board isn't working" complaints from the CEO seat are actually packet-
  discipline and chair-1:1-discipline problems: no decisions requested, no generative question,
  surprise items, dashboard-not-narrative, and no debrief loop. Fix those four cycles in a row
  before you propose committee restructures or bylaws changes. Own the CEO evaluation process
  from the executive seat — pre-set the criteria in writing, submit the self-evaluation memo, and
  respond to the written evaluation in writing — without trying to control the board's judgment.
- **As an advisor to a CEO/ED**: name which model the board is operating under (BoardSource
  partnership, Governance as Leadership, Carver/Policy Governance, or traditional approval) and
  align the artifacts to it before critiquing them; a Carver board reads a status-update report
  as noncompliance, and a traditional board reads a limits-only report as evasive. Push the CEO
  to move at least one agenda item per cycle into generative mode and to fix the chair 1:1 cadence
  before touching the full-board meeting design — most CEO-board pain lives between meetings, not
  in them.

<!-- next: written by tools/add-needs.mjs for AI Blocks; not part of the original skill. Edit that tool, not this section. -->
### After this
When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own:
- The [Nonprofit board meeting and role planner](https://useaiblocks.com/skills/nonprofit-board-meeting-and-role-planner). It takes the document.
- The [Nonprofit change rollout planner](https://useaiblocks.com/skills/nonprofit-change-rollout-planner). It takes the document.
- The [One-on-one agenda and feedback planner](https://useaiblocks.com/skills/weekly-one-on-one-prep-keeper). It takes the meeting notes.
- The [Work commitment and follow-up writer](https://useaiblocks.com/skills/executive-work-keeper). It takes the meeting notes and document.
- The [Executive meeting brief writer](https://useaiblocks.com/skills/executive-meeting-brief). It takes the meeting notes.
If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.
<!-- /next -->
