How to Build a Responsibility Chart for a Small Team

• List outcomes, not vague departments.
• Name one doer and one decision owner for each row.
• Test the chart against real work before calling it finished.

A customer asks when a job will finish. The salesperson assumes operations will reply, operations waits for the owner, and the owner thinks the account lead already handled it. Everyone is busy. Nobody clearly owns the answer.

A responsibility chart makes that gap visible. It links a piece of work to the people who do it, own the final call, give input and receive an update. A small team can build one useful page without copying an enterprise org chart.

Choose one process, not the whole company

Start with a process that crosses roles. Good candidates include quoting, customer onboarding, weekly scheduling, invoice follow-up or publishing a campaign. Pick work that often waits, repeats or returns for approval.

Do not map every duty in the business on day one. A wide chart becomes hard to review. One process with eight to twelve rows is enough to reveal where ownership is missing.

If the problem is a missing procedure, first write a one-page small-business SOP. The SOP explains how work moves. The responsibility chart shows who plays each part.

Write rows as clear outcomes

Use a verb and an object. “Approve the final quote” is clearer than “sales.” “Confirm the delivery date” is better than “operations.” Each row should describe a result that another person can recognise.

Keep rows at one useful level. Mixing “run marketing” with “check Tuesday's advert copy” makes the chart uneven. Break a broad outcome into smaller rows only when different people own the parts.

The Association for Project Management treats a responsibility assignment matrix as a way to connect planned work with an organisation's roles. Its qualification material also links the work breakdown and organisational breakdown when roles are assigned. For a small business, that means listing the work and the people before filling the grid.

Use four plain roles

RACI has four roles. The American Society for Quality describes them as responsible, accountable, consulted and informed. Translate those labels into words your team will use.

1. Doer: completes the work.
2. Decision owner: accepts the result or makes the final call.
3. Adviser: gives input before the decision.
4. Update recipient: needs the result after the decision.

A role is not a status prize. The decision owner needs enough authority to decide. GOV.UK's service-team guidance makes the same practical distinction: a service owner holds overall responsibility and decision authority, while a delivery manager removes blockers and supports the way the team works.

Build the first draft together

Put outcomes down the left side and role names across the top. Fill the chart in a short working session with the people who actually touch the process. Let the team challenge each assignment.

Labelled example: This invented service-firm chart shows a format, not a universal assignment. Change every row and role to match your team, customer promises and authority limits.

People may hold several roles. GOV.UK notes that the mix of roles and skills changes with a service's size and stage. A five-person company should map real hats, not invent full-time posts it does not have.

Run five checks on every row

First, look for a missing doer. A task with no doer is only an intention. Next, find rows with several doers and ask who coordinates their work.

Third, name one decision owner. Two final owners can create a quiet veto. Fourth, keep adviser lists short so routine work does not wait for a committee.

Last, ask whether every update recipient truly needs a message. Too many copied people hide the signal. The chart should reduce waiting, not create a new reporting burden.

If the team lacks the skill to hold a role, record that gap in the small-team skills matrix. The two tools answer different questions: the skills matrix shows capability coverage, while this chart assigns work and decisions.

Test it against three real cases

Choose one routine case, one urgent case and one awkward exception from recent work. Walk each case across the chart. Ask who acts first, who can decide, where advice enters and who closes the loop.

Watch for hidden verbs such as “checks,” “hands over” or “confirms.” Add a row when a real handoff has no home. Remove a row when it never changes a decision or result.

Link timing problems to the weekly capacity plan. A responsibility chart cannot fix an impossible workload, but it can show who must make the trade-off.

Publish the chart where work happens

Give the chart one owner and one version date. Keep it next to the process, project board or shared folder that the team already uses. A forgotten slide in a meeting deck will not change a handoff.

Review the first version after two weeks. Note any decision that still climbed to the owner, any task completed twice and any update that arrived late. Change the assignment, the authority or the process based on what happened.

Use the customer onboarding checklist as a test case when several roles touch a new account. If the chart cannot tell a new team member who decides the next step, it is still too vague.

Copy this one-page structure

1. Name the process and the chart owner.
2. List eight to twelve work outcomes.
3. Add current roles across the top, using names the team recognises.
4. Mark the doer for every row.
5. Name one decision owner.
6. Add advisers whose input could change the decision before work starts.
7. Add update recipients only after a result.
8. Test one routine, urgent and unusual case.
9. Record the version date and agree when the team will review it.

The best chart is not the fullest. It is the one a teammate can use to answer, “Who moves this now, and who can make the call?”

Frequently asked questions

What is a responsibility chart?

It is a grid that lists work in rows and team roles in columns, then shows who does, owns, advises on and receives updates for each item.

Can one person hold more than one role?

Yes. In a small team, one person may do the work and own the decision. The chart should still show both duties so a later handoff is clear.

Should every task go on the chart?

No. Start with recurring work, important decisions and handoffs that often stall. Tiny personal tasks can stay off the page.

How often should a small team review the chart?

Review it after the first two weeks, then when work, staffing or authority changes. A short quarterly check is a practical starting rhythm.

Sources and scope

ASQ: RACI roles and purpose · APM qualification handbook · GOV.UK: what each service-team role does · GOV.UK: set up a service team. The chart and examples are general operating guidance. They do not replace employment, safety or regulated-industry duties.