Quick answer: A university, research institute or specialist research partner can add expertise, facilities and methods that an internal team does not have, but collaboration itself does not make a project research. A relevant technical uncertainty may remain where an outcome cannot be known or determined in advance by a competent professional on the basis of current knowledge, information or experience. Before external work begins, the business should be clear about the question being tested, what each party is responsible for and how the resulting evidence will inform the next decision.
The 2026–27 Federal Budget announced R&DTI reforms for income years starting on or after 1 July 2028. Until those changes take effect, the R&DTI continues to be administered under the current legislation.
Collaboration should start from an unresolved technical question
Businesses often approach research organisations when an internal project reaches a limit.
The team may need access to specialised instrumentation. A manufacturing problem may require deeper materials expertise. A software system may need independent validation. A prototype may behave differently from the models used to design it.
Those can all be good reasons to collaborate.
But the first question should not be:
“Which university should we approach?”
It should be:
“What do we still need to learn?”
That distinction matters because an external technical service and a research collaboration can look very similar from the outside.
A laboratory may perform a recognised test and return a result. A university team may model a system using an established method. A specialist may analyse a sample using equipment that the business does not own.
If the method and expected interpretation are already established, this may simply be professional or technical service delivery.
For R&DTI purposes, current Australian Government guidance requires more than novelty or difficulty. A core R&D activity must be conducted for the purpose of generating new knowledge, involve an outcome that cannot be known or determined in advance, and require a systematic progression of work involving a hypothesis, experiment, observation, evaluation and logical conclusions to determine that outcome.
The research brief should therefore start with the unresolved technical question rather than with a list of tests.
For example:
Weak brief:
“Test this new material under high-temperature conditions.”
Stronger research question:
“Does the change in material composition prevent the loss of mechanical performance observed above the current operating range, and if so, what mechanism explains the change?”
The second version gives the external researcher something to investigate rather than simply something to measure.
Define the research interface before work begins
A collaborative research project has an interface between the business and the research partner.
That interface needs to be designed.
The business may understand the product, operating environment and commercial constraint better than the external researcher.
The research partner may understand the experimental method, measurement system or underlying science better than the business.
A useful brief makes clear how those two bodies of knowledge connect.
Before experimental work begins, the parties should be able to identify:
• the technical uncertainty being investigated;
• the hypothesis or competing explanations being tested;
• which variables are expected to change;
• which conditions need to remain controlled;
• what the research partner will measure or investigate;
• what information, specimens, software or operating data the business will provide;
• what result would support or weaken the hypothesis; and
• what business or engineering decision the evidence is intended to inform.
This does not mean the company must prescribe the experimental method to the researcher.
In many collaborations, the value of the external research team is precisely that it can design a better method.
But the method still needs to remain connected to the original technical question.
Australian Government R&DTI guidance describes an experiment as a scientific procedure undertaken to test a hypothesis. It states that records should explain how the experiment was conducted or planned and may, for example, describe the parameters varied, held constant, observed or measured.
A good collaboration can therefore allow the method to evolve while keeping the research question stable enough to understand why each experimental step was undertaken.
The same principle applies to broader research partnerships.
The Australian Research Council's Linkage Program promotes research partnerships between researchers and business, industry, community organisations and other publicly funded research agencies, encouraging the transfer of skills, knowledge and ideas and the development of longer-term research alliances.
The collaboration structure is useful because different parties contribute different capabilities.
It should not replace the need for a clearly defined research problem.
Keep the evidence chain intact across organisations
Research evidence becomes harder to manage when different organisations hold different parts of the record.
The business may hold the original design drawings.
The university may hold the raw experimental data.
A specialist facility may retain instrument files.
An engineer may have the notes explaining why one test condition was changed.
The project manager may have the email in which the team decided to abandon one hypothesis and test another.
Individually, each record may be useful.
The research story only becomes clear when they remain connected.
Current R&DTI record-keeping guidance states that records should be created at the time the activity is conducted and should show what was done, how the work was performed, when it occurred and who carried it out. Examples include experimental plans, trial records, test reports, research agreements and evaluations.
For collaborative research, that suggests a practical discipline:
Give each experimental activity a clear identity.
Link the external test or analysis to the relevant hypothesis.
Record which version of the prototype, dataset or formulation was supplied.
Preserve material changes to the method.
Record deviations from the original plan.
Retain the evaluation that explains what the external result means for the next experiment.
This is especially important when a research partner recommends a change.
Suppose an initial test cannot resolve the expected mechanism and the university proposes a different analytical technique.
That may be an entirely appropriate scientific response.
But the project record should show why the original method was insufficient, what the new method is expected to distinguish and how the revised experiment relates to the same research question.
Otherwise, the final file may contain several technically sophisticated reports without showing the systematic progression that connects them.
Formal collaborative programs recognise similar governance issues. For example, CSIRO's Industry PhD program uses collaboration agreements that address matters including confidentiality, project duration, funding arrangements and intellectual property.
The exact agreement required will depend on the project and professional legal advice may be appropriate. From a research-management perspective, however, the underlying lesson is simpler: decide who controls which information and how the project record will remain usable before work becomes distributed across several organisations.
Choose the collaboration structure after the research need is clear
Not every technically uncertain project needs a university.
And not every university engagement needs to become a long-term collaborative research program.
The appropriate structure depends on what is missing.
If the business already has a clear experimental design but lacks a particular instrument, a specialist laboratory may be enough.
If the unresolved issue requires deep disciplinary knowledge or a new scientific method, a university researcher or research institute may add the capability that the internal team lacks.
If the company expects an ongoing research relationship, a formal collaborative pathway may make more sense.
The ARC Linkage Projects scheme, for example, is explicitly designed to initiate or develop long-term strategic research alliances between higher education researchers and research end-users, rather than being structured as a simple testing service.
A Registered Research Service Provider is another model. Australian Government guidance describes RSPs as scientific or technical service providers that companies can engage to conduct R&D activities on their behalf, while making clear that using an RSP does not guarantee that the activities satisfy the R&DTI criteria; companies still need to self-assess.
These pathways solve different problems.
The useful sequence is therefore:
define the uncertainty → identify the missing capability → choose the collaboration structure.
Starting with the provider can lead to a technically competent project that answers the wrong question.
Starting with the research question makes it easier to decide whether the business needs a test facility, a domain expert, a university partnership, an RSP-supported research pathway or simply an internal engineering activity.
Conclusion
External research partners can extend the expertise, facilities and methods available to a business, but they do not replace a clearly defined research question.
A strong collaboration begins with the unresolved technical uncertainty, makes responsibilities and experimental interfaces explicit, and preserves the evidence chain as work moves between organisations.
When those links remain visible, external expertise becomes part of a coherent research progression rather than a collection of disconnected technical outputs.
Talk to Ignition Research if your business is considering bringing a university, specialist researcher or external facility into a technically uncertain project and the research question, experimental responsibilities or evidence pathway still need to be defined. 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.
Sources & Further Reading
Australian Government — Conducting core R&D activities for the R&D Tax Incentive
Australian Government — Record keeping for the R&D Tax Incentive
Australian Government — Get help from a research service provider
Australian Research Council — Linkage Projects
Australian Research Council — Linkage Program
CSIRO — Industry PhD Program Rules and Collaboration Agreement guidance
R&DTI note: Working with a university, research institute, specialist laboratory or RSP does not by itself make an activity eligible for the R&D Tax Incentive. Eligibility still depends on the actual activities conducted and the applicable R&DTI requirements.
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.
