How to Write Agency Roles and Responsibilities Your Team Will Use

In a three-person agency, everyone does a bit of everything and it mostly works. Somewhere around the fifth or sixth hire, it stops working. Two people answer the same client email. A monthly report goes out late because each person assumed the other was building it. A new hire spends their first month asking who approves ad spend.

None of this is a talent problem. It is a clarity problem, and it is fixable with a few documents that take an afternoon to draft. This article walks through how to write role definitions that people actually refer to, and how to keep them from going stale.

Symptoms that your roles are too fuzzy

Before you start writing, check whether you have the problem. Common signs:

• Clients email three different people about the same issue.
• Tasks sit in “someone should” territory during team meetings.
• The owner is the default approver for everything, including small decisions.
• New hires take longer than expected to become useful.
• Post-mortems end with “we thought you had it.”

If two or more sound familiar, the fix below will pay for itself quickly.

Start with outcomes, not job titles

The trap most agencies fall into is copying job titles from job boards. “Account Manager” means very different things at different shops. Instead, list the outcomes your agency must deliver every month, then assign an owner to each.

For a small paid-social agency, the list might look like this:

• New clients signed
• Clients onboarded within two weeks
• Campaigns launched and optimized
• Creative produced on schedule
• Monthly reports delivered
• Invoices sent and collected
• Clients renewed

Every outcome needs exactly one owner. Several people can contribute, but one name is on the hook. Once the outcomes are assigned, job titles almost write themselves.

Write a one-page role card for each position

A role card is a short, plain document. Long job descriptions get read once during hiring and never again. A single page gets pinned and used.

Role card template

Role: Client Success Lead Reports to: Founder Purpose in one sentence: Keep every client informed, satisfied, and renewing. Owns these outcomes: Onboarding completed, monthly reports delivered, renewals. Key recurring tasks: Weekly client check-ins, report review, renewal meetings. Can decide without asking: Meeting schedules, small scope clarifications, report format. Must escalate: Budget changes, scope additions, any mention of cancelling. Success looks like: Clients reply within a day, reports go out on time, renewals are signed before expiry. Tools used daily: CRM, shared inbox, calendar, reporting dashboards.

The “can decide” and “must escalate” lines matter more than people expect. They remove the owner as a bottleneck for small calls and make it obvious when something needs a second opinion.

Build a RACI chart for shared work

Role cards describe people. A RACI chart describes work that crosses between people. RACI stands for:

• Responsible: Does the work.
• Accountable: Owns the result and signs off. Only one per task.
• Consulted: Gives input before or during.
• Informed: Told when it is done.

Here is an example for an invented agency, Harbor & Pine Digital, with four roles:

Task	Founder	Client Success Lead	Media Buyer	Designer
Sales proposal	A	C	C	I
Client kickoff	I	A/R	C	C
Campaign build	I	C	A/R	C
Ad creative	I	C	C	A/R
Monthly report	I	A	R	I
Budget change request	A	R	C	I
Invoice follow-up	A	R	I	I

Two rules keep the chart useful. First, each row has exactly one A. Second, if one person has an R on nearly every row, you have found your bottleneck.

Document the handoffs

Most dropped balls happen between roles, not within them. For every place where work passes from one person to another, write down three things: what triggers the handoff, what must be included, and how the receiver confirms they have it.

A handoff example at Harbor & Pine:

1. Trigger: A deal is marked won in the CRM.
2. Included: Signed proposal, discovery notes, client goals, access list.
3. Confirmation: The Client Success Lead accepts the onboarding task within one business day.

Tools can carry a lot of this weight. With workflow automation, a won deal can create the onboarding task, assign it to the right person, and attach the notes automatically. The role card says who owns it; the automation makes sure they find out.

Make ownership visible day to day

Documents alone fade. Ownership needs to show up where work happens.

• Assign every task to a named person. Unassigned tasks default to nobody.
• Route client conversations to the owner. A shared inbox with assignment rules keeps clients from bouncing between people. See how a unified inbox handles this.
• Show open items by owner in weekly meetings. A dashboard filtered by person turns accountability into a simple review, not a confrontation.
• Set user permissions to match roles. A designer rarely needs billing access, and a media buyer rarely needs to edit contracts. On SaaSVisionary you can set user roles and permissions so each teammate sees what they need.

Onboard new hires with the role card

When someone joins, their role card becomes the backbone of the first two weeks. A simple plan:

1. Day one: Walk through the role card and RACI chart together.
2. First week: Shadow the current owner of each outcome they will take over.
3. Second week: Take over one outcome fully, with daily check-ins.
4. End of month: Review the card together and adjust anything that turned out wrong.

That last step is valuable. New hires spot gaps that long-time staff have stopped noticing.

Review roles twice a year

Agencies change quickly. New services, new clients, and new tools shift who does what. Put a recurring review on the calendar, every six months or after any major change, and ask each person three questions:

• Which tasks on your card did you not actually do?
• What did you do regularly that is not on your card?
• Where did you wait on someone else most often?

Update the cards and the RACI chart from the answers. The whole review usually takes an hour.

Frequently asked questions

How detailed should agency role descriptions be?

One page per role is the right length for most small agencies. Cover the purpose, owned outcomes, recurring tasks, decision rights, escalation rules, and what success looks like. Anything longer tends to go unread. Put step-by-step instructions for specific tasks in separate process documents and link to them from the role card.

What is a RACI chart and does a small agency need one?

A RACI chart lists shared tasks and marks who is Responsible, Accountable, Consulted, and Informed for each. Small agencies benefit because people wear several hats, which makes it easy to assume someone else owns a task. Even a seven-row chart covering sales, onboarding, delivery, reporting, and billing prevents most confusion.

Who should own client communication in an agency?

Usually one named client lead per account, often called an account manager or client success lead. Specialists can talk to clients directly, but the lead should be copied and should own the relationship. This keeps messages consistent and gives the client one reliable contact, which tends to build trust and reduce mixed signals.

How often should we update roles and responsibilities?

Review them every six months and after any big change, such as a new service line, a key hire, or a departure. Ask each person what they actually did versus what their card says. Small, regular updates keep documents accurate, while waiting years usually means starting from scratch.

Want ownership built into your daily tools? Try SaaSVisionary free for 14 days.