Grant Management for Large Trusts and Foundations

Large trusts and foundations in the UK collectively distribute billions of pounds each year. In recent data, UK trust and foundation grantmaking reached GBP 8.2 billion, representing a 12% year-on-year increase. That is an extraordinary amount of money flowing through systems that, in many cases, are not fit for purpose.

This guide is for the organisations managing those portfolios. If you oversee multiple programmes across different geographies and thematic areas, employ dedicated grants teams, report to boards of trustees, and are responsible for ensuring that millions of pounds reach the right organisations and create genuine impact, this is for you.

TL;DR

Large trusts face unique grant management challenges: complex approval workflows, multi-programme portfolios, board-level reporting, and the need for enterprise-grade security and audit trails. Many are trapped in expensive legacy systems or over-customised Salesforce instances that cost GBP 15,000 to GBP 50,000 or more per year to maintain. Modern purpose-built platforms like Plinth offer a way to scale without this complexity, using AI to handle volume and providing portfolio-level analysis that legacy systems simply cannot deliver.

What you will learn

How to structure grant management across multiple programmes and teams
Why legacy platforms are holding large funders back
The true cost of Salesforce customisation for grantmaking
How to build effective board reporting and governance packs
Approaches to portfolio-level impact analysis
How AI changes the economics of due diligence at scale
What to look for when choosing or replacing a grant management system

Who this is for

Directors of grants and programmes responsible for operational delivery
Heads of impact and learning building evidence across portfolios
Chief executives accountable to boards for effective grantmaking
Finance directors managing complex restricted funds and payment schedules
Operations and IT leads maintaining or replacing grant management systems
Trustees seeking assurance that processes are robust and efficient

The scale of the challenge

A large trust or foundation might manage:

5 to 15 active programmes, each with different criteria, timescales, and assessment processes
500 to 5,000 applications per year across those programmes
200 to 1,000 active grants at any time
GBP 10 million to GBP 100 million or more in annual distributions
Teams of 10 to 50 staff across grants, impact, finance, and operations
Reporting to a board of trustees, often quarterly, requiring comprehensive governance packs

The operational complexity is real. But the response to that complexity -- layering on more systems, more customisation, more process -- often makes things worse rather than better.

The legacy system trap

Blackbaud and its contemporaries

Let us be direct: legacy platforms like Blackbaud are showing their age. Many large trusts adopted these systems ten or fifteen years ago when the options were limited. They have since invested heavily in customisation, data migration, and staff training. Switching feels impossible.

But the cost of staying is significant:

Slow development cycles -- feature requests take months or years to materialise
Expensive maintenance -- annual licensing, hosting, and support contracts that consume budget better spent on grants
Poor user experience -- interfaces designed in a different era that staff tolerate rather than embrace
Limited integration -- difficulty connecting to modern tools for impact measurement, financial management, or applicant communication
Vendor lock-in -- data structures that make migration to any other platform a major project

If your grants team complains about your system at every opportunity, the problem is not your team.

The Salesforce question

Many large trusts have turned to Salesforce as a supposedly flexible alternative. Salesforce is a powerful CRM platform. But it is not a grant management system. Turning it into one requires significant customisation, and that is where the problems begin.

Typical costs for a Salesforce-based grantmaking setup:

Year 1: GBP 20,000 to GBP 60,000 or more, including licensing, implementation partner fees, and initial customisation
Ongoing: GBP 10,000 to GBP 30,000 per year in licensing, plus consulting fees every time you need changes
Hidden costs: staff time spent managing the platform, training new team members on complex configurations, and the dependency on a specific implementation partner who understands your setup

The result is often a system that technically does what you need but is fragile, expensive to change, and understood by only one or two people in the organisation. When those people leave, institutional knowledge goes with them.

This is not to say Salesforce is never the right choice. For organisations that already have deep Salesforce expertise and use it across multiple functions, adding grantmaking capabilities can make sense. But for most trusts, it is an expensive solution to a problem that purpose-built platforms solve more elegantly.

Multiple disconnected systems

The third common pattern is perhaps the most damaging: a patchwork of systems that each handle one part of the process. Applications in one tool, assessments in spreadsheets, decisions recorded in emails, payments managed in the finance system, impact data collected through yet another platform.

This fragmentation means:

No single view of an applicant or grantee across their full relationship with you
Manual data transfer between systems, introducing errors and consuming staff time
Reporting that requires pulling data from multiple sources and reconciling it
Audit trails that exist in theory but are nearly impossible to reconstruct in practice

