Hmm, what if you had a Stakeholder
table that had all the stakeholder details etc, and a Projects
table that had four linked fields to the Stakeholder
table, each linked field representing one of the RACI categories?
You could then see a per project or per stakeholder breakdown depending on the table you were looking at
Hmm, what if you had a Stakeholder
table that had all the stakeholder details etc, and a Projects
table that had four linked fields to the Stakeholder
table, each linked field representing one of the RACI categories?
You could then see a per project or per stakeholder breakdown depending on the table you were looking at
Hi Adam!
Thanks for your suggestion
I’m not entirely clear on how that would let me report the RACI allocations for each stakeholder if they differ between projects. I have a number of different stakeholders involved in different projects, but at different levels and its very hard to keep track of which stakeholders are on multiple projects and where they fall for involvement/communication for each project.
For example:
I have a stakeholder table that has all potential stakeholders, along with all of their relevant information (name, email, department, title, time zone, etc).
Bob Ross is a member of two different projects, Project A and Project B
On Project A, Bob is a core member and needs to be heavily involved
On Project B, Bob only needs to be informed, and doesn’t need to be involved on a regular basis.
Should I have one ‘Projects’ table with the following columns:
Column A: Project - This would designate the project that the stakeholder is involved in.
Column B: Stakeholder Name (this would be linked to the Stakeholder tab to autopopulate the stakeholder information (email, department, title etc)
Column C: Checkbox for R
Column
Checkbox for A
Column E: Checkbox for C
Column F: Checkbox for I
Or should I have one table for each project? I’m stumped :grinning_face_with_sweat:
Hi Adam!
Thanks for your suggestion
I’m not entirely clear on how that would let me report the RACI allocations for each stakeholder if they differ between projects. I have a number of different stakeholders involved in different projects, but at different levels and its very hard to keep track of which stakeholders are on multiple projects and where they fall for involvement/communication for each project.
For example:
I have a stakeholder table that has all potential stakeholders, along with all of their relevant information (name, email, department, title, time zone, etc).
Bob Ross is a member of two different projects, Project A and Project B
On Project A, Bob is a core member and needs to be heavily involved
On Project B, Bob only needs to be informed, and doesn’t need to be involved on a regular basis.
Should I have one ‘Projects’ table with the following columns:
Column A: Project - This would designate the project that the stakeholder is involved in.
Column B: Stakeholder Name (this would be linked to the Stakeholder tab to autopopulate the stakeholder information (email, department, title etc)
Column C: Checkbox for R
Column
Checkbox for A
Column E: Checkbox for C
Column F: Checkbox for I
Or should I have one table for each project? I’m stumped :grinning_face_with_sweat:
Hi Sarah, here’s an example I set up for you that might help:


Hi Sarah, here’s an example I set up for you that might help:


Thanks Adam! Really appreciate you taking the time to put that together