Blog / hiring

Audit a job posting for duties the team no longer performs

A posting audit that compares the published duties with the work the team actually does, so new hires are not hired into a role that has quietly changed.

Published:

Editorial illustration for Audit a job posting for duties the team no longer performs
In this article

Published November 16, 2026.

A job posting can outlive the job it describes. Tasks move to another team, a system replaces a manual step, and a temporary duty becomes permanent without anyone rewriting the advertisement. The posting keeps attracting people who expect the old role, and the first week becomes a negotiation about what the job really is. An audit compares the published duties with the work the team does now. It is a small exercise that prevents a large mismatch.

Start from the work, not the posting

Ask three people who do the job today to list what they actually did last week. Use a simple prompt and let them answer in their own words. Do not show them the posting first, because it will anchor their answers to the old description. Compare the lists after each person has written independently.

Include the person who supervises the role and the person who receives its output. A supervisor sees the assignments, while a customer or downstream team sees the result. Their views often reveal duties that the job holder has stopped mentioning. A task that everyone assumes is covered may have quietly disappeared.

Count how often each duty appears in a normal week. A task that happens once a quarter should not dominate the posting. A task that fills half of every shift should not be buried in a final line. Frequency is a rough but useful guide to what the role really is.

Look for duties that moved away

List the duties in the current posting and mark each one as still performed, moved, or gone. A moved duty belongs to another role now, even if the old role still helps out occasionally. A gone duty may have been replaced by a system or dropped altogether. The mark should reflect the normal case rather than an emergency exception.

Ask where each moved duty went and whether the handoff is working. A duty that moved without a clear owner can fall between teams. That gap may explain a quality problem or a complaint that the posting never mentions. The audit is a chance to surface the orphaned work.

Check the tools and systems named in the posting. A role that still lists a retired system will attract people with the wrong experience. It will also signal to current staff that the posting is not maintained. Update the tool list and the level of proficiency the role actually needs.

Separate the essential from the occasional

Mark each duty as essential, occasional, or no longer relevant. An essential duty is one the role cannot perform without, while an occasional duty is real but not weekly. The label helps a candidate understand the shape of the job. It also helps an interviewer ask about the right experience.

Do not let a long list of occasional duties hide the core of the role. A posting that lists twenty small tasks can read as a role with no focus. Group related duties into a few clear areas and name the main one first. A candidate should be able to repeat the core of the job after one reading.

Check whether the posting promises authority that the role does not have. A line about leading a team is misleading if the role only coordinates a schedule. A promise of independent decisions is misleading if every choice needs approval. Remove the inflated language and describe the real scope.

Compare the posting with the first-week reality

Read the posting next to the onboarding plan for the same role. The first week should deliver the tools, access, and training the posting implies. A mismatch here is a common source of early disappointment. The new hire arrives expecting one job and receives another.

Ask recent hires which parts of the posting matched their experience and which did not. Their answers are more useful than a survey about satisfaction. A recent hire remembers the specific gap between the promise and the first assignment. Record the gap and fix the posting or the onboarding, whichever is wrong.

Check whether the posting's language matches the team's actual schedule. A posting that implies fixed daytime hours will attract people who cannot work evenings. If the role rotates, say so clearly and describe the pattern. Ambiguity here produces a resignation in the first month.

Rewrite for accuracy rather than appeal

Rewrite the posting in plain language that a person outside the company can understand. Replace internal titles and acronyms with a short explanation. Describe the main duties, the schedule, the physical setting, and the reporting line. Accuracy is more attractive than a polished list of generic qualities.

Keep the requirements proportional to the work. A role that can be learned on the job should not demand years of prior experience. An unnecessary requirement narrows the pool and raises the chance of a mismatch. Remove any requirement that the team cannot explain in a sentence.

State the parts of the job that are hard, and pair each one with the support that exists. A role with frequent customer conflict should say so and describe the escalation path. A role with heavy lifting should describe the equipment and the team lift rule. Honesty about the hard parts builds trust before the first day.

Test the revised posting with real candidates

Show the revised posting to two or three people who are not on the team and ask what job they think it describes. Their summary is a quick test of whether the posting communicates the role. If their summary misses the core duty, the posting needs another pass. This step is faster than waiting for a bad hire to reveal the problem.

Ask a recent candidate whether the posting matched the interview. A candidate who expected a different job may still have accepted, but the mismatch will surface later. Record the answer and compare it with the next cohort. A pattern of mismatches points to the posting rather than the candidate.

Set a review date for the posting rather than treating the rewrite as final. A quarterly check is enough for most roles, while a role with rapid change may need a shorter cycle. Assign the review to the hiring manager and put it on the calendar. A posting that is reviewed on a schedule does not drift unnoticed.

Use the audit to improve the role itself

Treat a duty that no longer exists as a chance to simplify the role. If a task disappeared, ask whether the remaining duties still make a coherent job. A role can accumulate fragments from several old jobs and become hard to learn. The audit may reveal that the role should be redesigned rather than re-advertised.

Share the revised description with the current team before publishing it. The people doing the work will notice an error faster than a reviewer. Their corrections also give them a stake in the new version. A posting that the team recognizes is more likely to attract a colleague who fits.

Keep the audit notes with the posting file so the next reviewer can see what changed. A short record of the duties removed and the reason is enough. The record prevents the old language from creeping back. It also shows a candidate that the role has been thought through.