Charities and not-for-profit · Playbook 53

Grant applications and bid writing

Every bid drafted from the charity's own approved evidence, every figure traced to its source, each funder's terms checked first, and a named person approving before anything is sent.

  • Retrieval (RAG)
  • Generative AI
  • Human in the loop
  • Charity Commission (CC3, CC20)
  • Code of Fundraising Practice
  • Funders' terms
  • Failure to prevent fraud
  • UK GDPR

At a glance

The problem
A small team rewrites every bid from scratch, hunting for figures and stories across folders, under deadline
Typical volume
Around 150 trust, foundation and statutory applications a year, plus reports on the grants already won
Who's involved
Head of trusts and grants, bid writers, service leads, finance, the impact lead, data protection, trustees
Pilot
6–8 weeks on one funding round, after a 2–3 week discovery
Platforms
AWS, Azure, or a sovereign or on-prem stack

An illustrative scenario. The numbers are typical examples, not a client case study. The cloud services and UK rules were checked on 9 November 2026.

The business problem

Grants are a large share of income for many charities, and the work behind them is mostly searching. A bid writer reads the funder's guidance, works out whether the charity is eligible, then hunts for the latest outcomes figures, a case study someone agreed could be used, the right budget lines and the current safeguarding policy. The same facts are rewritten for every funder, in a different word count and a different order.

Figures drift. Last year's number of people supported appears in one bid and this year's in another. A case study is reused after the person's consent has lapsed, or in a way they never agreed to. Budgets in the bid don't match the finance system. None of this is dishonest, but funders notice, and some of it matters legally: government grant agreements usually let the funder claw money back if the application turns out to be inaccurate or misleading.

Funders have also changed. Many report far more applications than before, and some link the rise to AI tools. Experienced assessors say generic AI text is easy to spot: fluent, vague and interchangeable. Some funders now ask whether AI was used, some research funders set clear rules on it, and a few have closed open rounds altogether. A charity that uses AI to send more, weaker bids will lose ground. The aim here is fewer, better-evidenced bids, written faster.

What AI changes

  • Bid writers draft from one approved evidence library: outcomes figures, consented case studies, budgets, policies and organisation facts, each with an owner and an expiry date.
  • Before any writing starts, the funder's guidance and terms are checked: eligibility, deadlines, word limits, what they will and won't fund, and any rules on using AI in applications.
  • First drafts follow the funder's questions and word limits, and every figure, quote and claim links back to its source in the library.
  • Anything the library can't support is marked as a gap for a person to fill, not invented.
  • Service, finance and impact leads confirm their own figures. A named person approves every bid before it is sent.
  • The charity can answer accurately if a funder asks how AI was used, because each answer records what was drafted, what was edited and by whom.

How success is measured

Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.

Time to a first draft

Hours from deciding to apply to a draft ready for editing.

ExampleFrom 3 days to under half a day

Claims with a source

Share of figures, quotes and claims in a sent bid that link to an approved, in-date source.

ExampleEvery one

Figures corrected at sign-off

Figures the approver had to change because they didn't match finance or impact data.

ExampleFalling month on month

Ineligible applications

Bids started for funds the charity didn't qualify for, or that ruled out its approach.

ExampleClose to zero

Draft edit rate

How much writers change the drafts. Very high means it isn't helping; near zero can mean drafts are sent unread.

ExampleStable, and reviewed monthly

Success rate and funder feedback

Awards per application, and what funders say, compared with last year. AI doesn't win bids; this checks it isn't losing them.

ExampleNo worse than last year, then improving

UK regulation and controls

