WBSO with several projects: one document per RVO form

A client rarely hands you one neat project. You get a list: two or three developments, an ERP integration, a certification dossier, a market study. RVO wants one project form per S&O project and nothing that is not S&O. Twin sorts the list with you, and then writes one document per project inside a single Twin project for the client.

How it fits together

One project in Twin for the client and the application year.
One document per RVO project form: each document has its own type, its own start date, hours and export.
One project plan that all documents share, so the assistant keeps the projects apart while writing.

Sort the portfolio with the assistant

Go to Projects and click New project. On the Grant step pick the client. You do not have to choose a document type yet: click Skip. The assistant picks the type per project after the split.

The Grant step of the new project wizard with WBSO typed in the search box, the six WBSO document types and the Skip button boxed

On the Sources step drop the client's development plans, then Continue. On the Start step choose Open the project.
Rename the project by clicking its title, and check that the source is processed.

The project page with the uploaded source Ontwikkelplannen-2027.pdf boxed in the Files section

Start a New chat in the assistant panel and ask for the split. Name the source in your question, so the assistant reads it straight away:
Wij willen WBSO aanvragen voor 2027. De lijst staat in de bron Ontwikkelplannen-2027.pdf bij dit project. Deel dit portfolio in: welke ontwikkelingen zijn zelfstandige S&O-projecten, welke horen bij elkaar, welke zijn geen S&O, en welk RVO-projectformulier hoort bij elk project?
The assistant answers with the split: per development whether it is a stand-alone S&O project, merged with another one, or not S&O at all, with the reason, the RVO form it needs, new or follow-up, the hours and the cost option. It ends with a question, and waits.

The assistant's answer with the two stand-alone S&O projects FlexSeal and SealVision boxed, each with its RVO form, and the confirmation question boxed

The developments that are not S&O are named as such, each with the reason RVO would give.

The same answer, with the three items that are not S&O boxed: ERP integration, CE dossier and market study, each with a reason

Read the split as you would a colleague's proposal. If you disagree, say so in the chat and the assistant revises it. When it is right, confirm:
Akkoord met deze indeling. Maak voor beide S&O-projecten een document aan en schrijf ze volledig uit.

Let Twin write one document per project

On your confirmation the assistant creates a document per S&O project with the matching type, for example WBSO Fysiek product (excl. programmatuur) for a new seal head and WBSO Programmatuur for a detection method. It then writes the project plan with numbered bottlenecks per project and asks you to approve it.
Open the Plan tile on the project page and click Approve, then confirm in the chat. The plan carries the split, so every section writer knows which project it is writing for.

The project plan page with the portfolio split inside the plan boxed and the Approve button boxed

Both documents are written in parallel. Each Projectomschrijving describes its own project only; the other project is not mentioned.

The FlexSeal document in the editor with its Projectomschrijving boxed, describing the seal head only

Download one RVO form per project

Open each document, click Download and choose Latest version. Every document gives its own filled RVO project form as PDF plus a Word file.

The Downloads panel of the FlexSeal document with the PDF and Word files boxed

Each form carries its own start date, hours and milestones. Here FlexSeal starts on 1 January 2027 and SealVision on 1 April 2027, as the client planned.

Page 2 of the FlexSeal RVO form with the Projectomschrijving and Start project 01-01-2027 boxed

Page 2 of the SealVision RVO form (programmatuur) with the Projectomschrijving and Start project 01-04-2027 boxed

Page 3 of an RVO form with the Fasering werkzaamheden table boxed, three lines in mm-jjjj notation

What you check

The split. Two developments with their own technical result, own bottlenecks and own planning are two projects, even when they sit in the same machine. The assistant says why it split or merged; make sure you agree.
Milestones and tools. When the client's plan gives no interim dates or no programming languages, the assistant fills in a plausible planning or a generic tool set and tells you so in the chat. Confirm those with the client before submitting.
Hours per project. The hours in each document are the hours for that project. The total for the application is what you enter in the RVO portal.

Good to know

The project page lists every document with its own type badge, so you see the whole application at a glance.
The non-S&O work does not disappear: it stays in the plan as context for the assistant, so it does not creep back into a document or a milestone table.
You can also create the documents yourself with Add and New document, and instruct each one separately. The assistant then still writes from the shared plan.