Foundation Report Handoffs

The report isn't the problem - the coordination is

The grant report is due in 30 days. Program has the outcomes, finance has the numbers, development owns the funder relationship - and nobody is quite sure who owns what, which figures are verified, or which attachments are approved. That gap is where deadlines slip and unverified claims sneak into a funder submission.

This skill closes the gap. It is built for ownership and evidence handoff, not generic grant writing. Give it whatever you have - even a pasted funder instruction and a deadline - and your agent returns a complete coordination control pack, ready to run across every reporting cycle.

What you get in every pack

1. A reporting-readiness position - what's known, what's missing, the deadline, and the main coordination risk, with a plain truth boundary: it's an internal prep tool, not proof of compliance or acceptance
2. A funder requirement map - funder instructions normalized into a table (requirement, evidence needed, owner, reviewer, due date, status, source) with honest status flags (CONFIRMED / NEEDS SOURCE / MISSING / IN REVIEW / APPROVED / BLOCKED)
3. An ownership & RACI map - who is Responsible, Accountable, Consulted and Informed for each input, before any drafting starts
4. A missing-input queue - every gap with owner, request date, due date, blocker level (P0/P1/P2) and next move
5. Copy-ready request messages - initial request, reminder, escalation, finance validation and final approval - each ready to send
6. Claim-to-evidence & attachment controls - flag every claim without a source, figure without a finance check, story without consent, and attachment without a known owner or version
7. Seven review gates + an approval-ready handoff summary - source, program, finance, evidence, privacy/consent, development and leadership gates, ending in a compact status block that always reads NOT SUBMITTED until a human confirms

Why it works

It encodes how clean reporting actually happens: ownership before drafting, stateful tracking of every missing input, staged requests instead of chaotic email threads, and evidence controls that catch unsourced claims before a funder does. It is reusable cycle after cycle.

And it is safe by design: it never invents outcomes, beneficiary stories, budgets, dates, funder rules or approvals; it never backdates evidence or certifies compliance; it minimizes personal and beneficiary data; and it converts any legal, tax or audit question into a verification question for the qualified person. Unknowns stay as placeholders and status flags - never fake facts.

Works for nonprofits, funded projects and program teams reporting to any foundation or post-award funder.

Text-only skill: no scripts, no network calls, zero extra permissions. Tested on Claude.