The Money Does Not Arrive All at Once

An SBIR or STTR award is not a check. It is a schedule of work with payment tied to performance, and the paperwork that proves performance is a real deliverable — as real as the prototype. Depending on the agency, your award is either a grant (NIH, NSF, DOE, USDA style) or a contract (DoD, NASA style), and that single distinction determines how you invoice, what you report, and how tightly the statement of work binds you. Grants pay by drawdown or reimbursement against an approved budget with technical and financial reports on a set cadence; contracts pay against invoices tied to defined deliverables and often to milestone acceptance. Read your award document to learn which one you have before you plan cash flow. Projects House is an engineering firm, not a grants or accounting consultancy; this article is educational, and your award terms and agency supplement govern.

Milestones: Write Them So You Can Actually Hit Them

Reviewers reward specific, testable milestones, and then you have to live inside them for the entire period of performance. The milestones that survive contact with reality share four properties:

  • Measurable. "Demonstrate the sensor achieves the target resolution across the specified temperature range" beats "develop the sensor." A milestone you cannot fail is a milestone you cannot report.
  • Independent. If milestone three cannot start until milestone two finishes perfectly, one slip cascades through the whole schedule. Parallelize where the technology allows.
  • Evidence-producing. Each one should generate an artifact — a test report, a dataset, a video, a measured drawing — that goes straight into a progress report without new work.
  • Honest about hardware lead times. Tooling, custom PCBs, and long-lead components move on their own schedule. Build the real lead times into the plan; the hidden costs of hardware development are mostly hidden time.

Phase I periods of performance are short, and the single most common schedule killer is procurement, not engineering. Order long-lead parts in the first weeks, even if you will not use them until month five.

What You Will Actually Have to Submit

The specifics vary by agency, but the shape is consistent:

  • Technical progress reports on a defined cadence, covering work performed, results against milestones, problems encountered, and the plan for the next period.
  • A final technical report at the end of the period of performance. This is the document that follows you — it is what a Phase II reviewer reads, and it should read like a credible engineering result.
  • Financial reporting — for grants, a federal financial report on the schedule the award specifies; for contracts, invoices with supporting cost detail through the government's payment system.
  • Invention disclosures and utilization reports for anything patentable that came out of the work. The mechanics are covered in who owns the IP from a federal grant.
  • Property and subaward reporting if you bought equipment with award funds or pushed work to a subcontractor or research institution.

Two things make financial reporting painless or painful. The first is timekeeping: hours charged to the award must be recorded contemporaneously against the award, by person, with a documented process. Reconstructing timesheets after the fact is the classic audit finding. The second is your treatment of indirect costs — whether you use a negotiated rate or the de minimis rate the award allows, apply it consistently and be able to show the basis.

When Reality Deviates From the Plan

It will. Technical programs discover things, and discovering things changes plans. The rule that matters is simple: tell the program officer early, in writing. Agencies are used to technical redirection and generally accommodate it. What they cannot accommodate is learning at final report time that the work performed does not resemble the work funded.

Typical situations and the normal handling:

  • Schedule slip. A no-cost extension of the period of performance is routine when the work is progressing. Request it before the end date, not after.
  • Budget reallocation. Moving money between budget categories is often allowed up to a threshold without approval, and requires prior approval above it. Know your threshold.
  • Change in key personnel. A change of principal investigator almost always requires prior agency approval, and a significant reduction in the PI's committed effort usually does too.
  • Change in technical approach. Refining the method is normal. Substituting a different objective is a scope change and needs a conversation.
  • A negative result. A well-documented failure that closes off an approach is a legitimate research outcome. Report it as one, with the data. Hiding it and hoping is how a Phase II gets declined.

Design changes on the hardware side should flow through a real change process rather than living in someone's memory — the discipline in the engineering change order process is exactly what makes a technical report defensible.

A Management Routine That Makes Reporting Trivial

Teams that dread reporting are teams that generate no evidence during the work. Teams that report in an afternoon do five small things continuously:

  1. A weekly written log — what was done, what was measured, what broke, what is next. Fifteen minutes a week.
  2. Test reports as you go, each with date, setup, conditions, raw data, and conclusion. Never rely on remembering a result.
  3. Photos and video of every build and test. Reviewers respond to visible hardware more than to prose.
  4. Version-controlled design files and a versioned bill of materials, so the report can state exactly which revision produced which result. See the bill of materials guide.
  5. A single milestone tracker mapping every award milestone to its evidence artifact, reviewed at a standing weekly meeting. That is the whole of project management for a small award.

A Clean File Is an Asset for the Next Round

The reporting file you build during Phase I is the raw material for the Phase II proposal, and later for investor diligence. A crisp final report with measured results, honest limitations, and a clear path to the next technical objective is the strongest possible Phase II argument — reviewers are being asked to believe you can execute, and you have just documented that you can. The same file answers the questions an investor asks about technical risk. For how the phases connect, see SBIR Phase I versus Phase II; for sequencing federal money against equity, see combining grants with private investment; and for the broader program landscape, our government funding guide.

Let the Engineering Produce the Evidence

The best compliance strategy is engineering work that generates its own documentation. Projects House runs funded development programs so that each milestone ends with a tested article and a report that writes itself — prototypes, test data, drawings, and a manufacturing path. Tell us about your award through the contact form and we will help you build a plan you can report against.