What large trusts actually need

Enterprise-grade security and access control

Large trusts hold sensitive data: applicant financials, beneficiary information, trustee deliberations, and strategic plans. Your grant management system must provide:

Role-based access control so that team members see only what they need to see
Programme-level permissions allowing different teams to manage their own programmes without accessing others
Audit logging of every action taken in the system
Data encryption at rest and in transit
GDPR compliance including data retention controls and subject access request support
Single sign-on (SSO) integration with your identity provider

Multi-programme dashboards

Senior leaders and trustees need a portfolio view that shows performance across all programmes simultaneously. This should include:

Pipeline overview -- applications received, in assessment, recommended, and decided, across every programme
Financial summary -- commitments, payments made, and remaining budgets by programme and fund
Timeline view -- upcoming deadlines, decision points, and board dates
Risk indicators -- programmes with delayed reports, underspending grantees, or compliance concerns
Impact headlines -- aggregated outcomes data that shows what the portfolio is achieving

This should be available on demand, not compiled manually for each board meeting.

Complex approval workflows

Large trusts typically have multi-stage approval processes:

Initial eligibility screening
Detailed assessment by programme officers
Internal peer review or quality assurance
Recommendation to a panel or committee
Panel decision (which may refer back for more information)
Formal approval and conditions setting
Trustee ratification for grants above certain thresholds

Your system should model these workflows explicitly, with clear handoffs, deadline tracking, and automatic routing. Every step should be recorded, creating an audit trail that trustees and regulators can review.

Portfolio-level analysis

Beyond tracking individual grants, large trusts need to understand their portfolio as a whole:

Geographic distribution -- are you reaching the areas of greatest need, or clustering in places where applicants are most sophisticated?
Thematic balance -- does your portfolio reflect your strategic priorities, or has it drifted?
Organisation type -- what proportion goes to large charities versus small grassroots organisations?
Grant size distribution -- are you making a few large bets or many small ones, and is that deliberate?
Renewal patterns -- how much of your budget goes to existing grantees versus new organisations?
Outcome trends -- across hundreds of grants, what patterns emerge about what works?

This analysis should inform strategy, not just report on activity.

Board reporting

Trustees have a legal duty to ensure that the foundation's resources are used effectively. Your grant management system should support this by generating:

Decision packs with application summaries, assessment notes, and recommendations in a consistent format
Financial reports showing commitments, payments, and fund balances
Risk registers highlighting grants or programmes that require trustee attention
Impact summaries demonstrating outcomes across the portfolio
Conflict of interest records showing how conflicts have been managed

If your team spends days before each board meeting compiling packs from multiple sources, your system is failing you.

How AI changes the economics of large-scale grantmaking

The most significant development in grant management technology is the application of AI to processes that previously required extensive manual effort.

Due diligence at scale

A large trust receiving 2,000 applications per year might spend 30 to 60 minutes per application on basic due diligence: checking Charity Commission registration, reviewing accounts, verifying governance arrangements, and identifying potential risks. That is 1,000 to 2,000 hours of staff time per year -- the equivalent of one full-time employee doing nothing but due diligence.

AI can automate the vast majority of this work. Plinth's AI-powered due diligence automatically:

Verifies Charity Commission registration and checks for regulatory actions
Reviews filed accounts and flags financial concerns
Checks trustee and officer information against relevant databases
Identifies governance risks based on publicly available data
Produces a structured summary for each application, highlighting areas that need human attention

The result is not that humans are removed from the process. It is that humans focus on the applications that genuinely need their judgement, rather than spending hours on routine checks that a machine can do faster and more consistently.

Assessment support

Beyond due diligence, AI can assist with:

Summarising long applications into structured briefs for assessors
Identifying similar previous grants so assessors can learn from past experience
Flagging inconsistencies between different sections of an application
Benchmarking budgets against comparable grants in your portfolio
Drafting decision rationale based on assessment criteria and evidence

Impact analysis

AI is particularly powerful when applied to large volumes of qualitative data. A trust that receives 500 progress reports per year contains rich information about what is working, what is not, and why. Manually synthesising this into strategic insight is impractical. AI can:

Extract key themes from narrative reports across the portfolio
Identify patterns in outcomes data that human analysis might miss
Generate portfolio-level impact summaries for board reporting
Flag grantees that may need additional support based on their reporting

Common mistakes large trusts make

Over-engineering processes

Complexity is not the same as rigour. A 15-stage approval workflow does not make decisions better; it makes them slower. Regularly review your processes and ask whether each step adds genuine value or merely creates the appearance of thoroughness.

