Documentation

What SR&ED Teams Can Learn From the Orange Wall

Strong SR&ED claims are built like the Dutch Orange Wall — from rhythm and repetition, not year-end scramble. Here's the practical system for Canadian R&D teams: ongoing documentation and honest year-end reconstruction.

Marcus Webb · Editorial Lead 2026-06-15 7 min read

Turn this into a claim-ready next step. Check eligibility, estimate the possible credit, or preview what your CPA would review.

Check eligibility — free → Estimate refund View sample claim

It looks spontaneous. It is actually rhythm.

If you have not seen the Dutch Orange Wall, watch it. A stadium of football fans in matching orange — shirts, hats, scarves, face paint — create a visual effect that looks like an ocean wave. It happens at every match. It looks like a spontaneous moment of collective joy. It is not. It is the result of an established system: everyone knows the cue, the timing, the signal, and the role. It has been rehearsed and practised. The crowd has a rhythm.

SR&ED claims work the same way. The claims that get funded, and that survive audit, are not the ones assembled in a frantic year-end scramble. They are the ones built by teams that captured technical uncertainty, recorded experiments, and preserved context as it happened. The scramble is the penalty for not having a rhythm. The rhythm is the system that makes the claim almost effortless.

This article is a practical guide to building that rhythm — whether your team is in biotech, software, engineering, or any Canadian company doing work that advances the state of knowledge. The Orange Wall is the analogy. The checklist at the end is the system.

The five beats of the rhythm

A strong SR&ED claim has five repeating components. Contemporaneous capture — recording each element as the work happens — produces the strongest evidence. When that was not possible, each component can also be assembled defensibly from existing records. They are: technical uncertainty, experiments and iterations, evidence tied to decisions, researcher and engineer context, and time and cost support.

1. Name the technical uncertainty as it appears

The first beat is the most important, and the most commonly skipped. When an engineer, researcher, or scientist hits a problem that existing knowledge cannot solve, that moment is a technical uncertainty. The question that needs to be captured is: what did you know, what was missing, and what did you have to figure out?

Software example

A team building a real-time data pipeline discovers that standard stream processing frameworks cannot handle their specific latency requirements at the required throughput. The uncertainty is not 'we need to build a fast pipeline.' It is 'whether any existing stream processing approach can achieve sub-50ms latency at our specific data volume and distribution, and if not, what architecture can.'

Biotech example

A research team is developing a novel CRISPR guide RNA design for a rare disease target. Published approaches do not cover the specific genomic context. The uncertainty is not 'we need to design a guide RNA.' It is 'whether existing CRISPR design rules produce viable guides for this specific target sequence, and if not, what modifications to the design parameters are required.'

2. Record experiments and iterations as they happen

The second beat is the evidence of systematic investigation. The CRA does not evaluate whether you succeeded. They evaluate whether you experimented. The record needs to show what you tried, what you expected, what you observed, and what you concluded — including dead ends.

For software: experiment logs, benchmark results, architecture decision records, and commit messages that explain the reasoning, not just the outcome.
For biotech: lab notebook entries, assay results, protocol modifications, and failed experiment records with the rationale for each attempt.
For engineering: test reports, design iteration documents, simulation results, and prototype evaluations with rejection criteria.

Failed experiments are evidence

A systematic investigation that demonstrates an approach does not work is a valid SR&ED outcome. The finding that a path is not viable for your specific constraints is new knowledge. Do not hide the dead ends. Document them.

3. Tie evidence to specific decisions

The third beat is the connection between evidence and the decision it informed. Evidence that sits in a folder without context is weak. Evidence that shows 'we tried A, got result X, so we chose B' is strong. The decision trail is the narrative thread that runs through the claim.

Decision trail example

A biotech team tests three cell culture conditions. Condition 1 produces viable cells but low yield. Condition 2 produces high yield but unacceptable contamination. Condition 3, a modified version of Condition 1 with an added filtration step, meets both targets. The decision record should show: the initial hypothesis for each condition, the test protocol, the results, and the rationale for selecting Condition 3. The evidence for the claim is the entire trail — not just the final protocol.

4. Capture researcher and engineer context

The fourth beat is the human context. Who did the work? What was their expertise? What specific knowledge did they bring to the problem? CRA reviewers evaluate whether the people doing the work had the background to conduct a systematic investigation. The context does not need to be formal CVs. It needs to show that the team had the relevant expertise to identify and address the technical uncertainty.

For software: team composition, relevant domain experience, and specific technical backgrounds of the engineers who led the investigation.
For biotech: principal investigator qualifications, post-doc expertise, and the specific research background relevant to the target or method.
For engineering: design team credentials, relevant project experience, and the specific technical competencies that informed the investigation.

5. Connect the work to time and cost support

