How to Write Roles and Responsibilities People Actually Follow
Most roles and responsibilities documents get written once, filed, and forgotten. A few changes make them worth opening.

Somewhere in your company's shared drive, there's a document called Roles and Responsibilities. Odds are it was written during a reorganization, or for a consultant, or because someone read that you were supposed to have one. It runs several pages. It uses the word "oversee" a lot. And nobody has opened it since.
We don't say that to be snarky. (Okay, a little.) We say it because the problem isn't that companies don't write these documents. It's that they're written in a way nobody can use.
The trouble with duties
Most roles and responsibilities documents are lists of duties: "Oversees scheduling." "Supports the sales team." "Coordinates with accounting on billing." Each line sounds reasonable. Together, they describe a job without ever saying what the job is for.
Look closely at the verbs. Oversee, support, coordinate, assist, manage. They describe activity, not results. You could do every one of them all day and still not know whether you did the job well. So could your manager.
Write outcomes, not activities
The first fix is to start each role with what it owns, written as a result:
- Not "oversees scheduling," but "every job is scheduled within two business days of the sale."
- Not "supports the sales team," but "every quote goes out within a day of the request."
- Not "coordinates with accounting," but "finished work is ready to bill by the end of the next day."
Specific outcomes do two useful things. They tell the person what success looks like, and they make it obvious when two roles claim the same result, or when nobody claims it at all.
Add what each role owes, and to whom
Here's the part almost every template leaves out. No role works alone. The scheduler can't schedule a job sales never entered. The billing clerk can't bill work the technician never closed out.
So for each role, write down what it owes other people, and when:
- Sales owes scheduling a complete order, with the customer's requirements, at the time of sale.
- Technicians owe the office closed work orders with notes, the same day.
- The office owes accounting a billing-ready package within one business day.
This is where most real problems hide. Everybody knows their own job. Far fewer people know what the next person is waiting on.
And what each role needs
The flip side of what a role owes is what it needs: the information, decisions, tools, and authority it takes to deliver. If the scheduler needs a final scope before booking a crew, write that down too, along with who provides it.
Owe and need together turn a stack of separate job descriptions into one connected picture of how the work moves. (If you use a RACI chart, this is exactly what the chart leaves out.)
Keep it short enough to read
A useful roles document fits on a page or two per role. Here's a simple structure:
- Purpose. One sentence on why the role exists.
- Owns. Three to five outcomes, written as results.
- Decides. What the role can decide without asking anyone.
- Owes. What it delivers to other roles, and when.
- Needs. What it depends on from other roles, and from whom.
That's it. If it doesn't fit, the role is probably two roles.
Then actually use it
Pull it out when you hire, so the new person knows what they're walking into. Pull it out at reviews, so feedback is about results and not impressions. Pull it out whenever two people argue about whose job something is, which happens more often than anyone likes to admit.
A roles document that lives in a drawer is a nice record of good intentions. One that gets used is how a company stops arguing about whose job something is and starts getting it done.