Create a comprehensive RACI responsibility matrix that clearly assigns who is Responsible, Accountable, Consulted, and Informed for every project task and decision
You are an experienced organizational consultant specializing in governance frameworks and project management structures. You have developed RACI matrices for hundreds of projects ranging from small team initiatives to enterprise-wide transformations, and you understand the common pitfalls that make responsibility assignments fail in practice. I need you to create a RACI responsibility matrix for a project. The project is [PROJECT_NAME] and here is what it involves: [PROJECT_DESCRIPTION] The project operates in the [INDUSTRY:select:Technology,Healthcare,Finance,Manufacturing,Retail,Government,Education,Professional Services,Construction,Nonprofit,Energy,Media] industry. The organization size is [ORG_SIZE:select:Startup (under 50),Small Business (50-200),Mid-Market (200-1000),Enterprise (1000-5000),Large Enterprise (5000+)]. Here are the roles or team members involved in this project: [TEAM_ROLES] Here are the key tasks, activities, or decisions that need RACI assignments. If you do not have a complete list, work with the project description to generate appropriate tasks: [TASKS_OR_DECISIONS?] The project phase is [PROJECT_PHASE:select:Initiation,Planning,Execution,Monitoring and Control,Closing,Multiple Phases]. Any specific governance concerns or constraints I should know about: [CONSTRAINTS?] Please deliver the following: First, create the RACI Matrix itself as a comprehensive table. Each row represents a task, activity, or decision point. Each column represents a role. Use R for Responsible (does the work), A for Accountable (approves and owns the outcome with only one A allowed per row), C for Consulted (provides input before the work), and I for Informed (notified after completion). If a role has no involvement in a task, leave the cell empty. Include at least 15 to 20 tasks unless the project scope suggests fewer. Group related tasks under clear category headers within the table. Second, provide a RACI Validation Analysis that checks for common problems. Identify any tasks with no Accountable person assigned, any tasks with multiple Accountable persons which violates the single-accountability principle, any roles that appear overloaded with too many R or A assignments, any roles that are rarely involved and might be missing from key activities, and any tasks where everyone is merely Consulted or Informed but no one is actually doing the work. Third, create a Role Summary showing each role's total count of R, A, C, and I assignments. Add a brief workload assessment noting whether the distribution seems balanced or if certain roles carry disproportionate responsibility. Fourth, develop Assignment Rationale for the five most critical tasks or decisions. Explain why you assigned each role the way you did, what could go wrong if the assignments were different, and how the accountability structure supports project success. Fifth, provide Communication Guidelines based on the RACI assignments. Explain how Consulted parties should be engaged in advance, how Informed parties should receive updates, what forums or meetings might be needed for tasks with many stakeholders, and how to escalate when the Accountable person is unavailable. Finally, include Optimization Recommendations with three to five specific suggestions for improving the responsibility structure. This might include consolidating certain roles, adding a role that seems missing, adjusting assignments to reduce bottlenecks, or establishing clearer boundaries between similar roles. Format all tables in Markdown. Use clear section headers. Keep recommendations actionable and grounded in real project management challenges rather than theoretical ideals.
Use this prompt anywhere
10,000+ expert prompts for ChatGPT, Claude, Gemini, and wherever you use AI.
Get Early AccessA RACI matrix assigns exactly one role to every person on every task: Responsible, Accountable, Consulted, or Informed. Without this clarity, teams default to vague ownership where everyone assumes someone else is handling the work.
This prompt builds a complete RACI matrix from eight inputs that capture your project context and team structure. You provide [PROJECT_NAME] and [PROJECT_DESCRIPTION] to frame the scope, then specify [INDUSTRY] and [ORG_SIZE] so the output reflects real organizational dynamics rather than generic advice. The core inputs are [TEAM_ROLES] and [TASKS_OR_DECISIONS], which define the rows and columns of your matrix. Adding [PROJECT_PHASE] focuses the output on the current stage of work, and [CONSTRAINTS] flags any reporting lines or approval bottlenecks the matrix needs to respect.
The golden rule of RACI is that every task gets exactly one Accountable owner. This prompt enforces that rule while distributing Responsible, Consulted, and Informed roles to keep workloads balanced and communication channels clear. The result is a ready-to-use responsibility assignment matrix you can paste into your project management tool or share during kickoff.
Build yours in Dock Editor and pair it with a scope of work to lock down both who does what and what gets done. For the full planning chain, see project charter and work breakdown structure.
Enter [PROJECT_NAME], [PROJECT_DESCRIPTION], [INDUSTRY], and [ORG_SIZE]. These inputs ensure the matrix reflects your organization's structure and the project's domain rather than producing a generic template.
Fill in [TEAM_ROLES] with every person or role involved, and [TASKS_OR_DECISIONS] with the key activities and decisions that need ownership. These two fields form the rows and columns of your RACI grid.
Use [PROJECT_PHASE] to focus the matrix on the work happening now. This prevents the output from becoming an overwhelming document that tries to cover every task across the full project lifecycle.
Add any reporting lines, approval requirements, or organizational bottlenecks in [CONSTRAINTS]. The prompt uses these to ensure the Accountable assignments respect your actual decision-making hierarchy.
Check that every task has exactly one A, at least one R, and that no single role is overloaded with too many Responsible assignments. Share the final matrix with your team during kickoff and revisit it at regular check-ins.
A product manager maps roles across engineering, design, marketing, and sales teams for a launch with 20+ tasks, ensuring each deliverable has one clear Accountable owner and preventing duplicate effort between departments.
An IT director assigns RACI roles across infrastructure, security, application, and vendor teams for a cloud migration, clarifying who approves each cutover decision and who needs to stay informed about downtime windows.
A compliance officer builds a RACI matrix for an upcoming audit, assigning Responsible and Accountable roles for document preparation, evidence collection, and stakeholder interviews across legal, finance, and operations.
A general contractor creates a RACI chart covering permitting, subcontractor management, inspections, and client approvals, making sure the architect, engineers, and site supervisors each know their exact responsibilities.
Every task must have exactly one Accountable person. Multiple people can be Responsible for doing the work, but only one person owns the final decision. If a task has two Accountable parties, neither feels truly on the hook and approvals stall. This single-owner rule is what makes RACI effective for eliminating confusion about who signs off on deliverables.
Responsible means the person doing the work. Accountable means the person who approves or owns the outcome. Consulted means someone whose input is needed before a decision. Informed means someone who needs to know the result but does not participate in the work. Every task in the matrix gets one letter per team member from these four options.
The three biggest mistakes are assigning roles without stakeholder buy-in, treating the matrix as a one-time kickoff artifact that never gets updated, and over-assigning Consulted and Informed roles until everyone is copied on everything. Effective RACI matrices stay lean and get reviewed at regular check-ins as the project evolves.
Skip it when your team is small, works in the same department, has collaborated before, and already trusts each other on decision rights. RACI adds the most value on cross-functional projects where people from different teams need explicit role clarity. For a three-person team with clear reporting lines, the overhead outweighs the benefit.
The [TEAM_ROLES] input defines the columns of your matrix. List every role involved in the project, from project sponsor to individual contributors. The prompt then assigns R, A, C, or I to each role for every task. More specific role names produce a more actionable matrix than generic titles like 'team member.'
Yes. The [PROJECT_PHASE] variable lets you focus the output on planning, execution, testing, or any stage you specify. This keeps the matrix manageable instead of trying to cover every task across the entire project lifecycle in one document. You can generate separate matrices per phase and combine them later.
The RACI matrix connects directly to your project management plan by clarifying who owns each section of the plan. It draws scope boundaries from your scope of work and feeds accountability data into your project status report so stakeholders know whom to contact about each area of progress.
Discover more prompts that could help with your workflow.
Generate a professional service level agreement with performance metrics, uptime targets, response times, penalties, and escalation procedures
Generate a comprehensive project management plan with scope, timeline, resources, risks, and deliverables for any project type.
Generate a structured business case that analyzes costs, benefits, risks, and alternatives to win executive approval for your project or investment
10,000+ expert-curated prompts for ChatGPT, Claude, Gemini, and wherever you use AI. Our extension helps any prompt deliver better results.