Milan Bogojevic Blog

Read the reporting burden before you read the grant amount

7 min read updated 10 October 2026

A nonprofit worker compares a $15,000 grant requiring 60–80 reporting hours with a $40,000 grant requiring 10–15 hours, surrounded by paperwork.
A nonprofit worker compares a $15,000 grant requiring 60–80 reporting hours with a $40,000 grant requiring 10–15 hours, surrounded by paperwork.

The headline grant amount is the least useful number in a funding opportunity. What actually decides whether an application was worth making is the ratio between that money and the hours your team will spend meeting the reporting requirements, for every reporting period across the grant's full duration, not just once.

Why this matters for a small nonprofit team

A small organisation usually has one or two people who both write the grant application and later produce the reports it requires. There's no separate compliance department to absorb a demanding reporting schedule, so every hour spent on a quarterly narrative report or a mid-term evaluation is an hour not spent on the programme the grant is funding in the first place. The reporting requirements are also usually buried several clicks deeper in the funder's documentation than the headline amount, which means teams often don't see the real cost until after they've already committed to the application.

The nonprofit reality: a disclosed, hypothetical comparison

Imagine a small NGO choosing between two hypothetical funding opportunities it could apply to this quarter.

Grant A offers $15,000 over one year, but requires a quarterly narrative report, a mid-term review call with the funder, and an independent evaluation at closeout. Estimating honestly, that's roughly 60 to 80 staff hours across the year: drafting four narrative reports, preparing for and attending the review call, and coordinating the external evaluation.

Grant B offers $40,000 over the same year, tied to two simple milestones (a programme launched, a participant count reached), with one short report due at each milestone. That's closer to 10 to 15 staff hours total.

Grant A pays roughly $190 to $250 per staff hour of reporting effort. Grant B pays roughly $2,700 to $4,000 per staff hour. On the headline number alone, Grant A looks like the safer, more fundable-sounding opportunity. Once the reporting burden is priced in, Grant B is worth more than ten times more per hour of staff time it actually costs the organisation.

Project Streamline's 2008 report documented how application and reporting demands can divert nonprofit resources from mission work. It is an older study of administrative burden, not a current benchmark for the hours in this hypothetical comparison.

The Reporting Burden Ratio

I treat this as a simple, repeatable calculation, not a gut feeling: grant amount divided by estimated annual reporting hours gives you a dollars-per-hour figure you can compare directly across opportunities, the same way you'd compare any two uses of staff time.

Step What to do Why it matters
1. Find the reporting template Look for the funder's actual reporting template or past reporting requirements before you read the eligibility criteria If no template is published, that itself is a signal: requirements will likely be set after the award, which weakens your negotiating position later
2. Count the real data points List every distinct data point, narrative section, and deliverable the funder wants, then subtract what you already collect for other purposes The gap, not the full list, is your real added cost, and it recurs every reporting period for the grant's entire duration
3. Estimate honest hours Multiply your per-report estimate by the number of reports over the grant's life, including any mid-term review or closeout evaluation A single-period estimate hides the true cost of a multi-year grant with repeating requirements
4. Divide and compare Grant amount ÷ total estimated reporting hours = dollars per hour of reporting effort This is the number that's actually comparable across different grants, unlike the headline amount alone

Build your own benchmark, not a sector-wide one

After every application your organisation submits, won or lost, write down how many hours it actually took, separate from the hours spent on the programme work itself. Over a year, this builds a benchmark specific to your own team's speed and existing systems, which is more useful than any sector-wide average, because a sector average can't account for whether your organisation already has, say, a participant database that halves your data-collection time compared to an organisation starting from spreadsheets.

Use the same logged hours to set an annual proposal budget for a two-person team, so reporting commitments reduce the capacity available for new applications.

My view

I'd go further than just checking the reporting template: if a funder won't share one before you apply, I treat that as a real negotiating signal, not just an inconvenience. An organisation that asks for your reporting commitment up front, in writing, is usually easier to work with for the life of the grant than one that defines requirements only after you've already accepted the money. I'd rather walk away from an unusually generous headline amount than discover the reporting burden six months into a multi-year commitment.

What to do next

  • Pull the reporting template (or past reports, if no template exists) for the next grant opportunity you're considering, before you draft the application.
  • Count the distinct data points and deliverables it asks for, subtract what you already track, and estimate honest hours for the gap.
  • Multiply that per-report estimate across every reporting period in the grant's full term, including any mid-term or closeout evaluation.
  • Calculate the dollars-per-hour figure and compare it against at least one other opportunity you're weighing.
  • Start logging actual hours spent on your next three applications, win or lose, to begin building your own benchmark.

Conclusion

The grant amount tells you what you'll receive. It tells you almost nothing about what it will cost you to keep receiving it. A funding opportunity that looks generous on the surface can quietly become the most expensive thing your team works on all year, once the reporting hours are counted honestly and spread across the grant's full term. The fix isn't complicated, it's a habit: price the reporting burden before you commit, and keep your own record afterward so the next decision is faster than this one.

Then use funder timing and fit to decide which of the affordable opportunities deserves proposal hours now.

FAQ

Is there a reporting burden ratio that counts as "good"?

There's no universal good number, since it depends entirely on your organisation's own staff cost and capacity. The value of the ratio is comparative: calculate it the same way for every opportunity you're weighing, and use it to rank them against each other, not against an outside benchmark.

What if the funder doesn't publish a reporting template at all?

Ask for one, or ask a current or past grantee what the actual reporting process looked like. If neither is available, treat the unknown reporting burden itself as a risk factor, and weight it more heavily when comparing this opportunity against one where the requirements are already clear.

Should a small grant ever be turned down because of its reporting burden?

Yes, when the honest hourly cost is high enough that the time would clearly produce more value spent directly on the programme. This is exactly the kind of decision the reporting burden ratio is meant to make explicit, instead of leaving it as a vague feeling that "this grant is more work than it's worth."

How does this relate to deciding which funders to pursue in the first place?

The reporting burden ratio compares specific grant opportunities by dividing the grant amount by the total estimated reporting hours. Funder fit is a broader assessment of whether a funder's priorities, timing, and requirements suit your organisation before you select an opportunity.

Sources

About the author

Milan Bogojevic works on nonprofit grant intelligence, funding decisions and AI-assisted proposal processes for teams with limited capacity.

Last updated: 10 October 2026.

Next in Grant Intelligence