Cross‑Functional RACI + DACI Template (Activity Matrix & Decision Overlay)

What this template is for

This template helps teams clarify who does what (RACI) and who drives and approves decisions (DACI) for cross-functional work. Use it to reduce ambiguity, avoid duplicated effort, speed decisions, and make escalation simple and auditable.

When to use

Use the combined RACI + DACI matrix when your work contains both deliverables/tasks and explicit decisions that need a clear owner. Use RACI where execution and ongoing responsibilities matter, and use DACI for choices that require a driven decision process.

How to use this template

1. List activities or deliverables (one per row).
2. For each activity, assign RACI roles (Responsible, Accountable, Consulted, Informed).
3. If the row includes a decision, mark Decision Type = DACI and complete the Driver / Approver / Contributors / Decision Informed fields.
4. Define an escalation path (names/roles and condition) and expected decision timelines.
5. Keep role entries as role names (e.g., Product Manager) or person+role (e.g., Sam Lee — Product Manager). Prefer roles for long-lived matrices; prefer people for short projects.

Template matrix (copy into your spreadsheet or document)

Role rules and quick guidelines

• Accountable (A): Prefer exactly one Accountable per activity to avoid confusion. This is the person ultimately answerable.
• Responsible (R): One or more people who do the work; list the primary responsible person first.
• Consulted (C): People or teams whose input is required before work or decision—limit to essential stakeholders.
• Informed (I): People who should be notified of outcomes or major milestones; they are not required to provide input.
• DACI specifics: Use DACI when an explicit decision process matters. Driver coordinates, Approver signs off (try to keep Approver to one person), Contributors provide detailed input, and Informed are notified of the decision.

When to choose RACI vs DACI (practical heuristics)

RACI works well for operational activities and recurring deliverables where execution ownership and handoffs are the priority. DACI is better for decisions that require a clear owner to gather input, synthesize options, and secure approval. In many cross-functional projects you will use RACI for delivery rows and DACI for decision rows.

Escalation guidance

Define trigger conditions for escalation (e.g., missed deadline, conflicting approvers, unresolved dependencies) and list a short, named escalation path such as "Team Lead → Functional Manager → Sponsor" including time expectations (e.g., escalate after 3 business days without resolution). Put the escalation text in the Escalation Path column for quick reference.

Common pitfalls and how to avoid them

• Multiple Accountables: Leads to stalled approvals. Enforce one A per row.
• Too many Consulted: Slows progress. Limit C to those who must influence scope or risk.
• Mixing people and roles inconsistently: Choose either role-based or person-based entries and stick with it for clarity.
• Not updating the matrix: Treat this as a living artifact—review during kickoffs and at key milestones.
• Using DACI for every small decision: Reserve DACI for decisions that affect scope, budget, timeline, or risk materially.

Sample quick checklist before publishing

1. Every activity has exactly one Accountable.
2. Decision rows marked DACI have a Driver and Approver named.
3. Consulted and Informed lists are concise and role-focused.
4. Escalation path and decision deadlines are defined for critical items.
5. The matrix is stored in a shared, versioned location and reviewed by key stakeholders.

Next steps and variants

Consider adding columns for Status, Last Updated, and Owner Contact for operational tracking. For longer-lived programs, maintain a separate decision log that records the rationale, options considered, and final outcome for each DACI decision.

Tip: For reusable enterprise templates, prefer role names (e.g., "Legal Counsel") rather than individuals so the matrix remains valid across staffing changes.