It Worked in the Lab — What Does the Field Trial Actually Need to Prove?

The 2026–27 Federal Budget announced proposed R&DTI reforms applying from 1 July 2028. Until those changes take effect, the R&DTI continues to operate under the current rules.

A Field Trial Should Answer a New Question

Moving from a controlled environment into the field changes more than location.

Laboratory experiments deliberately reduce variation. Temperature may be controlled. Inputs may be selected. Sensors may be calibrated immediately before a test. Operators may follow one procedure. Equipment may run for a short, defined period.

The field removes many of those protections.

Inputs vary. Equipment ages. Weather changes. Operators intervene. Communications drop out. Loads fluctuate. Other systems interact with the experimental system.

That does not mean every field trial is R&D.

If established engineering knowledge already allows the expected field behaviour to be determined, implementation and commissioning may be the appropriate next step. Moving from laboratory scale to field or production scale does not, by itself, create a core R&D activity. The relevant question remains whether the specific outcome can be known or determined in advance from current knowledge, information or experience, or whether further experimentation is required to determine it.

The useful research question is therefore not:

It is something narrower:

That is what gives the field experiment a purpose.

Define the Transfer Risk Before Collecting Data

Consider a control system that performs reliably on a laboratory rig.

A team preparing a field test could identify several reasons why that result may not transfer:

Those are different potential sources of transfer uncertainty. Each could lead to a different hypothesis and experimental design.

Running the system in the field and recording everything may produce a large dataset, but it does not necessarily distinguish between those explanations.

A stronger design identifies the suspected transfer mechanism before the trial.

For example:

The experiment can then specify:

Government guidance describes core experimental work as a systematic progression through hypothesis, experiment, observation, evaluation and logical conclusions. Records should explain how the experiment was conducted or planned and may, for example, identify the parameters that were varied, held constant, observed or measured.

The discipline matters even where the project is not ultimately treated as an R&DTI activity. It helps distinguish a designed experiment from commissioning activity that happens to generate technical data.

Record the Operating Envelope, Not Just the Headline Result

Suppose the system meets its target on most days but fails during high temperature, unusual loading or degraded communications.

Calling the trial either a “success” or “failure” loses useful information.

The result may instead define an operating envelope.

That envelope describes the conditions under which the evidence currently supports the technical conclusion — and the conditions outside which the result remains uncertain.

A field record should therefore connect each important observation to its context.

Useful records may include:

Current R&DTI record-keeping guidance identifies experimental plans, trial records, test reports and evaluations as examples of evidence supporting a systematic progression of work.

The purpose is not to make the trial look more successful.

It is to make clear what the result actually supports.

Know When the Research Question Has Been Answered

A field project can continue long after the original uncertainty has been resolved.

Once the team knows the relevant operating limits and can use established engineering approaches to implement within them, later optimisation, monitoring and routine performance tuning may fall outside the original experimental investigation. Any later activity should be assessed on its own facts rather than assumed to remain R&D simply because it occurs within the same project.

A useful decision gate is:

If the team can answer that precisely, another experimental cycle may be technically justified. That does not, by itself, establish R&DTI eligibility; the activity must still satisfy the applicable requirements.

If the remaining work is applying what has already been learned, implementation may be the more accurate description.

The objective is not to keep a project labelled as research for as long as possible.

It is to know when research has produced enough evidence for engineering to take over.

Conclusion

A successful laboratory result answers only the question tested under the conditions in which it was produced.

A useful field experiment identifies what remains uncertain when those conditions change, defines the operating variables that matter, and records enough context to explain why the field result agrees — or does not agree — with the laboratory result.

When that uncertainty has been resolved and established engineering knowledge is sufficient to guide implementation, the research question may have reached its natural boundary even though the wider project continues.

Sources & Further Reading

• Australian Government — Conducting core R&D activities for the R&D Tax Incentive
  business.gov.au — Conducting core R&D activities

• Australian Government — Record keeping for the R&D Tax Incentive
  business.gov.au — R&DTI record keeping

• business.gov.au — Conducting supporting R&D activities for the R&D Tax Incentive

• business.gov.au — Manufacturing sector guide for the R&D Tax Incentive