Follow the claim from start to finish.

Welcome to SREDlog. Preparing an SR&ED claim means keeping the client's records, financial calculations, technical story, and tax forms aligned as the file develops. That can be a lot to hold together, especially when the information starts in different places. SREDlog brings that work into one place.

You can review the evidence, work through the numbers, prepare the descriptions, and carry the approved information directly into the forms without losing the source behind it. I'm going to show you how that works using Northwind Robotics. Northwind is developing an adaptive navigation system.

For this claim, we have technical notes, experiment logs, payroll, time records, and an invoice for materials used during testing. Before making any claim decisions, those records need to be organized and attached to the right work. Northwind can also upload records through its client portal or choose a supported connection and decide what to share with the firm.

Then, as each record comes in, I check the document type and connect the technical evidence to the project it supports. Payroll and other claim-wide records stay at the claim level. Once the records are in order, we can move into the financial review. One of Northwind’s records is this invoice for sensor test boards used in the prototype trials.

The invoice shows $2,000 in materials and records the tax separately. We want that information available for the claim without retyping it into another working file. So, I'll ask SREDlog to find the expenditure information in the records we already have. Over here, SREDlog has found the invoice and prepared a proposed entry.

At this stage, it's waiting for my review. I can see the amount, description, and source in one place. I'll check the category, confirm the project, and decide whether the expense should be included. Once those checks are done, I can post the reviewed amount to the T661.

And now, the same $2,000 appears on line 320 of the actual T661. This is the connection you want when reviewing a claim. You can move from the number in the form back to the decision and the client record that supports it without entering that same amount again in a separate T661.

Next, I'll work through payroll. SREDlog found an annual salary of $120,000 and the employee's recorded time for the project. The records show 800 project hours out of 2,000 working hours. Before I include anything, I can check both the source and the calculation. That gives us 40% allocation and a proposed SR&ED salary of $48,000.

The calculation looks right, so we'll include the payroll entry and post it. Now we can see forty-eight thousand dollars in salary and two thousand dollars in materials in the actual T661. Both amounts remain tied to the review that put them there. With the financial entries in place, we can move to the technical description.

Northwind's notes, experiment logs, and test records are already connected to the project. SREDlog can use those records to prepare a first draft so the technical review starts with something concrete on the page. The draft covers the technological uncertainty, the investigation and what Northwind's team learned during the adaptive navigation trials.

From here, I decide what the evidence supports. I can tighten the language, remove anything that goes too far, and make sure the description reflects the work that was actually done. The supporting documents stay beside the description while I work. When I hover over one, SREDlog highlights the wording connected to that source.

That way, I can check the statement in context, make an edit and save a new version as the review moves forward. Once I'm ready for the client's input, I can share that specific version with Annie who works at Northwind. She can read the description, leave feedback, and confirm whether it reflects the work her team carried out.

Then, when I return to the claim, her confirmation is attached to the exact version she reviewed. She confirms the facts and the SR&ED judgment remains with me at the firm. Once the descriptions are finalized and confirmed, I bring them into the T661 too.

Then I complete the company and preparer details and work through the remaining review items. In the exported draft, we can see the descriptions: $48,000 in salary and $2,000 in materials. SREDlog also prepares the supported federal and provincial forms selected for the claim. I can review them and export the supporting package with the source records and audit trail.

From there, the firm continues with its normal filing process. The preparation history stays with the claim whenever you need to come back to it. And if CRA reviews the claim after it's filed, SREDlog gives the firm a dedicated place to manage what comes next.

You can keep CRA's requests, due dates, correspondences, and the records used in each response connected to the filed claim. For Northwind, I can also generate an audit binder for the claim we've just prepared. This is the actual binder for the claim. It brings together the claim summary, project descriptions, approved labour, evidence map, review history, and the original source documents.

So, if questions come later, the firm can follow the claim back to their records and decisions behind it without having to rebuild the file under a deadline. And that's SREDlog. We started with Northwind's client records. Now the reviewed amounts are in the T661, the project description is tied to its evidence, and the client confirmation is saved with the claim.

If questions come later, the audit binder is ready. You still make the decisions. SREDlog keeps the work together and carries it forward so you can spend your time reviewing the claim instead of rebuilding it. If you'd like to see what SREDlog could look like for your firm, you can book a demo or start a free trial.

Thanks for watching.