Build a RACI Chart from Your Project Task List with Ownership Gaps Flagged

Turns a pasted task list into a RACI table with one Accountable per task, flags unowned or over-consulted tasks, and lists questions to confirm with your team.

You getRACI table, flagged tasks and gaps to confirm with the team

Prompt

Prompt
Act as a project coordinator who builds RACI charts for cross-functional teams.

I will paste my project task list right after this prompt, with the names or roles of the people involved. If I don't include people or roles, ask me up to 3 short numbered questions in one message about who is on the team and what each person owns. Wait for my answers before building the chart.

Rules:
1. Every task gets exactly one Accountable (A). If two people seem to share it, pick the most likely one and flag the choice.
2. Every task needs at least one Responsible (R). Mark tasks with no clear R as "NO OWNER".
3. Flag any task with more than 2 Consulted (C) as a likely bottleneck.
4. Use only the people and roles I give you. Do not add team members.
5. Keep task names under 8 words and keep my original order.

Output format:
1. RACI table: columns are Task, one column per person, then Flags.
2. Flagged tasks: numbered list with the issue and a suggested fix.
3. Gaps to confirm with the team: 3-6 yes/no questions I can paste into a team message.
4. Workload check: count of R and A per person, one line each.

End with one line naming the assumptions you made and any missing information.

Example output

Example for: a 5-person team relaunching a company website. Priya is the PM, Marcus the designer, Lena the developer, Tom in marketing, Ana in legal.

1. RACI Table

TaskPriyaMarcusLenaTomAnaFlags
Define relaunch goalsA/RCICI
Audit current site contentAIIRI
Design new homepageARCCI
Build page templatesACRII
Write new product copyCCCA/RC4 Consulted
Review privacy and cookie textIICIA/R
Set up analytics trackingIIRAIA assumed
Plan launch announcementAIIINO OWNER

2. Flagged Tasks

  1. Write new product copy has 4 Consulted. Suggested fix: keep Priya and Marcus as C and move Lena and Ana to I. Ana can review only the legal claims.
  2. Set up analytics tracking: I made Tom Accountable because marketing uses the reports, but Lena could own it. Confirm who signs off.
  3. Plan launch announcement has no Responsible. Suggested fix: assign Tom as R, since he already owns copy and analytics.

3. Gaps to Confirm with the Team

  • Tom, will you own the launch announcement as Responsible?
  • Is Tom, not Lena, the person who signs off on analytics setup?
  • Can Lena and Ana move from Consulted to Informed on product copy?
  • Ana, do you need to review the full product copy, or only pricing and legal claims?
  • Should Marcus be Consulted on the launch announcement visuals?

4. Workload Check

  • Priya: 1 R, 5 A
  • Marcus: 1 R, 0 A
  • Lena: 2 R, 0 A
  • Tom: 3 R (incl. suggested launch task), 2 A
  • Ana: 1 R, 1 A

Assumptions: analytics accountability was assigned to Tom based on who uses the data. No launch date was given, so the chart does not account for timing or capacity.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Requiring exactly one Accountable per task stops the shared ownership that lets work stall.
  • Flagging tasks with more than 2 Consulted surfaces review bottlenecks before they slow the project.
  • Ending with yes/no gap questions gives you a ready message to settle ownership with the team quickly.

Use at a project kickoff or when tasks keep slipping between people. Paste your task list and team names into ChatGPT, Claude or Gemini. Rough notes or a copied spreadsheet column work fine.

Common edits

  • Add a Due Date or Phase column to the table for time-bound projects.
  • Change the Consulted limit from 2 to 3 for larger teams or regulated work.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Productivity