Chapter 26: Managing the Grant After You Win — Reporting, Compliance, and Stewardship

This book has, until now, been almost entirely about getting the grant. But the award is not the finish line; it is the starting line of a new and demanding phase. Winning the grant means you now have to do what you promised — deliver the project, spend the money correctly, report on your progress, comply with the rules, and steward the relationship — under the watchful eye of a funder who is, in effect, your client and your most consequential future reference. Many grant writers pour everything into winning and then treat the management of the award as someone else's problem or an afterthought. That is a serious mistake, and this chapter — the closing skill of Part IV — explains why and how to manage a grant well. It also completes a circle the book has been drawing since Chapter 1: a grant is a transaction in which a funder buys progress toward their mission, and the award phase is where that progress is actually delivered — where the promise of the proposal either becomes real value in the world or doesn't. Managing the grant well is, in the end, simply keeping the promise the proposal made.

The reason it matters so much is captured in the chapter's threshold concept: stewardship of this grant is the strongest application for the next one. How you manage a funded award is not separate from grant-seeking; it is the most persuasive evidence a funder will ever have about whether to fund you again. A funder who watches you deliver what you promised, report honestly and on time, spend compliantly, and communicate well learns something no proposal can tell them: that you are trustworthy with their money and their mission. And the results, track record, and relationships you build through good stewardship become the foundation of every future proposal — the preliminary data for your next study, the demonstrated outcomes for your next foundation ask, the clean compliance record that makes the next federal award winnable. Manage this grant well, and you've written the most important part of your next proposal before you start it.

In this chapter we'll cover reading the notice of award and treating your proposal as a contract of promises, setting up the award in the first ninety days, delivering what you promised, meeting reporting obligations, managing the money and handling the changes every real project needs, satisfying the compliance and audit regime, and stewarding the relationship toward the next grant. Our anchors continue into their funded lives — Hernandez running her NIH R01, RYCC managing its Hartwell foundation grant, Lighthouse administering a government award — because the post-award world differs by funder just as the proposals did, and watching each steward its award shows the same threshold concept expressed in three registers: the research grant, the foundation grant, and the government grant each turned into the foundation for the next. (As always: post-award rules vary by funder and mechanism and change; verify specifics with your funder, your award terms, and your grants office.)

26.1 The Award Changes Everything: The Proposal Becomes a Contract

The first thing to understand is that winning changes the legal and practical nature of your proposal. Before the award, your proposal was an argument — a persuasive case for why you should be funded. After the award, your proposal becomes, in effect, a contract — a set of binding promises about what you will do, by when, with how much money, that you are now obligated to deliver.

