Each section of the technical report gives you a limited number of words to explain months of complex R&D. This constraint forces you to strip away everything but the essentials—the problem you couldn’t solve with existing methods, the work you did to push past it, and the knowledge you gained along the way.
A few hints before we dive in:
Let’s look at each section in the technical narrative:
What scientific or technological uncertainties did you attempt to overcome? (Maximum 350 words)
What work did you perform in the tax year to overcome the scientific or technological uncertainties described in line 242 (Summarize the systematic investigation or search) (Maximum 700 words)
What scientific or technological advancements did you achieve or attempt to achieve as a result of the work described in line 244? (Maximum 350 words)
Your technical narrative sets the tone for your entire SR&ED claim. If it’s strong, CRA reviewers will trust the rest of your submission. If it’s vague or off-target, they’ll dig deeper—and your audit risk increases.
Done well, this section becomes your strongest proof that your team is doing genuine R&D and deserves to be recognized for it.
The T661 form is different from a business or technology roadmap you might include in a grant proposal. Focus on clear, factual writing that proves you pushed beyond standard practice and generated new knowledge.
Official Guidance from CRA
CRA doesn’t provide a writing style guide, but does state that the technical narrative should be written in “the technical language and style of those who did the actual work, or who understand and are familiar with the work”.
Check the official CRA page here: Guide to Form T661