Cross-sector rules are on the UK regulation map.

  • Charity CommissionThe essential trustee (CC3, updated 16 September 2026) and the Commission's view on AI

    Trustees can delegate day-to-day work but not responsibility. The Commission hasn't issued AI-specific guidance; it expects trustees to apply their existing duties, not to rely on AI output for important decisions without reasonable independent checks, and to consider an internal AI policy. The trustees approve the charity's AI policy, and a named person, not the tool, approves each bid.

  • Charity CommissionCharity fundraising (CC20, revised 3 February 2026)

    The revised guidance covers trustees' oversight of fundraising, including grant fundraising and the use of AI, and how it fits with managing fraud and other risks. Report the AI-assisted process to the board like any other fundraising change.

  • Fundraising RegulatorCode of Fundraising Practice (in effect 1 November 2025) and its AI guidance (December 2025)

    Fundraising must be legal, open, honest and respectful, must not mislead, and needs appropriate evidence for claims. Grant applications must be prepared responsibly, and changes to how a grant is spent need the funder's written permission. Case studies must reflect real situations, say if details were changed, and have the person's clear and informed permission. The regulator's AI guidance asks for a person to check accuracy and fairness before use.

  • FundersEach funder's terms, including any rules on AI

    Funders' rules vary and change. UKRI's policy (September 2024), for example, lets applicants use generative AI with care, asks them to declare substantive use, rules out AI writing whole applications or sections without human involvement, and makes applicants responsible for anything falsified, fabricated or misrepresented. Other funders ask for declarations, discourage AI, or say nothing. The fit check reads each funder's current rules before drafting starts.

  • Cabinet OfficeGrants functional standard (GovS 015), grant agreements and the Procurement Act 2023 boundary

    Statutory funders must assess fraud risk and do due diligence on every scheme. The government's model grant funding agreement makes materially misleading or inaccurate information in an application an event of default. If a 'grant' is really a contract for services, it is a procurement, and supplying misleading information is an exclusion ground under the Procurement Act 2023. The library records which is which, as the annual return asks for government grants and contracts separately.

  • Home OfficeFraud Act 2006 and failure to prevent fraud (Economic Crime and Corporate Transparency Act 2023, in force 1 September 2025)

    A knowingly false statement to win a grant can be fraud by false representation. The corporate offence applies to large incorporated bodies meeting two of three tests (over 250 staff, over £36 million turnover, over £18 million assets), including large charitable companies, unless they had reasonable prevention procedures. A mid-sized charity may be below the thresholds, but the evidence check and sign-off log are good practice either way.

  • ICOUK GDPR and the Data Protection Act 2018

    Case studies, outcomes data and staff CVs are personal data, and stories about service users often touch special category data. Only consented, minimised case studies enter the library, consent records travel with them, personal details are checked before indexing, processing stays in UK regions, and the contract stops providers training their models on the charity's data.

The solution

Showing AWSAzuresovereign / on-prem services. Switch with the toggle; every diagram and table on this page follows it.

Grant applications and bid writing: reference architecture
  1. 01Channels

    • Funder guidance and terms
    • Funder portals and forms
    • Funder questions and feedback
  2. 02Intake

    • API GatewayAPI ManagementKong, or your existing API gatewayGrants pipeline events
    • Amazon TextractContent Understanding (Document Intelligence)Docling plus an open-weight vision modelReading funder documents
    • Amazon S3Blob StorageCeph, or IONOS S3 Object StorageBid and evidence store
  3. 03Intelligence

    • Bedrock Knowledge BasesFoundry IQ (Azure AI Search)OpenSearch, or PostgreSQL with pgvectorApproved evidence library
    • Agent
      Bedrock AgentCoreFoundry Agent ServiceLangGraph on KubernetesFunder fit and terms check
    • Agent
      Bedrock AgentCoreFoundry Agent ServiceLangGraph on Kubernetes, with open-weight models via vLLMBid drafting assistant
  4. 04Orchestration

    • Step FunctionsLogic Apps / Durable FunctionsTemporal, or n8nBid workflow and deadlines
    • EventBridge + SQSEvent Grid + Service BusApache Kafka or RabbitMQEvents and queues
  5. 05Systems of record

    • CRM and grants pipeline
    • Finance system and budgets
    • Outcomes data and consent records
  6. 06People

    • Person
      Bid writer: edits and checks every claim
    • Person
      Service, finance and impact leads confirm figures
    • Person
      Named approver signs off
  • Cloud or platform service (AWSAzuresovereign / on-prem)
  • AI agent
  • A person decides
  • Your existing systems
  • Outside your organisation

Components, side by side

