How to write a job description that defines accountability, not tasks

An employee tells his manager that something is not his job. Both of them are annoyed, both of them are partly right, and neither can point to a document that settles it. The job description exists — it was written to advertise the vacancy three years ago and lists eleven bullet points beginning with the word "handle".

That document was never going to settle anything, because it describes activity rather than accountability. Activity lists always have gaps, and the gaps are exactly where the argument happens.

The difference in one line

"Handles vendor coordination" is a task. "Materials are on site before the line needs them" is an accountability. The first can be done diligently while the outcome fails. The second cannot.

The practical test: read the line and ask what would be wrong if nobody did this. If the answer is "a task would be undone", it is a task. If the answer is "an outcome the business needs would not happen", it is an accountability.

Four things a description must settle

1. 1

   What the role owns

   Three to six outcomes, written as states of the world rather than as verbs. Not "prepares the monthly report" but "management has accurate headcount and cost figures by the fifth working day". Six is a maximum; roles with eleven accountabilities have none.

2. 2

   What the role decides

   What this person may settle without asking, and what they must escalate. This is the section most descriptions omit entirely, and it is the one employees most want. It should match the approval matrix rather than contradict it.

3. 3

   Who the role works with

   Which other roles it depends on and which depend on it. Most inter-departmental friction traces to a dependency neither side had written down.

4. 4

   How the role is judged

   The measures, stated plainly. If a role has accountabilities that nothing measures, either add the measure or accept that the accountability is aspirational.

A format that fits on a page

ROLE:            ______________________
REPORTS TO:      ______________________
DEPARTMENT:      ______  LOCATION: ______  GRADE: ______

PURPOSE (one sentence: why this role exists)
  ____________________________________________________

ACCOUNTABILITIES (3-6 outcomes, not activities)
  1. ____________________________________________
  2. ____________________________________________
  3. ____________________________________________

DECIDES WITHOUT ASKING          ESCALATES
  ____________________            ____________________
  ____________________            ____________________

WORKS WITH (role, and what each needs from the other)
  ____________________________________________________

MEASURED ON
  ____________________________________________________

REQUIRES (qualification, experience, competencies)
  ____________________________________________________

Note there is no "any other duties as assigned" line. That phrase is where accountability goes to be quietly removed, and every employee reads it as exactly that.

Write it before the vacancy, not for it

A description written in a hurry to post an advertisement is written to attract, not to define. It inherits whatever the last similar advertisement said, and it never matches what the role actually becomes once somebody is in it.

Written before hiring, it does three jobs at once: it defines the role, it gives the interview something to assess against, and it becomes the basis of the first appraisal. Written afterwards, it does none of them — which is why role design and job descriptions work starts from what the business needs owned rather than from the vacancy that triggered the conversation.

Fixing the ones you already have

Do not rewrite everything. Two situations justify the effort, and the rest can wait for a natural trigger.

• Where two people share a designation and do different jobs. That is two roles wearing one title, and it will surface at appraisal or increment time.
• Where an argument has already happened about whose job something is. Write that one immediately, while both parties remember the specifics.
• On a natural trigger otherwise — when the role next falls vacant, when someone is promoted into it, or when the structure changes. Rewriting descriptions nobody is currently disputing is a project that quietly stops.

The two-reader test

Before you accept a description as finished, take an awkward situation that has actually occurred — a customer complaint arriving out of hours, a quality issue found after dispatch, an employee query nobody wants — and ask two people to read the description and say who handles it.

If they disagree, the description has not settled the thing it exists to settle. That usually takes one more sentence, not a rewrite.

Where descriptions connect to everything else

A good description makes several other things easier, which is why it is worth more than the hour it takes. The interview has something to assess against. The appraisal has something to measure. The approval matrix has a role to attach limits to. And the next person into the role inherits a definition rather than a predecessor's habits.

It also exposes structural problems that were previously invisible. Two descriptions claiming the same accountability means the structure is unresolved, not that one description is wrong — and that belongs with organisation design rather than with editing the document. Equally, an accountability that appears in nobody's description is the activity that fails every few months because it was never anyone's job.

And once accountabilities are written as outcomes, the appraisal conversation changes character entirely — from an argument about effort to a discussion about results, which is the point at which role design and job descriptions work starts paying back in something other than tidiness.

Descriptions and the appraisal

The clearest sign a description is doing its job is that the appraisal stops being contested. When a role is defined by outcomes and the measures are stated, a review is a discussion about whether those outcomes happened — which two reasonable people can usually agree on, even when the answer is unwelcome.

Where descriptions are task lists, the appraisal becomes an argument about effort and attitude, because there is nothing else to point at. Managers dislike those conversations, avoid them, and the feedback arrives once a year in a form nobody can act on.

Descriptions for roles that share an outcome

The hardest descriptions to write are for two roles that contribute to the same result, and this is where most accountability language quietly fails.

A sales manager and a delivery manager both affect whether a client renews. Writing that both are accountable for renewals produces a description that reads well and settles nothing, because when a client leaves there is no basis for a conversation with either.

The workable approach is to split the outcome into the parts each genuinely controls. One is accountable for the commercial relationship and the renewal conversation; the other for delivery meeting what was promised. Both affect the result, one owns each half, and a failure can be located without an argument.

Where a genuine outcome cannot be split — and some cannot — the honest answer is to name one accountable role and describe the other as contributing, with a stated obligation to escalate when their part is at risk. That feels unfair to whoever is not named and it is considerably better than joint accountability, which in practice means that when something goes wrong each can reasonably point at the other, and usually does.

So the description is upstream of the performance conversation rather than a parallel piece of paperwork. That is why it is usually worth writing descriptions before touching the appraisal format — a better form over an undefined role changes nothing, which is the mistake most businesses make when they decide to fix performance management.