What counts as a systematic progression of work for R&D

Introduction

When a business sets out to claim the R&D Tax Incentive, one of the hardest concepts to get right is demonstrating that the work followed a systematic progression of work. AusIndustry and the ATO do not just look for a set of activities thrown at a technical problem. They expect to see a structured, scientific approach: a clear hypothesis, planned experiments, careful observations, rigorous evaluation, and a conclusion that feeds into the next cycle. This is the heartbeat of eligible R&D. Without it, even genuinely innovative work can fail a review.

This guide breaks down the five stages, step by step, and shows how to evidence each one so your claim stands up. It is general information only. It is not tax, financial, or legal advice. Every business is different, and you should discuss your specific circumstances with a registered tax agent before relying on any material here. The rules can change from year to year, so always verify current requirements with the ATO and AusIndustry.

GrantsMAX does not lodge claims or give advice. It reads your accounting data through secure, read-only connectors and prepares an evidence-backed application pack that your registered tax agent then reviews, refines, and lodges. This article draws on official guidance from business.gov.au, the ATO, and AusIndustry, and it reflects the division of responsibility that the law requires.

Prerequisites: What to have in place before you start documenting

Before you map out a systematic progression, you need a few foundations.

A clear understanding of eligible R&D activities

The R&D Tax Incentive targets activities that generate new knowledge or create new or improved materials, products, devices, processes, or services. The two categories are core R&D activities and supporting R&D activities. Core activities must be experimental activities whose outcome cannot be known or determined in advance on the basis of current knowledge, information, or experience, and must be conducted for the purpose of generating new knowledge. Supporting activities are those that have a direct, close, and relatively immediate relationship to the core activities.

Read the official definitions on business.gov.au and the ATO’s core and supporting activities page before you proceed. If your activities do not meet these tests, no amount of documentation will turn them into eligible R&D.

A connected accounting and records system

To build an audit-ready evidence trail, you need a system that captures the financial and operational data behind your experiments. The ATO expects contemporaneous records. GrantsMAX connects to Xero, MYOB, QuickBooks, Microsoft 365, and Google Workspace via read-only connectors, so it can pull timesheets, invoices, and project codes into the application pack without altering your books.

A registered tax agent who will review and lodge

Only a registered tax agent can lodge the R&D Tax Incentive schedule with the ATO. The agent must be comfortable with your documentation. GrantsMAX’s Accountant Review & Lodge Workflow hands your agent a completed pack inside a shared workspace, but the agent remains in control and the business owns the claim. Engage your agent early so they can advise on what records they will need.

An understanding of the scientific method in business

The systematic progression of work is essentially the scientific method applied to a commercial setting. You will need to articulate a hypothesis, design experiments, collect data, and draw conclusions. This guide will walk you through each stage.

Pro tip: Before you write anything, list the technical uncertainties your project faces. A systematic progression starts with a clear, well-defined problem. If you cannot describe the uncertainty in a sentence or two, you may not be ready.

Step 1: Formulate a clear hypothesis

Every R&D project must begin with a statement of what you are trying to prove or disprove. The hypothesis is more than a business goal. It is a technical proposition that can be tested.

What a hypothesis looks like in business R&D

AusIndustry’s guide to the R&D Tax Incentive explains that your activities must be conducted in accordance with a systematic plan. The plan starts with a hypothesis. For example:

• Software: “We believe we can reduce the false-positive rate of our fraud detection model below 0.1 percent by applying a novel ensemble of graph neural networks and gradient boosting. The current state of the art cannot achieve this on our data distribution.”
• Manufacturing: “We hypothesise that a new extrusion die geometry, combined with a controlled cooling protocol, will reduce material warpage in our composite panel to less than 2 millimetres over a 2-metre length, something not achievable with standard die designs.”
• Biotech: “We aim to test whether our modified CRISPR delivery vector can increase editing efficiency in primary hepatocytes to over 80 percent without observable cytotoxicity, overcoming the current limitation of approximately 40 percent with existing vectors.”

Each of these is specific, measurable, and grounded in a technical uncertainty that cannot be resolved by routine work. It is not “We want to build a better product.”

Pro tip: Tie the hypothesis to a specific technical uncertainty. The uncertainty must come from a gap in current knowledge, not from your team’s lack of expertise. Ask: Could a competent professional in the field determine the outcome without running the experiment? If yes, the work is likely not core R&D.

