That is a list of things done differentiated by user; it is an another approach that does not involve the use of the checklist style, but simulates it.
If I guessed it, if you need clarification let me know.
This is the right way to make independent detail screens
Just be able to make sure that the data you need is available on the screen; this is usually done with relation + lookup columns, or with single value columns.
If you let me explain the practical case I’ll explain how to achieve the result.
To collect data (asset class 1, asset class 2, risk type) you should define USC columns in the “Todo Table”.
So, for Assets data class 1 and 2 we have in the “Todo Table” a single relation towards the users row, therefore we can write this data into the user row with a “set column action”.
And where we’ve to write for Todo3?
Yes, I’ll do it in a little while.
If your data structure is what I see here, you could also do it all in one screen by setting component visibility criteria. But I will continue on the path of the independent screens that you set up in this app, so as not to confuse you. That’s okay too don’t worry.