Grant applications and bid writing: components on AWS, Azure and a sovereign or on-prem stack
LayerAWSAzureSovereign / on-prem
Intake: funder documents, pipeline eventsEach bid gets its own folder, holding the funder's guidance and terms at the date they were read.API Gateway, S3API Management, Blob StorageKong or your existing API gateway; Ceph or IONOS S3 Object Storage
Reading funder documentsGuidance comes as PDFs, web pages and portal forms. Questions and word limits are pulled out so drafts follow the funder's structure.Amazon TextractAzure Content Understanding (includes Document Intelligence)Open-source parsing (e.g. Docling) plus an open-weight vision model
DraftingBoth clouds offer a choice of models, including Claude. Prompts ask for the charity's own voice and specifics, not generic grant language.Amazon BedrockMicrosoft FoundryOpen-weight models served with vLLM on your own GPUs, or IONOS AI Model Hub
Evidence library (retrieval)Only approved content: outcomes figures with their period, consented case studies, budgets, policies and organisation facts. Each item has an owner and an expiry date.Bedrock Knowledge BasesFoundry IQ, built on Azure AI SearchOpenSearch, or PostgreSQL with pgvector
Personal data check before indexingCatches names and contact details left in case studies or notes before they reach the library. A person reviews what it finds.Amazon Comprehend PII detectionAzure Language in Foundry Tools (PII detection)Open-source PII detection (e.g. Microsoft Presidio)
Agent runtimeThe original Bedrock Agents closed to new customers on 30 July 2026; new builds use AgentCore.Amazon Bedrock AgentCoreFoundry Agent ServiceAn open-source agent framework (e.g. LangGraph) on Kubernetes
WorkflowTracks each bid from fit check to sign-off against the deadline, including who still needs to confirm a figure.AWS Step FunctionsLogic Apps or Durable FunctionsTemporal, or n8n
Middleware and eventsAmazon EventBridge, SQSEvent Grid, Service BusApache Kafka or RabbitMQ
Link to CRM, finance and outcomes dataConsent withdrawn or a figure updated arrives as an event, so the library changes without anyone remembering to tidy it.API Gateway, plus your existing integration platform if you have oneAPI Management, plus your existing integration platform if you have oneKong or your existing API gateway, plus your existing integration platform if you have one
Human reviewWriters edit where they already work. If the charity already uses Microsoft 365, drafts can land in the documents and channels the team already uses.In the team's existing documents and grants pipelineIn the team's existing documents and grants pipelineIn the team's existing documents and grants pipeline
GuardrailsBlocks drafts that state a figure, quote or partner name not found in the library.Bedrock GuardrailsFoundry guardrails (Azure AI Content Safety)Open-source guardrails (e.g. NeMo Guardrails, Llama Guard)
Identity, keys, data protectionWriters see the library, not the case management system behind it.IAM Identity Center, KMS, MacieEntra ID, Key Vault, PurviewKeycloak or your existing Active Directory; OpenBao or HashiCorp Vault; an HSM
Monitoring and auditLog every draft, every source used, every edit and every approval, kept with the bid.CloudWatch, CloudTrailAzure Monitor, Log AnalyticsPrometheus, Grafana, OpenTelemetry
UK data residencyIONOS AI Model Hub runs in German data centres: EU, not UK, residency. Some funders' terms may require UK processing.eu-west-2 (London)UK South / UK WestYour own UK data centre, or a UK or EU provider

On a phone, the table shows the platform you pick. Sovereign / on-prem means open, portable components you can run in your own data centre or with a UK or European provider; IONOS is shown as one example, and others exist. What sovereign cloud means →

Hybrid and on-prem

Many organisations keep core systems and sensitive data on their own servers. This is how the same design works across both.

Stays on-prem

The CRM, finance system and case management system stay where they are, whether hosted by a supplier or on the charity's own servers. Service user records never move into the AI. Only approved outcome figures and consented case studies are copied into the library.

Uses cloud AI

Reading funder documents, the evidence library and drafting run in a UK cloud region, or on the charity's own GPUs for the sovereign option. A charity of this size rarely needs its own GPUs; managed services in a UK region are usually the simpler choice.

How they connect

Through the API layer over encrypted connections, typically a site-to-site VPN for a charity this size, or AWS Direct Connect or Azure ExpressRoute for larger ones. Only library items and bid documents cross the link.

If the link drops

Bid writing carries on by hand, as it did before. Drafts and the last approved copy of the library are kept in the team's own documents, so a deadline is never lost to an outage.

The agents

What each agent may do through its tools, what it may not, and where a person signs off. The limits are enforced by the platform, not the prompt.

Funder fit and terms check

May do

  • Read the funder's published guidance, criteria and terms
  • Check eligibility, deadlines, word limits and exclusions against the charity's facts
  • Find any rules on AI use, declarations or confidentiality, and flag them
  • Summarise the fit, with its reasons, for the head of trusts and grants

May not do

  • Decide whether the charity applies
  • Register, log in to or submit anything on a funder's portal
  • Contact a funder
  • Accept a funder's terms

Where a person signs offThe head of trusts and grants decides whether to apply. Where a funder restricts or bans AI, the bid is written without the drafting assistant.

Bid drafting assistant

May do

  • Search the approved evidence library
  • Draft answers to the funder's questions within the word limits
  • Link every figure, quote and claim to its source
  • Mark gaps where the library has no evidence
  • Ask service, finance or impact leads to confirm their figures

