Federal Contract IP Checklist: Rights Categories, Assertions Table, Legends, Subject Inventions, and Deliverable Review

By Casey Scott McKay · 2024-02-11

This checklist runs the intellectual property questions in a federal contract from pre-proposal through delivery, challenge, and transaction. It begins with the component-level funding analysis that determines every rights category, then the commerciality determination and the scope-of-delivery negotiation that are the two places real leverage exists. It sets out the pre-award assertions table, the prescribed legends, and the delivery gate that prevents the most common loss of rights. It works validation challenge responses, the government purpose rights conversion clock, and Bayh-Dole administration from subject invention identification through reporting. It closes with subcontractor flow-down, FOIA submitter responses, and the diligence a buyer should run.

IP and Technology > IP and IT in Corporate Transactions | Checklist | Published 11 February 2024 - Updated 5 February 2026 | Casey Scott McKay - marksy.us

Summary. This checklist runs the intellectual property questions in a federal contract from pre-proposal through delivery, challenge, and transaction. It begins with the component-level funding analysis that determines every rights category, then the commerciality determination and the scope-of-delivery negotiation that are the two places real leverage exists. It sets out the pre-award assertions table, the prescribed legends, and the delivery gate that prevents the most common loss of rights. It works validation challenge responses, the government purpose rights conversion clock, and Bayh-Dole administration from subject invention identification through reporting. It closes with subcontractor flow-down, FOIA submitter responses, and the diligence a buyer should run.

Keywords: federal contract IP checklist · funding analysis · component level rights · commercial item determination · data item descriptions · assertions table · prescribed legends · delivery gate · validation challenge response · government purpose rights clock · subject invention disclosure · election of title · government license · section 204 · SBIR data rights · subcontractor flow down · FOIA submitter notice · section 1498 · novation · transaction diligence

How to use this checklist

| Phase | What it covers | |---|---| | 1 | Identify the clauses | | 2 | Decompose the deliverable | | 3 | The funding analysis | | 4 | Rights categories | | 5 | Commerciality | | 6 | Scope of delivery | | 7 | The assertions table | | 8 | Specifically negotiated licences | | 9 | Legends and marking | | 10 | The delivery gate | | 11 | Validation challenges | | 12 | Clocks | | 13 | Subject inventions | | 14 | Election and filing | | 15 | Government licence and Section 204 | | 16 | SBIR data rights | | 17 | Subcontracts | | 18 | FOIA | | 19 | Patent enforcement limits | | 20 | Transactions |

Boxes marked [Gate] must clear before a proposal is submitted, a deliverable is released, or a transaction closes.

The matter. A company delivered three years of design packages under a development contract. Nobody had filed an assertions table and nobody had applied a legend. The drawings went to a competitor bidding on production, lawfully, and the company's first knowledge of the problem was the competitor's proposal.

Phase 1. Identify the clauses

[ ] [Gate] List every IP clause incorporated, by number.
- Why. The clause set determines the framework, and civilian FAR contracts differ substantially from DFARS contracts.
- Trap. Reading the statement of work and not the clause list.
[ ] Check for clauses that should be there and are not.
- Why. Under G.L. Christian & Associates v. United States, a mandatory clause expressing a significant procurement policy is read in by operation of law.
- Trap. Assuming an omitted clause does not apply.
[ ] Identify the applicable data rights clause.
- Why. 48 C.F.R. § 52.227-14 for many civilian contracts; 48 C.F.R. § 252.227-7013 and 48 C.F.R. § 252.227-7014 for defence.
- Trap. Applying DFARS reasoning to a civilian agency contract or the reverse.
[ ] Identify the patent rights clause.
- Why. 48 C.F.R. § 52.227-11 and 37 C.F.R. § 401.14 implement Bayh-Dole.
- Trap. Treating patent rights as covered by the data rights clause.

Phase 2. Decompose the deliverable

