The Award-to-Invention Map Every Phase II Company Should Maintain

The grant administrator has the award file. Patent counsel has the patent docket. The engineers know what was actually built. The CEO knows which customers are interested. Finance knows the licensing or sales activity.

Each of those records may be accurate.

But has anyone reviewed them together?

That does not mean a company has done anything wrong. It simply means one innovation story may be managed through several different systems, by people doing very different jobs.

For a Phase II SBIR or STTR company, an award-to-invention map can make that story visible.

This is not a government-required form. It is an internal management and evidence tool.

What is an award-to-invention map?

An award-to-invention map is a source-linked record showing how a company’s federal awards, technical developments, invention disclosures, patent families, ownership documents, reporting records, and commercialization activity relate, or may relate, to one another.

“Source-linked” is the important part.

The map should not be a spreadsheet filled with conclusions from memory. Important entries should point back to identifiable evidence, such as an award document, statement of work, technical record, invention disclosure, patent file, assignment, iEdison record, license, or commercialization document.

The map can be a controlled spreadsheet, ledger, or lightweight database. The goal is not sophisticated software. The goal is a reliable record that someone owns and keeps current.

What a patent docket may not show

A good patent docket is essential. It can track filing dates, application numbers, prosecution events, continuity, issue dates, maintenance events, inventors, and ownership records.

For purposes of this article, a “patent family” simply means a group of related patent applications and patents sharing a filing lineage.

But the patent docket may not show which federal statement of work may relate to the underlying development, what technical records support that relationship, whether more than one award may be relevant, what was reported through iEdison, or what commercialization information exists.

That is not a criticism of patent counsel.

Patent counsel works with the technical, funding, and business information the company provides. If no one connects those inputs to the patent family, a well-maintained patent docket may still tell only part of the broader story.

What the award file may not show

The award file serves a different purpose.

It may contain the award notice, statement of work, modifications, budgets, progress reports, correspondence, and closeout materials.

But it may not contain a complete invention chronology, patent-family structure, assignment history, or current commercialization information.

The principal investigator may understand the funded technical work. The grant administrator may understand the award and reporting process. Patent counsel may understand the patent family. Management may understand the customer and licensing strategy.

The useful question is whether those records tell the same supported story when they are viewed together.

What should the map contain?

The exact structure will depend on the company, agency, funding instrument, portfolio size, and commercialization stage.

A practical map might include:

• the award number, agency, funding instrument, project title, period of performance, and funded technical scope;
• the principal investigator and responsible internal award contact;
• a short identifier and plain-English description for each invention or candidate invention;
• technical contributors and potential inventors, subject to legal review;
• relevant technical records and internal invention-disclosure information;
• the possible relationship between each invention and one or more awards, together with the evidence supporting that relationship;
• the related patent family, application status, assignee, and assignment source;
• relevant invention and patent-reporting records;
• government-support-statement status for U.S. patent applications and patents covering a subject invention, where applicable;
• utilization, licensing, sales, customer, financing, or Phase III information; and
• unresolved questions, responsible person, next action, source link, and last review date.

The phrase “candidate invention” is useful because it lets a company capture a technical development for review without prematurely declaring that it is patentable, federally funded, or a subject invention.

Build the map from evidence, not assumptions

The first version can be built through a straightforward process:

1. Inventory the actual federal awards and controlling award documents.
2. Inventory disclosed inventions and technical developments that may warrant review.
3. Inventory the active patent families.
4. Link proposed relationships to supporting evidence.
5. Mark uncertain relationships as unresolved rather than guessing.
6. Connect relevant ownership, assignment, and reporting records.
7. Add utilization and commercialization information.
8. Assign each open question to a person and a review date.

The uncertainty field matters.

“Confirmed,” “probable,” “possible,” and “unresolved” can be much more useful than forcing every relationship into a yes-or-no answer before the facts have been developed.

Timing alone does not answer the federal-funding question

This is where the legal framework deserves particular care.

Under 35 U.S.C. § 201, a “subject invention” is an invention of the contractor conceived or first actually reduced to practice in the performance of work under a funding agreement.

Timing alone does not determine whether an invention is a subject invention.

The federal regulations expressly distinguish work performed within the planned and committed activities of a government-funded project from separate but related work outside those activities. Closely related research may occur at similar times without producing the same legal result.

So the fact that an invention was developed while a Phase II award was active does not, standing alone, answer the question.

The actual funding agreement, incorporated patent-rights clause, funded scope, technical chronology, ownership facts, and applicable agency requirements matter.

That is precisely why the map should organize evidence before anyone tries to reach a legal conclusion.

