Event 03

Burn Rate Problem

Six months into the award, Marcus reviews the financial reports and notices that the project is spending much more slowly than expected.

Year 1 Event 03 Financial Monitoring

Story Scene

Research Finance notices a spending pattern

As part of routine award monitoring, David Patel from the Research Finance Office reviews the project’s financial activity. His role is to monitor project expenditures, financial records, reconciliations, and spending trends.

David notices that overall project spending appears lower than expected. The Personnel category is underspent, and participant incentive spending is also below projections. Because more than one budget category is affected, he contacts Marcus and requests a closer review.

Marcus receives David’s financial review email with the latest quarterly financial report attached. At first glance, the numbers appear positive. The project is well below budget. There are no overdrafts. No expenditures appear problematic.

However, Marcus knows that financial health cannot be measured by spending alone. He begins reviewing project activity alongside financial activity.

As Marcus compares project milestones with expenditures, a pattern begins to emerge: the project is not only spending less than expected. Several planned activities are occurring more slowly than anticipated.

Research Finance Partner

Meet David Patel

Portrait of David Patel

Finance Manager | Research Finance Office

David Patel oversees the financial administration of sponsored projects at Crescent State University. He works closely with Marcus to monitor project expenditures, review financial records, and identify spending patterns that may need additional review.

In this event, David notices that the project is spending less than expected across multiple budget categories. He brings the issue to Marcus so they can determine whether the numbers reflect efficient spending or delayed project activity.

Institution Crescent State University
Department Research Finance Office
Project Role Financial Oversight and Reporting
Focus Spending trends, variances, and forecasts

How David and Marcus work together

David helps answer, “What do the numbers tell us?” Marcus helps answer, “What do the numbers mean for the project?”

Training Concept

What is burn rate?

Burn rate is the pace at which a project spends its approved budget over time. In post-award management, Marcus is not only checking whether the project has money left. He is checking whether spending matches the project timeline and the work that should be happening.

Healthy spending pattern

Spending generally follows the approved project plan, timeline, staffing, and activity schedule.

Low burn rate

Spending is slower than expected. This may signal delays in hiring, recruitment, purchasing, participant activity, or other project work.

High burn rate

Spending is faster than expected. This may signal overspending, early purchases, miscoded expenses, or future budget shortages.

Trigger Issue

The financial report shows lower-than-expected spending

The project appears financially healthy because spending is below the approved budget. But Marcus needs to understand why spending is low before deciding that the project is on track.

Quarterly Financial Report

Provides a high-level snapshot of project spending.

  • Total spending is below expectations
  • Multiple budget categories are underspent
  • Burn rate is lower than projected

Budget-to-Actual Report

Compares planned spending against actual spending.

  • Personnel variance remains significant
  • Participant incentive spending is low
  • Overall project spending is behind schedule

Financial Forecast

Projects future spending based on current trends.

  • Continued underspending could lead to a large remaining balance
  • Future carryforward or extension discussions may occur

Marcus’s Analysis

The issue is not just the number. It is the reason behind the number.

Burn Rate Analysis

Six-Month Spending Review

Below forecast

Marcus reviews the financial reports and sees that the project is spending below forecast. That pattern connects back to earlier project events.

Known cause: Hiring delay

Personnel spending remains below projections because the Research Coordinator position was not filled as originally planned.

Known cause: Delayed recruitment

Participant incentive spending is lower than anticipated because recruitment activities started later than planned.

The financial report does not exist separately from the story of the project. The numbers reflect what has happened operationally.

Marcus should investigate whether spending patterns match project activity and project expectations.

Artifact Review

What Marcus reviews

Quarterly Financial Report

Marcus uses this report to identify whether spending is above, below, or generally aligned with expectations.

Budget-to-Actual Report

Marcus compares approved budget amounts to actual expenses charged to the award.

Burn Rate Analysis

Marcus calculates whether spending is occurring at the expected pace.

Financial Forecast

Marcus projects whether continued underspending could create a large remaining balance later in the project.

Financial Review Notes

Marcus documents his analysis and recommended next steps.

Email to Dr. Brown

Marcus communicates the spending trend and discusses project status with the PI.

Administrator Thinking

What Marcus notices

David has identified the financial pattern: overall spending is lower than expected. Marcus now needs to interpret what that pattern means for the project. The project is not overspent, but that does not automatically mean the project is healthy.

What the numbers show

  • Overall spending is below expectations
  • Personnel spending remains low
  • Participant incentive spending is low
  • The project has a lower-than-expected burn rate

What Marcus needs to ask

  • Are planned activities happening on schedule?
  • Is recruitment behind?
  • Will delayed spending affect Year 1 milestones?
  • Could this create carryforward or extension issues later?

Financial monitoring is not just about whether spending is high or low. It is about whether spending patterns match project activity.

Decision Point

What should Marcus do first?

A project has spent significantly less than expected six months into the award period. What should a research administrator do first?

Communication

How Marcus should communicate the trend

Key Takeaway

Burn rate tells a project story

Financial monitoring is not about determining whether spending is simply high or low. It is about determining whether spending patterns match project activity and project expectations.

Resources

References behind this scenario

These references show why Marcus reviews budget activity, burn rate, financial forecasts, and project progress together. A post-award research administrator is not only checking whether money was spent. The larger question is whether the spending pattern matches the project’s approved plan and actual progress.

2 CFR 200.303 — Internal Controls

This federal requirement frames the institution’s responsibility to monitor federal awards, identify financial or compliance concerns early, and maintain effective oversight throughout the award period.

Connection to Event 03: Marcus uses monitoring to identify that spending is behind expectations.

2 CFR 200.308 — Revision of Budget and Program Plans

This section matters when spending patterns or project delays may lead to changes in the approved budget, project scope, timeline, or planned activities that require review.

Connection to Event 03: continued underspending may later lead to rebudgeting, carryforward, or extension conversations.

Award Budget

The approved budget gives Marcus a baseline for comparing what the project expected to spend against what has actually been charged to the award.

Connection to Event 03: Marcus compares planned spending to actual spending to understand the burn rate.

Budget-to-Actual Reports

These reports help reveal whether project spending is aligned with the project timeline, staffing plan, participant activity, and expected pace of work.

Connection to Event 03: the report shows that personnel and incentive spending are both below expectations.

Back to Event 02 Continue to Event 04