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
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
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 like this
Turn Rough Notes into a Weekly Slack Team Update with Clear Blockers
Turns your messy weekly notes into a Slack-ready team update under 150 words, split into Shipped, Next and Blocked, with an owner and date for every blocker.
Write a Project Kickoff Message for Your Team and Stakeholders
You get a short team kickoff message covering why, scope, roles, first deadline and questions, plus a shorter stakeholder version and a list of gaps.
Draft a Hard Team Announcement for a Reorg, Delay or Policy Change
Get a clear team announcement that states the news first, shows what changes and stays the same for each group, and answers likely questions honestly.
Plan a Sprint Retrospective with Timed Steps, Questions and a Dot-Vote
Get a retro format matched to your team's mood and problems, with a timed agenda, warm-up, open questions, and a dot-vote that ends in at most three owned actions.
Prepare for Presentation Q&A with 10 Tough Questions and 30-Second Answers
Get 10 likely tough audience questions ranked by likelihood and difficulty, a 30-second answer for each, and clear flags where you lack evidence.
Write a Project Status Report with RAG Calls, Risks and Leadership Asks
Turns your raw project notes into an executive-ready status report with justified red/amber/green ratings, done vs. planned work, a risk table and specific decisions needed.