Hi @Bradley_Kramer - yes, given that you want every individual to check off that they have done the task, you really need to have these task assignments as individual records. The multiple assignees per task is, I guess, for those situations where this sort of individual feedback does not apply.
FWIW, I would approach this base design in a couple of possible ways:
- A table for tasks and a table for people. Tasks are linked to people, but you have to create a row/record for each person/task combination (this is essentially what we are talking about above).
- If the task itself is repeated multiple times, e.g. “read chapter 7” assigned to 10 different people, you could consider a tasks table, a people table and a tasks assignment table. Tasks Assignments links to both tasks and people. The advantage of this approach is that you don’t have to type the tasks multiple times but can simply select a task multiple times which probably saves a few keystrokes along the way.
Either of the above designs would also allow you to do summaries and roll-ups, e.g. total tasks assigned and total completed, which would be more difficult in a single task/multi-assignee scenario.