[ ] [Gate] Break the system into items, components, and processes.
- Why. Rights attach at that level, not at the contract level.
- Trap. A contract-level analysis, which concedes components that could have been asserted.
[ ] Identify which deliverables pertain to which component.
- Why. The rights in a document follow the funding of the thing the document describes.
- Trap. Assuming the document's authorship controls.
[ ] Separate sustainment data from replication data.
- Why. Form, fit, and function data and operation and maintenance manuals carry unlimited rights regardless of funding; detailed manufacturing data need not be delivered at all in many contracts.
- Trap. Asserting restrictions on data that is unlimited by category, which wastes credibility.

Phase 3. The funding analysis

[ ] [Gate] Determine the funding source for each component's development.
- Why. Exclusively private, mixed, or exclusively government determines the category.
- Trap. A small government-funded task order contaminating an otherwise private development.
[ ] Treat independent research and development correctly.
- Why. IR&D recovered as an indirect cost is generally treated as private expense under the current framework.
- Trap. Conceding private development because the costs were recovered indirectly.
[ ] Assemble the evidence now.
- Why. In a validation challenge the asserting party justifies the restriction, and reconstruction after the fact is weak.
- Trap. Discovering during a challenge that project accounting never separated the work.
[ ] Build and maintain the funding table.
- Why. Component, funding source, evidence, category, and conversion date is the document everything depends on.
- Trap. A table describing a product two revisions old.

Phase 4. Rights categories

[ ] Identify unlimited rights data.
- Why. Data developed exclusively at government expense, form, fit, and function data, operation and maintenance manuals, and data necessary for installation and operation all carry unlimited rights.
- Trap. Asserting restrictions on data that is unlimited by category.
[ ] Identify government purpose rights data.
- Why. Mixed funding produces rights permitting government purpose use and release, converting to unlimited after five years unless negotiated otherwise.
- Trap. Not recording the conversion date at the moment the category is assigned.
[ ] Identify limited rights technical data and restricted rights software.
- Why. 48 C.F.R. § 252.227-7013 and 48 C.F.R. § 252.227-7014 reserve these for exclusively private development.
- Trap. Assuming restricted rights are workable for modern software deployment; they generally are not.
[ ] [Gate] Confirm each category is supported by the funding evidence.
- Why. The assertion is only as strong as the record behind it.
- Trap. An assertion made on engineering belief with no accounting support.

Phase 5. Commerciality

[ ] [Gate] Assess whether the item or software is commercial.
- Why. 48 C.F.R. § 252.227-7015 governs commercial item technical data, and commercial computer software is generally licensed on customary commercial terms — a materially better position.
- Trap. Accepting non-commercial treatment because nobody asked for the determination.
[ ] Assemble the evidence. Commercial sales history, published pricing, the standard commercial licence actually used, and the absence of modification beyond commercial offerings.
- Why. The determination is factual and contestable.
- Trap. A "commercial" product sold only to government customers.
[ ] Watch modification. A commercial item modified beyond what commercial customers receive may lose the treatment for the modified portion.
- Why. The characterisation attaches to what is delivered.
- Trap. A heavily customised variant claimed as commercial.
[ ] Preserve the position in the contract file.
- Why. The determination will be revisited at follow-on and in validation challenges.
- Trap. A determination made verbally in a negotiation and never documented.

Phase 6. Scope of delivery

[ ] [Gate] Review every data item description before agreeing to it.
- Why. What you deliver is negotiable; the rights attaching to delivered data largely are not.
- Trap. Accepting a standard deliverable list that requires manufacturing process data.
[ ] Offer what sustainment actually requires. Form, fit, and function data, interface control documents, and operation and maintenance manuals.
- Why. The government's interest is sustainment and competition, and that interest can frequently be met without replication data.
- Trap. A binary posture that concedes everything or refuses everything.
[ ] Define source code delivery expressly.
- Why. "Software" without specification is a dispute, and source code delivery is the single most consequential term in many technology contracts.
- Trap. Silence read as requiring source.
[ ] Record any agreed narrowing in the contract.
- Why. A programme manager's understanding is not a contract term.
- Trap. A side agreement with no contractual effect.

