Managing R&D Evidence in Synnch

1. Why Evidence Matters

The R&D Tax Incentive is a self-assessment program. Registration does not confirm eligibility. If your claim is reviewed, you must be able to demonstrate:

What activities were conducted
That technical uncertainty existed
That experimentation occurred
That new knowledge was generated
That expenditure relates to those activities

The R&D Tax Incentive Guide to Interpretation emphasises the importance of records maintained during the activity, not reconstructed later.

Synnch is designed to make this documentation structured, traceable and defensible.

2. The Evidence Module: Your Central Repository

The Evidence module acts as the depository for all R&D documentation uploaded into Synnch.

This includes:

Documents uploaded directly into the Evidence module
Evidence attached to timesheet entries
Supporting attachments linked to projects

Everything ultimately lives within the Evidence module, even if uploaded from different parts of the platform.

This ensures that:

Evidence is centralised
Documents are linked to projects and activities
Nothing is siloed in personal folders
Your documentation trail remains intact

3. Two Types of Evidence in Synnch

Synnch distinguishes between two practical layers of evidence.

Overarching Project-Level Evidence

Uploaded directly into the Evidence module.

When uploading, you must select an existing Project.

This ensures the document is contextually linked to the correct R&D objective.

These documents are typically broader in nature, such as:

Project descriptions
Technical specifications
Experimental plans
Architecture documents
Design of experiment documentation
Board approvals
Literature reviews
Feasibility studies

After upload, the document is analysed using Synnch’s AI engine.

The AI reads:

Project descriptions
Core and Supporting activity descriptions
Associated framework details

A relevance score is then generated, indicating how strongly the document aligns with defined R&D activities.

This helps you:

Identify gaps in substantiation
Detect irrelevant documentation
Strengthen alignment between activity descriptions and evidence

This scoring does not determine eligibility. It supports internal review and quality control.

Task-Level Evidence (Platform Attachments)

Evidence can also be attached directly to a timesheet entry.

When logging R&D time, a team member selects:

Project
Core or Supporting activity

Evidence attached at this level typically relates to a specific task performed on that day.

Examples include:

Test outputs
Code snippets
Lab results
Screenshots
Meeting notes
Experiment logs

These attachments are automatically stored in the Evidence module under a dedicated folder called:

Platform Attachments

They are:

Linked to the relevant project
Linked to the activity via the timesheet
Collected centrally in the Evidence module

These documents are not automatically evaluated or assigned a relevance score.

If needed, manual evaluation can be performed later.

4. How the Structure Strengthens Compliance

The structured flow in Synnch creates traceability:

Project

→ Core / Supporting Activity

→ Time Logged

→ Evidence Attached

→ Expenditure Linked

This layered structure ensures that:

Evidence is tied to defined activities
Time allocations are supported by documentation
Expenditure can be substantiated
Documentation is not stored generically

Instead of folders like “R&D 2026,” Synnch connects documentation to eligibility logic.

5. What Makes Strong R&D Evidence

Strong evidence:

Demonstrates technical uncertainty
Shows experimentation
Records observations and conclusions
Links clearly to defined activities
Is created during the R&D process

It may include:

Experimental protocols
Test data and analysis
Iteration records
Technical discussions
Prototype images
Design documentation
Contracts and invoices

The goal is not volume, it is clarity and traceability.

6. Contemporaneous Documentation

Records created during experimentation carry significantly greater evidentiary weight than retrospective summaries.

Synnch supports contemporaneous documentation through:

Integrated timesheets
Structured evidence uploads
AI-supported alignment review
Centralised storage

The earlier documentation is captured, the stronger your position.

7. Best Practice Approach

To maintain defensible documentation:

Upload overarching project-level documents early
Attach task-specific evidence to timesheet entries
Keep activity descriptions technically precise
Periodically review AI relevance scores
Ensure expenditure aligns with documented activities

When structured properly, documentation becomes part of your development workflow, not an afterthought.