Grant rounds, applications, evaluation, disbursement and outcomes - in one auditable workflow.

Grant or contract, and why it matters

The label on the document does not decide the question. What decides it is the substance of the arrangement: who wants the activity to happen, who specifies it in detail, who takes the risk, and whether the funder receives something of direct economic benefit in return. If a funder specifies outputs precisely, controls how the work is done, and receives the service it would otherwise have had to buy, then it is a contract for pecuniary interest whatever the paperwork calls it.

This matters because the Procurement Act 2023, in force from 24 February 2025, applies to regulated contracts and not to genuine grants. Misclassifying a contract as a grant removes competition, transparency notices and the remedies regime from something that should have had all three. It is one of the more common findings in public sector audit, and it is usually not deliberate. It happens because a funding stream arrived labelled as grant funding and nobody tested the arrangement it produced.

The practical control is a short, documented classification test applied at the start of every funding decision, signed off by someone independent of the programme. It should record what the activity is, whose idea it was, who specifies delivery, what the funder receives, and the conclusion with reasons. It takes minutes to complete and it is the single piece of evidence that resolves the question two years later.

• Whose activity is it, and who initiated it
• Who specifies what is delivered and how
• Does the funder receive a direct benefit it would otherwise buy
• Who carries the delivery and financial risk
• Recorded conclusion, with reasons, approved independently

Designing a grant programme

Programme design determines the quality of everything downstream. The core decisions are the outcomes being funded, who is eligible, how much is available in total and per award, whether awards are one off or phased, what the funding cannot be used for, and how success will be judged. Vague outcomes produce vague applications, which produce assessment panels arguing about interpretation rather than merit.

Proportionality is the discipline most often missed. A programme making a large number of small awards to community organisations should not use the same application form as one making a handful of major multi year grants. Requiring three years of audited accounts from a group with an income below the audit threshold excludes exactly the organisations the programme is usually trying to reach.

Design should also decide, in advance, how much the funder will do after award. A programme with light touch monitoring and one end of grant report is a legitimate choice for small awards. A programme with quarterly claims, milestone verification and site visits is legitimate for large ones. What causes trouble is designing the application stage carefully and leaving the post award stage undefined, so monitoring becomes whatever the officer has time for.

Running the application round

A well run round publishes the criteria, the weightings, the eligibility rules and the timetable before it opens, and does not change them once it has. Applicants invest real effort in these processes, and shifting the goalposts mid round is both unfair and the fastest route to complaint. Where questions arise, answers should be published to all applicants rather than given privately, exactly as with a tender clarification log.

The application itself should ask only what will actually be assessed. Every question should map to a criterion, and any question that does not influence the score should be moved to a post award stage or dropped. Long forms do not improve decision quality, they filter for organisations with bid writing capacity rather than delivery capacity, which skews the portfolio towards the already well resourced.

Accessibility deserves genuine attention. Plain English, a clear word limit, a downloadable version of the questions so applicants can draft offline, a named contact for questions, and enough time to prepare all measurably widen the field. Where a programme is intended to reach smaller or newer organisations, a short expression of interest stage before a fuller application saves everyone effort.

Assessment, moderation and conflicts

Assessment should work like tender evaluation, because the same fairness expectations apply. Assessors score independently against published criteria with defined descriptors, record rationale that supports the score, and then moderate to a consensus. Moderation is a documented discussion, not an average and not a negotiation. The moderated score and its reasons are the record that will be relied on if a decision is questioned.

Conflicts of interest are more acute in grant making than in procurement, because funders often sit on the boards of the organisations applying, and because sectors are small. The register needs to capture connections at organisation level as well as personal ones, and the mitigation must be recorded: withdrawal from scoring, withdrawal from the room, or non participation in the panel entirely. Declaring a conflict and then scoring anyway is not mitigation.

Panels benefit from a short calibration exercise before scoring begins. Everyone scores the same one or two applications, then discusses the divergence. It takes an hour and it removes most of the inconsistency that otherwise surfaces at moderation, when it is far more expensive to resolve.

Feedback to unsuccessful applicants is worth the effort. It improves the quality of future rounds, it reduces the volume of appeals, and it is often the difference between an organisation applying again and writing the funder off. Feedback drawn straight from the recorded rationale takes little extra time.

• Independent scoring against published criteria and descriptors
• Calibration exercise before the panel scores in earnest
• Conflicts declared at organisation and individual level, with recorded mitigation
• Moderation documented as consensus with reasons
• Feedback drawn from the recorded rationale

Award, agreement and disbursement

The grant agreement is where a lot of later pain is avoided. It should state the funded activity and outcomes, the amount and the payment schedule, eligible and ineligible costs, reporting requirements and dates, what happens to underspend, what happens if delivery changes, record keeping and retention obligations, audit access rights, and the circumstances in which funding may be withheld or recovered. Recovery provisions that were never written down cannot be used.

