What the Charity Commission’s 2026 Guidance Means for Your Records
![]() |
Dean Murphy Growth Marketing Specialist, Submit.com |
Cloud grant management software gives a UK grant-making charity one place to keep the evidence its trustees need: how each application was checked, scored and decided, what the recipient agreed to, and how the grant was monitored. It does not make a charity compliant on its own. What it changes is whether that evidence exists in a consistent, searchable form, or is spread across inboxes, spreadsheets and shared drives.
That question became more pressing on 3rd of June 2026, when the Charity Commission published Making grants to charities and other organisations. The new guidance replaces earlier advice and now covers all grant-making, not only grants to organisations that are not charities. It also states that grant-making charities must have a written agreement in place in every case, and should monitor it to check the recipient is meeting the agreed terms (source: Charity Commission press release, 3rd of June 2026).
The guidance applies to a large part of the sector. The Commission’s analysis of 2024 annual returns found that grant-making charities awarded £17.84 billion in grants that year, and that 32,661 charities reported making grants (source: Charity Commission press release, 3rd of June 2026). Below, we set out what the guidance asks of trustees, the record each duty creates, and where a system such as Submit.com’s grant management software helps and where it does not.
Where this guidance applies. The Charity Commission’s guidance covers charities in England and Wales. Charities in Scotland are regulated by the Scottish Charity Regulator (OSCR), and charities in Northern Ireland by the Charity Commission for Northern Ireland. The record-keeping approach below is useful across the UK, but check your own regulator’s requirements.
What the 2026 guidance asks of grant-making trustees
The guidance sets out duties that run through the whole grant cycle. In summary, trustees should or must:
- Only make grants that help carry out the charity’s purposes, as set out in its governing document
- Agree processes for applying and for assessing applications, ask for enough detail to manage risk, and identify and review the risks in their grant-making
- Identify and manage conflicts of interest, following the Commission’s Conflicts of interest guidance (CC29)
- Make appropriate checks on applicant organisations before giving a grant, with more checks where the risks are higher
- Keep written terms of reference and clear reporting procedures when decisions are delegated to staff or a committee, while remaining responsible for those decisions
- Set out the grant terms in writing, including how the grant will be monitored
- Monitor each grant in proportion to its size and risk, and be able to show it helped carry out the charity’s purposes
- Explain the charity’s grant-making policy in the trustees’ annual report where grant-making is a significant activity
Source: Charity Commission, Making grants to charities and other organisations, 3rd of June 2026. For grants to organisations that are not charities, such as Community Interest Companies, the same guidance adds that trustees should keep a record of the decisions they make and be able to explain and justify them. Where risks are high, the Commission points to chapter 2 of its compliance toolkit on due diligence, monitoring and verifying the end use of charitable funds.
The record each duty creates
Each of those duties leaves a trail. The diagram shows the cycle as one continuous record, and the table maps each duty to the evidence a trustee board may need to point to and to how a grant management system can hold it. The final column matters as much as the others: some of the work always stays with people.
| Duty in the guidance | Evidence trustees may need | How a grant management system can hold it | What stays with your charity |
|---|---|---|---|
| Agree how grants are applied for and assessed | Published criteria, application questions and the assessment method | Configured forms, eligibility questions and scoring criteria, reused from one round to the next | Setting funding priorities and criteria, and reviewing them |
| Check applicant organisations | What was checked, who checked it and what they found | Required documents and registration details collected in the application, plus a separate due diligence stage | Looking up public registers and judging the results |
| Identify and manage conflicts of interest | Declarations and how each one was handled | Reviewer access limited by folder, notes kept on the application, and anonymised review where configured | Your conflicts policy and decisions about declared interests |
| Delegate decisions with clear reporting | Who decided, and under what authority | Role-based permissions, with time-stamped scores, comments and decisions | Terms of reference and reporting back to trustees |
| Set grant terms in writing | The agreement issued and the recipient’s acceptance | A post-award phase that holds the terms and the acknowledgement, with e-signature questions depending on plan | Drafting the terms, with legal advice where needed |
| Monitor grants in proportion to risk | Progress and final reports, evidence of spend and follow-up | Report phases, drawdown records, invoice uploads and automated reminders | Reading reports and acting on concerns |
| Report on grant-making | Totals, themes and outcomes | Dashboards and exports by programme, tag or stage | Writing the trustees’ annual report |
On a small screen, scroll the table sideways to see every column.
Due diligence: what software does and does not do
The guidance leaves trustees to decide which checks to carry out. It lists examples such as whether an organisation is a charity, whether it is genuine, whether it can deliver the work, whether it is well managed and whether the grant can be monitored, and it expects more checks where risks are higher (source: Charity Commission guidance, 3rd of June 2026).
A grant management system helps with collecting the information and keeping the record. In Submit.com, an application form can require a charity or company number, governing documents, accounts and policies before it can be submitted, so incomplete applications do not reach assessment. A separate due diligence stage can sit between assessment and award, which keeps the outcome of each check with the application it relates to.
The system does not carry out the checks for you. Submit.com does not look up the Charity Commission register or Companies House automatically, so staff still confirm registration and filings on the public registers, such as the Charity Commission register, and record what they found. That matters most for grants to organisations that are not charities, where the guidance warns trustees not to assume an organisation is a charity because its work looks similar to their own.
Showing how a funding decision was made
For small grant teams, the harder task is often not making a decision but showing afterwards how it was made. When scores sit in personal spreadsheets and panel discussion happens by email, rebuilding a decision for a trustee, an auditor or an unsuccessful applicant is slow and often incomplete.
In Submit.com, reviewers score against the criteria each programme sets, using weighted score bars, and their comments are time-stamped and kept with the application. Permissions control what each person can see: an external reviewer or trustee panel member can be limited to the applications in their assigned folder and prevented from downloading them. Optional anonymised review hides identifying details where a programme needs it, and audit trails record submissions, reviews, decisions and administrative actions (see Submit.com security and compliance).
Conflicts of interest need a policy before they need a feature. One practical approach in Submit.com is to keep a reviewer who declares an interest out of the folder holding that application, and to note the declaration and the decision about it on the application record. Your conflicts policy decides what happens; the system makes it visible later.
Written agreements and monitoring after the award
The written-agreement requirement is the most practical change in the 2026 guidance. The Commission says a letter or short agreement may be enough for low-risk grants, while higher-risk grants, such as multi-year funding or overseas work, need extra terms and conditions (source: Charity Commission guidance, 3rd of June 2026).
Your charity, with legal advice where needed, decides what the terms say. A grant management system makes sure each recipient receives them and that you can show they were accepted. In Submit.com, successful applicants can be invited into a post-award phase that holds the agreement and their acknowledgement, with e-signature questions available depending on plan. Later phases collect progress and final reports against the same application, so the agreement, the reports and the original assessment stay together.
For the money itself, grant tracking records the amount awarded, each drawdown and the remaining balance, and recipients can upload invoices or receipts as evidence of spend. Those are the kinds of monitoring the guidance describes, alongside milestone reports and an end-of-grant report. Automated reminders chase overdue reports without anyone working through a spreadsheet of deadlines.
How much monitoring a grant needs is a judgement for trustees. The software makes the chosen approach consistent across every grant; it does not choose the approach for you.
Reporting to trustees and in the annual report
Where grant-making is a significant part of a charity’s activities, the guidance notes that the charity may need to explain its grant-making policy in the trustees’ annual report (source: Charity Commission guidance, 3rd of June 2026). Board papers, funder updates and responses to questions about where money went all draw on the same data.
Reporting is easier when applications are tagged as they arrive rather than sorted at year end. Submit.com can tag applications automatically by theme, location or answer, and its dashboards and exports to Excel or CSV break funding down by programme, tag or stage.
Developing Healthy Communities, which runs community mental health and wellbeing grants in Northern Ireland, uses this to answer short-notice questions about where funding went, filtering funded projects by trust area and cross-referencing them with deprivation data. The team went live on Submit.com eight weeks after deciding to replace its previous system.
What “cloud” and “secure” should mean for charity data
Applicant data in a grant programme can include personal details, bank information and, in some funds, health or other sensitive information. Under UK GDPR, your charity is usually the controller of that data, deciding why and how it is used. A software provider that handles it on your behalf is a processor and acts only on your instructions. The Information Commissioner’s Office (ICO) explains that controllers carry the highest level of compliance responsibility (source: ICO, A guide to controllers and processors), so choosing a provider and agreeing data processing terms with it is part of your own accountability.
Submit.com stores and processes customer data in the European Economic Area (EEA). The UK has adequacy regulations covering every EEA country, which means personal data can be transferred from the UK to the EEA under UK GDPR (source: ICO, Is the restricted transfer covered by adequacy regulations?). If your charity has a policy that requires UK-only hosting, raise it at the start of any evaluation.
Beyond location, the controls worth checking are encryption in transit and at rest, multi-factor authentication, single sign-on, role-based permissions, configurable data retention and independent assurance. Submit.com encrypts data in transit and at rest, supports multi-factor authentication and, depending on plan, single sign-on. It is SOC 2 Type 2 certified and Cyber Essentials certified, and it is listed on the UK Government’s G-Cloud framework (see Submit.com security and compliance). Submit.com treats security as a shared responsibility: the platform provides the controls, and your charity configures and uses them in line with its own obligations.
Grants and awards in one platform
Many trusts and foundations run more than one kind of programme: grants, bursaries, fellowships or awards. These share the same building blocks: an application or nomination, a panel scoring against criteria, a decision and a notification. Submit.com runs grants, scholarships and awards programmes in the same platform, so one team can use the same permissions, scoring approach and audit trail across all of them. Our page on grant management for foundations covers how this works for grantmaking teams.
Questions to ask before you choose a system
- Can you show us the full history of one declined application: who saw it, who scored it and when?
- Where is our data stored and processed, and what data processing terms do you provide?
- How would we record a declared conflict of interest and keep that reviewer away from the application?
- How do we issue grant terms and collect acceptance, progress reports and evidence of spend?
- Which of the features we need are included in the plan we would buy?
If you are comparing platforms, our UK buyer’s guide to grant management software sets out how the main options differ, including where Submit.com is not the best fit.
See your own grant process in Submit.com
Book a demo and we’ll walk through one of your programmes, from application and due diligence to the grant agreement, monitoring and trustee reporting.
This article summarises published guidance for general information and is not legal advice.












0 Comments