Most WBSO dossiers are built too late.
The technical work happens throughout the year. Developers open pull requests, discuss trade-offs, close issues, test prototypes, investigate unknowns, and make decisions that explain the real R&D progress.
But the WBSO administration often happens much later.
At the end of the month, quarter, or even year, someone has to reconstruct what happened. Hours are pulled from spreadsheets. Evidence is collected from GitHub, Linear, documents, notes, and conversations. Advisors or founders try to connect project descriptions, registered hours, and technical progress after the fact.
That is exactly the problem we built R&Dossier to solve.
R&Dossier is a new WBSO administration platform for software, SaaS, and AI teams. It helps teams keep WBSO projects, hours, and technical evidence organized in one review-ready workflow, with integrations that bring relevant work from tools like GitHub and Linear into the dossier faster.
The idea is simple: your WBSO dossier should stay alive during the year, not be assembled under pressure at the end.
Start with the project
A good dossier starts with a clear WBSO project.
In R&Dossier, teams can create WBSO projects with the technical description, uncertainties, development steps, period, expected hours, and approved hours. That gives the administration a structure before the work starts drifting across tickets, pull requests, meetings, and notes.
Instead of treating the WBSO project as a static document, R&Dossier treats it as the center of the workflow.
Hours, evidence, team members, integrations, dashboard checks, and exports all connect back to the project.
Register hours while the work is still fresh
The most important habit is simple: register WBSO hours regularly.
When developers log hours close to the actual work, the notes are clearer, the project context is still fresh, and gaps are easier to spot. If someone worked on a qualifying technical challenge in March but did not register any hours, that should be visible in April — not discovered during a year-end review.
R&Dossier lets teams register hours per project, per person, and per day. Hours can be reviewed, confirmed, or flagged, so the team can keep the administration moving instead of waiting for a last-minute cleanup.
Bring in evidence from where the work happens
Most technical evidence already exists. It just does not live in the WBSO dossier yet.
GitHub contains pull requests, implementation details, and code review context. Linear contains issues, planning, technical decisions, and delivery history. Manual notes and documents often explain experiments, trade-offs, or validation steps.
R&Dossier scans connected tools and turns relevant activity into evidence candidates. Your team then decides what should become official evidence in the dossier.
That distinction matters. The goal is not to import everything. The goal is to keep a clean, defensible record of the work that actually supports the WBSO project.
Link evidence to hours
A pile of evidence is not enough.
For WBSO administration, the important question is whether the project, hours, people, and technical progress can be explained together. That is why R&Dossier lets teams link evidence to hour entries.
A pull request can support multiple hour entries. A single hour entry can be supported by multiple evidence items. Suggestions help surface likely matches, but the team stays in control of what gets linked.
This turns scattered activity into a more traceable dossier.
Review dossier health before it becomes urgent
R&Dossier also gives teams a dashboard for dossier health.
You can see evidence coverage, hours without linked evidence, unreviewed evidence, and other attention points. A short monthly review can prevent the familiar year-end scramble.
If evidence is missing, you can still fix it while the work is recent. If imported evidence is not linked to hours, you can make the connection while people still remember the context. If a project is drifting away from the original scope, you can catch it earlier.
Make the auditpack a byproduct
When the administration is maintained throughout the year, the year-end export should not feel like a rescue operation.
Projects are already structured. Hours are already registered. Evidence is already reviewed. Links between work, people, and technical progress are already in place.
R&Dossier turns that workflow into a structured auditpack export with projects, hours, evidence, evidence-hour links, and attention points for internal review, advisor handover, or control preparation.
It does not replace the official RVO process and it does not guarantee acceptance. It helps teams maintain a better WBSO administration while the work is actually happening.
That is why we launched R&Dossier.
Not as another filing system. Not as another spreadsheet.
But as a workflow for keeping your WBSO dossier alive throughout the year.