# Grant Narrative Architecture > Activate whenever the task involves writing, structuring, reviewing, or strengthening a grant proposal, funding application, letter of inquiry, needs statement, or any document requesting philanthropic, government, or foundation funding. Trigger on "write a grant," "review my proposal," "needs statement," "LOI," RFP responses, and budget narratives. Fire BEFORE drafting begins — grant narratives built without the funder's scoring logic in hand are written for the writer, and funders do not fund writers; they fund alignment. - Skill: `forexgod21/grant-narrative-architecture` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add forexgod21/grant-narrative-architecture` - Raw SKILL.md: https://api.skillmd.com/api/skills/forexgod21/grant-narrative-architecture/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Finance & Business - License: CC BY 4.0 - Author: Forexgod21 (https://skillmd.com/u/forexgod21) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/forexgod21/grant-narrative-architecture --- # Grant Narrative Architecture **Attribution:** YourVisionYourCreation LLC — yourvisionyourcreation.com **Doctrine class:** YVYC original — nonprofit category --- ## Universal So-What A grant proposal is not a description of your organization — it is an argument that a funder's money, moved through your program, produces the change the FUNDER exists to make. Proposals fail in a predictable way: they narrate the applicant's passion when the reviewer is holding a scoring rubric. This architecture builds the narrative on the rubric's skeleton, because reviewers fund what they can score. --- ## Core Doctrine ### 1. Funder Intelligence Before First Word No drafting until this file exists: - **Priorities:** the funder's stated mission and current funding priorities — in THEIR language, harvested from their materials - **Scoring logic:** the rubric, review criteria, or evaluation weights if published; the RFP's structure and emphasis if not — section point values dictate word allocation - **Portfolio scan:** what they have actually funded (past grantees, award sizes, geographies) — their behavior outranks their brochure - **Fit verdict:** honest, in writing — a mismatch pursued anyway costs the organization the hours AND the funder relationship. Declining to apply is a strategic act. ### 2. The Needs Statement — Evidence, Proximity, Gap The needs statement carries the proposal, and it has three load-bearing walls: - **Evidence:** the problem quantified with current, cited data — local data beating national data every time the program is local - **Proximity:** why THIS organization credibly holds this problem — lived connection, track record, community trust; proximity is the asset grant writers most often forget to claim - **Gap:** what existing services do NOT cover — the needs statement ends at the hole this program fills, not at "the problem is big" - The cardinal rule: the need belongs to the COMMUNITY, never the organization. "We need funding" is not a need. "Veterans in this county wait eleven weeks for peer support" is a need. ### 3. The Golden Thread One unbroken line through the entire proposal: ``` Need → Target population → Activities → Outputs → Outcomes → Evaluation → Budget ``` - Every activity traces back to the need and forward to an outcome - Every budget line traces to an activity — a budget item with no narrative anchor is a red flag reviewers hunt for sport - Every outcome has an evaluation method attached - The thread audit runs both directions before submission; a break anywhere is where the score dies ### 4. Outcomes Language Discipline - **Outputs** are what the program DOES (sessions held, people served). **Outcomes** are what CHANGES (employment gained, symptoms reduced, housing retained). Funders buy outcomes; outputs are the receipt. - Outcomes are specific, measurable, time-bound, and HONEST — a promise the program cannot measure is a liability in year-end reporting, and funders remember reporting failures longer than they remember proposals - Attribution modesty: claim contribution the program can defend, not transformation it cannot isolate ### 5. Budget as Narrative - The budget tells the same story as the prose, in numbers — a reviewer reading budget-first (many do) should reconstruct the program from it - Justification for every line: basis of estimate, not merely amount - Sustainability question answered before it is asked: what happens when this grant ends? "We will seek more grants" is the weakest legal answer; diversification, earned revenue, or institutional absorption are answers. - Indirect/overhead honest and within the funder's stated policy — lowballing overhead to look lean starves the organization the grant is meant to strengthen ### 6. The Compliance Gate and Reviewer's Read - The RFP's checklist is extracted into a compliance matrix on day one: every required element, format rule, page limit, attachment, and deadline — tracked to done. Disqualification on technicality is the most preventable failure in the field. - Before submission, the reviewer's read: one pass, timed, reading ONLY what a tired reviewer reads — headings, first sentences, bolded claims, budget totals. If the proposal does not score on the skim, the deep read never comes. --- ## Common Failure Modes | Failure | Cause | Correction | |---|---|---| | Beautiful proposal, no award | Written to the writer's passion, not the rubric | Funder intelligence file before drafting | | "Need" reads as organizational hunger | Community need never separated from org need | The need belongs to the community — always | | Reviewer flags budget-narrative mismatch | No golden thread audit | Both-direction trace before submission | | Year-end report cannot show promised change | Outcomes overpromised or unmeasurable | Outcomes discipline: measurable, honest, attributable | | Disqualified on format | No compliance matrix | RFP checklist extracted day one | | Skim-read scores low | Argument buried in paragraphs | Reviewer's-read pass: headings and first sentences carry the case | --- ## Non-Negotiables 1. Funder intelligence before the first drafted word. 2. The need belongs to the community, never the organization. 3. The golden thread is audited in both directions. 4. Outputs and outcomes are never conflated. 5. Every budget line has a narrative anchor and a basis of estimate. 6. The compliance matrix is complete before submission — no technicality disqualifications. --- *YourVisionYourCreation LLC — yourvisionyourcreation.com* *Licensed under CC BY 4.0*