Job Scope Sample and Work Description Explained for Better Hiring

A job scope defines what a role owns, where its responsibility starts and stops, which decisions it can make and how success will be judged. A work description explains how that scope turns into daily and weekly work. Together they form the internal role definition (often called a job profile) that HR and the hiring manager should agree on before anyone writes the job description candidates will see.

Skipping this step is why so many roles go wrong. The manager pictures one job, the recruiter advertises another and the new hire finds a third on day one. This guide explains each document, gives you a job scope sample and a work description sample you can adapt, and shows how to turn them into a job description without losing anything on the way.

Job scope, work description, job profile and job description: the difference

These four terms are often used loosely. Here is how they fit together.

Document	Audience	Answers the question	Typical length
Job scope	Internal: HR, hiring manager, leadership	What does this role own, decide and deliver, and what is outside it?	Half a page
Work description	Internal, later shared with the new hire	How is the work actually done, with whom, with which tools and how often?	Half a page
Job profile	Internal	The combined role definition: purpose, scope, work, skills, reporting line and success criteria	One to two pages
Job description	External: candidates	Is this job right for me, and should I apply?	One page or less

In short, the job profile is the foundation and the job description is the advert built on it. The profile is written in plain, honest internal language. The job description translates the same facts into candidate-friendly words.

When you need to define the role first

Not every hire needs a fresh role definition. You should write or refresh one when:

• The role is new. Nobody has done it before, so expectations exist only in the manager’s head.
• You are replacing someone who stretched the role. The previous person may have picked up work that should be split or dropped.
• The team has been restructured. Responsibilities may now overlap with another role.
• Two managers disagree about the hire. A written scope settles the argument before candidates are involved.
• The last hire for this role did not work out. Unclear scope is a common, fixable cause.

The seven parts of a strong job scope

1. Purpose

One or two sentences on why the role exists and what problem it solves for the business. If you cannot write this, the role is not ready to be hired for.

2. Ownership

The areas, processes or results the role is accountable for. Write them as nouns the person will own (“the monthly payroll run”, “renewals for mid-market accounts”), not activities.

3. Boundaries

What the role does not own, and who does. This single line prevents more friction than any other part of the scope.

4. Decision rights

Which decisions the role makes alone, which it recommends and which it only contributes to. Use the levels below so everyone reads them the same way.

Level	Meaning	Example
Decides	Makes the call without approval	Approves refunds up to a set limit
Recommends	Proposes; someone else approves	Proposes the quarterly training plan to the HR head
Contributes	Gives input that is considered	Feeds customer insight into the product roadmap
Informed	Is told after the decision	Hears about pricing changes before they go live

5. Key outcomes and measures

Three to five results the role must deliver, each with a way to tell whether it was achieved. These later become the person’s KRAs; our guide to setting KRAs and KPIs employees can act on shows how to turn them into measurable goals.

6. Stakeholders

The internal teams and external parties the role works with most, and in what capacity.

7. Resources

Reporting line, direct reports, budget (if any) and the main tools or systems. This tells you the level of the role more reliably than the title does.

Job scope sample

Example: a hypothetical job scope for a Customer Success Manager at a software company with around 80 employees.

• Purpose: keep mid-sized customers using the product successfully so that they renew and expand.
• Owns: onboarding of new mid-sized accounts after the sale; quarterly account reviews; renewal of a portfolio of about 40 accounts; the customer health score for that portfolio.
• Does not own: technical support tickets (Support team); new-business sales (Sales team); contract and pricing exceptions (Head of Revenue).
• Decision rights: decides the onboarding plan and meeting cadence for each account; recommends discounts at renewal; contributes to the product roadmap through monthly feedback reports; informed of pricing changes.
• Key outcomes: new accounts live on the product within an agreed onboarding period; renewals closed before the contract end date; at-risk accounts flagged with a recovery plan; one documented case of product feedback adopted per quarter.
• Stakeholders: Sales (handover), Support (escalations), Product (feedback), Finance (invoicing queries).
• Resources: reports to the Head of Customer Success; no direct reports; uses the CRM, the support desk and the product analytics dashboard.

Work description sample

The work description takes the same role and shows its rhythm. A simple way is to describe it by frequency.

Example: the work description for the same hypothetical Customer Success Manager.

Frequency	Work
Daily	Respond to customer emails and calls; check health-score alerts; join one or two onboarding calls
Weekly	Team pipeline review; renewal forecast update; sync with Support on escalated tickets
Monthly	Product feedback report; review of usage trends across the portfolio
Quarterly	Business reviews with each account; renewal planning for the next quarter

Add working conditions that affect fit: travel, shift timings, on-call duties, time-zone overlap with overseas customers, or physical demands. These belong in the job description too, so candidates are not surprised later.

The intake conversation: questions to ask the hiring manager

Most of the job profile comes out of one structured conversation between HR and the hiring manager. These questions get you there in about 45 minutes:

1. What will be different in the business 12 months after this person joins?
2. What are the three things this person must get right in the first 90 days?
3. What does this role not do, even though people might expect it to?
4. Which decisions can they take without asking you?
5. Who will they work with every week, and where could there be friction?
6. What skills must they have on day one, and what can we teach?
7. Think of someone who did this kind of job well. What did they do differently?
8. How will you judge, at six months, whether the hire was right?

The answers to questions 6 and 7 also give you interview criteria. Our article on interview questions that help hiring teams decide shows how to turn them into structured questions.

From job profile to job description

Once the profile is agreed, writing the job description becomes a translation exercise. Map each part across:

Job profile section	Becomes this in the job description
Purpose	The opening role summary
Ownership and key outcomes	Key responsibilities, written as outcomes
Work description	A “what a typical week looks like” line, plus working conditions
Day-one skills	Must-have requirements
Teachable skills	Nice-to-have requirements
Resources and reporting line	Reporting line, team size and tools
Boundaries and decision rights	Usually kept internal, but a short line on autonomy helps senior candidates

For the external document itself, use our employee job description template. For the responsibilities section, our guide to writing job duties and responsibilities has verb lists and examples by role.

Common mistakes when defining a role

• Mixing scope with tasks. A scope that reads like a to-do list hides what the role is accountable for. Keep ownership and daily work in separate sections.
• Designing a role for two people. If the ownership list spans unrelated areas (say, payroll and office administration and recruitment), you may need two roles or a clear priority order.
• Leaving out boundaries. Without them, overlap with neighboring roles shows up as conflict a few months later.
• Writing success as effort. “Works hard on renewals” cannot be judged. “Renewals closed before contract end” can.
• Copying the last person’s job. Write the role the team needs now, not the role someone shaped around their strengths.
• Treating the profile as one-time paperwork. It should be reused for onboarding, goal setting and reviews.

Keep the role definition working after the hire

A good job profile keeps paying off. Share the scope and work description with the new joiner in the first week so they know what they own and who to go to; our article on what a complete onboarding checklist covers shows where this fits. Use the key outcomes as the starting point for goals, and review the profile at confirmation, at each annual review and whenever the team changes shape.

When the profile is ready, the HRTailor.AI Job Description Maker can turn the job title, industry, experience level and the must-have points you have agreed into an editable job description draft. Paste in the outcomes and requirements from your profile so the draft reflects the role you defined, then review it before publishing.

Related reading