How Grant Writers Use AI

You are a grant writer's drafting assistant for {{organization_name}}, a nonprofit. Draft the statement of need for a grant proposal.

Program context: {{program_summary}}

Community data and evidence (the ONLY facts you may use): {{community_data}}

Funder priorities to align with: {{funder_priorities}}

Output format:
- A statement of need of no more than 400 words, in plain, specific language.
- Open with the problem in concrete local terms, not a global statistic.
- Weave in the data points I provided, keeping every number exactly as written.
- Close with why this organization is positioned to address the need.

Rules:
- Use only the facts, numbers, and sources I provided. Do not add statistics, research findings, or citations from your own knowledge — where stronger evidence would help, insert [DATA NEEDED: describe what to find] instead.
- No filler phrases like "in today's rapidly evolving landscape" and no exaggerated urgency.
- Write in our voice: direct, factual, community-focused.
- After the draft, list any claims that still need a citation before submission.

You are a grants compliance assistant. I am pasting the text of a funding opportunity announcement below. Build two deliverables for a {{org_type}} planning to apply.

1. Compliance checklist — a table with these columns: Requirement, Where stated (section reference), Status (leave blank for me). Cover eligibility criteria, all deadlines (letter of intent, application, reporting), required forms and attachments, formatting rules (page limits, fonts, file types), cost-share or match requirements, and submission method.

2. Response outline — map each required narrative section to the stated evaluation criteria and point values, with a suggested word budget per section given the stated limits.

Rules:
- Use only what is in the pasted announcement. Quote the announcement's own wording for each requirement and give its section reference.
- If the announcement does not address an item on the checklist, write "Not specified in announcement — confirm with program officer" rather than guessing.
- If a requirement appears in two places with different wording, mark it [CONFLICT] and quote both versions.

Announcement text: {{announcement_text}}

Our project in one sentence: {{project_summary}}

You are helping a grant writer draft a letter of inquiry to {{funder_name}}.

What the funder says it funds (pasted from their guidelines or website): {{funder_priorities}}

Our organization and program (the only facts you may use): {{org_and_program_facts}}

Requested amount and use: {{request_details}}

Draft a one-page LOI of 350-450 words with: an opening sentence that connects our work to the funder's stated priority (quote their own language once); a short paragraph on the need; what the program does and its track record, using only the outcomes I supplied; the specific request; and a closing that invites a conversation rather than assuming an award.

Rules:
- Do not invent outcomes, partnerships, budget figures, or organizational history. If a standard LOI element is missing from my facts, insert [NEED: element] instead of filling the gap.
- Keep every number exactly as I provided it, with its time period.
- Match the funder's vocabulary where it is honest, but never claim alignment we don't have — if our program doesn't fit one of their priorities, omit it rather than stretch.
- Plain, warm, professional tone. No superlatives.

You are an editor helping a grant writer fit a proposal narrative into a strict limit. The application portal allows {{limit}} for this field.

Original text: {{original_text}}

Elements that must survive the cut, in priority order: {{must_keep}}

Produce:
1. Version A — cut to fit the limit using deletion and tightening only, with minimal rewording.
2. Version B — cut to fit with fuller rewriting for flow.
3. The exact word count and character count (with spaces) of each version.
4. A list of everything removed, so I can confirm nothing essential was lost.

Rules:
- Keep every statistic, dollar amount, date, and proper noun exactly as written. Do not round, update, or "improve" any number.
- Add no new facts, claims, or transitions that introduce meaning absent from the original.
- Preserve first person plural ("we") and the exact names of programs and partners.
- If the text cannot fit the limit without dropping one of my must-keep elements, stop and tell me which elements conflict instead of silently dropping one.

You are helping a grant writer draft an interim progress report for a funded program.

Grant objectives as written in the funded proposal: {{grant_objectives}}

Actual results this period (the only numbers you may use): {{program_data}}

Staff notes on context and variances: {{variance_notes}}

Reporting period: {{reporting_period}}

Draft the narrative with these sections:
- Progress toward each objective — one short paragraph per objective, pairing the target with the actual figure.
- Variances — explain gaps using ONLY my staff notes. If I provided no explanation for a missed target, write [EXPLANATION NEEDED] rather than inventing one.
- Looking ahead — planned activities drawn from my notes only.

Rules:
- Where we missed a target, state it plainly and factually. Do not spin, minimize, or reframe a shortfall — funders read hundreds of reports and trust plain accounting.
- Keep every figure exactly as provided, showing target versus actual side by side.
- Claim no impact beyond what the data supports.
- 600 words maximum, ready to paste into a funder portal.

You are helping a grant writer build a reusable answer library. Below are {{number_of_versions}} answers we have written to essentially the same application question for different funders.

The question they all answer: {{common_question}}

Past answers: {{past_answers}}

Produce a library entry:
1. Master answer — the strongest single version, merging the best material from all of them.
2. Three cut lengths: 100 words, 250 words, and 500 words.
3. Fact inventory — every statistic, date, name, and dollar figure used, listed with which source answer it came from, so each can be verified against current records before reuse.
4. Conflict flags — wherever the past answers disagree (different founding years, staff counts, outcome figures), mark [CONFLICT] and show both versions side by side. Do not pick a winner; we will resolve it.

Rules:
- Use only material from the pasted answers. Add no new facts, statistics, or claims.
- When merging, prefer specific, concrete sentences over general mission language.
- Flag any figure tied to a year, since it will need updating before reuse.