Platform comparisons in the grants sector usually focus on form builders, workflow flexibility, and pricing. For a community foundation or a corporate giving programme, that framing is mostly adequate.
For a government agency or Crown entity in New Zealand, it is not. The evaluation criteria that matter most — immutable audit trails, conflict-of-interest enforcement at the data access level, ministerial reporting, data residency inside Aotearoa, OIA readiness — are structural requirements, not feature preferences. And most vendor comparison guides don't address them directly.
This article does. It is written for grants managers, IT managers, and procurement leads at NZ and AU government agencies who are actively evaluating grants platforms and need to know specifically where each one stands.
A private foundation choosing between platforms is weighing operational efficiency against implementation cost. The risk of getting it wrong is real but bounded: a grantee might receive a late payment, a board might lack adequate reporting, an assessor might score an application they shouldn't have.
For a Crown entity or government agency, the risk profile is different. The grants programme operates under the Official Information Act. Decisions made with public money are subject to scrutiny by the Office of the Auditor-General. Parliamentary reporting obligations are statutory, not discretionary. A conflict of interest that wasn't properly managed is not an administrative oversight — it is a governance failure with reputational and legal consequences.
Those aren't hypothetical risks. They are the actual operating environment for agencies like Te Māngai Pāho, NZ On Air, and Taupō District Council. The platform you choose either supports that environment structurally or it doesn't. The question this comparison tries to answer is which one does.
SmartyGrants built its position in Australasia by solving a real operational problem: enabling agencies to run contestable grant rounds without requiring custom development. Its form builder is mature, its assessment tools are well-understood in the sector, and its installed base means applicant organisations are already familiar with it. Those are genuine advantages, especially for agencies managing high-volume intake.
For the intake and assessment phase of grants management — advertising a round, receiving applications, assigning assessors, collecting scores, and communicating outcomes — SmartyGrants performs well. Many government agencies have used it for exactly that purpose for years.
The question is what happens when the evaluation moves beyond intake.
Most platform comparison articles evaluate features that apply equally to all types of funders: application forms, scoring rubrics, assessor portals, notification emails. Those things matter. But a Crown entity has additional requirements that don't appear on standard feature checklists:
OIA readiness. Can the system produce a complete, structured, timestamped record of every decision made on every application — in a form that can be disclosed — without manual reconstruction? The twenty-working-day clock on an OIA response starts when the request arrives, not when you find the files.
Ministerial and parliamentary reporting. Crown entities and government agencies are frequently required to report to ministers or to Parliament on the operation of their grant programmes. That reporting needs to be accurate, consistent, and auditable.
COI enforcement. Conflict-of-interest declarations are required governance practice. But a declaration that isn't enforced by the system is just a policy. The structural question is whether assessors who declare a conflict are automatically blocked from accessing that application's scoring data.
Data residency. For agencies subject to the Privacy Act and government security frameworks, where data is stored is a procurement requirement, not a preference. "Hosted in the cloud" is not an adequate answer.
Post-award accountability. Government grants don't end at approval. Accountability obligations — milestone reporting, payment conditions, contract management — carry the same transparency and audit requirements as the assessment process.
An audit trail in the genuine sense is a chronological, immutable, field-level log of every action taken on every application: who entered a score, when they entered it, whether they had a declared conflict, who approved a payment, which decision letter was sent and when. It is not a folder of decision memos or a spreadsheet of application statuses.
The audit trail requirements for NZ government grants programmes are covered in detail in a separate article. The relevant point for this comparison is structural: government-grade audit logging has to be built into the system at the data layer. It cannot be added by process or policy.
Tahua's audit trail operates at field level. Every change to every application record is logged against a named user with a timestamp. That log is immutable: it cannot be edited, and it is not dependent on user behaviour. Te Māngai Pāho, which administers a $60M+ annual programme, uses this as part of its accountability infrastructure. NZ On Air, which has parliamentary reporting obligations, relies on the same audit architecture.
When evaluating any platform for government use, ask: can you show me a sample audit log for a complete grant cycle, from application receipt to final payment? A log that shows status changes is not the same as a log that captures every field-level action.
Most grants platforms support conflict-of-interest declarations. Assessors are asked to declare whether they have a conflict with an applicant. The process stops there.
The structural question is what happens after the declaration. If an assessor declares a conflict and the system sends them an email confirming receipt, but does not automatically block their access to that application's scoring record, the declaration is a policy step, not an enforcement step. The conflict is documented but not prevented.
Tahua's COI management works at the data access level. When an assessor declares a conflict with a specific application, the system automatically recuses them: they cannot see that application's form data, scoring rubric, or assessment history. The recusal is logged as a permanent part of the audit trail. The programme manager does not need to manually reassign reviewers or hope that the assessor self-manages.
For a Crown entity running a contestable round with named assessors, the difference between documented-but-not-enforced and enforced-at-access-level is significant. If a conflict of interest complaint arises post-decision, the audit trail needs to show not just that the assessor declared a conflict but that they could not have influenced the outcome.
For NZ government agencies and Crown entities, data residency is a procurement requirement. The Privacy Act and the New Zealand Information Security Manual both inform how agencies should evaluate where their data is stored and processed.
Tahua is hosted on AWS ap-southeast-2, which is physically located in Sydney. All data remains within that region and does not transit through overseas jurisdictions. Storage uses AES-256 encryption. The platform is aligned with NZISM requirements.
When evaluating any platform, ask for explicit confirmation of the data residency jurisdiction and request the relevant security certifications. "Hosted in Australia or New Zealand" needs to be verifiable, not asserted.
Government grants do not end at approval. A contestable round managed by a Crown entity typically involves:
This is where most intake-focused platforms — including SmartyGrants — require workarounds. If milestone tracking happens in a spreadsheet and payment release is managed via email, the audit trail for the post-award phase is fragmented and potentially incomplete.
Tahua covers the full post-award lifecycle natively: milestone submission, evidence review and approval, automated payment creation in Xero, accountability report management, and public register publishing. Taupō District Council uses the public register feature specifically to meet community accountability obligations. Te Māngai Pāho manages its entire post-award workflow — including milestone tracking across a large portfolio — within the same system that handles intake and assessment.
Generic platform demonstrations will show you form builders, dashboards, and applicant portals. For a government procurement, those are the easy questions. Before you complete your evaluation, ask each vendor specifically:
The answers to those five questions will tell you more than a standard feature demonstration.
For Crown entities and government agencies that need a platform purpose-built for NZ public sector accountability requirements, Tahua's government grants management capability is worth evaluating specifically. You can also book a 30-minute demonstration that walks through the audit trail, COI enforcement, and post-award workflow in a government context.