Self-Managed R&D Documentation

Why self-managed

People who did the work are best placed to describe it. Giving them simple tools, on a schedule, makes the records better and the reviewer's job easier. A reviewer, however skilled, cannot know what an engineer tried in March unless it was written down. Self-managed documentation puts the writing in the hands of the person who knows, at the time they know it, and gives the reviewer a clean file at the end.

The tools described here are part of TaxTrex, a Swanson Reed product, offered white-label. Details are limited to what Swanson Reed has provided, and integrations, review tiers and partner pricing are proposals until confirmed.

A worked example (illustrative)

This scenario is invented. A mid-sized software company lists four projects in January and names a lead for each. Each month the leads receive a short survey. By June, the coordinator sees that one project has monthly answers and files, two have answers but no files, and one has gone quiet. She asks the quiet project's lead what happened: the team switched to a different approach and nobody wrote it down. They add a note about why, and the project's record is complete again. At year end, the reviewer exports the claim pack and finds a coherent file for all four.

Limits

Self-managed does not mean unreviewed. A licensed CPA or enrolled agent reviews the claim before it is filed, and the review tier is chosen by the partner. The tools help people record what happened. They do not decide eligibility, and they cannot create records for work that nobody documented. Integrations, review tiers and partner pricing are proposals until confirmed by Swanson Reed.

Each tool in a little more detail

The survey scheduler sends short surveys at the rhythm the partner chooses and chases people who have not answered. The project register is the list of projects and business components everything else attaches to, so that a note, a file or a cost always belongs somewhere. The evidence vault stores notes, files and approvals with dates, so a reviewer can see what was recorded when. Cost and time sync brings accounting and time information in and links it to the register. And the claim pack export gathers the result into a file the reviewer can work from.

Each tool has its own page. The tools are designed to feed one another: a survey answer lands in the vault against a project in the register, a cost from accounting links to the same project, and the export draws on all of it.

Making the vault useful

The vault is only as good as what goes into it. Encourage people to attach the thing they are describing: the test result, the design sketch, the comparison. A note that says "tried two approaches" is more convincing with the two results attached. Encourage short, specific statements over long vague ones, and dates over general periods. A reviewer reading the file months later will thank you.