Who Holds the Pen? Governing Joint Grant Bids Without Diluting What Each Partner Brings

Joint funding applications have become a familiar feature of the UK grants landscape. Funders frequently signal that they welcome partnership, and local authorities, national lottery distributors and place-based programmes often favour proposals that demonstrate shared delivery. For small charities and social enterprises, however, the appeal of a larger bid can obscure a quieter risk: that the partnership becomes a reporting arrangement rather than a genuine collaboration, and that one organisation's identity, beneficiaries and voice are gradually absorbed into the whole.

The solution is not to avoid collaboration. It is to govern it properly from the outset. A consortium works best when the administrative questions are settled before the money arrives, and when every partner understands precisely what it is contributing, what it is receiving and how decisions will be made when views diverge.

Choosing a lead applicant on capacity, not seniority

The lead applicant is usually the organisation that holds the grant contract, receives funds and carries legal responsibility for reporting. That role should be assigned on operational capacity rather than on size or reputation alone. A larger partner may have greater reserves but weaker grant administration; a smaller partner may have the closest relationships with beneficiaries but insufficient finance staff to manage a restricted income stream.

Before submitting a bid, the group should confirm in writing which organisation will act as accountable body, who will sign the funding agreement, and which bank account will receive payments. A short letter of delegation, signed by each partner's trustees or directors, can record these arrangements without creating an unnecessary legal structure. Where the partnership is likely to continue beyond a single grant, a simple memorandum of understanding is preferable to relying on correspondence and goodwill.

The lead applicant should also be honest about the administrative burden it is taking on. Holding the pen does not mean holding all the knowledge. A lead partner that controls every communication can leave others feeling like subcontractors, which undermines the trust that collaborative delivery depends upon.

Decision-making before the first payment

Consortiums often fail not because partners disagree about the project, but because they never agreed how disagreement would be handled. Decision-making structures should be set out before the application is submitted, not improvised once a query arises.

At a minimum, partners should agree the quorum for partnership meetings, the threshold for major decisions, the process for resolving deadlock and the route for escalating concerns that cannot be settled operationally. If a steering group will oversee delivery, its membership and terms of reference should be clear. If one partner holds a casting vote, that should be stated openly rather than discovered during a difficult meeting.

It is equally important to decide how beneficiary voice enters the partnership. A consortium that speaks about communities without creating a route for those communities to influence decisions will struggle to demonstrate genuine co-production to a funder. Small charities are often closest to the people they serve; their partners should recognise that proximity as a form of expertise, not merely as local colour.

Cost-sharing and the partnership tax

Collaborative bids carry costs that single-organisation bids do not. Coordination meetings, shared reporting, joint case studies and the reconciliation of multiple budgets all consume staff time. These costs are rarely labelled in a grant application, yet they determine whether a partnership is sustainable or merely exhausting.

Partners should agree how direct costs, overheads and coordination time will be apportioned. A simple percentage split may be appropriate where delivery is genuinely shared, but it can be unfair where one partner carries most of the administration. A more defensible approach is to identify the specific functions each partner performs and to cost them explicitly, including the time required to attend meetings and prepare shared evidence.

Where a funder permits, a modest coordination allowance should be included in the budget and attributed to the organisation undertaking that work. If the funder does not allow such costs, partners should decide in advance whether they will absorb them and on what basis. Unspoken assumptions about who will pick up the administrative slack are a common source of resentment later in the grant period.

Protecting brands, beneficiaries and data

A joint bid does not require partners to merge their identities. Each organisation should retain its own name, visual identity and relationship with its beneficiaries. The funding agreement or memorandum of understanding should state how partners will be described in public communications, whose logo appears where, and who is authorised to speak to the press or to the funder.

Consent arrangements deserve particular attention. If beneficiaries of one partner will be referred to another, or if case studies will be shared across the partnership, the basis for consent must be clear. Data protection requirements do not disappear because a grant is collaborative. A short data-sharing protocol, proportionate to the size of the partnership, will usually be sufficient.

Partners should also agree what happens if one organisation's reputation is damaged during the grant period. This is uncomfortable territory, but a consortium that has no agreed response to a safeguarding concern or public criticism will be forced to improvise at the worst possible moment.

Reporting once, not five times

Funders increasingly ask for a single narrative report from the lead applicant. That is sensible, but it places a premium on collecting evidence consistently across partners. Agreeing a small set of shared indicators, a common reporting timetable and a single template at the start of the grant will save considerable time later.

The lead applicant should resist the temptation to rewrite partners' contributions into a uniform voice. A report that reflects the distinct role of each organisation is more credible than one that smooths away the differences that made the partnership worthwhile. Where partners hold different views on progress, those views should be recorded rather than suppressed.

An exit that does not surprise anyone

Finally, the partnership should agree in advance what happens if a partner withdraws, if funding is reduced, or if the project ends earlier than planned. Responsibilities for assets, records and beneficiary referrals should be clear. A short exit clause is not a sign of pessimism; it is evidence that the consortium has taken its obligations seriously.

Collaborative bids can achieve things that individual applications cannot. But the consortium clause is not a formality. It is the point at which partners decide whether they are building a shared project or merely sharing a cheque. The difference is usually visible long before the final report.