May not do

  • Invent or round up a figure, outcome or partner
  • Use a case study without a current consent record for that use
  • Change a budget line
  • Send, submit or sign a bid

Where a person signs offA named approver signs off every bid, after the figures' owners have confirmed them. The agent's permissions are enforced by the platform's identity and policy controls, not by instructions in a prompt.

Middleware and integration

The CRM or grants pipeline stays the record of every application, decision and grant condition. The AI reads funder details from it and writes a draft status back through the API layer, never directly into its database.

The evidence library is fed by events, not copied by hand. An updated outcomes figure, a new budget or a withdrawn consent arrives as a message, the library item is replaced or retired, and every draft that used it is flagged for review.

The AI can be switched off without stopping fundraising. If it's paused, writers work from the same library through a normal search, exactly as they would without drafting help.

Process and people

  • A trustee-approved AI policy that covers bid writing, including when not to use AI and how use is recorded.
  • Every library item has a named owner and an expiry date. Expired items drop out of drafting until they are renewed.
  • Case studies only enter the library with clear, informed consent for fundraising use, and changed details are labelled as changed.
  • Writers rewrite drafts in the charity's own voice. A draft that reads like anyone's bid isn't ready.
  • A monthly review of a sample of sent bids against their sources, and of funder feedback.
  • Writers trained before go-live, including how to answer a funder who asks how AI was used.

Delivery plan

  1. 2–3 weeks

    Discovery

    Map today's bid process, measure the baseline, list current funders' AI rules, audit where evidence lives and the state of case study consents.

  2. Gate · must be true to passBaseline agreed, evidence owners named, DPIA started, AI policy drafted for trustees.

  3. 6–8 weeks

    Pilot

    One funding round, in shadow mode: the assistant drafts alongside writers working as normal, and the two are compared on accuracy, sources and time.

  4. Gate · must be true to passEvery claim in pilot drafts traced to a source, edit rate within agreed limits, and sign-off from the head of trusts and grants.

  5. 4 weeks

    Production

    Drafting goes live for trust and foundation bids, with monitoring, support and a rollback plan.

  6. Gate · must be true to passMonitoring, support model, rollback plan and writer training in place; trustees approve the AI policy.

  7. Ongoing

    Scale

    Add statutory bids, grant reports and renewals, then reuse the library for the trustees' report and supporter communications.

  8. Gate · must be true to passEach new bid type passes the same pilot gate.

Roles and RACI

Who is responsible, accountable, consulted and informed, by activity
ActivityDirector of fundraisingHead of trusts and grantsSolutions architectI can fill thisTechnical PMI can fill thisEngineersI can fill thisData protection leadFinance and impact leads
Business case and AI policyAccountableResponsibleConsultedConsultedInformedConsultedConsulted
Target architectureInformedConsultedAccountable and ResponsibleConsultedConsultedConsultedInformed
Evidence library content and ownersInformedAccountableConsultedConsultedResponsibleConsultedResponsible
DPIA and case study consentsConsultedConsultedConsultedInformedInformedAccountable and ResponsibleConsulted
Build and integrationInformedConsultedAccountableResponsibleResponsibleInformedConsulted
Pilot on a real funding roundInformedAccountableConsultedResponsibleResponsibleConsultedConsulted
Go-live decisionAccountableResponsibleConsultedResponsibleInformedConsultedConsulted
Run, monitor and improveInformedAccountableConsultedConsultedResponsibleConsultedConsulted

Business case and AI policy

Director of fundraising
A · Accountable
Head of trusts and grants
R · Responsible
Solutions architect
C · Consulted
Technical PM
C · Consulted
Engineers
I · Informed
Data protection lead
C · Consulted
Finance and impact leads
C · Consulted

Target architecture

Director of fundraising
I · Informed
Head of trusts and grants
C · Consulted
Solutions architect
A/R · Accountable and Responsible
Technical PM
C · Consulted
Engineers
C · Consulted
Data protection lead
C · Consulted
Finance and impact leads
I · Informed

Evidence library content and owners

Director of fundraising
I · Informed
Head of trusts and grants
A · Accountable
Solutions architect
C · Consulted
Technical PM
C · Consulted
Engineers
R · Responsible
Data protection lead
C · Consulted
Finance and impact leads
R · Responsible

DPIA and case study consents

Director of fundraising
C · Consulted
Head of trusts and grants
C · Consulted
Solutions architect
C · Consulted
Technical PM
I · Informed
Engineers
I · Informed
Data protection lead
A/R · Accountable and Responsible
Finance and impact leads
C · Consulted

