Quick answer: Define the boundary between what each party already owns, what the research may create and what each party will be allowed to use before substantive technical work begins. The objective is not necessarily to decide that one party owns everything, but to prevent uncertainty about access, confidentiality, commercial use and future research from appearing after valuable results have already been produced.
Separate what each party brings from what the project creates
A technical collaboration often begins informally.
A company has a prototype, dataset, algorithm, material formulation or manufacturing method.
A university researcher, specialist laboratory or external research provider has expertise, equipment or an existing method that could help answer the unresolved technical question.
The first discussions focus naturally on the experiment.
Can the problem be tested?
What equipment is required?
How long will the investigation take?
What would constitute a useful result?
But another research boundary is being created at the same time:
Which knowledge belongs to the project, and which knowledge arrived before it?
IP Australia distinguishes three categories that are useful for structuring this discussion.
Background IP
is intellectual property created before or outside the collaboration and brought into the project by one of the parties.
Project IP
is new intellectual property created through the collaboration.
Third-party IP
belongs to someone outside the collaboration but may still be needed for the work.
The distinction matters because a research partner may need access to a company's existing technology without receiving ownership of it.
A university may contribute an established analytical method.
A specialist may use proprietary software or know-how.
A company may provide confidential production data or an existing prototype.
None of those inputs automatically becomes jointly owned simply because it is used during a collaborative experiment.
The practical task is therefore to identify the inputs before they become mixed together.
A useful project record might identify:
• existing source code;
• drawings;
• datasets;
• test methods;
• materials;
• patents;
• know-how; and
• third-party tools relied upon by the research.
That exercise does not replace a legal agreement.
It gives the lawyers and commercial decision-makers something technically accurate to work from.
IP Australia's collaboration guidance specifically recommends identifying relevant background IP, understanding whether third-party IP will be used and deciding how any new project IP will be handled before the collaboration progresses. IP Australia
Ownership is only one of the questions
Commercial teams often begin with:
Who owns the new IP?
That matters.
But ownership alone may not determine whether the collaboration will work commercially.
What can each party use during the project?
What can each party continue using after the project finishes?
Can the results be used in further research?
Can they be licensed to another party?
Can either party improve or modify the resulting technology?
What happens to confidential information?
Can research findings be published?
The commercially important questions can therefore extend beyond ownership.
IP Australia's collaboration resources identify project outputs, commercialisation rights, further research, confidentiality and publication as matters that should be considered alongside ownership. Its model materials also prompt parties to identify project inputs, deliverables, project IP and post-project needs rather than treating the relationship as a single ownership clause. IP Australia
Treat the IP boundary as part of the research design
IP planning can look separate from experimental design.
In practice, the two can become closely connected.
An external laboratory develops a modification to the test method.
A university researcher creates a new algorithm while analysing proprietary data.
A research partner uses third-party software to perform the investigation.
In each case, the technical output and the right to use that output may need to be considered together.
These are not only legal drafting questions.
They affect what the research project should deliver.
Before work starts, the project team should be able to identify the technical outputs that matter to the next commercial decision.
• validated method;
• source code;
• prototype;
• dataset;
• design file;
• experimental result;
• physical sample;
• specification; or
• technical report.
The collaboration terms can then be built around the real research pathway rather than around a generic statement that "IP will be agreed later".
IP Australia warns that outsourced R&D can create misunderstandings about rights to results and recommends agreements dealing with project results, know-how, reports, physical research material, background information and confidentiality. It also recommends obtaining appropriate IP or legal advice for collaboration arrangements, particularly where joint ownership, broad licences or other material rights are being considered. IP Australia
Conclusion
Technical collaborations create value by combining different capabilities, but they also create new boundaries around access, use and ownership.
The strongest collaborations define those boundaries before the research begins: what each party brings, what the project may create and how the resulting knowledge can be used.
IP planning is therefore not separate from research design. It is part of making sure valuable technical results can actually become usable outcomes.
Sources & Further Reading
Talk to Ignition Research if your business is about to share proprietary technology, data, prototypes or technical know-how with a university, laboratory or specialist research partner and the research outputs have not yet been clearly separated from the IP each party is bringing into the project. 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. business.gov.au
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.
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.