Confusing data collection with learning

Collecting extensive monitoring data from grantees is pointless if you never analyse or act on it. Before adding a question to a reporting form, ask: who will read the answer, and what decision will it inform? If you cannot answer that, remove the question.

Treating all grants identically

A GBP 5,000 grant to a small community group should not require the same process as a GBP 500,000 strategic partnership. Proportionality is not just good practice for grantees; it is efficient use of your own team's time. Build tiered processes that apply appropriate scrutiny at each level.

Underinvesting in systems

Large trusts often spend millions on grants and thousands on the systems used to manage them. If your grants team is working around your technology rather than with it, the cost in staff time, errors, and missed insight dwarfs the cost of a better platform.

Neglecting the applicant experience

Your application process is the first impression organisations have of you. If it is confusing, inaccessible, or unnecessarily burdensome, you are filtering out the organisations least able to navigate bureaucracy -- often the grassroots groups doing the most important work.

How Plinth helps large trusts and foundations

Plinth is built to handle the scale and complexity that large trusts require, without the overhead of legacy systems:

Scales without complexity -- configure multiple programmes, workflows, and teams without writing code or hiring consultants
AI-powered due diligence processes hundreds of applications simultaneously, freeing your team to focus on assessment and relationship-building
Portfolio-level impact analysis synthesises outcomes data across your entire portfolio, generating the strategic insight that boards need
Multi-programme dashboards give senior leaders and trustees real-time visibility across all programmes
Configurable approval workflows model your decision-making process accurately, with full audit trails
Clear audit trails record every action, decision, and communication for governance and compliance
Modern, intuitive interface that staff actually want to use, reducing training time and increasing adoption
Purpose-built for grantmaking -- no expensive customisation required

For large trusts considering a system change, Plinth offers migration support to move your data from legacy platforms without disruption to active programmes.

Making the case for change

If you are reading this and recognising your own organisation's challenges, you may be wondering how to build the case for changing systems. Consider framing it around:

Staff time savings -- calculate the hours your team spends on manual processes that a modern system would automate
Opportunity cost -- what could your grants team achieve if they spent less time on administration?
Risk reduction -- quantify the governance risks of fragmented systems and incomplete audit trails
Total cost of ownership -- compare the full cost of your current setup (licensing, maintenance, consulting, staff time) against modern alternatives
Strategic value -- portfolio-level insight that your current system cannot provide has real strategic worth

FAQs

Can we federate grant management across countries or regions?

Yes. Modern platforms support multi-region configurations with local data controls, programme-specific permissions, and templates that maintain consistency while respecting local requirements. Ensure your platform complies with data protection regulations in each jurisdiction you operate in.

How do we manage review panels effectively?

Use a system that provides reviewer workspaces where panel members can access application summaries, score against agreed criteria, and declare conflicts of interest. Calibration tools help ensure consistency across reviewers. All of this should happen within the platform, not through emailed spreadsheets.

What about restricted donors and designated funds?

Tag grants and funds by donor to enable tailored reporting. Dashboards should filter by donor, programme, theme, or geography so that you can produce bespoke reports without bespoke data collection.

How long does migration from a legacy system typically take?

This varies significantly depending on the volume and complexity of your data. A straightforward migration of active grants and core data can often be completed in 8 to 12 weeks. More complex migrations involving historical data, documents, and custom fields may take 3 to 6 months. The key is planning: map your data early and clean it before migration.

Will our team adopt a new system?

Adoption depends on three things: the quality of the user experience, the quality of the training and support, and whether leadership genuinely commits to using the new system consistently. If your current system frustrates your team, you may find adoption is easier than you expect.

How do we handle the transition period?

Most organisations run old and new systems in parallel for a defined period (typically one to two grant cycles). New applications go into the new system from day one. Active grants in the old system are either migrated or managed there until they close. Avoid running parallel systems indefinitely -- set a firm end date.

Recommended next pages

Best End-to-End Systems for Large Programmes -- comparing platforms designed for scale
Blackbaud vs Plinth -- a direct comparison for organisations considering alternatives
Manage Large Volumes of Applications -- practical strategies for high-volume programmes
Audit Trails in Grant Software -- why they matter and what good looks like
AI-Driven vs Traditional Grantmaking -- understanding the shift
Align Grants with Strategy -- connecting portfolio management to organisational goals

This guide is maintained by the Plinth team and was last updated on 21 February 2026. If you have questions or suggestions, get in touch.

Can we store cookies?