Phase 7. The assertions table

[ ] [Gate] File it with the proposal.
- Why. 48 C.F.R. § 252.227-7017 requires pre-award identification, and post-award additions are limited.
- Trap. Planning to assert at delivery.
[ ] Identify data specifically. Drawing series, document numbers, software modules.
- Why. Generic assertions invite challenge and are hard to sustain.
- Trap. "All technical data delivered under this contract."
[ ] State the basis in the clause's terms.
- Why. The contracting officer assesses the claim against the regulatory categories.
- Trap. A commercial-style confidentiality rationale.
[ ] Name the asserting party.
- Why. Subcontractors may assert in their own name and should.
- Trap. A prime asserting generically on a subcontractor's behalf.
[ ] Index the supporting file.
- Why. The funding table, ledgers, and development records must be retrievable when a challenge arrives.
- Trap. Evidence held by a project team that has since disbanded.

Phase 8. Specifically negotiated licences

[ ] Consider one wherever the standard categories fit badly.
- Why. The parties may agree other terms provided the government receives at least limited or restricted rights.
- Trap. Accepting restricted rights for software because the alternative was not raised.
[ ] Draft to the actual use. Government-wide installation, support contractor access under non-disclosure, no modification, no redistribution, no source delivery.
- Why. The negotiated licence should describe what the government genuinely needs.
- Trap. A licence so narrow the government cannot operate the system, which will be renegotiated from a worse position later.
[ ] [Gate] Record it in the contract.
- Why. A negotiated licence not in the contract does not exist.
- Trap. Agreement in a technical exchange with no contractual instrument.
[ ] Mark deliverables with the negotiated legend.
- Why. The restriction still depends on the marking.
- Trap. A negotiated licence with standard legends, or none.

Phase 9. Legends and marking

[ ] [Gate] Use the prescribed legend for each category.
- Why. The legends are specified in the clauses, and non-conforming legends may be stripped after notice.
- Trap. A corporate confidentiality stamp, which preserves nothing.
[ ] Complete every field in the legend. Contract number, expiration date where applicable, and contractor name and address.
- Why. Incomplete legends are non-conforming.
- Trap. A template with placeholders never filled in.
[ ] Mark every page and every file.
- Why. Restrictions attach to marked deliverables.
- Trap. A marked cover sheet on an unmarked drawing set.
[ ] Match the legend to the assertion.
- Why. A mismatch invites a challenge and undermines the whole table.
- Trap. Limited rights legends on government purpose rights data.
[ ] Use the SBIR legend where applicable.
- Why. SBIR protection under the 15 U.S.C. § 638 framework depends on the prescribed legend.
- Trap. SBIR deliverables marked with ordinary limited rights legends.
[ ] Correct non-conforming markings on notice, within the period.
- Why. Correction preserves the restriction; inaction does not.
- Trap. A notice routed to a mailbox nobody reads.

Phase 10. The delivery gate

[ ] [Gate] Assign a named signer for every deliverable release.
- Why. This is the control that prevents the largest category of rights loss, and it costs minutes per release.
- Trap. A process owned by everyone and therefore nobody.
[ ] Check the legend is present, correct, and complete.
[ ] Check it matches the assertions table row.
[ ] Check subcontractor data is identified with the asserting party named.
[ ] Check the export review is complete where the deliverable contains controlled technology.
[ ] Record what was delivered, when, with what markings, to whom.
- Why. In a later dispute the delivery record is the evidence.
- Trap. Deliveries made through a portal with no retained copy of what was uploaded.
[ ] Sample and audit quarterly.
- Why. Gates degrade.
- Trap. A gate that exists on paper and is bypassed under schedule pressure.

Phase 11. Validation challenges

