Postgres SQL data modelling.

We are building a software solution that has a requirement for many forms, our stack is c# .net core, postgres with a React frontend.

We have built a form builder that already stores forms as 'Jsonb' in a table. But now we are looking to add a container of some description, that holds the details for many forms.

Some forms will need to be answered multiple times to satisfy the container as complete.

We are looking for somebody who can tell us how to best model this data. Our initial idea was to set up a container with an Id, title, description, and an array of form ids. But this falls short on determining the amount of times a form needs to be fulfilled. I suspect the solution will require multiple tables.

We look forward to hearing from database modelling experts who can help.

Thanks.