This transformation is formalized in the notice of award (the funder's official document awarding the grant, sometimes called a notice of grant award or award letter), which specifies the amount, the period of performance, the terms and conditions, and the reporting and compliance requirements you're accepting. Read the notice of award carefully — it is as binding and important as the funding announcement was, and it often contains specific terms, conditions, and obligations beyond what you anticipated. Accepting the award means accepting these terms.

The deeper shift is in how you must now regard your own proposal. Every promise you made — the aims you'll pursue, the activities you'll deliver, the outcomes you'll achieve, the people you'll serve, the budget you'll spend, the equity commitments you made (Chapter 25) — is now a commitment you must keep and report on. This is why honesty in the proposal matters beyond ethics: you will have to deliver what you promised, so a proposal that over-promised becomes a project that under-delivers, with all the relationship and reputational damage that follows. The proposal you wrote is the work you must now do.

📊 From the Field: This reframing should change how you read every chapter of this book in retrospect. All the craft of winning — the compelling significance, the rigorous approach, the realistic budget, the achievable outcomes — was, it turns out, also the craft of being able to deliver, because the winning proposal becomes the binding plan. The investigator who inflated outcomes to impress reviewers now owes those outcomes; the organization that budgeted unrealistically now has to execute that budget; the applicant who promised an over-ambitious scope now has to deliver it in the time and money available. This is the quiet discipline behind honest proposal-writing that the earlier chapters urged: not only that fabrication is unethical and detectable, but that everything you promise, you will have to do. The most fundable grant writers, over a career, are those whose proposals and delivery match — who promise what they can deliver and then deliver what they promised — because that match is what earns the renewals, the track record, and the reputation that compound into sustained funding. An over-promised, under-delivered grant can damage a funding relationship more than a never-submitted proposal ever could. Write, always, the proposal you can actually fulfill.

🧩 Productive Struggle: Before reading on, consider how the knowledge that "the proposal becomes a contract I must deliver" should change the way you write proposals in the first place. Jot your thinking. The resolution, which connects this chapter back to the whole book, is that you should write every proposal as a set of promises you genuinely intend and are able to keep — ambitious but achievable, honest about what you can deliver, with a budget you can actually execute and outcomes you can actually reach. The applicants who write proposals to win without thinking about delivery set themselves up to fail at the harder, longer phase that follows; the ones who write proposals they can deliver win and succeed. Knowing that the award turns the proposal into a contract makes you a more honest, more careful, and ultimately more fundable writer — because funders fund people who deliver, and you can only deliver what you honestly promised.

26.2 Setting Up the Award: The First Ninety Days

A funded grant doesn't run itself, and the period right after the award — call it the first ninety days — is when you set up the machinery that will carry the project. Getting this phase right prevents most of the problems that plague poorly-managed grants.

Setup typically involves several parallel tasks. Staffing: hiring or assigning the people the project needs (the personnel you budgeted, Chapter 11), which can take longer than expected and delay the project if not started promptly. Purchasing and contracts: acquiring equipment, supplies, and services, and setting up any subawards (Chapter 23) with their agreements. Required approvals: securing the regulatory approvals your project needs before certain work can begin — for research involving human subjects, Institutional Review Board (IRB) approval; for animal research, IACUC approval; and others depending on the work. These approvals can take weeks or months, and starting them late delays everything. Financial setup: establishing the account, budget tracking, and spending controls (usually with your finance office) so you can spend and track funds correctly from day one. Kickoff: orienting the team, confirming roles and the timeline, and aligning everyone on the promises to be kept.

For Hernandez's R01, the first ninety days mean hiring her research coordinator, finalizing the subaward agreements with her clinical sites (Chapter 23), securing IRB approval at every site before enrolling a single participant, and setting up the financial tracking — all before the science truly begins. The IRB approvals are especially unforgiving: she literally cannot enroll a participant until each site's board has approved the protocol, and those reviews run on the boards' schedules, not hers — so any delay in submitting them pushes back the entire trial. Skip or delay any of these, and the whole project slips.

Lighthouse's setup looks different but follows the same logic (composite). Having won a government reentry grant (Chapter 19), Lighthouse's first ninety days mean hiring the case managers and the lived-experience staff its program depends on (Chapter 25); executing the subaward agreements with its housing, behavioral-health, and employer-partner organizations (Chapter 23) so funds can flow and work can start; setting up the financial tracking and the documentation systems the government award's compliance regime demands (Chapter 19); establishing the data systems to track participants and outcomes; and holding a kickoff that aligns all four partner organizations on roles, referral processes, and the reporting calendar. Notice that for a multi-partner government award, the setup is heavier and more time-sensitive than for a single-organization foundation grant — more agreements to execute, more compliance machinery to stand up, more partners to align — which is exactly why starting immediately matters. A reentry participant can't be served until the case managers are hired and the partner referral processes work; the clock on the period of performance is already running while all this is built. The most common early-stage grant-management failure is treating the award date as the start of the work when it's actually the start of the setup. The work — the research, the program, the service delivery — usually can't begin until the setup is done: staff hired, approvals secured, accounts established, subawards executed. Because setup takes time (IRB approval alone can take weeks to months), a project that doesn't start setup immediately loses precious weeks of its period of performance and may struggle to deliver everything it promised in the time remaining. The fix is to begin setup the moment the award is in hand (or even, where permitted, to prepare in anticipation), treating the first ninety days as a distinct, urgent phase with its own checklist and timeline. The grants that run smoothly are the ones that set up fast; the ones that scramble at the end are usually the ones that treated the award date as a finish line and started setup late.

26.3 Doing What You Promised

It sounds obvious, but it is the heart of grant management and the thing most directly tied to future funding: do what you said you would do. The project you proposed — the aims, activities, outcomes, populations, and commitments — is what you are now obligated and trusted to deliver.

This means executing the project as proposed (or as appropriately modified, Section 26.5), achieving the outcomes you promised, serving the people you said you'd serve, and honoring the specific commitments you made — including your equity and community commitments (Chapter 25), which become real obligations to the communities and partners involved, not just proposal language. The progressive project you've built through this book — RYCC's expansion to three sites and 90 students, Lighthouse's reentry program, Hernandez's trial — now has to happen, and happen as promised.

Real projects, of course, encounter reality: things take longer, approaches need adjustment, circumstances change. That's normal and manageable (Section 26.5 covers handling changes). What matters is that you're genuinely working to deliver what you promised, communicating with the funder when things change, and not quietly abandoning commitments. A funder understands that projects evolve; what damages trust is a grantee who took the money and didn't deliver, or who changed the project substantially without telling anyone, or who let promised outcomes and commitments quietly lapse without a word.

🚪 Threshold Concept: Stewardship of this grant is the strongest application for the next one. Everything you do while managing a funded award — delivering the work, reporting honestly, spending compliantly, communicating well — is being observed by a funder deciding, consciously or not, whether you're worth funding again. A grantee who delivers what they promised, reports on time, manages the money cleanly, and communicates openly builds something no proposal can manufacture: a track record of trustworthiness. That track record, plus the concrete results and relationships the grant produces, becomes the most persuasive evidence in your next application — the preliminary data, the demonstrated outcomes, the clean audit, the program officer who'll vouch for you. Cross this threshold and you stop seeing grant management as post-award drudgery separate from grant-seeking, and start seeing it as the most important grant-seeking you do — because funders fund proven deliverers, and stewardship is how you prove it. The next grant is won, in large part, by how you handle this one.

🪞 Learning Check-In: Notice whether, having spent this whole book learning to win grants, you've thought of managing them as a lesser, more clerical task — someone else's job, or a tedious afterthought to the exciting work of writing proposals. That framing is exactly backwards for your funding future. The funder's experience of you as a grantee — did you deliver? report well? spend cleanly? communicate? — shapes your fundability more than any single proposal, because it's direct evidence rather than promises. If you find yourself mentally checking out once the award arrives, recognize that you're checking out of the most consequential evidence-building you'll ever do. The grant writers who build sustained funding aren't only good at writing; they're good at delivering, and they know the two are inseparable.

26.4 Reporting: Telling the Funder How It's Going

Funders require reports — and reporting well is among the highest-leverage grant-management skills, because reports are the funder's primary window into your stewardship. Reporting obligations vary by funder but cluster into a few types.

Programmatic / progress reports describe what you've done and what you've achieved — activities delivered, outcomes reached, progress against the objectives and timeline in your proposal. At the NIH, the annual progress report is formalized as the Research Performance Progress Report (RPPR); other funders have their own formats and schedules (annual, semi-annual, quarterly). These reports are where you demonstrate you're delivering what you promised (Section 26.3), and they feed directly into the funder's view of you.

Financial reports describe how you've spent the money — expenditures against your approved budget categories, often on the funder's schedule and format. These must reconcile with your actual spending and your programmatic progress (the budget-narrative coherence of Chapter 12, now in execution).

Final reports at the end of the period of performance summarize what the whole grant accomplished — the outcomes, the impact, the deliverables, the spending — and are part of closeout (Section 26.6). A strong final report is also the seed of your next proposal's evidence base: the outcomes you document here become the demonstrated results you cite in your next application, so a careful, evidence-rich final report does double duty as both a closeout requirement and a head start on what comes next. It is worth writing the final report not as a chore to be discharged but as the first draft of your next proposal's track record.

🔄 Check Your Understanding: Midway through a grant, a project hits a real setback — recruitment is slower than planned, or an approach isn't working. A grantee is tempted to omit this from the progress report and emphasize only what's going well, hoping to fix it before anyone notices. Why is that the wrong instinct, and what should they do?

Answer

It's the wrong instinct because hiding problems destroys the very trust that drives future funding, and forfeits help the funder could provide. Funders trust grantees who are candid about challenges far more than those who paper over them — a program officer who later discovers a concealed problem (in a final report, an audit, or a crisis) learns the grantee can't be trusted to be honest, which is far more damaging than the setback itself. The right move: report the challenge honestly and specifically, with the grantee's analysis and plan to address it (and, where relevant, a request for the funder's input). Program officers have often seen the problem before and can help — extend the timeline, connect resources, advise — but only if they know. Honest reporting of difficulties, handled with a plan, builds trust and demonstrates competent management; concealment, when discovered, destroys it. Stewardship includes telling the truth when things are hard.

