Grant Burn Rate: How to Calculate and Read It
Burn rate compares money spent against time elapsed — the single fastest health check a grant has. How to calculate it, how to read the four patterns, and the monthly rhythm that keeps donors calm.
Grant burn rate is the percentage of a grant's budget that has been spent, read against the percentage of the grant period that has passed. A grant 50% through its timeline that has spent 48% of its budget is burning healthily. One that has spent 22% — or 71% — has a problem that is cheaper to fix today than at report time. Burn rate is not a donor formality; it is the earliest warning instrument grant management has.
The calculation
Burn rate =
Total spent to date ÷ total approved budget × 100 — read against time elapsed: months completed ÷ grant duration × 100. Compute it per budget line, not just per grant: a healthy total routinely hides one line at 95% and another at 15%.
Two refinements make the number honest. First, include commitments — approved purchase orders and signed contracts are spent money walking slowly; a burn rate that ignores them understates reality by whatever is in the pipeline. Second, spend must be tagged to the grant and line at entry, or the burn rate is only as current as your last reconciliation marathon — the tag-at-entry principle is what makes the number available monthly instead of quarterly.
Reading the four patterns
| Pattern | What it usually means | The move |
|---|---|---|
| Spend % ≈ time % | Implementation on track | Verify per-line; confirm the story the total is telling |
| Spend % well below time % (underburn) | Delayed activities, hiring gaps, or procurement stuck | Accelerate, or request a no-cost extension early — donors grant them to planners, not to panickers |
| Spend % well above time % (overburn) | Front-loaded costs (sometimes fine) or budget lines sized wrong | Check if it is timing or trajectory; request realignment before lines exhaust |
| Total healthy, lines diverging | The budget's shape didn't survive contact with reality | Line-to-line realignment inside the donor's flexibility rules |
Why donors read it the way they do
- Underburn threatens their money: unspent funds at closeout often return to the donor's treasury and count against their own delivery targets — a chronically underburning grantee is a portfolio problem, not a thrifty one.
- Overburn threatens the program: money exhausted at month nine of twelve means activities stop or the organization eats costs it cannot recover.
- A final-quarter spending spike reads as panic procurement and attracts precisely the audit attention nobody wants — smooth burn is credibility.
- Silence is worse than variance: a grantee who flags a burn problem at month four with a plan gets flexibility; one who reveals it in the final report gets scrutiny.
The monthly rhythm
The 30-minute burn review, per grant
- Burn rate per line — actuals plus commitments — against time elapsed.
- Every line beyond ±15–20% of the timeline gets a one-line explanation from the program lead.
- Realignment needs identified while requests are still possible (most donors close them 1–3 months before the end date).
- Forecast to grant end: current trajectory × remaining months — the number that turns review into decision.
- The note to the donor drafted when the news is significant — proactively, not at report time.
Burn rate is one instrument on a larger dashboard — the full lifecycle from proposal to closeout is in grant budget tracking, and the multi-grant version of the discipline is dimensional fund accounting. What all of it assumes is a system where the number exists on demand: live budgets, tagged spend, and commitments counted.
What AWRA OpsHub does today
- Spend consumed as a percentage of the grant budget, live, with a grant modelled as a project carrying its budget amount.
- Actual cost assembled from real transactions — logged time at a cost rate, purchase orders, and booked expenses — not a figure anybody types in.
- Approved purchase orders count toward spend. Commitment is in the number before the invoice arrives, which is precisely the refinement this post argues for and the one spreadsheets usually miss.
- Budgets at task level as well as project level, so per-line burn works if you model a budget line as a task.
- A cost report across all grants at once, with labour, purchases and expenses shown separately.
- Departmental budgets with over / at-risk / on-track status on a monthly, quarterly or yearly period, for the core-funded side of the house.
More we can add to your workspace
- A time-elapsed comparison. The system reports the percentage of budget consumed. Reading it against the percentage of the grant period that has passed — the actual judgement in this post — is arithmetic you do, on dates the system already holds.
- A trajectory forecast, projecting the current run-rate to the grant end date. That is the forecast line in the review below, and today it is yours to compute.
- Committed and actual are summed, not separated. An approved-but-unreceived order and a paid invoice land in the same cost figure. If you need the pipeline as its own column, that is a build.
- Variance alerting. A rule that watches a line drifting past ±15–20% and tells you, so the review stops being a diarised habit.
- Grant budget lines as a first-class structure. A project holds one budget amount today, so sub-lines mean modelling them as tasks or as separate projects — both work, and it is a structuring decision you make deliberately at grant setup.
- A realignment or no-cost-extension workflow. Donor correspondence lives outside the system.
The honest split: the numerator is automatic, the judgement is not. Spend-to-date per grant is live and already includes commitments, which is the genuinely hard part. The read against time elapsed, the forecast to grant end, and the conversation with the donor are a monthly half-hour a person owns. If you want the comparison and the forecast computed and alerted rather than calculated, ask us to price it instead of assuming a dashboard does it.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsRead every grant in thirty seconds
Live spend against budget per grant, built from logged time, purchase orders and expenses, with approved commitments already counted — so the only thing left to do is read it against the calendar.
See burn rates in AWRAFrequently asked questions
What burn rate variance is acceptable?
A working convention: within ±10% of time elapsed needs no comment; ±10–20% needs an explanation and a plan; beyond ±20% needs donor conversation. Seasonal programs legitimately burn unevenly — the standard is explained variance, not uniformity.
Should burn rate include staff costs and overheads?
Yes — everything charged to the grant burns it, including personnel allocations and indirect cost recovery. Personnel usually burns linearly, which conveniently makes it the baseline; activity lines are where the drama lives.
How is burn rate different for multi-year grants?
Same math, but read against the year's workplan budget as well as the total: a three-year grant burning 30% at year one may be perfectly on plan. Most multi-year donors expect annual burn discipline within the overall envelope — two clocks, both watched.
What is a no-cost extension and when do we ask?
An extension of the grant period without additional funds — the standard remedy for underburn caused by legitimate delay. Ask the moment the trajectory shows funds outlasting the timeline, with a revised workplan attached. Requests at month eight of twelve read as management; requests in the final month read as confession.
