The Scope of Job Analysis and When It Is Required

Job analysis is the systematic examination of a position's content, the knowledge and competencies it requires, its relationships with other roles and its outputs. The aim is not to record what the person does today, but to define the function of the role within the organization. This distinction matters. Definitions written around the person become void when that person leaves; definitions written around the role retain their validity when the position is handed over.

The circumstances requiring job analysis differ from one another and each demands a different scope. When a new position is created, the analysis is carried out to establish the role's boundaries with other positions. When the organizational structure changes, the distribution of duties across merging or separating departments needs to be redesigned. When the salary structure is to be reviewed, grading positions by job size rests on analysis data. When a performance system is being established, which role a target is assigned to depends on the clarity of role boundaries. Beyond these four circumstances, reviewing job descriptions at defined intervals is also a standard HR practice.

The first decision HR teams make in setting the analysis scope is whether the exercise will cover the whole organization or a specific department. Analysis run across the organization simultaneously provides comparability between positions and creates the coherence required for salary grading; on the other hand it takes longer and uses the HR team's capacity intensively. Department-based analysis produces results faster but makes comparison of exercises conducted in different periods more difficult. In a phased approach, a common analysis format is set across the organization and departments are addressed in sequence; because the format remains fixed, the results stay combinable.

Who will conduct the exercise becomes clear alongside the scope decision. Job analysis conducted entirely by the HR team secures format coherence but carries the risk of insufficient penetration into the technical content of departments. Where the work is left to department heads the technical content is strong, but formats diverge and results become non-comparable. The method that works in practice is for HR to take ownership of format and method, for a designated liaison from each department to carry out technical validation, and for descriptions to be finalised by HR. Sharing these roles in writing at the outset prevents approval ambiguities arising during the work.

In scheduling the exercise, the time per position needs to be estimated realistically. The sum of the questionnaire, interview, manager validation and writing stages requires three to four hours of HR effort for a position of medium complexity. On this basis a scope of one hundred positions creates a load that cannot be carried single-handedly; dividing the scope into periods or allocating work within the team is decided at the planning stage.

Taking an inventory of the current position before analysis allows the exercise to be planned realistically. Answers to the questions of how many positions have written job descriptions, how many of these have been updated within the past three years, and which departments have no descriptions at all provide the basis for prioritisation. The inventory exercise also makes title confusion visible: positions doing the same work being defined under different titles, or roles of differing job size carrying the same title, are topics to be addressed during the analysis.

Data Collection Methods and Implementation Sequence

The data collection method used in job analysis is chosen according to the nature of the position and the scope of the exercise. Analysis conducted with a single method remains incomplete; using several sources together ensures both that content is verified and that different perspectives are recorded.

The principal methods used in practice are as follows:

•     Structured questionnaire: The position holder is asked standard questions on their task list, time distribution, decision authorities and the units they communicate with. It allows a large number of positions to be surveyed in a short time; however, written responses often contain general statements and do not produce sufficient detail on their own.

•     Interview: In a face-to-face interview with the position holder, questionnaire responses are deepened. What inputs start the task, which decisions rest with the position holder and to whom which output is delivered are set out in detail.

•     Manager validation: In an interview with the manager to whom the position reports, the expected content of the role is compared with its actual content. Differences between the two sides are the most direct indicator of role clarity problems.

•     Observation: In operational and field positions, following the flow of work on site reveals intermediate steps not visible in written sources.

•     Document review: Process flow charts, work instructions, authority matrices and reporting samples allow declaration-based information to be verified.

The sequence in which methods are applied affects the result. Starting with document review allows the interview to be entered well prepared and shortens interview time. Applying the questionnaire before the interview gives the position holder the opportunity to think through their duties in advance. Manager validation is left to last; this way differences between the position holder's account and the manager's expectation can be addressed in the same session.

A common difficulty HR teams face during data collection is that position holders perceive the exercise as an evaluation. This perception leads to duties being declared more broadly than they are, or to some duties being omitted. Announcing the purpose of the exercise in writing at the outset, stating clearly how the results will relate to salary or headcount decisions, and running interviews in a standard format reduce this risk.

Preparing the interview question set in advance ensures that sessions run by different interviewers produce comparable output. The question set is designed to cover the task's input and output, decision points, systems and tools used, units contacted, recurring difficulties encountered, and aspects of the position that have changed in the past two years. The last topic is particularly valuable; it shows how the role has evolved and allows the description to be written so that it also covers the period ahead.

In processing the data collected during analysis, recording duties together with frequency and duration information is important. A duty performed once a year and a duty carried out daily appearing with equal weight on the same list does not reflect the real content of the role. Recording the time distribution as a percentage provides data both for prioritising the job description and for workload assessment at the following stage. When the scope of the analysis is addressed alongside succession work, the succession plan prepared for critical positions is also fed from the same data set.

Writing the Job Analysis: Structure and Language

Once analysis data is collected, the job description is written. A usable job description consists of defined sections, and each section serves a different function. Before moving to the writing stage, the task items collected in the analysis need to be grouped. Raw data often contains a large number of items that are sub-steps of one another. Gathering these items under the areas of responsibility whose outputs they jointly produce both increases the readability of the description and clarifies which headings performance targets will be tied to.

