impact-report-writer
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.
What this skill does
# Impact Report Writer
Frameworks for creating compelling impact reports that communicate program outcomes, organizational effectiveness, and social change to stakeholders, funders, and the public.
## Impact Report Structure
### Standard Report Template
```
IMPACT REPORT: [Organization Name]
Reporting Period: [Fiscal Year / Program Period]
1. LETTER FROM LEADERSHIP (1 page)
- Personal voice from ED/CEO
- Year's theme or narrative arc
- Highlight 1-2 major achievements
- Thank supporters
2. MISSION AND VISION (half page)
- Mission statement
- Vision statement
- Theory of change (brief)
3. YEAR IN NUMBERS (1-2 pages — highly visual)
- 5-8 key metrics as large callout numbers
- Simple icons or graphics per metric
- Year-over-year comparison where relevant
- Geographic reach map (if applicable)
4. PROGRAM HIGHLIGHTS (3-5 pages)
For each major program:
- Program description (2-3 sentences)
- Key outcomes with data
- Beneficiary story/testimonial
- Photo or visual element
5. STORIES OF IMPACT (2-3 pages)
- 2-3 detailed beneficiary narratives
- Before/during/after arc
- Direct quotes
- Respectful, consent-based storytelling
6. FINANCIAL SUMMARY (1-2 pages)
- Revenue by source (pie chart)
- Expenses by category (pie chart)
- Program vs admin ratio
- Year-over-year financial comparison
- Key financial health indicators
7. DONORS AND SUPPORTERS (1-2 pages)
- Donor acknowledgment lists (by tier)
- Partner organizations
- Volunteer recognition
- In-kind supporters
8. LOOKING AHEAD (1 page)
- Next year's goals
- Strategic priorities
- Call to action for supporters
- How to get involved
```
## Metrics and Outcomes
### Output vs Outcome vs Impact
| Level | Definition | Example | Measurement |
|-------|-----------|---------|-------------|
| **Outputs** | What you did / produced | "Served 500 meals" | Activity logs, counts |
| **Outcomes** | What changed for beneficiaries | "85% reported reduced food insecurity" | Surveys, assessments |
| **Impact** | Long-term systemic change | "Neighborhood child malnutrition rate dropped 15%" | Population-level data |
### Metrics Selection Framework
```
METRICS FRAMEWORK:
REACH METRICS (How many?):
- People served: ______
- Communities reached: ______
- Programs delivered: ______
- Hours of service: ______
- Volunteers engaged: ______
DEPTH METRICS (How much change?):
- % showing improvement: _____%
- Average change in [indicator]: ______
- Completion/graduation rate: _____%
- Satisfaction score: ______/10
DURATION METRICS (How lasting?):
- 6-month follow-up retention: _____%
- 12-month sustained outcomes: _____%
- Recidivism/relapse rate: _____%
- Long-term tracking data: ______
EFFICIENCY METRICS (At what cost?):
- Cost per beneficiary served: $______
- Cost per outcome achieved: $______
- Program expense ratio: _____%
- Fundraising efficiency: _____%
COMPARISON:
- Year-over-year change: _____%
- Benchmark vs similar orgs: ______
- Goal vs actual: ______
```
### Year-in-Numbers Page Design
```
YEAR IN NUMBERS LAYOUT:
[Large number] [Icon] [Label]
12,500 [people] People Served
[Large number] [Icon] [Label]
94% [chart] Satisfaction Rate
[Large number] [Icon] [Label]
$2.3M [dollar] Programs Delivered
[Large number] [Icon] [Label]
85% [arrow] Showed Improvement
[Large number] [Icon] [Label]
47 [map pin] Communities Reached
[Large number] [Icon] [Label]
1,200 [hands] Volunteer Hours
DESIGN RULES:
- Maximum 8 metrics on one page
- Use the largest, most impressive numbers
- Round to clean numbers (12,500 not 12,487)
- Include one comparison ("up 23% from last year")
- Use consistent icon style
- White space between metrics
```
## Data Visualization Guidelines
### Chart Selection Guide
| Data Type | Recommended Chart | When to Use |
|-----------|------------------|-------------|
| **Part of whole** | Pie or donut chart | Revenue by source, expense breakdown |
| **Comparison** | Bar chart (horizontal) | Program outcomes side by side |
| **Change over time** | Line chart | Multi-year trend data |
| **Before/after** | Paired bar chart | Pre-post program comparison |
| **Geographic** | Map with color coding | Where programs operate |
| **Single metric** | Large callout number | Year-in-numbers hero stats |
| **Progress** | Progress bar or gauge | Goal completion percentage |
| **Ranking** | Horizontal bar (sorted) | Top programs by outcome |
### Visualization Best Practices
```
DATA VIZ RULES FOR IMPACT REPORTS:
DO:
✓ Start bar charts at zero
✓ Label data points directly (avoid legends when possible)
✓ Use organization's brand colors
✓ Include data source and date
✓ Round numbers for readability
✓ Use consistent scales across similar charts
✓ Make charts accessible (alt text, patterns not just color)
DON'T:
✗ Use 3D charts (distorts perception)
✗ Use more than 5-6 colors in one chart
✗ Include raw data tables (summarize visually)
✗ Use pie charts with more than 5 slices
✗ Truncate axes to exaggerate change
✗ Present data without context or comparison
```
## Storytelling Framework
### Beneficiary Story Template
```
IMPACT STORY TEMPLATE:
TITLE: [Compelling, human-centered headline]
THE CHALLENGE (2-3 sentences):
[Describe the situation before your intervention]
[Include specific, relatable details]
[Build empathy without exploiting vulnerability]
THE JOURNEY (3-5 sentences):
[How the person connected with your program]
[What services/support they received]
[Key moments of growth or breakthrough]
[Direct quote from the beneficiary]
THE OUTCOME (2-3 sentences):
[Measurable change in their situation]
[How their life is different now]
[Forward-looking statement about their future]
PULL QUOTE:
"[Powerful direct quote that captures the transformation]"
— [First name], [program name] participant
ETHICAL STORYTELLING CHECKLIST:
[ ] Informed written consent obtained
[ ] Story reviewed and approved by subject
[ ] Subject chose how to be identified (name, photo)
[ ] Story preserves dignity and agency
[ ] Subject is portrayed as active, not passive
[ ] No poverty porn or exploitation of vulnerability
[ ] Cultural context respected
```
## Financial Transparency
### Financial Summary Template
```
FINANCIAL SUMMARY: FY [Year]
REVENUE: AMOUNT %
Government grants $________ ___%
Foundation grants $________ ___%
Individual donations $________ ___%
Corporate sponsorship $________ ___%
Program/earned revenue $________ ___%
Other $________ ___%
TOTAL REVENUE: $________ 100%
EXPENSES: AMOUNT %
Program services $________ ___%
Management and general $________ ___%
Fundraising $________ ___%
TOTAL EXPENSES: $________ 100%
KEY RATIOS:
Program expense ratio: ___% (target: >75%)
Admin expense ratio: ___% (target: <15%)
Fundraising expense ratio: ___% (target: <10%)
Revenue growth (YoY): ___%
Operating surplus/deficit: $_______
Months of operating reserves: ___ months
NOTES:
- Audited financial statements available upon request
- [Organization] is a 501(c)(3) tax-exempt organization
- EIN: [Number]
```
## Report Design Guidelines
### Accessibility and Readability
```
DESIGN STANDARDS:
TYPOGRAPHY:
- Body text: 11-12pt minimum
- Headlines: 18-24pt
- Call-out numbers: 36-72pt
- Line spacing: 1.4-1.6
- Maximum line width: 75 characters
COLOR:
- Use brand colors consistently
- Ensure 4.5:1 contrast ratio for Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.