[ ] [Gate] Diary the response deadline the day the challenge arrives.
- Why. 48 C.F.R. § 252.227-7037 and 48 C.F.R. § 252.227-7019 set short response periods, and the restriction can be stricken if missed.
- Trap. A challenge treated as correspondence rather than as a deadline.
[ ] Read what is actually challenged.
- Why. Challenges are frequently narrower than they appear.
- Trap. Mounting a global defence of every assertion.
[ ] Respond with evidence. Project ledgers, engineering records, development history, and a declaration from someone with knowledge.
- Why. The asserting party justifies the restriction.
- Trap. Argument without records.
[ ] Concede what cannot be sustained.
- Why. A partial concession preserves credibility on the assertions that can be sustained.
- Trap. A defence that collapses entirely and taints the rest.
[ ] Preserve the marking pending resolution, confirming the position in the applicable clause.
[ ] Appeal where warranted under 41 U.S.C. § 7103 and 41 U.S.C. § 7104.
[ ] Feed the outcome back into the funding documentation.
- Why. A sustained challenge identifies a gap that exists elsewhere too.
- Trap. Treating the loss as a one-off.

Phase 12. Clocks

[ ] [Gate] Diary every government purpose rights conversion date.
- Why. Five years, converting to unlimited rights, is the clock nobody watches.
- Trap. Discovering the conversion when a competitor uses the data commercially.
[ ] Diary the post-final-payment challenge window.
- Why. The government may challenge markings for a defined period after final payment, with exceptions.
- Trap. Disbanding the programme team while the window is open.
[ ] Diary Bayh-Dole periods. Disclosure, election, and filing under 35 U.S.C. § 202 and 37 C.F.R. § 401.14.
[ ] Diary SBIR protection periods per award.
[ ] Diary utilisation reporting obligations.
[ ] Review the register quarterly with a named owner.
- Why. A clock register nobody reads is a list.
- Trap. Dates held in a departed contracts manager's spreadsheet.

Phase 13. Subject inventions

[ ] [Gate] Determine subject invention status for every disclosure.
- Why. 35 U.S.C. § 202 reaches inventions conceived or first actually reduced to practice in performance of work under a funding agreement.
- Trap. Missing the second limb — an invention conceived privately but first reduced to practice under the contract is caught.
[ ] Build the intake route from engineer to patent function.
- Why. The disclosure clock starts when the invention becomes known to personnel responsible for patent matters.
- Trap. Inventions sitting in a project folder for a year.
[ ] Record the conception and reduction to practice facts.
- Why. They determine status and will be tested later.
- Trap. A disclosure form with no dates.
[ ] Identify the funding agreement.
- Why. The disclosure must identify the contract.
- Trap. Work performed across multiple contracts with no allocation.

Phase 14. Election and filing

[ ] [Gate] Disclose to the agency within the prescribed period.
- Why. Late disclosure risks loss of title.
- Trap. A disclosure prepared but never transmitted through the agency's system.
[ ] Elect to retain title within the prescribed period.
[ ] File within the prescribed further period, and address foreign filing within its own period.
[ ] Include the government support statement in the specification.
- Why. It is required and its absence is a compliance finding in diligence.
- Trap. Continuations filed without carrying the statement forward.
[ ] Use 35 U.S.C. § 205 to keep disclosures out of public release while filing.
[ ] File utilisation reports and treat the obligation as continuing.
[ ] Audit annually for inventions identified, disclosed, elected, filed, marked, and reported.
- Why. The gaps are cheap to close and expensive to discover in diligence.
- Trap. An audit of the patent portfolio that never checks Bayh-Dole compliance.

Phase 15. Government licence and Section 204

[ ] Understand what the government holds. A non-exclusive, non-transferable, irrevocable, paid-up, worldwide licence to practise or have practised on behalf of the United States.
- Why. "Have practised" permits a competitor to make the item for the government.
- Trap. Promising an exclusive licensee something the government licence defeats.
[ ] [Gate] Check 35 U.S.C. § 204 before any exclusive licence to use or sell in the United States.
- Why. Products must be manufactured substantially in the United States absent waiver.
- Trap. A licensee planning offshore manufacture with no waiver sought.
[ ] Note march-in exposure under 35 U.S.C. § 203.
- Why. Rarely exercised but a live policy question, and a real diligence item.
- Trap. Treating it as nonexistent.
[ ] Check 35 U.S.C. § 209 where title was not elected or was lost.
- Why. The government licenses federally owned inventions under its own framework.
- Trap. Assuming a lost election is unrecoverable in all respects.

