Quick answer: Sometimes. A supplier specification, test report or engineering assurance may provide enough accessible knowledge for a competent professional to know or determine the outcome in advance, in which case the remaining work is more likely to involve implementation or established engineering. But where the supplier evidence does not cover the material combination, operating environment, system interaction or performance condition that matters to the project, a genuine technical uncertainty may remain if a competent professional still could not determine the outcome without experimental work.
Supplier knowledge is part of the knowledge you already have
Technical teams sometimes describe a problem as uncertain because nobody inside the company knows the answer.
That is not the relevant boundary.
Current Australian Government guidance asks whether a competent professional could know or determine the outcome in advance using knowledge, information or experience that is publicly available or reasonably accessible anywhere in the world when the activity begins.
Supplier knowledge can form part of that evidence base.
A product datasheet may define an operating envelope.
An application note may explain known limitations.
A supplier engineer may have experience with the same material, protocol or duty cycle.
A formal test report may show that the component has already achieved the required performance under conditions materially equivalent to yours.
If that evidence answers the technical question, a company cannot create uncertainty simply because it has not yet implemented the solution itself.
The work may still be difficult.
It may require careful commissioning, integration, configuration or engineering judgement.
But difficulty is not the same thing as an outcome that could not be determined in advance.
The legislative test for core R&D activities is narrower. Section 355-25 of the Income Tax Assessment Act 1997 requires an experimental activity whose outcome cannot be known or determined in advance on the basis of current knowledge, information or experience, but can only 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.
The practical question is therefore not whether the supplier is confident.
It is whether the evidence behind that confidence actually covers the outcome your project needs.
Read the envelope behind the assurance
Supplier statements often become less definitive when the operating conditions are examined closely.
Consider an industrial component rated for a particular application.
The supplier may have extensive evidence showing that the component performs reliably under its validated conditions.
Your project may differ in one important respect.
The feed material may have greater variability.
The temperature may cycle differently.
The equipment may interact with another control system.
The duty cycle may be more aggressive.
The component may be installed in a geometry the supplier has not characterised.
The question is no longer simply:
“Does this product work?”
It becomes:
“Does the evidence supporting this product remain predictive under the conditions that matter here?”
Before treating a supplier assurance as the answer, the technical team should examine one connected set of questions:
• What configuration, material, load, environment or data was the supplier evidence based on?
• Which conditions in our project are materially different?
• Has the supplier actually tested those differences, or are they being inferred from experience?
• Does the published evidence measure the property our decision depends on?
• Is the supplier describing an established performance limit, or offering an engineering judgement outside its validated envelope?
• Would another competent professional, given the same information, reasonably be able to determine the outcome without running the proposed experiment?
The distinction can be subtle.
A supplier saying, “We have installed this component many times” may be highly relevant if those installations genuinely match the project conditions.
The same statement may be much less informative where every previous installation operated within a different range.
A warranty is also not the same thing as experimental evidence.
It defines a commercial commitment. It does not necessarily establish how the system will behave under every technically relevant condition inside or outside that commitment.
The useful task is to identify what the evidence actually supports.
Use supplier gaps to define what remains unresolved
Finding that supplier evidence is incomplete does not automatically mean the next step is R&D.
It may simply mean more information is needed.
The supplier may hold unpublished test data.
A standard method may already cover the condition.
Another manufacturer may have characterised the same interaction.
A competent specialist may be able to resolve the question through established engineering analysis.
Research becomes more relevant only where those routes still do not make the technical outcome determinable in advance and the answer requires hypothesis-driven experimentation.
At that point, the supplier evidence should help narrow the experiment rather than being discarded.
Suppose a pump supplier has established performance across a defined range of fluid viscosities, but the company's process stream contains a variable suspended-solid fraction that has not been characterised with that pump geometry.
The supplier evidence may already establish the hydraulic behaviour under the known conditions.
The remaining research question should not be:
“Will the pump work?”
It might instead be:
“Does increasing suspended-solid concentration change the flow instability mechanism enough to prevent the required operating range from being maintained?”
That is a more useful question because the supplier's existing knowledge has removed part of the uncertainty.
The experiment can then focus on the unresolved difference.
This is also where project teams should resist the temptation to convert every supplier limitation into a research opportunity.
If the supplier says that the component is unsuitable for the condition, and established technical knowledge explains why, the answer may already be known.
If the supplier provides a standard alternative that addresses the problem, implementing that alternative is not made experimental simply because the preferred product failed.
The role of the evidence review is to reduce unnecessary experimentation, not create more of it.
Record the point where known evidence stops
If the project does proceed into experimental work, the transition from supplier knowledge to project-specific uncertainty should be visible in the record.
Australian Government record-keeping guidance states that records should be created at the time the activity is conducted and should include background research used to establish that an outcome could not be known in advance. Examples of records that may demonstrate the systematic progression include experimental plans, records of trial runs and test reports showing results and evaluation.
For a supplier-dependent project, that record might capture the relevant specification or test report, the operating conditions it covers, correspondence or technical advice received from the supplier, the project condition that falls outside that evidence and the reason a competent professional could not resolve the remaining question from established knowledge.
It should also preserve changes.
If the supplier later provides new information that resolves the issue, the need for further experimental work may disappear from that point onward. That later information does not, by itself, change what knowledge was reasonably accessible when the earlier activity began.
If the first trial shows that the assumed mismatch was irrelevant, the project may move back towards implementation.
If the test exposes a different mechanism, the hypothesis may need to change.
That is not a documentation inconvenience.
It is the research pathway becoming more precise as evidence accumulates.
For founders and CFOs, this distinction also provides a useful investment gate.
Before approving another test campaign, ask whether the business is paying to discover something genuinely unresolved or simply paying to confirm something that established supplier or industry knowledge already makes predictable.
For CTOs and engineering leads, the same question can be framed technically:
Where, exactly, does the supplier's validated knowledge stop being predictive for our conditions?
If the team can define that boundary, the next research step can be proportionate.
If it cannot, the next useful activity may be evidence review rather than another experiment.
Conclusion
Supplier specifications, test reports and technical advice can materially reduce uncertainty, but their value depends on the conditions and assumptions that support them.
A useful evidence review identifies what a competent professional could already determine from accessible supplier and industry knowledge, where that knowledge stops being predictive, and whether the remaining gap genuinely requires experimental work.
The objective is not to find a reason to experiment. It is to define precisely what — if anything — still needs to be discovered.
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
Federal Register of Legislation — Income Tax Assessment Act 1997, Division 355
Australian Government — Get help from a research service provider
Talk to Ignition Research if your project depends on a supplier's specification, engineering assurance or validated operating envelope but your actual conditions sit outside what that evidence clearly covers. 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.
