A useful job description identifies the purpose of the role, essential work, decision authority, working relationships, and observable success standards. It should help a manager explain the job and help an employee understand the expected result. Update it when the work changes rather than only when the role becomes vacant.
Retrospective field note: August 2026. Written October 2026.
A job description says "takes ownership." The employee believes that means acting independently; the manager expects approval before every change. Both can point to the same document. Use the drafting method below to replace that ambiguity with the result, authority, and review rhythm the work actually needs.
Start with the result the role exists to produce
Write one sentence connecting the role to a business outcome. Then list the recurring outputs that support it. Avoid turning every activity the current employee performs into an essential part of the job.
The work should describe a real role. Do not build a description around one person's preferred methods or around skills that the organization may want someday.
Distinguish essential work from incidental tasks
Use the appropriate HR review to identify essential functions and required qualifications. The EEOC's performance and disability guidance discusses essential and marginal functions and the relevance of accommodation.
This article offers a drafting method, not a legal determination that a particular requirement is appropriate. Test physical, scheduling, credential, and experience requirements against the actual job and applicable obligations.
Add decision authority
Name the decisions the role can make, the commitments requiring approval, and the situations requiring escalation. Include interfaces with other roles where ambiguity creates repeated conflict.
A fictional coordinator role might prepare a vendor recommendation while the operations leader approves the spending commitment. Without that distinction, the coordinator can become responsible for an outcome they lack authority to deliver.
Use observable success standards
Replace "excellent communication" with a description of the work: who needs what information, by when, and in which form? Replace "takes ownership" with the expected response when a dependency blocks progress.
A useful standard can be discussed using evidence. It should leave room for appropriate ways of performing the work rather than prescribing one person's style.
Try this four-part format:
- The output or responsibility.
- The expected quality or completion condition.
- The relevant timing or review rhythm.
- The person who resolves a conflict or exception.
Check the description with the people doing the work
Ask the manager and employee to identify where the description differs from reality. Note unassigned work, duplicated responsibilities, and duties that migrated into the role without a decision.
Resolve those issues rather than rewriting the document to make every existing arrangement appear intentional. A revised description should reflect a reviewed operating choice.
When should you review it again?
Useful triggers include a reporting-line change, a new service, a changed system, or a recurring disagreement about responsibility. An annual check can support the process, but the work may change sooner.
Review the description alongside onboarding and performance conversations so the same expectations appear throughout the employee experience.
The insight to use: a role description can expose a design decision leadership has avoided. When two people disagree about authority, settle the work arrangement before polishing the wording.
Read performance documentation examples for managers, or explore Work Architecture when the role itself needs examination before the description can be improved.