Warning: Avoid marketing or business-as-usual statements. “We will increase market share” or “We will redesign the user interface” are not hypotheses for R&D eligibility. The ATO and AusIndustry see through these quickly.

How to document the hypothesis

Write it down in a dated document, lab notebook, or project management tool at the time you start the project. Link the hypothesis to the underlying scientific or technological principles. Later, when GrantsMAX drafts your AI Application Pack, it will pull this narrative into the activity description, but you need to have recorded it contemporaneously.

Step 2: Design and run experiments to test the hypothesis

Once you have a hypothesis, the next step is to design a series of experiments that will put it to the test. A systematic progression requires that you do not just try random things. You plan.

What counts as an experiment

An experiment in the R&D context is an activity that generates new knowledge by manipulating variables under controlled conditions and measuring the outcome. It is not a prototype build for demonstration, a trial run for production, or a market test. The experiment must directly address the hypothesis.

For the manufacturing example above, the team would design a protocol that varies die geometry and cooling rates, measure the resulting warpage, and compare it against a control. In software, the team would implement the fraud detection ensemble, run it on a reserved test dataset, and record false-positive rates and other metrics. The key is that you are generating data to answer a question, not just trying things until something works.

Pro tip: Document your methodology before you start. Describe what you will test, how you will test it, what data you will collect, and what success looks like. This pre-experiment plan is strong evidence of a systematic approach.

Warning: Do not jump to a solution without testing. If you build a full working system and then reverse-engineer some experiments, the review may treat the whole project as production development. The experiments must drive the design.

Evidencing the experimental work

The ATO’s record-keeping requirements mandate that you keep records that show the activities were performed and the relationship to the core R&D. Good evidence for this step includes:

• Experimental protocols and design documents.
• Dated lab notes, logbooks, or Jira tickets describing what was tested and why.
• Photographs or videos of apparatus and test setups.
• Records of failed experiments, unexpected results, and modifications to the plan.
• Timesheets and asset usage logs that allocate time and equipment to the R&D activity.

GrantsMAX’s Audit-Ready Evidence Trail feature indexes your emails, invoices, and timesheets so that every cost line in the application is traceable back to a source document. This mapping helps your accountant stand behind the claim.

Step 3: Make detailed observations and capture data

As you run the experiments, the observations you make become the raw material of your scientific record. A systematic progression is not just about doing the work, it is about carefully recording what happened.

Types of evidence to collect

Observations can be quantitative (measurements, logs, performance numbers) or qualitative (colour changes, material behaviour, error patterns). Whatever the form, the data must be captured at the time and in a way that can be reconstructed later. Examples include:

• Instrument readings, sensor logs, and test outputs.
• Screenshots of software performance dashboards.
• Annotations on design drawings showing failures or modifications.
• Written notes from team debriefs after each experiment.

Pro tip: Use contemporaneous records. Date everything. If you write a summary a week later, note that it is a retrospective and attach the raw data. The ATO and AusIndustry may test whether records were created at the time of the activity.

Warning: Reconstructed records will not satisfy a review. A spreadsheet compiled months after the fact with no supporting source data is a red flag. If you do not have the raw data, the activity may not be substantiated.

How GrantsMAX surfaces the right data

GrantsMAX connects to your accounting and productivity tools to pull in employee timesheets, supplier invoices, and project codes. It can match these to the R&D activities you define, giving your accountant a head start on the evidence pack. However, the quality of the output depends on the records you kept at the time. The AI does not invent data.

Step 4: Evaluate the results against the hypothesis

After an experiment, you must sit down and interpret what the data means. This is the evaluation stage. It is where you prove that the work followed a logical progression, not a haphazard one.

How to draw meaningful conclusions

Evaluation is not just a statement that the experiment succeeded or failed. It should discuss:

• Whether the results support or refute the original hypothesis.
• The statistical significance of the findings, where applicable.
• Any surprising outcomes or anomalies.
• What the results imply for the next iteration.

For the biotech example, the team might find that the editing efficiency reached 75 percent in the first trial, close to the 80 percent target, but observed cytotoxicity in some batches. The evaluation would detail the cytotoxicity levels, possible causes, and a plan to adjust the delivery protocol in the next experiment.

Pro tip: Document both successes and failures. A failed experiment that teaches you something new is still R&D. In fact, a series of failures that systematically eliminate approaches can be strong evidence of a progression. Do not hide dead ends.

