RACI matrix: who decides and who does the work?

A RACI matrix identifies who performs an activity, who is answerable for its result, whose input is needed and who receives updates. For a small business, it makes handoffs and decision ownership explicit within a defined process, with one accountable owner for each activity.

An order sits between sales and production because each team believes the other has confirmed the delivery date. More reminders may move that particular order, but the next one can face the same uncertainty. A useful responsibility matrix gives people a shared explanation of the work and a clear next step when a decision is waiting.

The method below is an original starting point for a Canadian small business. Its manufacturing example is entirely fictional. Suggested trial periods are practical choices to adapt, rather than measured benchmarks or promises of improvement.

RACI matrix: what do the four letters mean?

Responsible identifies who does the work; Accountable identifies the owner answerable for completion; Consulted identifies people providing input; Informed identifies those receiving updates. Microsoft’s guidance on defining roles explains these distinctions and recommends one accountable person for each task.

Agree on that legend before assigning letters. In ordinary conversation, “responsible” can refer to both the person preparing a result and the person authorizing it. For this exercise, A carries final accountability and the relevant decision authority; R produces the deliverable. Write those meanings beside the table so a new employee can interpret it without guessing.

The UK government’s Global HR Design reference also specifies one accountable party for each task or deliverable. That convention is useful for identifying a decision owner. A small business can use the principle without adopting the public service’s organizational model.

Which process should a small business map first?

Choose one handoff with a visible problem: accepting an order, approving a purchase or preparing for a new hire. Define its beginning and end. “From the customer’s request to an accepted order confirmation” gives the team a clearer boundary than “improve communication.” Keep the first attempt small enough for the people involved to review together.

Invite the people who actually perform the work. Walk through a recent file without assigning blame. Where did it stop? What information was missing? Which decision had to be made again? Record what is needed to understand the sequence. A process discussion should give people room to explain constraints rather than become an impromptu performance assessment.

Turn that sequence into deliverables with action verbs and completion conditions. “Validate feasibility” and “approve a price exception” are usable rows. “Manage the customer” combines too many decisions to guide a handoff. Our guide to OKRs for small businesses can help define the outcome that matters; the matrix then identifies the contributions needed to pursue it.

How do you assign letters without adding a bottleneck?

For each row, state the deliverable and who needs to receive it. Identify the role with authority to answer for the result, then the role leading the work. One role can hold both R and A when its authority allows that combination. Several people may contribute, but give the trial a recognizable coordination point so unfinished work has somewhere to go.

Check actual authority before adding A. Someone cannot meaningfully accept a production date without access to capacity information. Specify what information and resources that role can use, what it can decide and what requires escalation. The table should reflect existing delegations or an explicitly agreed change. A letter does not create a new authorization by itself.

For every C, write the question that needs input and when that input is required. Consulting everyone about every detail can slow routine work. For each I, identify a useful update: an accepted confirmation, a change notice or a decision summary. An update should not silently become another approval step.

Read the finished draft across rows and down columns. A row without anyone doing the work leaves a gap. A column holding nearly every decision may expose a capacity problem. Discuss workload and backup arrangements before redistributing letters. Clear documentation helps people coordinate the resources they have; it does not create additional time.

What does a fictional order handoff look like?

Entirely fictional example: a small manufacturer in Trois-Rivières wants to clarify how it confirms custom orders. Four roles take part in the exercise below. This is an illustrative arrangement, not a client story or an observed business result. R/A means one role performs the activity and is accountable for it.

Activity and deliverable	Sales	Coordination	Production	Management
Confirm the customer’s requirements	R/A	C	C	I
Validate feasibility and delivery date	C	R	A	I
Approve a price exception	R	C	C	A
Send the accepted order confirmation	I	R/A	C	I

Here, sales gathers the customer’s requirements. Coordination prepares the feasibility information, while production owns the date it accepts. A price exception follows a separate decision path, with management accountable for that choice. Coordination then sends a confirmation that reflects the accepted decisions.

Before the trial, the team rehearses an order with an impossible requested date. Who prepares an alternative, and who can accept it? If the group cannot answer, it clarifies the deliverable or authority before proceeding. The matrix has not demonstrated a faster turnaround simply by being completed. The team still needs to observe subsequent orders to assess whether the new arrangement helps.

How do you keep responsibilities useful after the workshop?

Give the document an owner, approval date and version number. Set a review point after a few files, perhaps after a two-week trial if the volume supports it. Examine unresolved expectations and decisions passed back and forth. Agree on changes with the affected roles, explain the current version and make it easy to find where people work.

M360 Compass’s official RoleAlign page describes documented roles and responsibilities and accountability linked to objectives. Its Momentum page confirms recorded decisions, clear owners and deadlines, and action follow-up. These functions can support the responsibilities and follow-through agreed during your process review. Ask how your matrix would be represented during a demonstration; this article does not assume automatic RACI generation or a dedicated matrix editor.

Include the relevant handoffs when introducing a new employee to the work. Our 30-60-90-day onboarding plan offers a structure for that introduction. Later, during performance reviews in a small business, distinguish role expectations, resources provided and observed contributions. A letter in a matrix cannot establish someone’s performance on its own.

Frequently asked questions about role clarity

Does every task need a RACI matrix?

Start with a process where expectations overlap or decisions repeatedly stall. Map the deliverables that require a meaningful handoff. Routine actions that everyone already understands do not each need a separate row in a new document.

Can two people be accountable for the same row?

The convention used here assigns one A per row. If two authorities own different decisions, separate those decisions into distinct activities. The same person can hold R and A when their authority and resources match the work.

What if people disagree with the proposed assignments?

Return to a concrete file and the decisions people are actually authorized to make. Invite those involved to explain the gaps. Someone with authority to define the roles must resolve the disagreement; completing the table cannot replace that agreement.

When should the matrix be updated?

Review it when a role, delegation or process changes, and after the initial trial. Keep the reason for each adjustment. Remove superseded versions from everyday working spaces so employees are not following conflicting instructions.

To connect responsibilities with decisions and team follow-up, request a M360 Compass demonstration with one specific process you would like to examine.