Free Resource for Nonprofits and Local Governments

Pre-Award to Post-Award Grant Compliance Workflow

A step-by-step grant compliance workflow for nonprofits and local governments, from deciding to apply through award setup, spending, reporting, monitoring, closeout, and renewal, with what has to be true at each stage before you move to the next.

Jump to Checklist
Use browser Print to save as PDF

Best for

Organizations setting a standard way of running every grant

Use it to

Know what has to be true at each stage before moving to the next

Format

Web page now, print-friendly PDF anytime

Why this matters

Grant compliance is not one task. It is a different set of tasks at each stage of the award, and the ones skipped early show up late: a match accepted at application that nobody budgeted, a requirement never listed at setup, a budget overspent because nobody looked until the report was due. This workflow lays out the seven stages and the handful of things that must be true at each one, so a grant is run the same way whoever is running it.

1

Before you apply

Most compliance problems are accepted at application time. Decide with the rules in view, not just the dollars.

  • Read the funding notice for match, reporting frequency, allowable costs, and period of performance before deciding to apply
  • Confirm your organization can meet the administrative requirements: audits, procurement rules, record retention, insurance
  • Check registrations the funder requires are current (SAM.gov and a UEI for federal funds, state registrations, charity registration)
  • Decide who will own the grant internally if it is awarded, by name
  • Build the budget from your real cost structure, including indirect costs the funder allows
  • Save the funding notice and the application as submitted in the grant file, even before the award

Quick check: Before applying, can you name the reporting frequency, the match, and the one cost rule most likely to bite?

2

Award and setup

The first thirty days after the award set up everything that follows. Do them deliberately.

  • Read the full agreement, including the terms and conditions it references, and list every requirement and deadline
  • Set up the grant file using one standard folder structure
  • Create the grant in your accounting system with a code and the approved budget categories
  • Put every reporting deadline on a shared calendar with reminders ahead of each one
  • Hold a kickoff with finance and program staff: scope, budget, rules, reporting, who does what
  • Confirm the award is signed, returned, and acknowledged the way the funder requires
  • Note the award in board minutes or wherever your governance requires

Red flag: The grant is spending before anyone has listed its requirements.

3

Spending

Every dollar has to be allowable, allocable, reasonable, and documented at the moment it is spent.

  • Expenses are coded to the grant and an approved budget category when they are entered, not reconstructed later
  • Purchases follow your written procurement policy and the award's thresholds
  • Costs that need the funder's prior approval get it before the money is spent
  • Staff time on the grant is recorded as it happens and approved after the period
  • Shared costs follow a written allocation method
  • Budget-to-actual is reviewed at least monthly, with changes requested before a category is overspent
  • Invoices, proof of payment, and approvals go into the grant file as they occur

Quick test: Pick last month's largest grant expense. Was it allowable, in budget, approved if needed, and filed?

4

Reporting

Reports are assembled from the file, not written from memory.

  • Each report has a named owner and a start date well before the due date
  • Financial figures are pulled from the ledger and reconciled to it
  • Program figures are collected the same way every period, from the same sources
  • Financial and program reports are checked against each other before submission
  • Reports are submitted the way the funder requires, and a copy plus confirmation is filed
  • Drawdowns or reimbursement requests match reported, incurred expenses

Red flag: The report's numbers and the ledger's numbers for the same period have never been compared.

5

Monitoring and mid-course changes

Grants drift. Catching it early keeps a change request from becoming a finding.

  • A monthly or quarterly compliance review: spending pace, upcoming deadlines, open requirements
  • Budget modifications, scope changes, and no-cost extensions are requested in writing before they are needed
  • Funder correspondence that changes anything is saved in the grant file
  • Subrecipients, if any, are monitored and their reports collected on schedule
  • Site visits and monitoring letters are prepared for from the file and answered in writing
  • Staff changes trigger a handoff: the new owner reads the agreement and the requirement list

Quick check: When the program officer last visited or wrote, was the answer in the file or in someone's memory?

6

Closeout

The award ends on a date. Compliance ends when the closeout is accepted and the records are retained.

  • Final financial and program reports submitted by the closeout deadline, usually 90 or 120 days after the period ends
  • Final drawdown made, or unspent funds returned, the way the award requires
  • Equipment purchased with grant funds dispositioned per the award and recorded
  • The funder's closeout acknowledgment or letter saved in the file
  • Record retention date calculated and recorded, usually at least three years after closeout
  • Open findings or questioned costs resolved and documented

Red flag: The last report went in, and nobody knows whether the funder considers the grant closed.

7

Renewal and the next application

A clean closeout is the strongest part of the next proposal.

  • A one-page summary of what the grant did: outcomes, dollars, lessons
  • Reporting history and findings reviewed before reapplying, with fixes in place
  • Relationship notes: who the program officer is and what they cared about
  • Costs and effort data from this award used to budget the next one accurately
  • Compliance capacity judged honestly before taking on more or larger awards
  • The grant file archived intact, so the next team can learn from it

If this funder asked for a renewal proposal next week, would the last award help you or embarrass you?

Signs the workflow is missing

If several of these feel true right now, your grants are being run by memory.

  • Applications are decided on the dollars, with the rules read after the award
  • Nobody lists the requirements and deadlines when the award arrives
  • Expenses are coded to grants at report time, not when they happen
  • Budget modifications are requested after a category is already overspent
  • Monitoring visits are prepared for in the days before them
  • Closeout means the last report was sent
  • Each new grant is set up differently, by whoever got it

Self-score

Give yourself 1 point for every statement you can honestly say is true.

  • We read the rules before deciding to apply
  • Every award gets a requirement list and a calendar within 30 days
  • Expenses are coded to the grant as they happen
  • Budget-to-actual is reviewed monthly
  • Reports are built from the ledger and the file
  • We request changes before we need them
  • Closeout is confirmed in writing and a retention date is set
  • Every grant is run the same way

7 to 8: Strong foundation

4 to 6: Some gaps, manageable if addressed now

0 to 3: High risk of preventable problems

Next step

Want the setup stage done for you?

Upload the agreement and GrantGuard produces the requirement list, the deadline calendar with alerts, and the budget categories, then tracks spending, documents, and reports against them for the rest of the award, so stages two through six run from one place.

Start Free 30-Day Trial Book a Demo
Print this page to save as PDF

Related guides