Skip to main content
Lesson 02 · Technical writers and reviewers

Writing the technical report

Lines 242, 244 and 246 answered the way a research and technology advisor reads them.
  • 9 min read
  • With video
  • 6 sections
In this lesson
01

Line 242: the uncertainty

Line 242 answers the why. State the objective of the new or improved product or process with measurable targets, describe the existing knowledge and the due diligence you did, explain why standard practice could not reach the objective, and then state each uncertainty in one or two sentences, as missing knowledge.

Frame the uncertainty as missing knowledge of how things interact or behave, not as an optimization exercise. Keep the work done in the year out of 242.

Up to 350 words, or 50 lines. Plain paragraphs, no bullets or symbols.

  • Objective with metrics
  • Existing knowledge and due diligence
  • Why standard practice falls short
  • Each uncertainty in one or two sentences
02

Phrases that do not establish an uncertainty

Some reasons are not uncertainties. Playing around with variables, not knowing how to do something, the work being more complex, never having done it before, or conditions not being ideal. Neither is business risk. If the field already knows the answer, it is not SR&ED.

  • Playing around with variables
  • Not knowing how to do something
  • More complex, or never done before
  • Conditions not ideal, or business risk
03

Line 244: the work, as cycles

Line 244 answers the how. Open with where the year started, then write each cycle the same way. To address the uncertainty, we tested a hypothesis, by an experiment, and found a result, from which we concluded an insight that led to the next step.

A good hypothesis is specific and reasoned: by doing X, then Y, so that Z. A general aim to build something that works is not a hypothesis.

Say what contractors did, why significant materials were needed, and explain anything that may draw attention: a high share of specified employees, or growth of 20% or more over the prior year. Up to 700 words, or 100 lines.

  • To address the uncertainty
  • we tested a hypothesis
  • by an experiment
  • and found a result, from which we concluded an insight
04

Line 246: the advancement

Line 246 states two things. First, the new or improved product or process you achieved or attempted, ideally against the metrics in line 242. Second, the knowledge gained: what the team now understands that it did not before, such as how one factor affects another.

  • The new or improved product or process
  • Measured against the 242 targets
  • The knowledge gained
  • No repetition of 242 or 244
05

Section C and the details

Keep the title to 60 characters and about the technology. Use real start and end dates that match when the costs start and end. List one to three key individuals with their education, experience and role on the project, in under two lines. Tick at least three kinds of evidence, including time records.

  • Title of 60 characters, about the technology
  • Dates that match the costs
  • One to three key individuals, brief
  • At least three kinds of evidence
06

Contractors on line 267

If contractors are claimed on the project, line 267 is yes, and lines 268 and 269 list each contractor by company name with its business number, or NR if it is not registered. Sredible fills these from the resource allocations, and line 244 should say briefly how the contractors took part.

  • 267 is yes when contractors are claimed
  • 268: company name
  • 269: business number, or NR
  • Describe their role in 244

General guidance on the SR&ED program, not tax advice for a particular claim. Narration is synthetic.

Next lessonPerceived risks in a submissionThe financial and technical patterns that draw a CRA review, and how to address them before filing. 8 min.

Learning SR&ED for client work?

The Sredible Consultant Certificate turns these lessons into a credential that claim preparers look for.