Phase 16. SBIR data rights

[ ] Identify SBIR and STTR awards and their deliverables.
- Why. 15 U.S.C. § 638 establishes the programmes, and the associated data protection is frequently a small company's most valuable government-market position.
- Trap. Treating SBIR deliverables as ordinary contract deliverables.
[ ] [Gate] Apply the SBIR legend to every SBIR deliverable.
- Why. The protection depends on the marking.
- Trap. Unmarked SBIR data, which loses the protection entirely.
[ ] Track the protection period per award.
- Why. The periods are defined and run from award.
- Trap. Assuming the period restarts with each new award.
[ ] Distinguish data generated under the award from prior and new development.
- Why. The protection covers what the award generated.
- Trap. Broad claims covering technology developed outside the award.
[ ] Preserve the Phase III position.
- Why. Work deriving from Phase I or II may be awarded as Phase III without further competition, and SBIR data rights follow.
- Trap. Failing to identify the derivation when the Phase III opportunity arises.

Phase 17. Subcontracts

[ ] [Gate] Flow down the data rights and patent rights clauses.
- Why. The clauses require it, and a gap leaves the prime owing the government what it cannot obtain from its supplier.
- Trap. A purchase order with commercial terms only.
[ ] Collect subcontractor assertions before proposal submission.
- Why. The prime's table under 48 C.F.R. § 252.227-7017 must cover subcontractor deliverables.
- Trap. Asking for assertions after award.
[ ] Let subcontractors assert in their own name.
- Why. The clauses contemplate identification of the asserting party, and generic prime assertions weaken the position.
- Trap. A prime that will not name its supplier and thereby weakens both.
[ ] Do not demand unlimited rights reflexively.
- Why. Suppliers with valuable privately developed components will decline to bid.
- Trap. A standard purchase order requiring assignment of everything.
[ ] Allocate validation challenge responsibility and cost.
- Why. The evidence for a subcontractor's assertion is the subcontractor's.
- Trap. A prime obliged to defend an assertion it cannot support.
[ ] Address marking responsibility and delivery route.
[ ] Note that Bayh-Dole flows down, with subcontractors dealing directly with the agency on election and reporting.

Phase 18. FOIA

[ ] Mark submissions as confidential commercial information.
- Why. Agency procedures generally require pre-disclosure notification to submitters of information so marked.
- Trap. Unmarked submissions released with no notice.
[ ] Treat the information as private in fact.
- Why. Food Marketing Institute v. Argus Leader Media makes exemption four under 5 U.S.C. § 552 turn on customary and actual private treatment plus an assurance of privacy.
- Trap. Claiming confidentiality for information the company circulates freely.
[ ] [Gate] Name a recipient for notifications and prepare a template objection.
- Why. The windows are short and a release cannot be undone.
- Trap. A notification sent to a general contracts mailbox.
[ ] Write the objection to the current test. Specific information, customary and actual private treatment, the assurance relied on.
[ ] Consider reverse-FOIA with 18 U.S.C. § 1905 supporting the argument.

Phase 19. Patent enforcement limits

[ ] [Gate] Remember that injunctions are unavailable.
- Why. 28 U.S.C. § 1498 makes the remedy against the United States, and against contractors acting for it with authorisation and consent, compensation in the Court of Federal Claims.
- Trap. A strategy premised on stopping a second source through patent enforcement.
[ ] Check whether authorisation and consent applies.
- Why. It is a contract question, and its presence determines whether ordinary infringement exposure remains.
- Trap. Assuming every government-related activity is covered.
[ ] Understand the measure. Reasonable and entire compensation, generally approached as a reasonable royalty, with patent-act enhancements limited.
[ ] Watch the limitations analysis, which differs from ordinary infringement.
[ ] Plan accordingly. Where data rights permit a second source, the patent sets a price rather than preventing the outcome.

