Managing Grant Agreements

Grant Agreements is where grant staff publish and manage the versioned compliance agreement that grantees accept. It is step 1 of Grant Compliance. Agreement templates are versioned and append-only: you never edit a published version in place, and publishing a new version requires grantees to re-accept. The version body is hashed, so each acceptance proves exactly which terms the grantee saw.

Publishing a new version

To publish a version:

• Enter a Version label (for example, v1.0 2026-06-01).
• Edit the Agreement body, written in Markdown. It is pre-filled from the standard agreement template; use Reset to standard template to start over from it.
• Placeholders like {{token}} are filled in server-side for each grantee at signing — grantee and signer details come from the acceptance form, and grantor details from your governance configuration. The Preview highlights the fields that get substituted. The base agreement carries no fixed grant amount — grant financials come from the board approval, not from the template.
• Optionally set Default terms (JSON) for template-level defaults such as the reporting schedule.

Click Publish version to make it available for acceptance.

Published versions and acceptances

Below the editor, two tables track the record:

• Published versions — every version with its label, language, a short hash of its body, and when it was published.
• Recorded acceptances — each grantee acceptance with the organization, the signer, when they accepted, and a reference ID.

How grantees accept

Grantees accept a published version from their own dashboard. For the grantee-facing walkthrough of that flow, see Accepting Your Grant Agreement. When you publish a new version, grantees must accept the new version before continuing; the prior acceptance is kept as superseded.