Post-Award Grant Management: What to Do After You Win

Most grant-writing content stops at “you won.” That's the dramatic moment, the email you screenshot, the line on next year's board report. But the hard 80% of a grant's lifecycle starts after the award letter arrives — and the way you handle that 80% is what determines whether the same funder writes you a check again.

This guide walks through what actually happens after you win: reading the award letter for what it really obligates you to, setting up your deliverables and spending ledgers, hitting the reporting cadence funders expect, surviving budget revisions and no-cost extensions, and closing the grant cleanly. Get post-award management right and your funder relationships compound. Get it wrong and your next LOI lands in the “we had problems with them” pile.

Step 1: Read the award letter like it's a contract — because it is

The award letter, Notice of Award, or grant agreement is a legal document. The day it arrives, your job stops being “celebrate” and becomes “index every promise embedded in this paper.” Most teams skim it once, file it, and rediscover its requirements at the worst possible moment — usually 60 days into the project when someone realizes the funder requires a kickoff report nobody started.

Read every page and pull out, on a single page of your own:

• The period of performance. The exact start and end dates that money can be obligated and spent. See period of performance — costs incurred outside this window are unallowable, full stop, with a narrow exception for pre-award costs if the agreement explicitly authorizes them.
• The award amount and its splits. Total award, federal share vs. non-federal match if applicable, direct vs. indirect, and any restrictions on specific budget lines (“up to $X for travel, capped at Y% of personnel”).
• The reporting calendar. What reports are due, when, in what format, and to whom. Federal awards usually require a Federal Financial Report (FFR/SF-425) and a programmatic progress report at fixed intervals. Foundations typically want one interim narrative + one final.
• The deliverables you promised. Numbers, milestones, populations served, outputs, and outcomes — copy them verbatim from your proposal into your tracking system. The program officer will compare your final report against this list.
• Special conditions. Many award letters add clauses on top of the standard terms — IRB approval before research starts, letters of support that need countersignatures, prior approval required to rebudget more than 10% across categories, mandatory subrecipient monitoring. Miss one and the funder can claw back funds.
• The terms incorporated by reference. Federal awards bind you to the OMB Uniform Guidance (2 CFR 200) by reference, plus the agency's own General Terms and Conditions. That's another 200 pages of rules you just signed up for. You don't need to memorize them, but you do need to know they exist and which sections govern your spending, reporting, and audit obligations.

Save that one-page summary somewhere your finance lead, program lead, and executive director all see weekly. It's the source of truth for everything that follows.

Step 2: Build the deliverables ledger before week one

Every promise you made in the proposal is now a deliverable. The most common post-award failure mode is realizing in month nine that you committed to outputs nobody on the implementation team knew about — usually because the proposal was written by the development team and the work is being done by a program team that never saw it.

Within the first two weeks of the award, create a deliverables ledger that lists, for each commitment:

• What you said you would do, in the funder's language
• The numerical target (250 students tutored, 4 community workshops, 1 evaluation report)
• The due date or milestone
• Who on staff owns it
• Where the proof of completion will live (sign-in sheets, pre/post surveys, dataset, photos, etc.)

Most teams discover, doing this exercise, that the proposal promised more than they remembered. That's fine — you'd rather discover it in month one than month eleven. If a commitment looks unrealistic now, flag it for a budget revision conversation early; funders are far more receptive to a heads-up in month two than to bad news in the final report.

Step 3: Stand up a separate spending ledger per award

Restricted grant dollars must be tracked separately from your general operating funds. That's not a best practice; it's a Uniform Guidance requirement for federal awards (§ 200.302) and a baseline expectation for any private foundation that funded a specific program. The auditor wants to see, on demand, exactly how every dollar of award X was spent and how it was attributed to the budget categories you proposed.

Practically, that means:

• A dedicated class, fund, or project code in your accounting system for each award. QuickBooks classes, Sage projects, or whatever your general ledger calls them — every transaction either belongs to the award or it doesn't.
• Time and effort certification for personnel charged to the grant. If a staff member is 40% on the award, you need contemporaneous timesheets supporting that allocation, not a percentage estimated after the fact. Personnel is the largest line on most budgets and the most-audited.
• A clear test for allowable costs: reasonable, allocable to the award, and not on the agency's unallowable list (alcohol, fundraising, lobbying, entertainment, first-class travel, etc. for federal awards). When in doubt, ask before you spend.
• A monthly drawdown discipline. Don't let actuals drift more than one cycle from your budget — a month of unreviewed spending becomes a quarter and a quarter becomes a final-report scramble.

For a deeper read on what counts as allowable and how the math works, the budget narrative guide covers personnel, fringe, indirect costs, and the MTDC (Modified Total Direct Costs) calculation in detail. The same definitions apply post-award — the only difference is now you're defending real numbers to a real auditor instead of estimates to a reviewer.

Step 4: Hit the reporting cadence the way the funder expects it

Reports are not the place to be creative. The funder has a template, a length expectation, and a calendar; deliver against all three and you'll be in the top quartile of their grantees on responsiveness alone.

The four flavors of report you'll see most:

• Programmatic / narrative. What did you do this period, against what you promised? Lead with the numerical outputs (X tutored, Y workshops held), then the stories that humanize them, then what didn't go to plan and how you're adjusting. Funders read the “what didn't go to plan” section closely — silence there reads as dishonesty, not as everything-was-perfect.
• Financial. Federal grants require an FFR (SF-425) on a quarterly, semi-annual, or annual schedule depending on the award. Foundations usually accept your internal financial statement filtered to the project. Every line in the narrative should reconcile to a line in the financial; mismatches are the single most common cause of bounced reports.
• Outcomes / evaluation. For multi-year awards or anything with a logic model, the funder may want pre/post measurements demonstrating change. Plan how you'll collect baseline data before the program starts — you can't baseline retroactively.
• Final report. The summary at closeout: total spending against budget, total deliverables against targets, impact narrative, and what you'd do differently. This is the single most important document you'll write for that funder relationship — it gets read by the program officer who decides whether to renew, by their successor, and by anyone the funder consults later when you apply elsewhere.

Set the due dates as calendar holds at least two weeks before the actual deadline. Reports submitted in the last 24 hours read as afterthoughts. Reports submitted three days early read as professionalism, full stop.

Step 5: Keep the audit trail you'd want if your auditor showed up tomorrow

For federal awards, the standard is contemporaneous documentation: receipts, invoices, timesheets, contracts, and approvals saved at the time the transaction happened, not reconstructed at audit time. For private foundation awards, the bar is lower but the principle is identical: you should be able to defend any number on any line of any report with paperwork that already exists.

Practically, store the following in a single, organized place per award:

• The signed grant agreement and any amendments
• The approved budget and any approved revisions
• All correspondence with the program officer, especially anything that grants approval (rebudgeting, scope change, no-cost extension)
• Receipts, invoices, and supporting documentation for every expense
• Time-and-effort records for every staff member charged to the grant
• Subrecipient agreements, monitoring records, and their own audit reports
• All submitted reports and the funder's acknowledgments

Federal grant records must be retained for three years from the date of submission of the final expenditure report (Uniform Guidance § 200.334). If your organization spends more than $750,000 in federal awards in a single fiscal year, you trigger a Single Audit — a comprehensive audit of all your federal funding by an independent auditor.

Foundations rarely audit, but they do ask: what was your fundraising ratio on this project, can you give us the participant demographic breakdown, what does the photo of the workshop look like? An organized award folder turns those asks into 60-second responses instead of half-day archaeological digs.

When things go sideways: budget revisions and no-cost extensions

Reality drifts from the proposal. A staff member leaves, a partner backs out, a vendor raises prices, a participant population is smaller than projected. Funders know this. What they don't tolerate is finding out about it in the final report.

Two tools handle most drift:

• Budget revision (rebudgeting). Moving money between approved budget categories. Federal awards typically allow up to 10% of the total budget to be moved without prior approval; anything more requires a written request to the program officer. Foundations vary — some are flexible by phone, others require formal letters. Either way, ask before you spend, and document the answer.
• No-cost extension (NCE). Extra time without extra money — the most useful flexibility a funder offers. Federal awards generally allow one 12-month NCE on request, granted automatically for many programs. Apply at least 60 days before the period of performance ends; later than that and the agency may say no even when they would have said yes earlier.

The unifying rule: never let a problem become a surprise. A program officer told in month four that the cohort will be 80 instead of 100 will work with you. The same news at the final report reads as either incompetence or evasion, and either reading kills the relationship.

Step 6: Close the grant out cleanly

Closeout is the formal end of an award. For federal grants you have 120 days after the period of performance ends (Uniform Guidance § 200.344) to file the final FFR, the final programmatic report, and any other required closeout documents. Foundations are usually less prescriptive but expect a final narrative + final financial within 60–90 days.

A clean closeout has four pieces:

• Reconcile final spending. Total drawdowns minus total expenses must equal zero. Any unspent balance returns to the funder unless the agreement explicitly allows carryforward to a follow-on award.
• Submit the final reports. Programmatic, financial, and any required outcome / evaluation reports — ideally on the same day, so the funder reviews them together rather than chasing you for the missing piece.
• Settle subrecipients. If you passed money to partners, their final reports come to you first; you reconcile them; you submit the consolidated information to the prime funder.
• Archive everything. Audit retention starts from the date of the final report submission, so the closeout date is also the start of your three-year clock.

A grant that closes out cleanly is invisible to the funder — and invisible is exactly what you want. The grants funders remember are the messy ones.

The relationship play: how this becomes year two

Funder relationships are built post-award, not at proposal time. The proposal is the audition; the management is the role. A program officer with twenty grantees in their portfolio remembers the three who were responsive, hit their reports, and proactively shared program updates between cycles. Those three get the call when a new funding window opens.

Practical moves that compound:

• Send unsolicited mid-period updates. A two-paragraph email with one number and one story, no ask attached, every quarter. Most grantees never do this; it disproportionately moves you up the program officer's mental ranking.
• Share the read-only portal link with the funder. Some program officers love being able to glance at deliverable status and spending without opening an email thread. Offering a link signals confidence and saves them work.
• Lead the renewal conversation early. Three to four months before the period of performance ends, ask the program officer how they'd prefer to handle the next cycle. You're inviting them to think of you as the default option for the next budget.
• Cite the outcomes in your next LOI to anyone. A grant you closed out cleanly is the strongest possible credential in your next LOI: “In our most recent grant from [funder], we delivered X against a target of Y, on time and within budget.” That sentence is worth more than your entire mission paragraph.

The bottom line

Grant writing wins you a grant. Grant management wins you a funder. The teams that build durable funding pipelines aren't the ones with the best proposal templates — they're the ones who treat the period after the award letter as the most important chapter of the whole engagement.

Read the award letter like a contract. Build the deliverables ledger in week one. Run a separate spending ledger per award. Hit every report on time. Document everything. Communicate problems early. Close out cleanly. Do that on five grants in a row and your next five proposals are no longer cold pitches — they're renewal conversations.