"Best practice" in grants management is sometimes framed as a compliance matter — the things you need to do to satisfy an auditor or a regulatory review. That framing is too narrow. Best practice grants management is about designing programmes that work well for everyone involved: applicants who get a fair process, funders who get good decisions, governance bodies who can demonstrate oversight, and programme staff who can do their jobs without burning out.
This guide covers the practices that distinguish well-run grant programmes from ones that generate unnecessary risk, inconsistent outcomes, and administrative overhead.
The most common design error in grants management is building the application form before the assessment framework is confirmed. The two are logically dependent: the form should ask exactly what you need to assess applications against your criteria — no more, no less.
A documented assessment framework includes:
- The criteria against which applications will be evaluated
- The weighting of those criteria (expressed as percentages or relative scores)
- The standard of evidence required to meet each criterion
- The scoring methodology (numeric scales, descriptive bands, or hybrid approaches)
Organisations that build their application forms first, then try to retrofit an assessment framework, end up with either forms that collect information they never use, or assessors trying to evaluate applications against criteria that the form didn't actually measure.
The framework documentation should be completed and approved by governance before the round opens. It is a governance decision — the criteria reflect the programme's theory of change — not an administrative detail.
Ineligible applications that reach the assessment stage waste assessor time, create potential for inconsistent treatment, and generate administrative cleanup work. Best practice eligibility screening prevents this by building the check into the application process itself.
This means:
- Eligibility questions are the first thing an applicant encounters
- The portal confirms eligibility (or ineligibility) before allowing the full form to be completed
- Ineligible applicants receive an immediate, clear explanation of why they do not qualify
The eligibility criteria need to be sufficiently precise to be objectively determinable. "Significant community benefit" is not an eligibility criterion — it is a judgement call that belongs in the assessment. "Registered with Charities Services NZ with a charitable purpose relating to X" is an eligibility criterion. The distinction matters because eligibility is meant to be a rule, not an exercise of discretion.
Most grant programmes have a conflict of interest policy that describes what assessors should do when they have a conflict. Fewer have a process that makes doing the right thing the path of least resistance.
Architectural COI management means:
- COI declarations are a mandatory step in the assessor workflow, not a reminder email
- The form captures sufficient detail to distinguish different types of conflict (financial interest, prior relationship, current role, etc.)
- The decision about how to manage a declared conflict is documented by the panel convenor, not left implicit
- The conflict and its management are part of the permanent assessment record
An assessor who receives ten applications and a PDF COI policy is in a worse position than an assessor who encounters a structured declaration screen that requires them to review each application against their conflicts before they can access it. The system design should support the right behaviour, not assume it.
The most common audit and OIA problem in grants management is not bad decisions — it is decisions made in the system but documented outside it. Panel recommendations made in a meeting, communicated by email, and later transcribed into a database create a chain of records that is difficult to reconstruct and easy to challenge.
Best practice means:
- Scoring happens in the grants management system, not in a spreadsheet that is later uploaded
- Panel recommendations are recorded in the system at the time of the meeting
- The basis for the final decision is captured in structured fields, not a summary paragraph written after the fact
- Every action that affects a grant outcome is timestamped and attributable to a named user
The test is not whether the information is somewhere — it is whether a complete, coherent decision record can be produced without manual reconstruction. If answering an OIA request requires someone to assemble the record from multiple sources, the process was not documented to best practice standard.
The common pattern of robust pre-award management and weak post-award management creates risk at the point where most grant funding is actually deployed. An organisation that cannot demonstrate what happened after it awarded grants has a compliance gap, even if its assessment process was rigorous.
Post-award best practice includes:
- Milestone schedules documented in the system at the point of award, not created separately
- Automated reminders to grantees approaching milestone deadlines (not a manual calendar check)
- Report submissions received and acknowledged in the system, not by email
- Payment releases triggered by milestone completion, with an auditable record
- Variations to grant conditions handled formally, with a record of the request, review, and decision
The key question for any post-award process: if a grantee was asked to demonstrate that they complied with their grant conditions, would the funder be able to confirm or deny that from the system records alone?
Programme managers in well-run grant teams do not spend significant time compiling board reports from spreadsheets. Governance reporting should be a byproduct of systematic record-keeping, not a separate task.
This requires:
- Programme-level dashboards that aggregate current status without manual compilation
- Standard report formats that governance bodies can receive on a consistent schedule
- Grant portfolio views that show active grants, milestone status, and outstanding obligations across all programmes
When governance reporting is manual, it is typically backward-looking (what happened last quarter), based on snapshots (accurate as of when it was compiled), and inconsistent between reporting periods. When it is systematic, governance bodies can ask questions about current programme status and receive accurate answers without creating work for programme staff.
Inconsistency between rounds is a significant risk for funders that run repeated programmes. Eligibility criteria that were interpreted one way in 2024 and a different way in 2025 create grounds for complaints from applicants who received different treatment without understanding why.
Best practice means:
- Eligibility criteria are reviewed before each round opens, and any changes are documented and communicated
- Assessment templates carry over between rounds with explicit version control
- Assessors new to a programme are trained against the same framework as experienced assessors
- Decisions in round N can be compared to decisions in round N-1 for consistency
This consistency requirement is partly about fairness to applicants, and partly about institutional knowledge. A programme that runs the same way each year builds a record that can be used to identify trends, demonstrate impact, and respond to governance questions about comparative round performance.
For funders looking to implement these practices systematically, a purpose-built platform makes most of them structural rather than aspirational. Tahua is built around the accountability requirements of the NZ/AU grants landscape — for government funders, community foundations, and Iwi organisations.