A fictional example

Imagine a fictional 20-person materials company with two DOE awards, four candidate inventions, and three patent families.

Its patent docket is current. Its award files are orderly.

While building the map, however, the team notices that one patent family may relate to technical work performed under both awards. The inventors remember the development somewhat differently, and the project records do not immediately resolve the chronology.

The map does not determine whether the invention is a subject invention. It does not decide which award is relevant or what reporting action may be appropriate.

Instead, it does something more basic first.

It identifies the uncertainty, the relevant documents, the people who need to be interviewed, and the question that needs to be resolved.

Without that connection, the issue might remain invisible until closeout, licensing discussions, financing diligence, or a change in counsel.

When should the map be reviewed?

The map works best as a living management record rather than a one-time cleanup exercise.

Useful review points include:

• the beginning or modification of a federal award;
• a new technical development or invention disclosure;
• preparation of a patent application;
• award closeout;
• an invention-reporting or utilization-reporting event;
• a change in patent counsel or grant personnel;
• a new university or subcontractor relationship;
• a license, financing, acquisition, or Phase III opportunity; and
• preparation for investor, customer, licensee, or acquisition diligence.

A company with a small portfolio may decide that periodic review is enough. A company with several active awards, frequent technical developments, or significant transaction activity may need a more regular cadence.

iEdison is part of the record, not the whole analysis

NIST describes iEdison as an interagency online reporting system through which recipients of federal funding agreements can report subject inventions and complete other Bayh-Dole-related reporting for participating agencies.

That distinction matters. Not every agency necessarily uses iEdison for every relevant reporting obligation, and current NIST guidance tells recipients to contact an agency directly when it does not use the system.

For agencies and records that do use iEdison, the system can contain important invention, patent, and utilization information.

But an iEdison record does not, by itself, establish the complete technical chronology, ownership chain, inventorship analysis, funding relationship, or patent-family history.

Portal administration and legal analysis are different jobs.

The portal may show what was entered. The broader record should also allow the company to understand what evidence supports the entry and how it relates to the underlying award, invention, and patent family.

NIST’s current invention-disclosure checklist illustrates this point. It asks users to make sure the disclosure document and the iEdison invention report concern the same invention and to reconcile information such as inventors and funding agreements.

That is the same basic discipline an award-to-invention map is intended to support across the broader portfolio.

What the map does not prove

An award-to-invention map is an inventory, evidence index, and coordination tool.

It is not a compliance certificate or a legal opinion.

By itself, it does not determine:

• whether an invention is a subject invention;
• who the legally correct inventors are;
• who owns an invention;
• whether every applicable reporting requirement has been satisfied;
• whether a patent is valid or enforceable;
• whether a government-rights issue exists;
• whether a historical inconsistency is legally significant; or
• whether a particular issue can or should be corrected.

Those questions may require legal analysis, agency-specific review, additional documents, or further fact development.

The map’s value is that it gives the responsible people a supported factual record from which those questions can be identified and addressed.

This is a management tool, not a fear exercise

A 2026 Government Accountability Office review found that federal funding recipients reported challenges including inconsistent requirements among agencies, time-consuming utilization reporting, and delays involving extension requests.

But GAO also reported an important counterpoint: a representative of small businesses said that compliance generally does not prevent small companies from bringing federally funded inventions to market.

That balance matters.

The goal is not to assume that every Phase II company has a serious problem.

The goal is to reduce fragmentation and make the company’s innovation record easier to understand, maintain, report, and explain.

A well-built map can help management, technical personnel, grant staff, patent counsel, and commercialization teams work from the same evidence. It can also make closeout and diligence less dependent on institutional memory.

Who owns the complete picture?

A company can build the first version internally.

Start with the awards, candidate inventions, active patent families, and source documents. Mark uncertainty honestly. Then have the people responsible for technical work, federal awards, patents, ownership, and commercialization look at the same record together.

For a structured starting point, use Cognivito’s Award-to-Invention Readiness Checklist.

At Cognivito, I help federally funded technology companies connect their award, invention, patent, reporting, ownership, and commercialization records through a coordinated legal and operational process.

But whether that work is handled internally or with outside help, the central question is the same:

Who owns the complete award-to-invention-to-patent picture at your company?

Sources and further reading

• 35 U.S.C. Chapter 18, Patent Rights in Inventions Made with Federal Assistance
• 37 C.F.R. Part 401, including §§ 401.1 and 401.14
• NIST iEdison
• NIST iEdison Organization User Guide
• NIST Bayh-Dole and iEdison Invention Disclosure Checklist
• GAO-26-107971, Technology Transfer