Phase 20. Transactions

[ ] [Gate] Obtain assertions tables, delivery records, and challenge outcomes for every contract.
- Why. They establish what the target actually holds.
- Trap. An IP diligence request list with no government contract section.
[ ] Verify the funding evidence supports the assertions.
[ ] Diary every government purpose rights conversion into the model.
- Why. They are dated events that convert restricted positions into unrestricted ones.
- Trap. A valuation assuming permanent exclusivity.
[ ] Audit Bayh-Dole compliance — disclosures, elections, filings, support statements, and reports.
[ ] Check 35 U.S.C. § 204 exposure on exclusive US licences.
[ ] Check SBIR positions and remaining protection periods.
[ ] Plan the novation.
- Why. Government contracts generally require a novation agreement to transfer, which takes time and agency cooperation.
- Trap. An asset deal timetable that ignores it.
[ ] Check organisational conflicts of interest created by the combination.
[ ] Price the exposures and prepare sell-side with a clean funding table, specific assertions, and complete marking records.

Phase 21. The three tables

[ ] The funding table. Component, development contract or IR&D project, funding source, evidence reference, asserted category, government purpose rights conversion date, reviewed date and owner. One row per component.
[ ] The assertions table. Technical data or software identified specifically, basis for assertion in the clause's terms, asserted rights category, and name of the asserting party. Filed with the proposal.
[ ] The clock register. Every dated obligation in one place: government purpose rights conversions, Bayh-Dole disclosure, election and filing periods, validation response deadlines, SBIR protection expiries, utilisation reporting dates, and the post-final-payment challenge window. Owner and review cadence named.
[ ] Keep all three current, because each decays as products change, contracts are added, and people leave.
[ ] Make them retrievable by someone who was not there. The most common diligence finding is that the person who knew is gone.

Phase 22. Three worked scenarios

Scenario A — the unmarked delivery. Three years of design packages delivered with no legend. The data carries unlimited rights and the government may lawfully provide it to a competitor. There is no cure. What can still be done: assert and mark going forward, seek a specifically negotiated licence for future deliverables, redesign the commercially critical content into a component developed privately after the fact, and treat the patent position as the remaining control — remembering that 28 U.S.C. § 1498 makes it a price rather than a bar.

Scenario B — the contaminated component. A limited rights assertion is challenged, and project accounting shows a small government-funded task order contributed to the component's development. The assertion cannot be sustained as limited rights. The right response is to concede that component, sustain the others with clean evidence, and fix the accounting so the boundary is visible for the next contract. A global defence would have cost all of them.

Scenario C — the forgotten conversion. Mixed-funding data delivered under a contract five years ago converts to unlimited rights. A competitor obtains it and enters the commercial market. Nothing can be undone. What should have happened: the conversion date diarised at the moment the category was assigned, and the commercially critical content moved into a privately developed component in year three — which is an engineering project with an eighteen-month lead time, not a legal remedy available in week one.

Phase 23. Metrics

[ ] Assertion coverage. Contracts with restricted deliverables that have a filed pre-award assertions table.
[ ] Assertion specificity. Assertions identifying data by document or module.
[ ] Funding evidence coverage. Asserted components with documented component-level funding records.
[ ] Marking compliance. Deliverables passing the gate with correct legends, sampled quarterly.
[ ] Marking incidents. Releases without correct legends, with root cause.
[ ] Challenge outcomes. Received, answered within period, sustained, stricken.
[ ] Clock currency. Conversions diarised; number converting within twelve months.
[ ] Bayh-Dole timeliness. Disclosed, elected, filed, marked, and reported within periods.
[ ] Flow-down completeness. Subcontracts with required clauses and collected assertions.
[ ] FOIA responsiveness. Notifications received and objections filed within the window.
[ ] The board number. Proportion of core technology deliverable to competitors for government purposes now or within two years.

Phase 24. Working with other advisers

