Quick answer: Paying a university to conduct research does not by itself determine who owns every output or who may use the underlying methods, data and intellectual property. A collaboration agreement should distinguish the research deliverables from background IP, project IP, third-party IP and the licences or access rights needed for the intended commercial use. The practical question is not simply who owns the research result, but whether the business can actually use it for the purpose for which the research was commissioned.
Receiving the Research Result Is Not the Same as Being Able to Use It
A university research project can reach a technically successful conclusion while leaving an important commercial question unresolved:
Can the business actually use the result?
Consider a manufacturer that funds a university investigation into an improved production method.
The university completes the agreed experiments and provides a report showing that one approach performs well under the tested conditions.
The research itself may have been successful.
But implementation may depend on an analytical model owned by the university, specialised software licensed from a third party, a laboratory procedure that was not included in the deliverables, or technical know-how held by the research team.
The company has received the research conclusion.
It may not yet have everything required to reproduce, modify or commercialise it.
That distinction is easy to miss when ownership, access and technical delivery are treated as one issue.
They are not.
IP Australia distinguishes between background IP, project IP and third-party IP in collaborative research.
Background IP
is generally IP created before or outside the collaboration and contributed by one of the parties.
Project IP
is new IP created through the collaboration.
Third-party IP
belongs to someone outside the collaboration but may still be required to perform or use the research.
Current IP Australia guidance recommends identifying those categories early and agreeing how relevant IP will be owned, protected, licensed and used.
However, practical use of research results may depend on more than IP ownership alone.
Experimental data, software configurations, analytical procedures, calibration information, physical samples, technical reports and practical know-how may all affect whether a business can make use of the findings.
The central question is therefore not:
“Did we pay for the research?”
or even:
“Do we own the project IP?”
It is:
“Do we have the rights, deliverables and technical information needed to use the result in the way we intend?”
Define the Deliverables Separately From the IP
A useful university research agreement should distinguish what the university will deliver from who will own or be licensed to use the intellectual property associated with those deliverables.
IP Australia's research collaboration model materials make this distinction explicitly. Their contract structure deals separately with deliverables, background and third-party IP, project IP and commercialisation arrangements. ipa
For a business, that means several separate questions need to be resolved.
What evidence will the business receive?
A final report may summarise the research without transferring all of the evidence used to reach the conclusion.
Depending on the purpose of the project, the business may also need:
• underlying experimental data;
• metadata and data definitions;
• test reports;
• relevant observations and failed trials;
• analysis outputs;
• model or software versions; or
• information needed to interpret the results independently.
Not every project requires every item.
The appropriate deliverables depend on what the business needs to do with the research after completion.
If the findings will support a major engineering or investment decision, access to the underlying evidence may be more important than if the research is intended only to answer a narrow internal question.
Restrictions may also legitimately apply because of privacy, confidentiality, ethics requirements or third-party obligations.
Those restrictions should be understood before the research begins rather than discovered at handover.
What background or third-party IP is needed to use the result?
A university may use existing software, methods, models or laboratory processes while conducting the research.
Those resources do not automatically become project IP merely because they were used during the project.
IP Australia recommends identifying background IP contributed by each party and any third-party IP required for the collaboration, together with the licences needed to use it. ipa.dev.ipaustralia.gov.au
This matters because a business may own a project output while still relying on background IP that it does not own.
For example, the university may develop a new project-specific method but implement it using an existing analytical platform owned by the university.
The business may therefore need a licence to the background technology in order to commercialise the project result.
Ownership of the new result alone may not solve that problem.
Who owns the project IP, and who may commercialise it?
Project IP does not have to be owned by the business simply because the business funded the work.
Depending on the agreement, it may be owned by the business, the research organisation or, in some circumstances, both parties.
The more important commercial question is often what each party is permitted to do with it.
IP Australia's guidance specifically recommends deciding who is best placed to own, protect and commercialise project IP and documenting relevant licensing arrangements. Its research collaboration contract templates also distinguish ownership of project IP from the rights to commercialise it. ipa.dev.ipaustralia.gov.au
A business may therefore need to consider:
• whether its licence is exclusive or non-exclusive;
• whether commercial use is permitted;
• whether the licence covers the relevant territory and application;
• whether modifications or improvements are permitted;
• whether background IP required for commercialisation is included; and
• what happens if additional project IP emerges during the research.
These are contractual and legal questions and should be addressed with appropriate professional advice.
The important research-management point is that they should be identified before technical success makes them urgent.
Make Technical Usability Part of the Completion Test
Even where the rights are clear, the business may still be unable to use the result if the technical handover is incomplete.
Suppose a university develops an environmental monitoring method for an engineering company.
The method successfully distinguishes between the operating conditions investigated during the project.
But the business later wants to reproduce the method at another site.
It discovers that the result depends on sensor calibration procedures, preprocessing settings and a model configuration that were not described in the final report.
Nothing about that necessarily changes the ownership of the research result.
The problem is practical usability.
The completion process should therefore ask whether the agreed deliverables are sufficient for the intended next step.
Depending on the project, useful handover material may include:
• tested assumptions;
• instrument or equipment configurations;
• relevant software and model versions;
• calibration information;
• data-processing procedures;
• known operating limits;
• limitations of the experimental method;
• unresolved technical questions; and
• the location of supporting records that remain with the university.
This is a practical handover framework rather than a prescribed legal or R&DTI template.
The objective is not always to make the business fully independent of the university.
In some collaborations, continued access to specialist researchers, facilities or proprietary methods may be part of the intended model.
What matters is that this dependency is known and commercially acceptable.
Accept the Project Against Its Intended Use
A university research project may meet its contractual research milestones without establishing that a technology is ready for commercial deployment.
The business should therefore distinguish two acceptance questions.
The first is:
Has the university delivered the research outputs and rights agreed under the collaboration?
The second is:
Are those outputs sufficient for the business's intended next use?
Those questions may produce different answers.
A materials investigation may successfully establish that a formulation performs well under defined conditions.
But the company may still need engineering work before it can manufacture the formulation at another facility.
A software project may demonstrate a new analytical method but still depend on a university-owned tool that requires a licence for commercial use.
A research report may fully satisfy the agreed scope while leaving further validation necessary before deployment.
The nature of any remaining gap should be identified accurately.
A contractual or licensing restriction is not evidence of technical uncertainty.
Likewise, the fact that implementation is difficult, expensive or dependent on specialist expertise does not by itself establish a new R&D activity.
Further experimental work may be appropriate only where a new technical outcome remains unable to be known or determined in advance and the applicable R&DTI requirements are otherwise satisfied.
Keep the Research Agreement Inside the Evidence Chain
For projects that may also be relevant to the R&D Tax Incentive, the research agreement can form part of the supporting project record.
Current Australian Government record-keeping guidance states that records should be created at the time the activity is conducted.
It identifies experimental plans, records of trial runs, test reports showing results and evaluation, and contracts or research agreements as examples of records that may help demonstrate the systematic progression of R&D work. business.gov.au
That does not mean a university contract or final report establishes R&DTI eligibility.
The eligibility of activities must still be assessed against the applicable requirements.
External research delivery, including work conducted through a Research Service Provider, does not itself guarantee that the underlying activities qualify for the R&DTI. business.gov.au
The agreement is therefore valuable because it can help establish what the project was intended to investigate, what each party was expected to do and what evidence or outputs were meant to be produced.
It should complement the experimental record, not replace it.
Conclusion
A university can successfully deliver a research project without necessarily transferring everything a business needs to reproduce, modify or commercialise the result.
Ownership is only one part of the arrangement.
A useful collaboration also defines the deliverables, access to experimental evidence, licences to required background and third-party IP, rights to commercialise project IP and the technical information needed for the intended next step.
The final test is therefore not simply:
“Who owns the result?”
It is:
“Can we use the result in the way the project was meant to enable?”
If the answer depends on information, rights or access that have not yet been agreed, the research may be technically complete while the commercial handover is not.
Sources & Further Reading
Australian Government — Record keeping for the R&D Tax Incentive
Australian Government — Get help from a research service provider
Talk to Ignition Research if your business is considering university-led research and needs to define the technical outputs, evidence and handover requirements before the investigation begins. As a Registered Research Service Provider, Ignition Research assists businesses with research question definition, experimental design, technical investigations and contemporaneous supporting records within its registered research fields.
RSP registration confirms that the provider has met the relevant registration requirements for its registered research fields. It does not constitute government endorsement of a project or guarantee R&DTI eligibility.
We do not determine R&DTI eligibility or provide tax advice. The R&D Tax Incentive is a self-assessment program, and companies remain responsible for assessing their activities, expenditure and circumstances and obtaining appropriate tax advice.
This article provides general information only and is not tax, legal or financial advice.
Working on a project like this?
Tell us what you're building and the part you're not sure will work. A researcher from our Adelaide team (registered Research Service Provider RSP000047) reads every enquiry and replies within two business days. No documents needed.
