A grant offer letter does two things at once. It communicates a funding decision to the applicant — you have been successful, here is what we are offering. And it defines the terms of that funding — here is what you are agreeing to, what conditions apply, and what happens if conditions are not met.
Most offer letters do the first job adequately. Many do the second job poorly — either because conditions are vague, accountability requirements are unspecified, or the consequences of non-performance are unstated. When problems arise later in the grant lifecycle, the offer letter is the document everyone refers back to. If that document is unclear, the problem is harder to resolve.
Grant details. The amount, purpose, and grant period need to be stated precisely. "Up to $50,000 for the purposes outlined in your application" is not precise enough. The purpose should be stated specifically (for the delivery of the summer youth employment programme as described in the application submitted 14 March 2025) with a clear statement that funds may only be used for that purpose. The grant period should specify start and end dates, not just a year.
Conditions precedent. If there are conditions that must be met before the offer can be accepted or before funding is released, they need to be listed explicitly. Common conditions precedent: signing and returning the acceptance within a specified period, providing evidence of insurance, providing bank account details, providing signed IRB/ethics approval. If these conditions are not listed, they cannot be enforced.
Reporting requirements. What does the grantee need to report, in what format, and when? Vague requirements like "provide a progress report annually" are insufficient. The offer letter should specify: what information the progress report must contain (financial statement, milestone status, outcome data), the deadline (by 31 March each year), and the format (using the funder's template, available at [link]). If reporting is a condition of payment release, this linkage should be stated explicitly.
Milestone schedule. For grants with staged payments, the milestone schedule should be in the offer letter or attached as a schedule. Each milestone should specify: what must be delivered, by when, what evidence of delivery is required, and what payment is released on delivery. The milestone schedule is the accountability architecture for the grant — if it is not clear, accountability is not enforced.
Variation process. Grants rarely proceed exactly as planned. The offer letter should specify how variations can be requested, who has authority to approve them, and what changes require written approval versus what can be managed through informal notification. Without a clear variation process, grantees who need to vary their programme operate in uncertainty, and funders who want to enforce original conditions may find that they have tacitly accepted variation through inaction.
What happens if conditions are not met. The offer letter needs to address the consequences of non-performance — not as a threat, but as a documented understanding. If a grantee fails to submit required reports, what is the funder's response? If milestones are not met, can funding be withheld or reclaimed? If the grant is used for purposes outside the approved scope, what action can the funder take? Many funders are reluctant to include this language, fearing it will seem adversarial. The alternative — having no agreed consequences and needing to improvise a response when problems arise — is worse.
Repayment obligations. If the grant or part of the grant needs to be repaid (because conditions were not met, because the organisation dissolves before the programme is complete, or because unused funds at the end of the grant period are to be returned), repayment obligations should be specified. The amount, the trigger, the process, and the timeline for repayment should all be in the offer letter.
An offer letter that does not require a formal acceptance is a one-sided communication. The grantee has received the offer but has not confirmed they understand and agree to the conditions.
For most grants, the acceptance mechanism should require:
- A signed acceptance from an authorised officer of the grantee organisation
- Confirmation that the conditions have been read and understood
- Confirmation of bank account details for payment
- Satisfaction of any conditions precedent
The acceptance creates a record that the grantee received and agreed to the terms. It is the starting point for the accountability relationship. Without it, disputes about whether conditions were understood and agreed to are harder to resolve.
Conditions that cannot be objectively assessed. "Deliver high-quality services to the community" is not a condition — there is no standard against which to assess compliance. "Deliver services to a minimum of 150 participants, with attendance recorded and reported quarterly" is assessable.
Implied conditions that are not stated. Funders sometimes assume that grantees know they cannot on-grant the funding without approval, or that they must notify the funder of significant changes to the funded programme. Unless these requirements are stated, they are not conditions of the grant.
Conditions that conflict. Offer letters sometimes contain internally inconsistent conditions — a reporting deadline that predates the end of the activity it is supposed to report on, or milestone requirements that cannot all be satisfied within the grant period. These create disputes that could have been avoided by reading the offer letter carefully before it was sent.
No mechanism for dispute resolution. If the funder and grantee disagree about whether a condition has been met, or about whether a variation request should be approved, who decides? Having an escalation process in the offer letter — even a simple one — prevents disputes from becoming impasses.
Most funders use offer letter templates. Templates are efficient and ensure consistency across grants. But templates need to be updated when legislation changes, when the funder's approach changes, and when experience reveals gaps in the existing language.
A template that has been used without review for five years may contain conditions that no longer reflect the funder's practice, omit conditions that have become important, or include language that is no longer legally accurate.
Annual review of offer letter templates — by someone with relevant legal knowledge and someone with programme management experience — is a worthwhile investment. A programme that makes 100 grants per year using a defective template has 100 defective grant agreements in place.
For funders looking to improve their grant agreement and documentation processes, the grants management solution pages cover how Tahua handles automated offer letter generation, condition tracking, and milestone management. To discuss your specific programme requirements, book a conversation.