Payment profile is a real decision, not an administrative one. Paying wholly in arrears protects the funder and can be fatal for a small organisation without reserves, which then either declines the grant or funds delivery on a credit card. Paying wholly in advance transfers all the risk to the funder. A profile with an initial payment, milestone linked instalments and a retained final element balances the two, and should be set according to the recipient's size and the funder's assessment of risk.

Variations happen in almost every programme of any size. Delivery partners withdraw, costs move, participant numbers differ from forecast. A clear, light variation process with a defined threshold below which the recipient can flex without approval prevents the two common failure modes: recipients quietly delivering something different from what was funded, and funders spending more time on minor variations than on the original assessment.

Monitoring, assurance and recovery

Assurance should be proportionate to risk and value, and the risk assessment should be done once, at award, rather than debated at each claim. A simple tiering approach works well: low value awards to established recipients get light touch reporting, higher value or higher risk awards get evidence based claims, and the highest tier gets verification visits and sampled transaction testing. Publishing the tiering rules means recipients know what to expect.

Claims processing is where most funder time goes and where most delay is created. The fixable causes are consistent: unclear evidence requirements, so recipients submit the wrong thing; no standard claim format, so every submission is different; and no visibility for the recipient, so they chase by email and the officer spends the day answering. A structured claim workflow with a defined evidence list and visible status removes most of that overhead.

Recovery is uncomfortable but necessary, and it depends entirely on the agreement and the record. Where funds have been used for ineligible costs, or the activity has not been delivered, the funder needs the contractual right, the evidence, and a decision made at the right level. It is far easier when the monitoring record already shows what was reported, when, and what evidence supported it, rather than when the file has to be reconstructed under dispute.

• Risk tier set at award and published, not renegotiated per claim
• Defined evidence list per claim type
• Visible claim status for recipients to reduce chasing
• Retention and audit access rights written into the agreement
• Recovery decisions taken at the right level, on the recorded evidence

Transparency, subsidy control and public reporting

Grant awards attract public interest, and funders should assume every award will eventually be examined. Publishing what was awarded, to whom, for what and for how much, along with the assessment criteria used, is both good practice and a straightforward way to reduce freedom of information workload. Where a programme is small or recipients are individuals, publication needs handling carefully for data protection reasons, but the principle holds.

Subsidy control is a separate consideration that funders sometimes miss. Where a grant is made to an organisation carrying out economic activity, the subsidy control regime may apply and the assessment needs to be recorded, including any exemption relied on. That assessment belongs on the file with the classification test, not in an adviser's memory.

Where grant funding requires the recipient to buy goods or services, the funder should be explicit about what procurement standards apply. Many grant conditions require recipients to demonstrate value for money and to run competitive processes proportionate to value. Those conditions only work if they are stated clearly at award and if the evidence expected is described, otherwise recipients discover the requirement at claim stage when the purchase has already been made.

Where grant management meets procurement

Many organisations run both. A council runs grant programmes for the voluntary sector and procures services from providers, sometimes from the same organisations. A funder disburses grants and also buys evaluation, audit and programme management for itself. Keeping these on separate systems with different governance produces duplicated supplier records, inconsistent due diligence and a fragmented picture of who the organisation actually works with.

The overlap is largest in due diligence. Financial standing checks, safeguarding policies, insurance, governance documents, policies on equality and data protection: the same evidence is collected for grant applicants and for tenderers, usually twice, usually by different teams, usually with different expiry tracking. Holding it once, against the organisation, with expiry dates and renewal prompts, removes a genuine burden from both sides.

The other overlap is capacity. Grant rounds and procurement pipelines compete for the same officers and the same governance meetings. A single view of what is coming, when, and who is needed for it turns two competing workloads into one plannable one. That is a scheduling problem, and it is solvable once the information is in one place.

How eSourcing Data supports grant management

eSourcing Data covers source to contract, and the same building blocks apply cleanly to grant making: structured application rounds with published criteria and timetables, independent scoring with recorded rationale, moderation, organisation records with assurance documents and expiry tracking, award and agreement records, claim and milestone workflows, and analytics across the portfolio. Governance and audit run through all of it, so the record is created as work happens rather than assembled afterwards.

For funders that both grant and procure, holding both in one environment removes the duplicated due diligence and gives a single view of every organisation the funder deals with, whether as grant recipient, supplier or both. Below threshold workflows cover the smaller purchases that grant programmes generate, which are otherwise the least documented spend in the organisation.

The software is available to public buyers through RM1557.15 G-Cloud 15, with 28 software services listed on the Digital Marketplace plus cloud support services, and framework purchases are made as call off contracts. Data is held in the UK and the platform is GDPR compliant. The Procurement Library sets out the official Procurement Act guidance, Procurement Policy Notes and commercial playbooks, which is the right starting point for teams working through the grant and contract boundary.