Navigating Intellectual Property in Joint Lab-Industry Projects

Joint research between a federal laboratory and a private company can turn publicly funded science into a product, service, or industrial process. It can also create uncertainty about who owns an invention, who may use project data, and whether a business can secure enough commercial exclusivity to justify investment.

These questions become more complex when an Australian company works with a United States federal laboratory. The project may involve US federal statutes, agency policies, export controls, procurement rules, Australian patent law, and contractual terms governing research results. Intellectual property needs to be addressed before technical work begins, rather than treated as paperwork at the end.

The Federal Laboratory Consortium for Technology Transfer helps businesses locate relevant federal capabilities, technologies, and laboratory contacts. Its network can be a useful starting point for identifying a laboratory with the equipment, expertise, or existing invention needed for a collaboration.

A sound arrangement distinguishes pre-existing assets from new results, sets practical rights for each party, and connects protection strategy with the intended market. For an Australian business, that may mean planning for customers in Sydney and Melbourne while also preserving rights in the United States and other export markets.

Start with the project’s legal architecture

The first step is identifying the agreement that will govern the work. A Cooperative Research and Development Agreement, commonly called a CRADA, is often used when a US federal laboratory and an outside organisation collaborate on research and development. A CRADA can address personnel, facilities, funding, confidential information, inventions, publication, and licensing discussions, although the exact terms depend on the agency and project.

A company should review the laboratory’s statutory authority and technology-transfer policy before assuming that a familiar commercial contract will be available. Federal laboratories may have limits on assigning inventions, granting exclusive rights, accepting funds, or sharing certain information. The government may retain rights needed for public purposes, national security, or continued federal use.

The commercial partner’s internal authority matters as well. The people signing a collaboration agreement should have power to commit the company, and any parent company, university partner, investor, or subcontractor with an interest in the research should be identified early. A clean chain of authority helps prevent later disputes over whether a researcher was allowed to disclose or license a result.

Separate background assets from new results

Background intellectual property includes patents, software, designs, trade secrets, laboratory methods, datasets, prototypes, and specialist know-how that existed before the collaboration. Each party should list the assets it brings into the project and state whether the other party may use them. A vague reference to “relevant technology” can create uncertainty about whether an entire product platform has been made available.

Foreground intellectual property is created during the joint work. The agreement should define whether this includes only patentable inventions or also copyright, algorithms, experimental data, technical drawings, biological materials, improvements, and negative results. Clear definitions are particularly important where a new result modifies a pre-existing tool owned by one party.

Inventorship and ownership are different concepts. Under US patent law, inventorship depends on who contributed to the conception of claimed subject matter, while ownership generally follows agreements and assignments. An Australian company should keep dated laboratory records and contribution logs, because a project manager’s title or funding contribution does not by itself establish inventorship.

Joint ownership can look fair but may be difficult to administer. Different countries apply different rules to a jointly owned patent, including whether one owner can license or exploit the invention without the other’s consent. A better arrangement may allocate ownership by invention category and provide the non-owning party with a defined licence, revenue share, or research-use right.

Match protection to the route to market

Patents are valuable when a technical feature can be described clearly, is new, and supports a defensible commercial product. Filing strategy should account for the countries where the product will be made, sold, or licensed. An Australian business may need protection through IP Australia, the United States Patent and Trademark Office, and potentially a PCT application before selecting further national jurisdictions.

Confidentiality can be more effective than patenting for manufacturing parameters, training data, calibration procedures, or business methods that are difficult to reverse engineer. Trade-secret protection requires practical controls, such as restricted access, confidentiality agreements, secure repositories, staff training, and procedures for handling departing employees and contractors.

Publication creates a special risk. A federal scientist, university collaborator, or company engineer may want to publish a paper, present at a conference, or release code. The agreement should allow reasonable review for confidential information and patent filings without giving either party an indefinite veto over legitimate research communication. Australian universities and public research institutions commonly value publication, so the review timetable should be negotiated before experiments start.

A short delay to file a patent application can preserve options, while an unplanned presentation may destroy novelty in some jurisdictions. The project team should use a disclosure register and require legal or technology-transfer review before public release. This is especially important for demonstrations at trade events in Melbourne, Brisbane, or Sydney.

Define licences that investors can use

Ownership alone does not guarantee commercial freedom. A company may own a newly created patent yet lack rights to use a federal laboratory’s background software, test method, material, or platform. The agreement should therefore include the licences needed to develop, manufacture, market, maintain, and modify the resulting product.