Warning: Do not cherry-pick data. An evaluation that ignores inconvenient results may be seen as an attempt to fabricate a narrative. Your contemporaneous records should show a complete, warts-and-all picture.

Official expectations

Industry Innovation and Science Australia, the board that advises on the R&D Tax Incentive, often comments on the need for genuine experimentation. AusIndustry’s case studies include examples where evaluation led to a change in direction. They reward thoroughness.

Step 5: Conclude and document the next cycle

A systematic progression does not end with a single experiment. The conclusion should set up the next hypothesis. This cycle is what transforms a set of discrete activities into a true research program.

Closing the loop

Write a concise conclusion that states:

• Whether the hypothesis was supported or rejected.
• What new knowledge was gained.
• What new technical uncertainties emerged.
• The next hypothesis to be tested and the rationale.

For the software example, if the ensemble reduced false positives to 0.12 percent, still above the target, the conclusion might propose testing a different feature engineering technique in the next sprint. The link between the results and the next step must be explicit.

Pro tip: Map each conclusion to a future experiment. This creates a chain of experiments that a reviewer can follow. A clear narrative of “we tried A, we learned B, so we tested C” demonstrates systematic progression better than any single document.

Warning: A single experiment is rarely enough to satisfy the progression requirement, unless the outcome truly resolves all uncertainties. Most R&D involves many cycles. If your claim covers only one or two experiments, be prepared to show why that was sufficient.

Documenting the cycle for the ATO

Your overall project narrative should tell a story that incorporates all five steps. When GrantsMAX drafts your application pack, it will structure the narrative to highlight the progression. But the content must come from your records. The R&D Tax Incentive plain-English guide explains how the ATO expects these cycles to be reported.

How GrantsMAX helps build the evidence trail

This five-step process generates a lot of documentation. GrantsMAX does not replace your record-keeping, but it organises what you already have and prepares a pack that makes your accountant’s review efficient.

First, the platform assesses your business against program eligibility rules using your Xero, MYOB, or QuickBooks data, flagging areas a reviewer would scrutinise. It then scans for relevant grants and R&D incentives, matching them to your activity profiles. Once you confirm the R&D activities, the AI Application Pack Drafting engine pulls your accounting entries and builds the cost structure while weaving in the activity narratives.

Throughout, GrantsMAX maintains an audit-ready evidence trail that ties each activity and cost line to its source, whether it is a timesheet, an invoice, or an email. The pack is then handed to your registered tax agent through the Accountant Review & Lodge Workflow. The agent reviews, refines, and lodges, and you, the business, own the final claim.

The entire process is built on a foundation of governance and trust. Connections to your systems are read-only. GrantsMAX never writes back, never changes your books, and never lodges a claim itself. It prepares the evidence so your accountant can do their job with confidence.

For technology companies, the drafting engine understands software workflows and can incorporate your Jira tickets and Git commits. For manufacturers, it pulls in shop-floor data and materials invoices. The platform’s industry-specific intelligence is detailed on pages for technology companies and manufacturers, and the same rigour applies to R&D-active startups.

When the next financial year arrives, GrantsMAX can refresh the claim through the annual refresh channel. This ensures each period’s progression is recorded and linked to the previous year’s conclusions, reinforcing the systematic cycle.

Summary and key takeaways

A systematic progression of work is not a paperwork exercise. It is the actual scientific method you follow in your R&D. The ATO and AusIndustry want to see that you:

1. Started with a clear hypothesis framed around a genuine technical uncertainty.
2. Designed and ran experiments that tested that hypothesis in a controlled way.
3. Captured observations and data at the time the work was done.
4. Evaluated the results honestly and drew meaningful conclusions.
5. Used those conclusions to inform the next cycle of hypothesis and experiment.

Every step must be documented with contemporaneous records, from lab notes and test logs to timesheets and invoices. An auditor’s question is rarely “Did you do the work?” It is “Can you prove you did the work in a structured way?”

GrantsMAX exists to turn your business data into that proof. It does not promise any outcome, nor does it guarantee a claim will be approved. It prepares an evidence-backed pack that your registered tax agent can review and lodge, with you as the claim owner.

If you are ready to build a stronger, more defensible R&D claim, we invite you to join the GrantsMAX waitlist at grantsmax.com. Read the concepts behind the platform to understand how it fits into your workflow, and discuss with your accountant whether it is right for you.

Remember: this article is general information only. Always confirm the current rules with the ATO and AusIndustry, and consult a registered tax agent before taking any step that affects your tax obligations.