Connect Google Drive — Build Claims Straight From Your Files

Not every R&D team runs its work through Jira or Linear. Manufacturing, hardware, process engineering, and plenty of other technical teams do their design and experimentation in documents and spreadsheets, not issue trackers. Until now, getting that evidence into a claim meant manually zipping files and uploading them one batch at a time. Now you can just connect Drive.

Browse and select, not zip-and-upload

Connect Google Drive from Sources and pick files or whole folders with Google's own file picker — the same one you already know from Docs and Gmail. Select a handful of documents or a folder with hundreds of files in one pass; SREDr pulls in everything you selected and keeps watching for changes.

This is a different way of building a claim than connecting a project tracker: instead of issues and tickets, the evidence is the documents themselves — design specs, test plans, meeting notes, experiment write-ups — read the way a technical reviewer would read them.

We don't just read the latest version — we read how it evolved

SR&ED is about the work of arriving at an answer, not just the answer. A design doc that went through eight rounds of revisions during the tax year tells a very different (and much more convincing) story than a single final snapshot.

For every Drive document, SREDr:

• Extracts the current content as evidence, same as any uploaded file.
• Pulls the document's revision history for the claim's period and picks a representative sample across the year — the first version, the last version, and up to one per day in between — so a document that changed constantly isn't reduced to one data point, and one that changed rarely isn't padded with noise.
• Builds a diff between consecutive revisions and summarizes what actually changed, so the write-up can point to how the approach developed, not just what it looked like at the end.

If revision history can't be read for a particular file (permissions, an unsupported format), the current content is still captured as evidence — you never lose an extraction because history wasn't available.

Built for work that doesn't live in a tracker

Plenty of eligible SR&ED work never touches a project tracker: engineering drawings and revision logs in manufacturing, test protocols and lab notebooks in process or materials R&D, design specs and BOMs in hardware. If that's where your team's work lives, Drive connection is the fastest way to get real evidence into a claim — no exporting, no reformatting, no manual uploads of one file at a time. Point SREDr at the folder your team already uses and let it do the reading.

Where to look

1. Open a claim's Sources tab and click Connect under Google Drive.
2. Sign in with Google and pick the files or folders you want included.
3. Add or remove files anytime before you run the claim — SREDr re-syncs on the next gather.