The position identity section contains the title, the position reported to, reporting positions, the department and grade information. This section should be exactly consistent with the organization chart; a reporting relationship appearing in the job description but not on the chart indicates that the structure operates differently in practice, and that gap needs to be resolved first.

The purpose of the position section defines the role's function within the organization in two or three sentences. It is essential that this section is not a summary of the task list; the purpose explains what outcome the role serves. "To carry out purchasing processes" is a task statement; "to ensure that the materials required by the production plan are procured on time under defined quality and cost conditions" is a purpose statement.

In the duties and responsibilities section, the duties identified in the analysis are written as items beginning with an action verb. Each item should have an output; a task item whose output cannot be defined is usually part of another item. Keeping the number of items limited increases the usability of the description. A list of thirty items may cover the whole of daily work but does not show the priorities of the role; eight to twelve main responsibility items provide sufficient resolution for most positions.

The authority section defines which decisions the position can take alone, on which it makes recommendations and on which it obtains approval. In most job descriptions this section is either left blank or covered with general statements; yet the absence of written authority limits is among the principal sources of delay in decision processes. Financial limits, signature authorities and the level of authority over personnel decisions are stated concretely in this section.

The required qualifications section covers education, experience, technical knowledge and competency requirements. The point to attend to in writing this section is that the characteristics of the current position holder should not be converted into a qualifications list. The minimum conditions the role requires and the qualifications the present incumbent happens to hold are different sets; confusing the two narrows the recruitment pool unnecessarily.

The working relationships section shows which parties inside and outside the organization the position is in regular contact with, and for what purpose that contact takes place. This section is neglected in most descriptions; yet a significant proportion of disputes over role boundaries arise from two positions contacting the same stakeholder for different reasons. Writing relationships together with their purpose allows these disputes to be resolved in advance.

Setting an internal standard on the length of job descriptions is also useful. Descriptions running beyond two pages are not read in practice; descriptions compressed onto a single page lead to the authority and relationships sections being cut. A volume of one and a half to two pages is sufficient for most positions to carry all sections. Fixing the template within HR also removes formatting differences between departments.

The language of job descriptions should be consistent across the organization. The casual use of "coordinates" in one position, "is responsible for" in another and "follows up" in a third at the same level makes comparison between grades difficult. HR teams setting a standard verb set before the analysis and using it in all descriptions makes subsequent grading and salary work easier.

Connecting Job Descriptions to Systems and Keeping Them Current

The value of a job description is measured by the systems it is connected to. A description without connections stays in the file and loses currency over time.

On the recruitment side, the job description is the source of the advertisement text and the interview assessment form. The required qualifications section determines which areas interview questions will cover; the task items form the framework of the experience questions put to candidates. Where this connection is established, different interviewers assessing the same position against different criteria is prevented.

On the performance management side, the job description forms the ground on which targets are assigned. Setting an employee a target on an output not appearing in their job description produces an assessment that is difficult to justify at period end. The reverse also holds: target sets corresponding to none of the main responsibility areas in the job description push the real function of the role into the background.

On the training planning side, the gap between the competency requirements in the job description and the employee's current level is the source of the training need. Training calendars created without this comparison take shape according to demand and become detached from role requirements. On the salary structure side, job descriptions are the input to job evaluation. Grading positions by scope of responsibility, decision impact and required knowledge level is only possible where descriptions are written in the same format and at the same level of detail.

The legal dimension of job descriptions is another topic HR teams take into account. A job description signed as an annex to the employment contract forms a basis regarding the parties' obligations; on the other hand, descriptions written in great detail can limit flexibility when duties change. The approach preferred in practice is to write main areas of responsibility in detail and daily work steps in general terms. This balance both preserves role clarity and leaves room for the distribution of duties to be adapted to organizational needs.

How job descriptions are shared with employees also affects the outcome. A description signed only at induction and filed away limits its function to the moment of hiring. Keeping the description in an environment the employee can access, raising it in the period-opening target conversation and sharing the updated version when duties change turns the document into a reference that is actually used.

Keeping descriptions current requires responsibility to be defined. A workable approach is to make review of the job description a step in the annual performance cycle; in the period-opening target conversation the manager and employee confirm together whether the description remains valid and pass any proposed change to HR. Alongside this, adding job description updates to the completion steps of organizational change, new system implementation and process improvement work prevents the gap from widening. Designing job descriptions with these connections in place within HR systems setup work markedly reduces the corrective burden later on.

How the results of the exercise are communicated internally is also part of planning. Job analysis work, where the scope is broad, can create expectations of headcount or salary change. Sharing the purpose, scope and the decisions in which results will be used in writing at the start, and communicating the outputs obtained and the next steps to department heads on completion, allows this expectation to be managed. The information gap arising where no communication is made produces interpretations independent of the exercise itself and also affects participation in the next HR initiative.

At Kaan Böke Management Consulting, we run job analysis work end to end — from the design of data collection to the writing of job descriptions and the establishment of their connections with HR systems. With 35+ years of corporate experience and a 25+ year C-level leadership perspective, we deliver strategic and actionable solutions. To assess your organization's role clarity needs together, you can get in touch with us.