Report well, and a few principles make the difference. Report on time — late reports signal disorganization and can hold up funding (including future payments). Report honestly — including challenges and shortfalls, not just successes; funders trust grantees who are candid about difficulties far more than those who paper over them (and they often can help). Report specifically — concrete outcomes and evidence, not vague assurances. Connect to the promises — show progress against what you proposed, closing the loop the funder is tracking.

🗣️ From the Review Panel: (A program officer reflects on reports.) Reports tell me everything about whether I want to keep funding an organization. The good grantees report on time, tell me clearly what they accomplished against what they promised, and — crucially — are honest when something didn't go as planned, because then we can problem-solve together and I trust them. The ones that worry me send reports late, or full of vague generalities that dodge whether they actually hit their outcomes, or that hide problems until they've become crises. When it's time to consider a renewal or a new application, I remember exactly how an organization handled its reporting. A grantee who stewarded their last grant well — delivered, reported honestly, communicated — starts our next conversation with enormous credibility. One who went dark and missed reports starts in a hole, no matter how good the new proposal looks. Your reports are, in a real sense, your next application.

📐 Project Checkpoint — Draft a first-90-days post-award management plan: Imagine your project is funded. Draft a first-90-days plan: (1) Setup tasks and timeline — staffing, purchasing, required approvals (IRB/IACUC if applicable), subaward agreements, financial setup, kickoff — with who owns each and when it must be done. (2) A reporting calendar — every report due (programmatic, financial, final), its format, its deadline, and who prepares it, mapped across the period of performance. (3) Your promise list — the specific aims, outcomes, populations, and commitments (including equity commitments) you must now deliver and report on. (4) A budget-management plan — how you'll track spending against categories and what changes might need prior approval (Section 26.5). Save it in your "My Proposal" document. Writing this before you're funded makes you both a better manager and a more honest proposer, because you'll see what delivering your promises actually requires.