[ ] Government contracts counsel for clause interpretation, commerciality positions, validation challenges, and claims under 41 U.S.C. § 7103.
[ ] Patent counsel for subject invention determinations, Bayh-Dole administration, government support statements, and the 35 U.S.C. § 204 analysis.
[ ] Cost accounting and finance, who own the funding evidence that decides validation challenges. Involve them before the assertion, not after the challenge.
[ ] Engineering programme leads, who own deliverable content and the data item description negotiation.
[ ] Export control counsel, because defence work engages the ITAR and EAR analysis alongside data rights. See Export Control Checklist.
[ ] Corporate development, for novation planning and organisational conflict analysis.
[ ] Agency-experienced outside counsel, because practice varies between agencies and programme offices in ways the regulations do not capture.

Phase 25. Scoping and the client conversation

[ ] Ask what the client is trying to protect. A commercial product entering the government market, a purpose-built system, or a research position. The advice differs.
[ ] Say early that clause negotiation is mostly unavailable, and that the leverage is in funding characterisation, commerciality, and scope of delivery.
[ ] Say early that marking is where rights are actually lost. Clients expect a legal answer; the answer is a two-line checklist and a named signer.
[ ] Set expectations on the funding analysis. For an established product line it is weeks of accounting work, and it cannot be skipped.
[ ] Identify the clocks in the first memorandum, because they are the exposures the client does not know it has.
[ ] Be candid about what cannot be fixed. Data delivered unmarked is gone, and telling the client early lets them redesign rather than litigate.

Phase 26. The one-paragraph brief

Federal contract IP position — [entity], [date]. Contracts with restricted deliverables: [N]. Assertions filed pre-award on [N]; [N] identify data specifically. Funding evidence: [N] per cent of asserted components documented at component level. Commerciality determinations: [N] sought, [N] obtained. Specifically negotiated licences: [N], covering [scope]. Marking: delivery gate operating since [date]; [N] releases, [N] incidents. Validation challenges: [N] received, [N] answered in period, [N] sustained. Government purpose rights conversions: [N] within twelve months, affecting [components]; mitigation [status]. Bayh-Dole: [N] subject inventions, [N] disclosed in period, [N] elected, [N] filed, [N] with support statements; utilisation reports current to [date]. Section 204: [N] exclusive US licences, [N] waivers. SBIR: [N] awards, protection running to [dates], legends applied on [N] per cent of deliverables. Flow-downs: [N] of [N] compliant. FOIA: [N] notifications, [N] objections filed in window. Section 1498: [assessment of enforcement options]. Board number: [N] per cent of core technology deliverable to competitors for government purposes now or within two years. Recommended actions: [list].

Phase 27. Vehicle-specific boxes

[ ] FAR-based civilian contracts. 48 C.F.R. § 52.227-14 governs data, with limited rights and restricted rights available through the alternates. The framework is less granular than the DFARS one, and the assertion and marking discipline matters just as much.
[ ] DFARS contracts. 48 C.F.R. § 252.227-7013, 48 C.F.R. § 252.227-7014, and the assertion and validation clauses. The most developed framework and the one this checklist principally tracks.
[ ] Commercial item acquisitions. 48 C.F.R. § 252.227-7015 for technical data and customary commercial licences for software. Establish and document the determination.
[ ] Grants and cooperative agreements. Bayh-Dole applies through the standard patent rights clause at 37 C.F.R. § 401.14; data terms vary by agency more than in FAR-based contracts.
[ ] Other transaction agreements. Nothing is prescribed and nothing is presumed. The negotiated terms are the whole answer, and gaps get filled by ordinary contract interpretation rather than by a framework built to respect private investment. Bring counsel in before the technical scope is settled.
[ ] CRADAs. Their own framework for inventions made under the agreement and for protecting collaborator background information.
[ ] Consortium participation. Read the member agreement as well as the government agreement, because rights allocation among members frequently surprises participants.
[ ] SBIR and STTR. 15 U.S.C. § 638 with its own data protection, its own legend, and the Phase III sole-source route.

Phase 28. If you can only do five things

