Quick answer: A technically uncertain project can legitimately require several specialists, but dividing the work should not divide the research logic. Someone—or a clearly defined project function—should retain a clear view of the hypotheses, experimental sequence, interfaces between work packages and how each provider's result informs the next decision. Where an outcome cannot be known or determined in advance by a competent professional on the basis of current knowledge, information or experience, the relevant experimental activities still need a coherent research pathway, and each proposed core R&D activity must satisfy the applicable systematic-progression requirements.
Different specialists can answer different parts of the same question
Complex technical projects rarely fit neatly inside one organisation.
A software company may need an external cybersecurity specialist.
A manufacturer may need materials analysis from one facility and process modelling from another.
A building-product developer may involve a fire-testing facility, structural engineer and materials specialist.
An AI project may require a domain expert, data engineer and independent performance evaluator.
There is nothing inherently unusual about this.
The problem begins when each provider receives an isolated task without seeing how that task relates to the underlying research question.
One supplier is asked to run a test.
Another is asked to model a component.
A university researcher investigates a mechanism.
An internal engineer modifies the prototype.
Each piece may be technically competent, yet the business can still finish with four reports and no clear conclusion.
Under the R&DTI, a core R&D activity must involve an outcome that cannot be known or determined in advance by a competent professional on the basis of current knowledge, information or experience. That outcome must be determined through a systematic progression of work based on principles of established science, proceeding from hypothesis to experiment, observation and evaluation and leading to logical conclusions. The activity must also be conducted for the purpose of generating new knowledge. business.gov.au
That progression does not disappear when external specialists become involved.
The project still needs to answer:
What uncertainty are all these work packages collectively trying to reduce?
Without that connection, the business may be purchasing a collection of technical services without a clear research pathway connecting them.
Give each provider a question, not just a task
A weak multi-provider scope often starts with deliverables.
“Run these samples.”
“Build this model.”
“Review the code.”
“Test the prototype.”
Those instructions describe work, but not necessarily research.
A stronger scope explains why the work is being done and what decision its result needs to inform.
Consider a company developing a new composite assembly.
A testing facility may be asked to measure mechanical behaviour.
A materials specialist may investigate the failure surface.
A simulation provider may model load transfer.
Those activities become much more useful when they sit inside one explicit sequence.
The project might begin with a hypothesis that a particular interface is responsible for premature failure.
The physical test establishes when and where failure occurs.
The materials analysis examines whether the expected interface mechanism is present.
The model tests whether that mechanism is sufficient to explain the observed behaviour.
The combined evaluation then determines whether the hypothesis is supported, weakened or needs to change.
Each provider has a different method.
They do not need to perform the same work.
They do need to contribute to the same decision chain.
A similar principle appears in the registration criteria for Research Service Providers. Under section 3.01 of the Industry Research and Development Regulations 2022, an RSP that will subcontract part of its services must be able to manage that subcontracting and understand and explain the subcontractor's results to the R&D entity receiving the services. Federal Register of Legislation
That is a useful principle even outside a formal RSP arrangement.
Outsourcing capability should not outsource understanding.
If nobody on the project can explain how a specialist result affects the hypothesis, the project has lost part of its method.
Control the interfaces between providers
The highest-risk part of multi-provider research is often not the technical work itself.
It is the handover.
Provider A changes the specimen preparation method, but Provider B assumes the original method was used.
A modeller uses one material property while the physical testing team uses another batch.
A software evaluator tests a later version than the one described in the experiment plan.
A university team reports an unexpected mechanism, but the internal development team continues with the next prototype before the implication is discussed.
These are interface failures.
They make otherwise valid evidence difficult to combine.
As a practical research-governance framework, a multi-provider plan should define several things before work begins:
• which research question each work package addresses;
• what inputs each provider will receive;
• which system, specimen, model, dataset or software version is authoritative;
• which conditions need to remain comparable;
• what raw data or intermediate evidence must be returned, not only the final report;
• how unexpected findings will be escalated;
• who evaluates results across providers; and
• who decides whether the next experiment proceeds, changes or stops.
The purpose is not to create administrative overhead.
It is to prevent the experimental chain from breaking at organisational boundaries.
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 of potentially relevant records include contracts or research agreements, experimental plans, records of trial runs and test reports showing results and evaluation. business.gov.au
For a multi-provider project, those records need to connect.
A laboratory report should point back to the configuration it tested.
A modelling result should identify which experimental assumptions it used.
A specialist opinion should distinguish established knowledge from interpretation of the project's new observations.
A project decision should show which evidence caused the team to change direction.
The content matters more than the document format.
Decide early how information, decisions and IP will be governed
Technical governance and commercial governance also intersect.
A collaboration can generate background knowledge, new project IP, raw data, methods and potentially patentable results.
Those rights should not be discovered after the most valuable finding has already been produced.
IP Australia recommends addressing IP management early in a collaboration, including identifying the background IP each party contributes, deciding how project IP will be owned, protected and used, and documenting relevant access and licensing arrangements. ipa
That legal structure is separate from the scientific method, but the two need to align.
For example, the business may technically need access to raw measurements to evaluate the experiment, while the provider’s standard contract only supplies a summary report.
A university researcher may need publication rights, while the business needs time to assess patent protection.
A specialist may use proprietary analysis software but still need to explain enough of the method for the result to be interpreted.
These issues are easier to resolve before the research begins.
They are much harder after an unexpected result becomes commercially important.
For founders and CFOs, the practical question is therefore not simply:
“Which provider is best?”
It is:
“Which capabilities need to be external, and what must remain connected internally so that we can still make and explain the decision?”
For CTOs and engineering leads, the corresponding question is:
“If three specialists return three different pieces of evidence next month, who is responsible for turning them into one technical conclusion?”
That person or function does not need to perform every experiment.
But someone—or a clearly defined governance function—has to hold the method together.
Conclusion
If three specialists return three different pieces of evidence, somebody needs to be responsible for turning them into a coherent technical conclusion.
That person or function does not need to perform every experiment. It does need to understand how the work packages relate to the hypotheses, what evidence each provider has generated and what the combined results mean for the next decision.
External capability can be distributed. The research logic should remain connected.
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
Federal Register of Legislation — Industry Research and Development Regulations 2022
Talk to Ignition Research if your technical project needs several laboratories, consultants, university researchers or specialist providers and the challenge is keeping those work packages connected to one research question and decision pathway. 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.
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.