26.5 Managing the Money and Handling Changes

A real project rarely unfolds exactly as budgeted, and managing the money — including handling the changes every project needs — is a core grant-management skill governed by specific rules.

Spending within the rules. You spend the grant on what you budgeted, within the funder's cost rules (allowable, allocable, reasonable — Chapters 12, 19), tracking expenditures against your approved categories. Spending outside the rules, or wildly off your budget, creates compliance problems and audit findings.

Rebudgeting. When you need to move money between categories (spend less on one line, more on another), that's rebudgeting — and whether you can do it freely or need the funder's permission depends on the rules. Many funders allow modest rebudgeting within thresholds without approval but require prior approval for significant changes. Know your award's rebudgeting rules before you move money.

Prior approval. Certain changes require the funder's advance written permission — prior approval — before you make them: significant rebudgeting, a change in scope, a change in key personnel (e.g., the PI leaving or reducing effort substantially), extending the timeline, and others depending on the funder. Making a prior-approval change without getting approval first is a compliance violation, even if the change itself was reasonable. The rule: when in doubt about whether a change needs prior approval, ask the funder before acting.

Carryforward. When you don't spend all of a budget period's funds, carryforward is the (sometimes automatic, sometimes approval-requiring) process of moving unspent funds into the next period. Rules vary; know whether your unspent funds carry forward automatically or need permission.

