The Funding Relationship Audit: Grant, Contract and the Test That Comes First

Public bodies use the word 'grant' to describe a wide range of funding relationships. Sometimes the label is accurate. Sometimes it is a convenient shorthand for an arrangement that, on closer inspection, has all the hallmarks of a contract. The distinction is not academic. It determines which procurement rules apply, how subsidy control is assessed, what remedies are available if delivery falters, and how auditors and regulators will view the decision. The safest time to test the character of the relationship is before the first payment leaves the account.

Why the label carries legal consequences

A grant is generally a payment to support an activity or recipient, often with conditions attached, rather than a payment for a specified service delivered to the funder. A contract is an enforceable exchange: the funder receives something—goods, works or services—in return for consideration. In public funding, the line can blur. A grant may require outputs, reporting and repayment on failure. A contract may be light-touch and collaborative. Neither label is conclusive.

The consequences of mislabelling are practical. If an arrangement is in truth a public contract above the relevant threshold, the Procurement Act 2023 and its procedures may apply. If it is a subsidy, the Subsidy Control Act 2022 requires the public authority to consider the subsidy control principles and, where applicable, transparency or referral requirements. A public body also needs a lawful source of power for the funding and must respect its own governance and financial regulations. Calling a contract a grant does not remove those obligations; it simply hides them.

Reading the substance: the indicators that matter

No single feature decides the question. Decision-makers should look at the arrangement as a whole and ask what the funder is actually buying, controlling and enforcing.

• Consideration and benefit. Is the payment made in return for a defined service or asset that the funder needs? Or is it support for a recipient-led activity that aligns with a public objective?
• Specification and control. Does the funder prescribe how, when and by whom the work is done? Outcome reporting is common in grants; day-to-day direction is more consistent with a contract.
• Selection and competition. Was the recipient chosen because it was the best provider following a competitive process, or because it is a suitable recipient for grant support?
• Payment mechanics. Are payments linked to invoices, milestones or delivery of specified outputs? Grant payments may also be milestone-based, so this is indicative rather than decisive.
• Remedies and consequences. Can the funder terminate for breach, claim damages, require replacement or step in? A grant may permit clawback, but a contract typically creates reciprocal enforceable obligations.
• Risk allocation. Who bears cost overruns, liability, insurance and delivery risk? Contractual risk transfer points towards a contract.
• Exclusivity and branding. Does the funder require exclusive use, service levels, IP assignment or public branding as a service provider?
• Dispute resolution. Is there a contractual mechanism for disputes, or a grant conditions process?

The key question is not whether the document says 'grant'. It is whether the parties intended to create legal relations in which the funder receives a service in exchange for payment, with enforceable consequences if it is not delivered.

A pre-payment checklist for public bodies

Before approving funding, the following tests should be recorded:

1. Identify the power. Confirm the statutory or common-law power to fund and, if relevant, to contract. Record the vires analysis.
2. Describe the purpose. State whether the funding supports a recipient's activity or purchases a service for the public body.
3. Map the benefit. Identify what the funder receives and whether that benefit is the object of the arrangement.
4. Test control. Assess the degree of direction over staff, methods, timetable and deliverables.
5. Check procurement. Apply the Procurement Act 2023 thresholds and exceptions honestly, including any intended competition.
6. Assess subsidy control. Consider whether financial assistance confers an advantage and document the subsidy control assessment.
7. Review the terms. Look for enforceable service obligations, indemnities, liability caps, termination rights and dispute clauses.
8. Confirm approvals. Ensure the decision has the right governance sign-off, including finance and legal review.
9. Plan monitoring. Match reporting to the legal character of the arrangement; do not use grant-style light monitoring for a service contract.
10. Document the rationale. Record why the label chosen is the correct one, not merely the convenient one.

What can go wrong after payment starts

If a contract has been treated as a grant, the public body may face a procurement challenge, audit findings or a subsidy control issue. It may also find that it has weaker remedies when performance fails, because the documents do not create the contractual levers it assumed. Conversely, if a grant has been drafted as a contract, the recipient may challenge clawback, variation or termination on contractual grounds, and the public body may face disputes it did not anticipate.

There is also a transparency dimension. Funding arrangements attract freedom of information and audit scrutiny. A decision record that explains the legal character of the arrangement is far more defensible than one that relies on a label. Public money and public accountability are better served by a clear analysis at the outset than by a retrospective attempt to recharacterise the relationship.

Getting the label right

Grant or contract is not a matter of preference. It is a legal conclusion drawn from the purpose, terms and practical operation of the funding relationship. Public bodies should use a standard diagnostic, involve legal advisers early and document the reasoning before payments begin. Recipients should ask the same questions, because the label affects their obligations, exposure and dispute options. A short period of analysis at the front end is usually cheaper than a procurement challenge, a subsidy control query or a contractual dispute at the back end.