Local government operates grants programmes under a different accountability standard than most other funders. Decisions made about ratepayer or government-allocated funds are subject to OIA requests, audit scrutiny, and elected member oversight in a way that decisions made by private trusts are not. That accountability obligation shapes every aspect of how a well-run local government grants process needs to work.
Most local councils run multiple concurrent grants rounds. A typical mid-sized territorial authority might operate a community events fund, a discretionary community grants round, a contestable arts and culture fund, and a separately governed emergency grants facility. Each of these may have different eligibility criteria, different assessment frameworks, and different delegation levels for final decisions. Managing this complexity across a shared grants administration function — often with a small team and high staff turnover — is a significant operational challenge.
Probity in grants administration is not a preference; for local government, it is a legal and policy obligation. The OAG's better practice guidance on managing conflicts of interest and the Treasury's framework for contestable funding both set standards that public sector grants programmes need to meet.
The practical requirements this creates:
Documented assessment processes. Every decision must be traceable to a published criterion set. An assessor who scores an application needs to record that score against specific criteria. A panel that recommends funding must record the basis for that recommendation. The documentation cannot be assembled retrospectively — it needs to be created as part of the process, with timestamps that establish when each step occurred.
Conflict of interest management. Assessors reviewing applications from organisations in which they have a financial, professional, or personal interest must declare that conflict and be managed out of that assessment. For local government panels, where assessors are often appointed from the community because of their sector knowledge, COI rates can be significant. A process that relies on assessors self-reporting conflicts without a structured declaration step and a documented management process creates risk.
Audit trail completeness. When an OIA request arrives asking for the basis of a funding decision, the answer needs to come from a complete, contemporaneous record — not from someone's memory or a retroactively compiled file. The audit trail needs to cover every material step: when the application was received, who reviewed it, what scores were assigned, what the panel discussed, what the final recommendation was, and who approved it.
Equality of process. Different applications for the same fund need to be assessed by the same process. Departures from the published criteria — even well-intentioned ones — create legal and reputational risk. If one application was given additional time to provide information that others were not offered, that needs to be documented and justified. Consistency of process is both an equity requirement and a probity requirement.
Many local councils have historically managed grants through combinations of spreadsheets, email, shared drives, and general-purpose project management tools. Some have used generic form-builder tools for applications. The problem is not that these tools fail technically — it is that they do not produce the documentation record that the probity standard requires without significant manual effort.
A spreadsheet can store scores, but it cannot record who entered a score, when they entered it, or whether the score was changed after entry. An email thread can contain a COI declaration, but that declaration is not associated with the specific application it relates to, is not searchable across all assessors for a round, and is stored in a personal inbox rather than the programme record.
The manual work required to compensate for these gaps — compiling assessment records from multiple sources, assembling COI logs, producing decision documentation for governance sign-off — creates overhead that falls on programme coordinators who have other responsibilities. It also introduces the possibility of error in a context where errors have formal consequences.
For larger councils or regional bodies running multiple concurrent rounds, panel management is one of the most operationally intensive parts of the grants function.
Panel members are typically appointed for their sector expertise. A community grants panel might include a representative from the local disability sector, a financial capability assessor, a youth sector worker, and someone with governance experience. The combination of expertise and connection to the community creates COI risk — but that risk is manageable with the right process.
Key operational requirements for panel management:
Automated assignment. Assessors should be assigned to specific applications based on their declared expertise areas and their conflict declarations, with the system preventing them from seeing applications where they have declared a conflict.
Consistent rubric visibility. Every assessor reviewing an application should see the same scoring criteria and the same guidance notes. Assessors who assess in parallel need to arrive at scores independently, before group discussion.
Aggregated scoring without premature consensus. Individual scores need to be recorded before aggregation is visible. Assessors who can see how others have scored before they submit their own scores are not producing independent assessments.
Panel deliberation record. Where panel discussion changes individual scores or produces a recommendation that diverges from the aggregate scores, the basis for that discussion needs to be recorded.
For local government grants, the accountability obligation does not end with the decision. Funded organisations have conditions attached to their grants. Those conditions need to be communicated, tracked, and enforced.
Common accountability failure modes in local government grants programmes:
The consequence of these failures is not just administrative. When a council makes a subsequent funding decision about an organisation that has not met previous accountability requirements, and those accountability failures are not visible in the system, the council is making that decision without the information it needs.
Grant decisions in local government typically require formal governance sign-off — either by a committee of elected members or by officers acting under delegated authority. That sign-off process creates documentation requirements of its own.
The committee or officer making the final decision needs:
- A summary of all applications, their eligibility status, and their assessment scores
- The panel's recommendation, including the basis for that recommendation
- Any conflicts of interest declared and how they were managed
- In some cases, the full application record for any grants being declined or where the decision departs from the panel recommendation
Producing this governance package from a spreadsheet-based system requires manual compilation that creates both workload and risk of error. A purpose-built system should be able to generate this package directly from the assessment data, with all records timestamped and attributed.
For councils and Crown entities reviewing their grants administration, the government grants management page covers how Tahua handles probity requirements, assessment workflow, and post-award accountability. To discuss your programme's specific requirements, book a conversation.