No-cost extension. If you reach the end of your period of performance with work remaining and unspent funds (and no need for more money), a no-cost extension extends the time to finish without additional funds — a common and usually straightforward request, but one that typically must be requested before the period ends and may require funder approval. The no-cost extension is the standard tool for a project that needs more time but not more money.

🎓 Going Deeper — handling change as a normal part of grant life: New grantees sometimes fear that any deviation from the proposal is a failure or a violation. It isn't — change is normal, and funders expect it; what matters is handling it correctly. A few principles clarify. First, distinguish changes you can make freely (minor adjustments within the rules and thresholds) from changes requiring prior approval (significant rebudgeting, scope changes, key-personnel changes, timeline extensions) — and when unsure which category a change falls in, ask before acting. Second, recognize that the no-cost extension is a normal, common, usually-granted tool, not an admission of failure: many well-run projects need a bit more time, and requesting an extension before the period ends is routine good management, not a red flag — though repeatedly needing extensions, or asking at the last minute, signals poorer planning. Third, communicate changes proactively: a funder who hears early about a needed change, with your reasoning and plan, experiences a competent partner managing reality; a funder who discovers an unauthorized change in an audit experiences a problem. Fourth, document every change and approval, so your records show that what you did was authorized. The skill isn't avoiding change — it's managing it transparently and within the rules, which is itself part of the stewardship a funder is watching. Handled well, navigating a mid-project change can actually build trust, because it shows the funder you manage difficulty responsibly.

