A grant writer can use eight ChatGPT prompts across a bid: needs statement, project description, aims and objectives, outcomes with indicators, a risks table, a sustainability paragraph, a plain-English summary and a reviewer-style critique. Feed each one your verified evidence, then check every figure, source and promise against the original before it reaches a funder.
ChatGPT writes fluent grant prose and will happily invent a plausible statistic to fill a gap. That is the danger in this work, so each prompt below comes with a sample output and a short verification checklist for that specific output. The order follows a real application, so you can work through it top to bottom.
Set up the evidence pack before the first prompt
Do this once per bid. Create a one-page document called the evidence pack and put into it only things you can point to: the organisation's own figures (people served, waiting list, sessions delivered), published statistics with the exact source and year, quotes from beneficiaries that you have consent to use, and the funder's stated priorities copied from the guidance. Number each item E1, E2, E3.
Every prompt below tells ChatGPT to use only items from that pack and to cite them by number. A draft that says "(E3)" after a claim is easy to check; a draft with an unreferenced percentage is a red flag. Remove the reference numbers once the facts are verified and the funder's format does not need them.
The plan you draft on matters for confidentiality. On a personal ChatGPT account (Free, Plus or Pro) the setting called "Improve the model for everyone" starts switched on, and you turn it off under Settings, then Data controls; OpenAI's help page adds that it does not train on content from Business, Enterprise and Edu workspaces by default. If you write bids for clients, a business workspace or a strict redaction habit is the safer option: replace organisation names, beneficiary details and unpublished figures with placeholders, and put them back in your own document. For a comparison of what dedicated tools add, see the best AI app for grant writing.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowNeeds statement: built only from the evidence pack
The needs statement is where invented statistics do the most damage, because reviewers check them. Never ask for "statistics about youth unemployment". Instead, give the model what you have and ask it to shape it.
You are helping a grant writer draft a needs statement of about 350 words.
Funder priority (copied from guidance): [paste]
Evidence pack (use ONLY these items, cite each by number):
E1: [our own data, with date]
E2: [published figure, source name and year]
E3: [beneficiary quote, consent confirmed]
E4: [local gap we have observed, described plainly]
Rules:
- Every factual claim must end with its evidence number, for example (E2).
- If a claim needs evidence that is not in the pack, write [EVIDENCE NEEDED] instead of inventing it.
- Do not add statistics, percentages, study names or quotations of your own.
- Structure: the problem, who is affected, why existing provision falls short, why now.
- Plain English, no jargon, no "vulnerable" without saying who.
Illustration: a community bicycle workshop applying for a small grant to run free repair sessions for people who commute by bike on low incomes. The pack holds E1 (the workshop turned away 64 people in the last quarter because slots were full), E2 (a published travel survey figure with its source) and E4 (the nearest repair shop is 5 miles from the estate). A sample output, labelled illustrative:
Many residents on the estate rely on bicycles for the daily journey to work, but repairs are out of reach for those on low incomes. In the last quarter the workshop turned away 64 people because all sessions were full (E1). The nearest commercial repair shop is five miles away (E4), which adds a bus fare or a long walk to every repair. [EVIDENCE NEEDED: figure for how many residents commute by bike.] A free, drop-in service closes that gap.
The [EVIDENCE NEEDED] flag is the model behaving well. A weaker draft would have filled it with a percentage. Your job is to supply a sourced number or rewrite the sentence without one.
Verify: tick off each (E#) against the pack; confirm the pack figure was copied correctly, including units and dates; search the draft for any digit that has no evidence number beside it; check that "turned away" in the draft means what your records mean, not "enquired".
Project description: activity a reviewer can picture
Reviewers score on whether they can imagine the project running. The prompt below forces concrete detail: who does what, where, how often, and what the participant experiences. Supply the plan; do not let the model design it.
Write a project description of about 300 words from my plan below. Do not add activities.
Plan:
- Weekly drop-in, Saturdays 10:00-14:00, community hall
- Two trained volunteers plus one paid coordinator (15 hours a week)
- Participants bring a bike; we fix it with them, teaching one skill per visit
- Tools and spares budget in the application: [amount]
- Start date [date], 40 sessions in the first year
Write in the future tense ("participants will..."). Open with what a participant experiences.
Mark any detail missing from the plan as [DETAIL NEEDED].
A sample output opens: "A participant wheels in a bike with a flat tyre and leaves knowing how to mend one." Good openings like that are the model's strength. Its weakness is padding: you will often see "a welcoming, inclusive environment" with no evidence behind it. Replace phrases like that with something observable, for example "tea is provided and a volunteer greets every arrival by name".
Verify: count sessions, hours and staff against the plan; confirm the budget figure matches the budget sheet; remove any activity you did not list; check dates against the funder's project window.
Aims and SMART objectives with targets your team set
Many forms ask for one aim and three to five SMART objectives (specific, measurable, achievable, relevant, time-bound). ChatGPT is good at tightening loose wording into that shape, provided you give it the numbers.
Turn these rough goals into one aim and four SMART objectives.
Rough goals: [paste]
Targets I can actually deliver: [numbers I have confirmed with the delivery team]
Funding period: [dates]
Rules: use only my targets, one measurable result per objective, start each with a verb,
no objective may promise more than my target. List any goal you could not make measurable.
A sample objective from the same workshop: "Deliver 40 drop-in sessions between April and March, with at least 8 participants repairing their own bike at each session." Note how the target (8) came from the team. If the model had chosen 20, the objective would look more impressive and then be impossible to meet. Compare each number to last year's attendance before accepting it.
Verify: ask the delivery lead whether each number is achievable with the staff and hours in the budget; check every deadline falls inside the funding period; make sure each objective can be reported on later with data you actually collect.
Outcomes versus outputs, each with a measuring method
An outcome is a change in people's lives; an output is something you deliver. Funders mark down applications that confuse the two. The prompt asks the model to separate them and to name how you would measure each, using methods you already use.
Separate outputs from outcomes for this project and add an indicator and measurement method for each outcome.
Project: [two-sentence summary]
Data we already collect: [sign-in sheets, a short end-of-session form, follow-up call at 3 months]
Rules: only use measurement methods from my list; do not invent baseline figures;
mark baseline as [BASELINE NEEDED] if I have not given one. Put the result in a table.
| Type | Item | Indicator | Method |
|---|---|---|---|
| Output | Drop-in sessions held | Number of sessions | Sign-in sheet |
| Output | Bikes repaired | Number repaired | Repair log |
| Outcome | Participants can fix a puncture | Share who say yes at end of session | End-of-session form |
| Outcome | Participants keep cycling | Share still cycling at 3 months | Follow-up call |
This is the shape of a sample output, labelled illustrative. The baseline column was left as [BASELINE NEEDED] by the model. That is correct: you cannot claim improvement without a starting point, and inventing one is the fastest way to lose reviewer trust.
Verify: confirm that each measurement method is already in use or in the budget; check that outcomes describe a change rather than an activity; make sure the targets match the SMART objectives you approved earlier. For a longer walk-through of the whole sequence on one bid, AI prompts for grant writing with a worked example goes further.
A delivery-risk table specific to this project
Generic risks ("lack of funding", "staff turnover") read as filler. Ask the model for risks specific to the project description, and ask it to rank them by likelihood and impact, so the reviewer sees you have thought about delivery.
From the project description below, list six delivery risks specific to this project, each with likelihood (low/medium/high), impact, and one mitigation that uses resources already in the plan.
Do not suggest mitigations that cost money not in the budget.
Project description: [paste]
A good sample row: "Volunteer drop-out reduces sessions below the two-volunteer minimum. Likelihood medium, impact high. Mitigation: coordinator keeps a reserve list of four trained volunteers and cancels a session rather than running it with one." A weak row would be "Lack of engagement. Mitigation: engage more." Delete anything that reads like that.
Verify: check each mitigation really exists in the plan; remove any mitigation that promises extra spend; ask a colleague who delivers the project which risk you missed. They usually spot one within a minute.
Sustainability: what continues and what stops
Funders want to know what happens when the grant ends. The temptation is to promise match funding or income streams that do not exist. Hand the model your real plans and ask it to describe them without inflation.
Write a 120-word sustainability paragraph.
What will continue after the grant: [volunteer trained pool, tools bought, partnership with the community hall]
What will need new funding: [coordinator hours]
Funding routes we are genuinely pursuing: [names of schemes we have applied to or will apply to]
Rules: do not claim any funding is secured unless I say so; state honestly what would stop if no new funding arrives.
The sentence about what stops if no funding arrives is the one models omit and reviewers like most. A sample: "The tools and the trained volunteers remain; sessions would drop from weekly to monthly without the coordinator's hours."
Verify: check that no funding source is described as secured unless you hold a letter; confirm any partnership with a named body is in writing; read the paragraph aloud and ask whether a trustee would sign it.
The summary box, compressed from approved sections
The summary box on most forms is read first and sometimes read alone. Ask the model to compress the finished sections, not to write from scratch, so the facts are already approved.
Summarise the application in 100 words for a reader who will read nothing else.
Use only the text below. Include: the problem, what we will do, who benefits, how many people, how much we are requesting, and the main outcome.
Do not add any claim that is not in the text. Text: [paste the final needs statement, project description and outcomes]
Summaries are where numbers drift. A sample output might round 64 turned-away people to "dozens" or turn "40 sessions" into "weekly sessions all year". Compare every number with the approved sections. If you need to check the compressed version against the source line by line, paste both into a new chat and ask: "List any claim in the summary that is not in the full text." This second pass is cheap and catches most drift.
Verify: the amount requested matches the budget to the dollar; the number of beneficiaries matches the objectives; the summary promises nothing the outcomes table does not.
An assessor's-eye critique before you press submit
The last prompt switches the model from writer to scorer. Paste the funder's criteria and the full draft and ask it to mark it as a sceptical assessor would. This is the most useful prompt for finding gaps, because you are no longer asking it to be creative.
Act as a grant assessor using the scoring criteria below. Score each criterion out of 5 with one sentence of reasoning,
quote the exact sentence from the draft that supports the score, and list the three weakest points.
Do not rewrite anything. Criteria: [paste]. Draft: [paste]
Illustrative output: "Criterion 2, evidence of need: 3 out of 5. The draft relies on one local figure (E1) and gives no published comparison. Weakest points: no source for commuting numbers; the risk table repeats the sustainability paragraph; the outcomes lack baselines." Treat the scores as prompts for thought, not truth: the model has no idea how a real panel behaves. The quoted sentences are the useful part.
Verify: check that each quoted sentence actually appears in the draft (models sometimes misquote); take the three weakest points to a human reader; fix the gaps with real evidence, not new prose.
The fabricated-statistics check in four steps
Run this over the whole application once all eight outputs are merged. It takes about 30 minutes on a 3,000-word bid.
- Highlight every number. Percentages, counts, years, monetary amounts, ratios. In a word processor, search for digits and mark them.
- Trace each one. Next to each number write where it came from: pack item, budget sheet, delivery log, funder guidance. If you cannot name the source, delete the number or find one.
- Check each named source exists. Open the document or page and confirm the figure and year. Models invent report titles and attribute real-sounding statistics to real-sounding organisations.
- Check each quote. Compare quoted beneficiaries or officials against your original notes, including consent.
A realistic mistake: an early draft said "research shows that 78% of free repair sessions lead to long-term cycling". The writer had asked for "supporting research" in an earlier prompt. No such research was in the pack and none could be found. The sentence went. If you only take one habit from this tutorial, make it never to ask a chat model for evidence, only to arrange evidence you hold.
Cost per beneficiary: a sum the reviewer will do anyway
Assessors divide the amount requested by the number of people reached, so do the sum before they do. Say the workshop asks for $9,600 and the objectives promise 40 sessions with at least 8 participants each. That is 320 participant visits, or $30 a visit. If the same people return, the number of distinct people is lower and the cost per person higher, so state which you mean. Ask ChatGPT only to format the sum, never to choose the denominator:
Write two sentences explaining the cost per participant visit and the cost per unique participant.
Use these figures exactly: requested [amount], sessions [number], expected visits per session [number], expected unique participants [number].
Do not round, estimate or add comparisons with other projects.
Illustrative output: "The request of $9,600 equates to $30 per participant visit across 320 visits. With an expected 120 unique participants, the cost per person is $80." Check the arithmetic yourself with a calculator. Language models are unreliable at multi-step sums, which is why the prompt tells it not to round and why you should recompute. If you want to see why, why AI is bad at maths shows what goes wrong in quotes and invoices.
Repairing one over-confident outcomes sentence
This is the edit you will make most often. The first draft of an outcomes paragraph read: "Our programme transforms lives, improving wellbeing and employability for hundreds of young people." Three problems: "transforms lives" cannot be measured, "hundreds" contradicts the 120 unique participants in the objectives, and "employability" appears nowhere in the outcomes table.
Ask the model to repair it with the problem named, not just "make it better":
Rewrite this sentence so every claim matches the outcomes table below. Remove any claim the table does not support. Keep it under 30 words.
Sentence: [paste]
Outcomes table: [paste]
The result, illustrative: "By the end of the year, an expected 120 residents will have learned to repair a bicycle and 60% will report still cycling after three months." Notice that the 60% is a target from your own plan, not a prediction the model made. If your plan has no target, the sentence should not carry a percentage.
Matching the funder's own wording without copying it
Scoring grids use specific words: "need", "impact", "value for money", "partnership". Paste the criteria and ask the model to list which words from the criteria appear in each section of your draft. Where a criterion has no matching section, add a sentence from your own evidence; do not let the model write one. This keeps your application aligned with what is scored while the substance stays yours.
Confidentiality and funder rules around AI drafting
Two separate questions arise. First, what may you share with the tool? Keep beneficiary names, case notes, unpublished accounts and the client's internal strategy out of any personal-plan chat. Use placeholders such as [ORG], [AREA] and [AMOUNT] and restore them offline. If you hold a client's confidentiality clause, read it before using any AI tool, and tell the client how you work.
Second, what does the funder expect? Published policies differ more than most writers assume. One large public research council expects applicants to be open about substantive generative-AI use, such as summarising data, comparing literature or generating an abstract, says minimal use such as improving the English or cutting the word count needs no declaration, and bars generating whole sections without human involvement. Another major public research funder says it will not treat applications substantially developed by AI as the applicant's original ideas. Many smaller trusts and foundations say nothing at all. Read the guidance for each programme, note exactly what it asks you to declare, and keep a line in your bid file recording what you used AI for, so the declaration is quick and accurate if one is required. Whether funders reject AI-assisted bids covers what they have said publicly. Whatever the funder's policy, you are the author of record: if a figure is wrong, the funder will not blame the tool.
For free-tier and low-cost options, free AI for grant writing compares what ChatGPT, Claude and Gemini give you on their free plans, which matters if you are a small organisation writing your own bids.
Saving the eight prompts so they work for the next bid
Keep the eight prompts in one document, each with its rules block and its verification list. Store the evidence-pack template there too. For the next bid, copy the file, clear the pack and start again. Do not keep old evidence in the pack: statistics age, and last year's figure sitting in a template is how stale numbers reach a new application.
Track time. A typical split for a small bid is about 90 minutes of evidence gathering, 45 minutes prompting and tidying, 60 to 90 minutes verifying, and 30 minutes on the reviewer-style critique. If verification is shorter than drafting, you are probably trusting the output too much. If you want help setting up a routine like this for a team, that is the kind of work my AI implementation consultation covers.
Questions grant writers ask about using ChatGPT on bids
Will ChatGPT invent statistics in a needs statement?
Yes, it can produce plausible figures and citations that do not exist. Never ask it to supply evidence. Give it the figures and sources you have already verified, and tell it to write [EVIDENCE NEEDED] wherever a claim has no source in your pack.
Can I paste a client's application into ChatGPT?
Only on a plan and under a contract that allow it. On a personal plan, data may be used for training unless you switch that off, so use placeholders and keep beneficiary details out. Business workspaces are not used for training by default, but check your client's terms first.
Do funders mind AI-assisted drafts?
Policies vary and are changing, so read each funder's guidance and application form before you submit. Some ask for a declaration. What every funder cares about is that the facts are true and the organisation can deliver what it promises.
How long should I spend verifying one output?
Budget about as long as the draft took to generate, then some. A 400-word needs statement with six claims usually takes 20 to 30 minutes to source properly. If that sounds too slow, the draft contained too many unsupported claims.
Further reads
- AI Grant Writing Software: What Each Costs a Freelance Grant Writer — See what grant-specific software costs a freelancer.
- Grant Writing AI Agent: What It Can Draft in a Business Grant Bid — Know what an agent can and cannot draft for a bid.
- Questions to Ask Before Buying AI That Touches Client Data — Questions to settle before client data touches any AI tool.
- How to Use ChatGPT as a Business Adviser Without Being Misled — Stay sceptical of confident answers on strategy and facts.
- AI Grant Writing Tools Compared for Small Non-Profits — A wider comparison for small non-profits.
- Can AI Write a Sports Club Grant Application? What Funders Expect — A sports club grant application drafted with AI: what funders assess, how to read their AI rules, and how the committee checks every claim.
- Grant Writer Rates: What to Charge When AI Drafts Faster — Freelance grant writer rates by hour and by project, plus a worked quote showing how AI drafting should change your pricing, and why percentage fees are out.
- Grant Budget Narrative: Draft It With AI and Reconcile Every Figure — Line-by-line budget justification drafted with AI, plus a figures register that proves every number in the narrative matches the spreadsheet.
- Grant Report Template: Draft Funder Reports With AI From Project Data — A filled-in funder progress report drafted by AI from project data: outcomes table, narrative, lessons learned, and the evidence checks before sending.
- Logic Model Template: Build One With AI From a Client's Programme — Build a logic model from a client's programme notes with AI, then gap-check the causal links and match the funder's wording, with a filled example.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: OpenAI Help Center page on data controls in ChatGPT; two public research funders' published policies on generative AI in applications (all checked 4 November 2026).