Turn scattered activity into linked SR&ED evidence
The evidence for a claim is already there — in commits, tickets, design docs and timesheets. The work is collecting it, understanding it, and tying it to the projects it supports.
That collect-understand-link loop is what SREDlog's evidence pipeline does.
3-day trial · no card · AI included, no setup
Collect from where the work lives
Connect GitHub for a read-only sync of commit and repo activity, upload documents and spreadsheets, or reference a source by link. The repo-to-project mapping stamps synced activity into the right claim automatically.
Understood, not just dumped in a folder
- AI reads each item and classifies it — what kind of document, what technical work it shows, how relevant it is to SR&ED.
- Tables and hours are pulled out where they exist.
- Every classification is a proposal a person confirms; nothing is assumed.
Linked into the claim
Evidence is tied to the project it supports, and from there into the narratives and the numbers — so the drafted T661 can cite the exact evidence behind a sentence, and the binder traces every figure to its source.
Frequently asked questions
The client installs the GitHub App and picks repos; the sync is read-only using short-lived installation tokens. No personal access tokens, least privilege, the client controls the grant.
Documents, dev logs, tickets, timesheets, images and PDFs (and CSV, XLSX, DOCX, TXT). You link each item to the project it supports.
No. It surfaces and classifies the technical work in your evidence as proposals; you confirm the classification, the project link and any extracted hours.
Yes — isolated per firm, encrypted at rest, streamed only through authenticated routes, never used to train AI. See security.
Keep reading
Connect your evidence in minutes
Start a free trial, connect GitHub or upload your first documents, and watch scattered activity become linked, audit-ready evidence.
3-day free trial · No credit card required