Build and integration

Director of fundraising
I · Informed
Head of trusts and grants
C · Consulted
Solutions architect
A · Accountable
Technical PM
R · Responsible
Engineers
R · Responsible
Data protection lead
I · Informed
Finance and impact leads
C · Consulted

Pilot on a real funding round

Director of fundraising
I · Informed
Head of trusts and grants
A · Accountable
Solutions architect
C · Consulted
Technical PM
R · Responsible
Engineers
R · Responsible
Data protection lead
C · Consulted
Finance and impact leads
C · Consulted

Go-live decision

Director of fundraising
A · Accountable
Head of trusts and grants
R · Responsible
Solutions architect
C · Consulted
Technical PM
R · Responsible
Engineers
I · Informed
Data protection lead
C · Consulted
Finance and impact leads
C · Consulted

Run, monitor and improve

Director of fundraising
I · Informed
Head of trusts and grants
A · Accountable
Solutions architect
C · Consulted
Technical PM
C · Consulted
Engineers
R · Responsible
Data protection lead
C · Consulted
Finance and impact leads
C · Consulted

R ResponsibleA AccountableC ConsultedI Informed· not involved

Where I'd fit

Option A

Lead the architecture

If there's no architect on the programme, I'd own the design end to end: the evidence library and how it stays current, the link to your CRM and finance data, the drafting and the sign-off gates. I'd report to your director of fundraising and keep the trustees' AI policy and the build in step.

Option B

Support your architect

If your partner or your own team already has an architect, I'd take on the evidence library, the retrieval and the integration with your CRM and finance systems under their lead, and give them a second senior opinion on data protection and the controls around sign-off.

Where this goes wrong

  1. Goes wrong

    Drafts read like everyone else's bid, and assessors notice.

    How the design avoids it

    Drafts built from the charity's own evidence, rewritten in its own voice, with funder feedback reviewed monthly.

  2. Goes wrong

    The tool is used to send more bids, not better ones.

    How the design avoids it

    A fit check before any writing, and success rate and funder feedback measured alongside time saved.

  3. Goes wrong

    A figure in the bid doesn't match the accounts or last year's report.

    How the design avoids it

    Figures come only from the library, each owner confirms theirs, and the approver sees the source next to every number.

  4. Goes wrong

    A case study is used beyond what the person agreed to.

    How the design avoids it

    Consent records travel with each case study, are checked before drafting, and withdrawals retire it everywhere.

  5. Goes wrong

    A funder's rule on AI is missed.

    How the design avoids it

    The fit check reads every funder's current terms first, and the bid record shows how AI was used.

On the horizon

Changes already announced or under way that affect this design. More in the UK horizon scan.

  1. From October 2026
    UKRI's changes to grant assessment: staff-led triage with desk rejection, more distributed peer review, and a trial comparing AI-assisted assessment with past decisions. Funding opportunity pages will say how each call is assessed.

    For charities that apply to research funders, feed each call's assessment notes into the fit check. With desk rejection, an eligibility mistake costs the whole bid.

  2. Under way
    Funders responding to higher application volumes: more invitation-only programmes, shorter first-stage forms, and more questions about AI use.

    Keep a per-answer record of AI use, and put the time saved into relationships and fewer, stronger bids.

  3. Year ends from 31 December 2026
    The first trustees' reports under Charities SORP 2026. Tier 2 and Tier 3 charities must explain the impact they make, and funders will be able to compare bids with the published report.

    Draw bid figures from the same approved figures as the trustees' report, with the same periods and definitions.

  4. Late 2026 to 2027
    The ICO's final guidance on anonymisation and pseudonymisation for research, archiving and statistics, after its consultation from August to October 2026.

    Review how outcomes data is de-identified before it enters the library once the final guidance lands.

Questions to ask your partner or vendor

Good answers are specific. Vague answers to any of these are worth following up.

Copy them into your next supplier meeting

  1. Where does every figure in a draft come from, and who confirmed it?
  2. How do we know a case study's consent still covers this use?
  3. What happens when a funder says no AI, or asks how we used it?
  4. How will we measure quality and success rate, not just time saved?
  5. Is our data used to train anyone's model, and where is it processed?
  6. Who owns the evidence library and keeps it current after you leave?

Planning something like this?

Whether you need someone to lead the design or to support the architect you already have, let's talk it through.

Sam Naseem
Sam NaseemBirmingham, UK · UK & Europe
Available now