Winning a BARDA award changes who you report to. The board still wants the science. The funder now wants proof that the schedule, the budget, and the technical story all say the same thing, every reporting period. Earned value management (EVM) is how that proof gets made, and small teams usually set it up too late.

This is a practical guide for biotech and medical device teams under about 100 people who just signed a federal contract and do not yet have a program office to run it.

Earned value in plain terms

EVM compares three numbers for every piece of work in your plan:

  • Planned value (PV): the budget for the work you scheduled to finish by now.
  • Earned value (EV): the budget for the work you actually finished.
  • Actual cost (AC): what you really spent to finish it.

From those three you get the two questions every funder asks. Are we on schedule? Schedule variance is EV minus PV, and the schedule performance index (SPI) is EV divided by PV. Are we on budget? Cost variance is EV minus AC, and the cost performance index (CPI) is EV divided by AC. An index below 1.0 means you are behind or over.

The math is simple. The discipline behind it is not.

What actually governs your EVM requirement

Read your contract first, not a blog post. Whether EVM applies, how formal it has to be, the report format, and the variance thresholds that trigger an explanation are all set in the contract and its reporting requirements.

Two pieces of context help. HHS used to set department-wide dollar thresholds for EVM in its acquisition regulation (HHSAR 334.201), and a 2025 HHS class deviation struck that section out, which makes your contract language even more important. And ASPR, BARDA’s parent office, published a “7 Principles” intent guide in 2011 that describes a lighter-weight EVM approach for many of its programs, rather than full compliance with all 32 guidelines of the ANSI/EIA-748 standard. Whatever tier you land in, expect to explain significant variances in terms of cause, impact, and corrective action.

Where small teams slip

These are the patterns we see most often when a small team takes on its first federally funded program.

The baseline is the proposal. The schedule and budget written to win the award become the baseline by default. Proposals are written to persuade. Baselines have to be executable. Rebuild the plan from the real work, with real owners, before you measure anything against it.

Work is not tied to contract options. Federal contracts are usually structured as a base period plus options. If your plan does not map work packages to the option and milestone each one supports, you cannot show the funder what the next option decision depends on.

Earned value has no rules. Teams claim progress by feel: “about 60 percent done.” Pick a credit method for each type of work before it starts (0/100 for short tasks, 50/50, or weighted milestones for longer ones) and write it down. Otherwise your EV is an opinion.

Actuals arrive late. Accounting closes the month on its own calendar, and CDMO invoices lag the work by weeks. If cost data is not in the same period as the progress data, your CPI swings for no real reason. Agree on accrual estimates for major vendors so each period is complete.

The CDMO is a single line. Technology transfer and manufacturing are often the largest cost and schedule risk on the program, yet they sit in the plan as one block. Break vendor work into the deliverables you can verify, so you know it slipped before the invoice tells you.

Variance explanations are written after the funder asks. By then the conversation is about credibility, not the variance. Review the numbers internally first, every period, and draft the cause, impact, and corrective action before the report goes out.

A 90-day setup plan

Days 1 to 30: build the baseline. Translate the statement of work into a work breakdown structure. Assign an owner to every work package. Build a resource-loaded schedule and tie each package to the contract option or milestone it supports. Set the earned value credit rule for each package.

Days 31 to 60: connect the data. Align your chart of accounts or cost codes with the work packages so actual cost lands in the right place. Set up accrual estimates for CDMOs and other major vendors. Run one dry-run reporting cycle internally and fix whatever does not reconcile.

Days 61 to 90: run the rhythm. Hold a monthly performance review before every funder report. Track the variances that cross your contract’s thresholds, write the explanations, and log the corrective actions. Put a change-control process in place so baseline changes are approved and traceable, not quietly absorbed.

After 90 days the numbers stop being a reporting chore and start being an early-warning system, which is the point.

The real payoff

EVM done well is not about pleasing the contracting officer. It tells a small team, months ahead, which work package is going to cost them the next option. That is worth more than any single report.

We have led a BARDA-funded Class III device program through CDMO technology transfer with earned value reporting to the federal funder. If your team just won an award and needs this set up without a full-time hire, see how we support federally funded programs or start a conversation.