A logistics company in Pune needs to hire a dispatch supervisor for its second warehouse. The existing job description, found in a folder, says “supervises dispatch operations and ensures timely delivery”. It was written years ago for a different site. Nobody can say what the person actually does. That is the situation job analysis is for, so let us follow it from the first visit to the finished documents.
Step 1: decide what you are trying to learn
Job analysis is the systematic collection of facts about a job: tasks, the context they happen in, the tools used, and what a person needs in order to do them well. It is about the job, not the person currently holding it. That distinction matters, because the current supervisor, Ravi, is excellent and has done the job for eight years. If you simply write down what Ravi does, you will describe Ravi.
The output you want is two documents. A job description states the purpose, duties, reporting line and conditions of the role. A job specification states the qualifications, knowledge, skills and attributes a candidate should have. People mix them up constantly, and the usual result is a posting that lists duties where requirements should be.
Step 2: collect data using more than one method
Each method has a blind spot, so use at least two.
- Observation: the analyst spends a full shift on the dock. This shows things nobody mentions, such as that the supervisor spends the first hour reconciling vehicle arrival slips against the plan. It is slow and poor for rare events, like the monthly stock audit.
- Interview: talk to Ravi, his manager and two dispatch clerks. Interviews reveal reasons and exceptions, but people inflate their importance or forget routine tasks.
- Questionnaire: a short structured form on task frequency, to check how widely the interview claims hold.
- Records: shift handover logs, WMS reports, incident registers. They tell you what actually happened rather than what people remember.
Suppose observation shows Ravi spends roughly two hours a day resolving driver disputes about loading order. Nobody listed that in the interview, because it feels like noise. Yet it shapes the requirements: patience, firmness, ability to speak with drivers in Marathi and Hindi.
Step 3: separate tasks from duties
Raw notes list dozens of tasks: checking slips, assigning docks, calling transporters, signing gate passes. Group related tasks into five or six duties with a clear outcome each. “Plans and runs daily outbound loading so that scheduled vehicles leave on time” is a duty. “Signs gate passes” is a task under it.
Then ask of each duty: how often, how important, and what happens if it is done badly. A task done twice a year but with severe consequences (customs documentation, say) may still deserve a line. A daily task with no consequence may not.
Step 4: write the description
The final draft has a title, a purpose in one or two sentences, the reporting line (reports to warehouse manager; supervises 12 loaders and 3 dispatch clerks), the main duties, key interfaces such as transporters and customer service, working conditions (rotating shifts, physical environment), and scope: decision limits, safety responsibility, any budget authority. Use verbs that say what is achieved. Avoid “assists in” and “responsible for”, which hide the real accountability.
Step 5: write the specification, and be strict with yourself
Now the question is what a candidate needs, not what Ravi happens to have. Ravi has a B.Com and learned everything on the job. Does the role really require a degree? Probably not; what it requires is comfort with a warehouse system, basic numeracy for reconciliations, a working knowledge of loading safety and some experience leading a crew. Writing “graduate” because everyone else does it excludes capable candidates, and in some roles, it may not be defensible.
Split requirements into essential and desirable. Essential: at least three years in warehouse or dispatch work, one year leading a team, fluency in a local language. Desirable: experience with a specific WMS, forklift safety certificate. Anything that is only a preference should not sit in the essential list.
Step 6: check it, then use it
Show the draft to Ravi and his manager and ask what is wrong, missing or overstated. Employees often catch tasks the analyst missed; managers catch aspirations dressed up as duties. Date the document and set a review point, perhaps yearly or when the process changes. A description that is not reviewed turns back into the folder document you started with.
The finished pair feeds more than hiring. The description anchors job evaluation and grading, the specification shapes interview questions and screening, and the duties become the basis for performance goals. That reuse is the reason the work is worth doing carefully.
Figures and names in the examples are illustrative.
Leave a Reply