The fifth beat is the financial connection. The time spent on the investigation, the wages of the people doing it, the materials consumed, and the overhead attributable to the work. This is the cost side of the claim. The rhythm requires that time and cost are tracked contemporaneously, not estimated from memory at year-end.

Time tracking that works

A software company uses a simple project code in their time tracking system for qualifying investigation work. The code is applied when an engineer is working on a technical uncertainty that meets the SR&ED test. At year-end, the total hours under that code are the basis for the wage claim. The accuracy is high because the tracking was done at the time. The alternative — asking engineers to estimate their time allocation nine months later — is inaccurate and invites scrutiny.

The honest year-end reconstruction

Not every team has a rhythm in place. Many Canadian companies discover SR&ED only after the fiscal year has closed. The work is real. The eligibility is genuine. But the evidence was not captured. The question is: what can be done honestly and defensibly?

Year-end reconstruction is possible, but it requires a different standard. The evidence must be assembled from whatever contemporaneous records exist — commit logs, design documents, meeting notes, lab notebooks, email threads, calendar entries, and project management tools. The claim is built from the traces that the work left behind, not from memory.

Start with the technical outputs: the code, the designs, the prototypes, the assay results. These are the physical evidence that the work happened.
Work backwards from the outputs to the uncertainty: what problem did each output address? What was the gap in knowledge that required the investigation?
Use the team's calendar and project management data to reconstruct the timeline: who worked on what, when, and for how long.
Interview the team members who did the work, but record their responses as recollections, not as primary evidence. The primary evidence is the contemporaneous record.
Be honest about gaps. A claim that acknowledges missing records and explains why is more credible than one that pretends every detail was documented.

Reconstruction is not invention. The CRA distinguishes between assembling evidence from existing records and creating evidence that did not exist. The former is legitimate. The latter is fraud. The line is clear: if the record did not exist at the time the work happened, it cannot be created afterward to support the claim.

The 80% rule for contractors

If your team used contractors for the qualifying work, remember the CRA's 80% rule: contractor fees are capped at 80% of the total qualifying wage claim. If you spent $100,000 on internal wages and $200,000 on contractors, the contractor portion is capped at $80,000. The claim totals $180,000, not $300,000. Plan your time allocation accordingly.

The practical checklist

This checklist is designed to be used weekly or at the end of each sprint. It takes five minutes per project and builds the rhythm that makes year-end claims straightforward.

Did any new technical uncertainty arise this week that existing knowledge could not resolve? If yes, name it in one sentence.
What experiments, tests, or investigations were conducted to address that uncertainty? Record what was tried, what was expected, and what was observed.
What evidence was generated that shows the reasoning process? Save the documents, logs, or records that demonstrate the investigation.
What decision was made based on the evidence? Connect the evidence to the specific choice it informed.
Who did the work? Note the team members and their relevant expertise.
How much time was spent on the investigation? Record the hours, days, or percentage of effort.
What materials, compute, or other resources were consumed? Track the costs associated with the investigation.
Did any experiments fail? Document the failure and the rationale for abandoning the approach.
Are the records saved in a shared location that the team can access at year-end? Confirm the storage and naming convention.
Is there a recurring reminder to repeat this checklist? Set the rhythm.

The checklist is the Orange Wall. Each beat is a fan in the crowd. When the signal comes, each person knows their role. The wave happens. The claim is built.

What the rhythm actually costs

The rhythm sounds like extra work. It is not. It is a small investment of time that eliminates the large investment of panic. The five-minute weekly checklist replaces the week-long year-end scramble. The contemporaneous record replaces the reconstruction. The defensible claim replaces the risky one.

For a Canadian company with qualifying work, the financial return is substantial. A CCPC with $150,000 in qualifying wages gets approximately $52,500 in federal refundable credits, plus provincial credits. A company with $500,000 in qualifying wages gets approximately $175,000 in federal credits. The rhythm that captures the evidence is the system that captures the money.

The alternative is the consultant model: hand over your project files at year-end, pay a percentage of the claim, and hope the reconstruction is defensible. The percentage fee on a $500,000 claim is typically $25,000 to $75,000. The rhythm eliminates that fee. The tools that support the rhythm — simple time tracking, shared documentation, and systematic note-taking — cost a fraction of the consultant percentage.

SREDY.IO is built for this. The platform supports both ongoing documentation as the work happens and defensible year-end reconstruction from existing records. Check your eligibility free, explore a full sample claim package, or estimate your potential refund — all at a fixed flat fee, with no percentage taken from your claim.

This article is for general information only. SR&ED eligibility depends on the specific facts of each project and is determined by the CRA. All claims should be reviewed by a qualified Canadian CPA before filing.

documentation rhythm evidence biotech software year-end team workflow