Key licence terms include field of use, territory, duration, sublicensing, exclusivity, performance milestones, royalty calculations, reporting, audit rights, and termination. An Australian company targeting mining, construction, health, or clean-energy customers may need different fields of use from another licensee. A carefully drafted field can preserve public-sector or research applications while supporting private investment.

Exclusivity is often the most commercially sensitive point. An exclusive licence may help a company raise capital and justify regulatory spending, but a federal laboratory may need to preserve access for government work, emergency response, or additional research partners. Exclusivity can be limited by sector, geography, application, or time and tied to development milestones.

Federal technology-transfer opportunities can also involve an existing invention rather than a new joint result. For example, a business assessing building controls may review HVAC energy technologies before deciding whether it needs a collaborative development agreement or a licence to an already available technology.

Control data, software, and technical know-how

Data rights should be negotiated separately from patent ownership. A dataset may contain personal information, commercially sensitive measurements, government-restricted information, or material supplied by a third party. The agreement should identify who may collect, store, analyse, reproduce, publish, commercialise, and transfer the data.

Software requires particular care because source code, object code, documentation, models, interfaces, and open-source components can carry different rights. A project may produce an algorithm that is patentable in some circumstances, while the implementation remains protected by copyright and the training or test data is controlled under contract. Open-source licences must be checked before code is incorporated into a commercial product.

Federal laboratories may impose cybersecurity, records-management, facility-access, or information-classification requirements. A company should know where project data will be hosted, who can access it, whether cloud services are permitted, and what happens when the agreement ends. Australian organisations may also need to consider the Privacy Act 1988, the Australian Privacy Principles, and cross-border data transfers.

Know-how is easily overlooked because it may never appear in a patent or source-code repository. Laboratory protocols, failed approaches, instrument settings, and informal engineering judgments can determine whether a prototype works outside a controlled facility. The collaboration should define how this information is documented and whether it is included in a licence or protected as confidential information.

Account for Australian commercial conditions

An Australian company entering a US federal collaboration should map both jurisdictions before making public claims about ownership or market readiness. The Australian Patents Act 1990, US patent rules, agency regulations, and contract terms may produce different outcomes. Australian counsel can coordinate with US patent and government-contract specialists, particularly where the invention could be exported or supplied to government customers.

Local market conditions should shape the licence. A technology designed for American building codes may require adaptation for Australian standards, climate zones, or procurement requirements. A building-energy product tested in a cold US region may need validation for summer cooling loads in Perth or humid conditions in Brisbane. The party paying for that adaptation should receive appropriate rights to the resulting improvements.

Sector context also affects value. A mining technology may be tested near Perth and sold to operators across Western Australia, while a medical device may need evidence acceptable to Australian regulators and hospital procurement teams in Sydney. A disaster-resilience tool could be relevant to bushfire-prone regional communities, flood-exposed areas around Brisbane, and state emergency agencies, but each customer group may require different performance evidence and data arrangements.

Federal technology is often relevant to these practical needs. A company exploring emergency-management products can examine disaster response technologies alongside its own field requirements, then determine whether a licence, technical assistance arrangement, or joint research project offers the clearest route to deployment in Australia.

Build governance for disputes and change

Joint projects evolve. The original research question may produce a different invention, require a new subcontractor, or reveal that a planned product is not commercially viable. Governance provisions should establish a steering committee, technical leads, approval thresholds, meeting records, and a process for changing the work plan without accidentally changing ownership or confidentiality rights.

The agreement should require prompt invention disclosures and set deadlines for deciding whether to file patent applications. It should also state who pays prosecution and maintenance costs, what happens if the owner stops paying, and whether the other party may continue protection. Without these provisions, a valuable patent can lapse while the parties debate responsibility.

Dispute clauses should be practical and proportionate. They may cover escalation to senior executives, expert determination for technical questions, mediation, arbitration, or court proceedings. The governing law, venue, language, and available remedies matter when one party is in Australia and the other is a US federal entity subject to sovereign-immunity limits and specific administrative procedures.

A final review should test whether the agreement supports the project’s real commercial path: research, prototype development, regulatory approval, manufacturing, sales, support, and future improvements. When ownership, licensing, confidentiality, publication, data use, and governance are aligned from the outset, intellectual property becomes an operating framework for collaboration rather than an obstacle discovered after the science is complete.