⚠️ Common Pitfall: Making a change that required prior approval without getting it first. Grantees, focused on the work, sometimes make a sensible-seeming change — shifting significant money between categories, changing a key staff member, adjusting the scope, or letting the period lapse — without realizing the funder's rules required advance approval. Even when the change is reasonable, making it without the required prior approval is a compliance violation that can lead to disallowed costs (you may have to pay back the money) or audit findings, and it damages trust. The fix is to know your award's prior-approval requirements (in the notice of award and the funder's rules) and to treat the funder as a partner you consult before significant changes, not after. A quick email to your program officer or grants office asking "does this change need prior approval?" before you act prevents the most common and most avoidable compliance problems in grant management.

26.6 Compliance, Records, and the Audit

Beyond reporting and money management, a grant carries ongoing compliance obligations — heaviest for federal awards (Chapter 19), lighter but real for foundations — that continue throughout the award and into closeout.

Following the rules throughout. Federal awards operate under the Uniform Guidance (2 CFR 200, Chapter 19) — cost principles, procurement standards, financial-management requirements — and your award's specific terms and conditions. Compliance isn't a one-time check; it's an ongoing discipline of spending, documenting, and operating within the rules for the life of the award.

Records and documentation. You must keep records — financial records, documentation of expenditures, records of what you did and achieved — and retain them for a required period after the grant ends (often several years), because you may need to produce them for an audit or review. The grantee who can't document how funds were spent has a serious problem; the one with clean, complete records is protected.

The audit. Organizations expending significant federal funds face the Single Audit (Chapter 19) — a rigorous audit of their federal awards — and other funders may audit or review grants as well. A clean audit (no findings, or minor ones well-addressed) is itself a credential that makes future funding easier; an audit with serious findings is a problem that follows you. Good records and consistent compliance throughout the award are what produce a clean audit.

Closeout. When the grant ends, closeout is the formal process of completing the grant: submitting final programmatic and financial reports, reconciling and returning any unspent funds, meeting final deliverable and records requirements, and formally concluding the award. A clean, on-time closeout is the last impression you leave on a funder — and, like everything else, it shapes whether they fund you again.

Closeout deserves a moment of emphasis because it's where tired grantees most often stumble. By the end of a multi-year award, the team is depleted, the exciting work is done, and the temptation is to let the final reports, the financial reconciliation, and the records wrap-up slide — to treat the last administrative mile as an afterthought. This is a costly mistake, because closeout is the funder's final, lasting impression, the moment they formally assess whether the whole grant delivered, and the gateway to the next award. A grantee who delivers a strong, on-time final report; reconciles the budget cleanly and returns any unspent funds promptly; and meets every closeout requirement leaves the funder with a closing impression of competence and trustworthiness. A grantee who submits a late, thin final report; can't cleanly account for the spending; or drags out the closeout leaves a closing impression of disorganization — the last thing the funder remembers when the next proposal arrives. Run closeout with the same care as setup; the bookends of an award shape its memory as much as the middle.

🔍 Why Does This Work?: Why does diligent compliance and record-keeping — seemingly the most bureaucratic, least creative part of grant work — so directly affect future funding? Because it's the clearest possible evidence of the one thing every funder most needs to know: can this organization be trusted with money? A funder is accountable (to its board, its donors, or the taxpayers) for the funds it distributes, and its biggest risk is a grantee who mismanages or can't account for the money. An organization with clean records, consistent compliance, and a clean audit history removes that risk — it's demonstrably safe to fund. An organization with audit findings, missing records, or compliance problems is the risk the funder fears. So compliance isn't separate from fundability; it's a direct measure of it. The "boring" discipline of keeping good records and following the rules is, in the funder's eyes, the difference between a safe bet and a liability — which is exactly why it shapes whether the next grant comes. Stewardship, again, is the application.

26.7 Strategy: Steward This Grant Into the Next

Pull the threads together into the post-award strategy that closes Part IV. Read the notice of award as the binding contract your proposal became; set up the award fast in the first ninety days; deliver what you promised, including your equity and community commitments; report on time, honestly, and specifically; manage the money within the rules and get prior approval before significant changes; maintain compliance and clean records through to a tidy closeout; and, throughout, treat the funder as a partner you communicate with openly. Above all, hold the threshold concept: stewardship of this grant is the strongest application for the next one.

✅ Best Practice: Treat the funder as a partner throughout the award, not just at report time — and keep the relationship warm between the formal touchpoints. Beyond the required reports, the strongest grantees maintain genuine communication with their program officer or funder contact: a brief update when something noteworthy happens (a milestone hit, a participant success story, an early result), a proactive heads-up when a challenge or change is coming, an invitation to see the work in person, a thank-you that's specific rather than rote. This does several things at once. It keeps the funder engaged and invested in your success rather than waiting passively for the report. It builds the relationship that, especially at foundations (Chapter 18), drives renewal and deepening partnership. It ensures that when you need something — a no-cost extension, advice on a problem, prior approval for a change — you're asking a partner who knows and trusts you, not a stranger. And it means the funder's experience of you, across the whole award, is of a communicative, engaged, trustworthy grantee — exactly the impression that makes the next conversation start with credibility. The relationship discipline of Chapter 2 and the stewardship of Chapter 18 don't end at the award; they run through the entire life of the grant, and they're a major part of how this grant becomes the next one.

The post-award world differs by funder, mirroring the proposal differences of Part III:

What unifies them is the threshold concept. Whether it's RYCC stewarding its Hartwell grant toward a renewal (Chapter 18's stewardship-to-partnership arc), Lighthouse building a clean federal compliance record toward its next government award (Chapter 19's trusted-grantee logic), or Hernandez turning her R01's results into the preliminary data for her next study (Chapter 16's mechanism arc) — in every case, how they manage this grant is the foundation of their next one. The book's whole spine reaches its natural conclusion here: a grant is a mission transaction (Chapter 1) in which the funder buys progress toward their goals, and delivering that progress — stewarding the award well — is both the fulfillment of this grant's promise and the strongest possible argument for the next one. Getting the grant was never the end; using it well, and being seen to use it well, is what sustains a funding career.

📊 From the Field: The most concrete way stewardship becomes the next application is that a well-run grant generates the evidence the next proposal needs. Watch it across the anchors. Hernandez's funded R01, delivered well, produces results — findings, data, demonstrated feasibility — that become the preliminary data anchoring her next grant (Chapter 9), the publications that build her track record, and the basis for a renewal or a new study. RYCC's stewarded foundation grant produces demonstrated outcomes — 90 students served across three sites, measured skill and confidence gains — that become the evidence base for its next, larger foundation ask and the trust that earns a Hartwell renewal (Chapter 18). Lighthouse's cleanly-administered government award produces a compliance track record and outcome data — participants employed, a clean audit — that make it competitive for a larger federal competition and credible as a direct applicant rather than only a subrecipient (Chapter 19). In each case, the grant didn't just do good in the world; it manufactured the raw material for the next proposal — results, track record, relationships, and a demonstrated ability to deliver. This is the deepest sense in which stewardship is the application: a well-stewarded grant literally writes the evidence section of your next one. The grant writers who understand this manage every award with the next proposal already in mind — not cynically, but because doing the work well and building toward the future are the same act.

🔄 Check Your Understanding: Two organizations each receive a first grant from the same funder for comparable projects. A year later, one is invited to apply for a larger renewal and the other is not — and the projects went comparably well. Name two stewardship factors, from this chapter, that could explain the difference.

Answer

Several are valid. Two clear ones: (1) Reporting and communication — the renewed organization reported on time, honestly (including challenges), and specifically against its promised outcomes, and communicated openly with the funder, while the other reported late, vaguely, or went dark — so the funder experienced one as a trustworthy partner and the other as a worry, regardless of comparable project results. (2) Compliance and money management — the renewed organization spent within the rules, got prior approval for changes, kept clean records, and closed out tidily (a clean audit/record), while the other had compliance problems, made prior-approval changes without approval, or couldn't document its spending — making one demonstrably safe to fund again and the other a risk. Both reflect the threshold concept: stewardship of this grant is the strongest application for the next one — the funder funds the proven deliverer, and stewardship (not just project success) is how delivery is proven and observed. (Also acceptable: delivering all promised commitments including equity/community ones; a strong final report that seeds the next proposal's evidence.)

Spaced Review

Retrieve these from earlier chapters without looking back, then check against the collapsed answers.

1. (From Chapter 25) How do the equity and community commitments you wrote into a proposal become real obligations after the award, and why does that connect to this chapter's honesty theme?
2. (From Chapter 18) How does foundation stewardship (Chapter 18) exemplify this chapter's threshold concept, and how does the post-award relationship lead to renewal?
3. (From Chapter 19) How do the compliance regime, records, and Single Audit of government grants (Chapter 19) operate in the post-award phase, and why do they affect future funding?

Answers

1. The equity and community commitments in your proposal (community-led design, lived-experience leadership, serving specific populations, Chapter 25) become binding obligations once funded — promises to real communities and partners you must now keep and report on — which is why authentic, honest proposal commitments matter: you have to deliver them, and a proposal that performed equity it didn't practice becomes a project that fails the communities it claimed to serve, damaging trust and future funding. 2. Foundation stewardship (honest reporting, delivered outcomes, open communication, Chapter 18) is the threshold concept in the foundation register: a well-stewarded grant builds the trust that leads the funder to renew, often at a higher level, turning one grant into a lasting partnership — the post-award relationship is where the next grant is won. 3. Federal awards carry ongoing Uniform Guidance (2 CFR 200) compliance, required record-keeping and retention, and (above a threshold) the Single Audit throughout the award and into closeout; they affect future funding because a clean compliance and audit record makes an organization demonstrably safe to fund again (a trusted grantee), while audit findings or compliance problems mark it as a risk — so stewardship of the compliance obligations is, again, the application for the next grant.

Chapter Summary

Key Takeaways

• The award is the starting line, not the finish. Winning means you must now deliver what you promised, spend correctly, report, comply, and steward the relationship — under a funder who is, in effect, your client.
• Threshold concept: stewardship of this grant is the strongest application for the next one. How you manage a funded award is the most persuasive evidence a funder will ever have about whether to fund you again — and it builds the track record and results that anchor every future proposal.
• The notice of award turns your proposal into a binding contract of promises. Read it carefully; every promise (including equity commitments) is now an obligation to deliver and report on. This is why honest proposals matter — you must deliver them.
• Set up the award fast in the first ninety days: staffing, purchasing, required approvals (IRB/IACUC), subaward agreements, financial setup, kickoff. The award date starts the setup, not the work; late setup loses time you can't recover.
• Report on time, honestly (including challenges), and specifically, against your promised outcomes (programmatic/RPPR, financial, final reports). Your reports are, in effect, your next application.
• Manage the money within the rules: rebudget within thresholds, get prior approval before significant changes (rebudgeting, scope, key personnel, timeline), handle carryforward and no-cost extensions per the rules. Making a prior-approval change without approval is a violation.
• Maintain compliance and clean records throughout (Uniform Guidance for federal awards), face the Single Audit if applicable, and close out cleanly. A clean record is a credential; findings follow you.

Action Items

1. Read the notice of award carefully and treat your proposal as the contract of promises you must now keep.
2. Run a first-90-days setup: staffing, approvals (IRB/IACUC), subawards, financial setup, kickoff — start immediately.
3. Build a reporting calendar — every report, format, deadline, and owner — and report on time, honestly, specifically.
4. Know your money rules — rebudgeting thresholds, prior-approval requirements, carryforward, no-cost extension — and ask before significant changes.
5. Keep clean records and maintain compliance throughout, to a tidy closeout — and treat it all as building the case for your next grant.

Common Mistakes

• Treating the award as a finish line and the management as an afterthought (it's the strongest evidence for future funding).
• Starting setup late — losing weeks of the period of performance to slow hiring or approvals.
• Over-promising in the proposal, then under-delivering on the contract it became.
• Late, vague, or dishonest reports — or going dark — which damage the trust that drives renewal.
• Making a prior-approval change without approval, or failing to keep records — creating compliance and audit problems.

Decision Framework — "How do I steward this grant toward the next?"

1. What did I promise, and what are the terms? → Read the notice of award; list every promise and obligation to deliver and report on.
2. Is the setup done fast? → Staffing, approvals, subawards, financial setup in the first ninety days.
3. Am I reporting well? → On time, honest (including challenges), specific, connected to promised outcomes.
4. Am I managing the money correctly? → Within the rules; prior approval before significant changes; clean records.
5. Am I building the next application? → Delivered results, clean compliance, strong relationship, tidy closeout — the evidence for the renewal or next grant.

🔁 Carry this forward: Managing the grant closes Part IV's cross-cutting skills — resubmission, collaboration, AI, equity, and stewardship — that apply across every funder. Part V now turns to sector-specific applications: how everything you've learned plays out for academic researchers (Chapter 27), nonprofits (Chapter 28, where RYCC's and Lighthouse's worlds are developed in full), K-12 educators (Chapter 29), artists and cultural organizations (Chapter 30), and community development (Chapter 31). The universal craft and cross-cutting skills become a toolkit you'll now see applied to the specific realities of each sector.