RACI Matrix Builder

What is a RACI Matrix?

RACI is a responsibility assignment matrix that clarifies roles and responsibilities:

  • R = Responsible (Does the work)
  • A = Accountable (Owns the outcome, final decision maker)
  • C = Consulted (Provides input before action)
  • I = Informed (Notified after action)

When to Use RACI

  • Designing a Target Operating Model (TOM)
  • Clarifying roles after reorganisation
  • Resolving accountability confusion
  • Onboarding new teams or systems
  • Preparing for regulatory reviews

RACI Matrix Template

Example: Trade Lifecycle - FX Spot Trade

ActivityTraderSalesMiddle OfficeOperationsRiskComplianceFinance
Client RequestCRI----
Quote GenerationRC--I--
Trade ExecutionR/AII-II-
Trade CaptureR-CII--
Trade ValidationI-R/ACC--
Confirmation-CRA---
Settlement Instruction--CR/A--I
Settlement Reconciliation--IR/A--I
P&L CalculationI-CCR-A
Regulatory Reporting--ICIR/AI

Legend:

  • R = Responsible
  • A = Accountable
  • C = Consulted
  • I = Informed
  • - = Not involved

RACI Rules

Golden Rules

  1. One Accountable per Activity: Each row must have exactly ONE 'A'
  2. At Least One Responsible: Each row must have at least ONE 'R'
  3. Accountable Can Be Responsible: 'A' and 'R' can be the same person for small teams
  4. Consult Before, Inform After: 'C' = two-way dialogue; 'I' = one-way notification

Common Mistakes to Avoid

Multiple Accountables: Diffuses responsibility No Accountable: Creates orphaned processes Too Many Consulteds: Slows decision-making Everyone Informed: Creates email overload

RACI Template (Blank)

Activity / DecisionRole 1Role 2Role 3Role 4Role 5
[Activity 1]
[Activity 2]
[Activity 3]
[Decision 1]
[Escalation 1]

Step-by-Step Guide

Step 1: List Activities

Down the left column, list all:

  • Key process steps
  • Decisions that need to be made
  • Escalation scenarios
  • Reporting requirements

Step 2: Identify Roles

Across the top, list:

  • Job titles or team names (not individual names)
  • Systems (for automated activities)
  • External parties (regulators, auditors)

Step 3: Assign RACI

For each activity, ask:

  1. Who owns the outcome? → A
  2. Who does the work? → R
  3. Who needs to be consulted before? → C
  4. Who needs to know after? → I

Step 4: Validate

Check:

  • Does every activity have exactly one 'A'?
  • Does every activity have at least one 'R'?
  • Are there too many 'C's? (Consider limiting to 2-3 per row)
  • Are there too many 'I's? (Use distribution lists, dashboards)

Step 5: Review with Stakeholders

Walk through the matrix with affected teams. Resolve conflicts.

RACI Variations

RACI-VS

Adds:

  • V = Verifies (Quality check)
  • S = Signs off (Formal approval)

RASCI

Adds:

  • S = Supportive (Assists the Responsible party)

DACI

Used in decision-making:

  • D = Driver
  • A = Approver
  • C = Consulted
  • I = Informed

Real-World Example: Change Management

ActivityBusiness OwnerProject ManagerChange ManagerIT LeadQACompliance
Define Change ScopeARCC-C
Impact AssessmentCCR/ACCC
Change ApprovalAICC-C
Change ImplementationICIR/ACI
TestingCC-CR/AI
User CommunicationCCR/AI-I
Training DeliveryCCR/AI-I
Go-Live DecisionARCCCC
Post-Implementation ReviewCR/ACCCI

Integration with Operating Model

RACI matrices fit into the broader Target Operating Model:

Strategy
    ↓
Operating Model Components:
    ├── Processes (BPMN diagrams)
    ├── Organisation (Org chart + RACI)
    ├── Technology (System architecture)
    ├── Data (Data flows + lineage)
    ├── Governance (Decision rights + RACI)
    └── Controls (Risk & control matrix + RACI)

Governance Example

Decision TypeFront OfficeMiddle OfficeRiskCFOCEO
Limit Exceptions <£50kA/RCI--
Limit Exceptions £50k-£500kCA/RCI-
Limit Exceptions >£500kCCCA/RI
New Product ApprovalCCCAR
Trading Desk P&L Sign-offCCCA/RI
Risk Policy ChangeCCRAI
Regulatory AttestationCCCCA/R

Using RACI for Regulatory Compliance

When designing RACI for regulated environments:

  1. Segregation of Duties: Ensure 'R' and 'A' are different people for high-risk activities
  2. Dual Control: For critical activities (e.g., payments >£1M), require two 'R's
  3. Management Oversight: Show where senior management 'A' sits
  4. Audit Trail: Document who was 'A' at time of activity
  5. Attestation: Link 'A' to regulatory attestations

Common Use Cases

1. Post-Merger Integration

Clarify who does what when two organisations merge operating models.

2. Outsourcing

Define boundaries between internal teams and third-party providers.

3. Automation

Show transition from manual ('R' = person) to automated ('R' = system).

4. Agile Teams

Clarify product owner (A) vs scrum master (R) vs team members (R/C).

Tools & Tips

Best Practices

  • Use job titles, not names (people change, roles don't)
  • Start simple (5-10 activities), then expand
  • Review quarterly and update as org evolves
  • Link to process diagrams (BPMN) for full picture

Recommended Tools

  • Excel/Google Sheets: Simple, flexible, version control via SharePoint
  • Confluence: Collaborative editing, easy to link to other docs
  • Visio: Visual RACI swimlanes integrated with process maps
  • Dedicated Tools: ARIS, Signavio (for enterprise-scale TOM design)

Next Steps

  1. Download this template
  2. Map roles and activities for one high-impact process
  3. Review with stakeholders
  4. Identify gaps, overlaps, and conflicts
  5. Update job descriptions to reflect RACI

Need Expert Help?

If you need support designing a Target Operating Model, clarifying governance frameworks, or preparing for a regulatory review, contact our team for a consultation.


Template Version: 1.0 Last Updated: January 2025 License: Free for commercial use with attribution