A funding decision can be difficult to explain even when the team has considered the application carefully. The explanation may be spread across an assessment form, meeting notes and an email. When someone asks why a decision was made, reconstructing the answer becomes another piece of work.
For grant-provider teams, a decision trail is a practical way to connect those pieces. It should show what the team considered, how the decision relates to the programme’s criteria, and what happens next. This is a process-review checklist, not advice about legal compliance or a substitute for your organisation’s policies.
Before the round opens, check that the assessment team and applicants are working from the same criteria. Separate eligibility checks from the considerations used to assess eligible applications. If a criterion is ambiguous, resolve it before reviewers begin rather than leaving each assessor to interpret it differently.
Consider a hypothetical community funding round with three published assessment criteria: community benefit, feasibility and an achievable delivery plan. The assessment record should refer to those criteria. A preference introduced during a meeting should not silently become an additional test that applicants never saw.
Keep the criteria version with the round’s records. That gives a later reviewer a starting point without relying on someone’s memory of what the programme intended.
A score or a decision label does not explain itself. Ask reviewers to record the evidence they considered and how it relates to the relevant criterion. Distinguish information supplied by the applicant from assumptions, unanswered questions and the team’s judgement.
In the hypothetical round, an application might describe a clear community need but leave the delivery timetable uncertain. A useful note would identify that uncertainty under feasibility, record any clarification received, and explain how it influenced the recommendation. “Not a strong application” gives the next person much less to work with.
Where the final decision differs from the recommendation, record the reason for the difference. The aim is a readable account of the decision, not a longer form for its own sake.
Use your programme’s own conflict-of-interest rules. Make it clear where declarations are recorded, who considers them, and what participation arrangements follow. Do not assume that every declared relationship requires the same response.
Suppose a reviewer in the hypothetical round declares a connection with one applicant. Record the declaration and the participation decision made under the programme’s rules. Keep that record connected to the relevant assessment so a later reader can understand who contributed, without having to infer it from attendance alone.
Once the decision is made, check the applicant-facing communication against the recorded outcome. State what happens next, any information the applicant needs to provide, and the contact route the programme actually offers. Do not promise feedback, reconsideration or reporting arrangements that have not been established.
For a funded application, the next step might be confirmation of the agreed delivery timetable. For an unsuccessful application, it might be the outcome notification and the existing feedback process. The record should make it possible to see what was communicated and when.
Choose one decision and ask a colleague who was not involved to follow it from the published criteria to the assessment, decision and applicant communication. Note where they need an explanation from the original team.
Use those gaps to improve the next round’s process: a clearer criterion, a more useful reasoning prompt, or a better connection between records. Avoid measuring success by the number of fields completed alone.
Could a colleague understand one of your recent funding decisions from its records, without asking the person who made it?