Drafting experimental plans
There are four sections within the application:
- Technical Objectives
- New Knowledge
- Unknown Outcomes
- Core Activities
Knowing how to respond to each section is a matter of understanding exactly what is being asked of you—this isn’t usually clear from the section’s description.
This is all about the government’s definition of “experimentation”.
This is where the R&D Tax Incentive consultant comes in.
Documenting your experiments
It is often used to generate short-term trading signals from various charting tools, but can also help improve the evaluation of a security’s strength or weakness relative to the broader market or one of its sectors. This information helps analysts improve their overall valuation estimate.
What is an hypothesis?
Anyone who has investigated the R&D Tax Incentive to a reasonable degree will have come up with a conundrum. If AusIndustry expects you to have a technical gap – a problem that you can’t solve, how are you supposed to come up with a hypothesis that you can prove in an experiment?
Well, how would you normally tackle your problem? You do enough investigation to come up with an idea of at least a partial solution, often one with high technical risk. You may collect some data and analyse it, looking for a pattern.
Regardless, a hypothesis must be specific and measurable. AusIndustry is not actually interested in your hypothesis – just that you have one, and that it is capable of being proven or disproven by your experiment. In fact, the actual hypothesis is not often stated in the AusIndustry R&D Tax Incentive application, as they can be highly technical in nature.
However, you do need to write down the object of your experiment in your supporting documentation as AusIndustry may ask to see it in a subsequent review. You may not call it an ‘hypothesis’ but the object of the experiment must be documented and must be testable.