[ ] Build the funding table at component level, with evidence references.
[ ] File a specific assertions table with the proposal.
[ ] Put a named signer on a delivery gate and check every legend, every time.
[ ] Diary the government purpose rights conversions and the Bayh-Dole periods.
[ ] Negotiate the deliverable list, not the clause.

Phase 29. A note on posture

[ ] Understand the government's interest before arguing with it. Federal procurement policy favours competition and long-horizon sustainment. A contracting officer seeking broad rights is usually protecting the ability to sustain a system for decades and to compete follow-on work, not trying to take a company's technology.
[ ] Offer the sustainment package. Form, fit, and function data, interface control documents, and operation and maintenance manuals meet most of that interest without supplying replication data.
[ ] Do not adopt a binary posture. A contractor that refuses everything invites an unlimited rights position; one that concedes everything gets one. The productive conversation is component by component.
[ ] Be accurate. An assertion that cannot be sustained damages the assertions that can, and contracting officers remember.
[ ] Keep the relationship. The same programme office runs the follow-on, and a data rights dispute conducted badly costs more than the rights at issue.

Outcome. The company rebuilt its practice around three artefacts. The funding table decomposed the system into forty-one components and identified thirteen developed exclusively with private funds, with project ledger references for each. The assertions table, filed pre-award under 48 C.F.R. § 252.227-7017, identified those thirteen by drawing series and named the two subcontractors asserting in their own right. The delivery gate — one named engineer signing a two-line checklist per release — caught eleven unmarked packages in the first year. Two validation challenges arrived in year two; both were answered within the period with ledger extracts and a declaration, and both assertions were sustained. The government purpose rights conversion on the mixed-funding components was diarised, and the commercially critical interface was redesigned into a privately developed component before the conversion date. On the follow-on procurement the company competed on price and capability rather than watching a competitor build its product from data it had delivered without a legend.

Key Authorities at a Glance

| Authority | Where it applies | |---|---| | 35 U.S.C. § 200 | Phase 13 | | 35 U.S.C. § 202 | Phases 13, 14, 15 | | 35 U.S.C. § 203 | Phase 15 | | 35 U.S.C. § 204 | Phase 15 | | 35 U.S.C. § 205 | Phase 14 | | 35 U.S.C. § 209 | Phase 15 | | 37 C.F.R. § 401.14 | Phases 1, 13 | | 48 C.F.R. § 52.227-11 | Phase 1 | | 48 C.F.R. § 52.227-14 | Phase 1 | | 48 C.F.R. § 252.227-7013 | Phases 4, 9 | | 48 C.F.R. § 252.227-7014 | Phases 4, 8, 9 | | 48 C.F.R. § 252.227-7015 | Phase 5 | | 48 C.F.R. § 252.227-7017 | Phase 7 | | 48 C.F.R. § 252.227-7019 | Phase 11 | | 48 C.F.R. § 252.227-7037 | Phase 11 | | 10 U.S.C. § 2320 | Phase 4 | | 28 U.S.C. § 1498 | Phase 19 | | 41 U.S.C. § 7103 | Phase 11 | | 41 U.S.C. § 7104 | Phase 11 | | G.L. Christian & Associates v. United States | Phase 1 | | 5 U.S.C. § 552 | Phase 18 | | Food Marketing Institute v. Argus Leader Media | Phase 18 | | 18 U.S.C. § 1905 | Phase 18 | | 15 U.S.C. § 638 | Phase 16 |

The five things people get wrong

Analysing funding at contract level rather than component level. It concedes rights that could have been asserted, before any negotiation begins.

Not filing an assertions table pre-award. 48 C.F.R. § 252.227-7017 requires it then, and later assertion is limited.

Delivering unmarked data. It carries unlimited rights regardless of who funded the development. This is the failure that produces the scenario at the top of this checklist.

Arguing about clause text instead of the deliverable list. The scope of delivery is negotiable; the rights attaching to delivered data largely are not.

Letting the government purpose rights clock run unwatched. Five years converts to unlimited, and companies discover it when a competitor uses the data commercially.