How to read an award letter for obligations

An award letter arrives looking like good news, and it is. It is also a contract. Everything your organisation is now obliged to do — and every condition under which the money can be taken back — is in that document and the documents it points to. Reading it properly, once, is the highest-leverage hour in the whole grant lifecycle.

It is a contract

The practical consequence of that framing: you are not skimming for the amount and the end date. You are looking for every sentence that creates a duty, and every sentence that creates a condition. Those sentences are rarely flagged, rarely in one section, and frequently written in a register designed to be unambiguous rather than readable.

Do this before the money is spent, not when the first report is due. Several of the obligations you will find are things you must set up in advance — cost-tracking granularity, time-and-effort records, procurement procedures — and which cannot be reconstructed retrospectively.

The four buckets

Every obligation in an award letter falls into one of four kinds.

Reporting

What you must send, to whom, in what format, by when. Watch for programmatic and financial reports having different deadlines, different recipients and different submission portals. Note the format requirement explicitly — “via the agency portal” is a different obligation from “by email to your programme officer”, and portal registrations can take weeks.

Financial

The budget you are held to, what counts as an allowable cost, indirect-cost treatment, matching or cost-share requirements, and the mechanics and timing of drawdowns or invoices. Cost-share is worth special attention: it creates a documentation obligation, not just a funding one, and unsubstantiated match is a common audit finding.

Approvals

Anything requiring the funder’s written consent before you act. Typically: budget reallocations beyond a stated percentage, changes to scope or objectives, changes in key personnel, no-cost extensions, and subawarding any portion of the work. Record the tolerance, not just the existence of the rule — “prior approval required” is unusable; “prior approval required for any line moving more than 10%” is actionable.

Records and conduct

Record retention periods, audit access rights, insurance, conflict-of-interest and procurement policies, non-discrimination and reporting-of-concerns clauses, and any acknowledgement requirements for publications or signage. Low drama, easy to skip, and precisely the category an auditor can verify instantly.

The documents you were not sent

This is the single most commonly missed part of an award. Award letters routinely bind you to documents that are not attached — a funder’s general terms and conditions, an agency grants policy statement, a programme-specific addendum, or a body of regulation cited only by number.

Phrases to hunt for: incorporated by reference, subject to, in accordance with, as set forth in, governed by. Each one is a pointer to a document you now need to obtain, read and store alongside the award.

Trigger language to search for

When you have the document as text, searching for the language that creates duties will find most of them faster than reading linearly. Obligations tend to announce themselves:

• Duties: shall, must, is required to, agrees to, will provide, no later than, within [n] days
• Conditions: if, in the event that, should, exceeds, equal to or greater than, unless
• Approvals: prior written approval, prior consent, may not … without, subject to approval
• Consequences: termination, suspension, disallowed costs, repayment, high-risk

The consequences list is worth reading even though it creates no task. Knowing which failures are recoverable and which put the award itself at risk is what lets you triage sensibly when something does slip.

Always cite the page

Whatever you extract, record where it came from — document and page. This sounds fussy and pays for itself the first time somebody asks “are we actually required to do that?”

Without a citation, every extracted obligation is a claim someone has to take on trust, and re-verifying it means re-reading the whole agreement. With one, it is a ten-second check. It also means a colleague who joins in two years can audit your interpretation instead of inheriting it.

This is the part Grantwell automates: upload the award letter and every obligation comes back with the page it was found on, so the source is always one click away rather than a memory of having read something.

This guide is general information about how grant compliance work is commonly organised, not legal, audit or accounting advice. Grant rules change, and terms vary by funder and award — always check your own award documents and the current regulation, and talk to your auditor about your specific circumstances.