Skip forward into hiring notes
RosterAcorn

3 tests for each job requirement before you post it

Run three tests on every requirement before you post it: whether other staff could take over the task, whether the requirement is job-related and consistent with business necessity, and whether it targets the skill the job actually needs. The second test is the one the sources here state as a standard, because a requirement that has an adverse impact on a protected group must meet that standard. The EEOC's guidance on race and color discrimination gives the rule and examples.

> Sharp takeaways > > - Name the duty that makes the job exist before you write any requirement. > If most current staff can already take over a task, treat the requirement as a preference. > - A requirement with adverse impact must be job-related and consistent with business necessity. > - Write schedule and quota demands with exact hours and minimums.

Start with the duty that makes the job exist

Every requirement in a job post should trace back to a duty the job performs. The fastest way to find that duty is to ask why the position exists. The Job Accommodation Network's job description topics page gives a proofreading example that makes the point: "The ability to proofread accurately is an essential function, because this is the reason that this position exists." The sentence does not justify the skill by saying it sounds professional. It ties the skill to the reason the role exists, and that link is what makes it essential. Well-developed assessment tools allow agencies to specifically target the competencies and skills they seek. ( opm.gov)

Apply the same logic to your own drafts. Write the purpose of the role in one plain sentence before you list any requirements. A proofreader's purpose is accurate text. If accuracy is the purpose, accuracy is an essential function and belongs in the list. If you cannot name a purpose that a requirement serves, the requirement probably came from an old posting, a habit of the hiring manager, or a competitor's listing, and nobody has checked it against the work.

The same page also presents numbered situations. One opens with "Situation 2: The new Food Service Manager is a person who has multiple sclerosis." The scenario is a reminder that a job description should describe the work the job requires, not the particular person who might fill it. A requirement written around a person's features, rather than a duty, stops measuring the job and starts measuring the person.

A practical exercise makes this concrete. Take each requirement in your current draft and attach a one-line duty statement. Use verbs and outcomes, such as "reconciles the weekly register against deposits" or "answers the phone during store hours." If a line cannot be written as a duty, flag it. The requirements that survive this step must then be tested against all three tests: test one, test two, and test three.

Test one: Can other staff take over the task?

The first test asks whether the duty could be shared. The JAN page states the condition this way: "There are a limited number of other employees available to perform the function, or among whom the function can be distributed." The sentence describes two conditions under which a function stays fixed to one person: few other employees can perform it, or it cannot be distributed among them. Either few employees can perform it, or it cannot be spread among the people who are there. When many employees can do the task, or it can be divided among them, the task is less likely to define the job. When few can do it, the task may be central.

Run this test on every duty you confirmed in the first step, and answer three questions in writing. How many current staff already do this work well? Could a colleague cover it during an ordinary week, not only during an emergency? Is the skill a real need of the job, or is it a convenience the team has grown used to? Put the answers beside the requirement. If most of the team already does the task and the rest could learn it, the honest label is usually a preference, not a must-have.

Small firms feel this test more sharply than large ones. A three-person office can look as if every task belongs to one person, when the work could be shared with some reorganizing. That does not mean every task can be shared. It means the decision should follow from the count rather than from a feeling about who does what. Where the count is high, drop the requirement or move it to the preferred list. Where the count is low, keep the requirement and be ready to explain why nobody else can take it on.

The second test carries legal force. The EEOC's guidance on race and color discrimination gives a clear example of a physical rule: "For example, a requirement that employees be at least six feet tall might have an adverse impact on Asian Americans due to average height and weight differences, and thus such a requirement would need to be job-related and consistent with business necessity." The sentence has two parts that matter for a hiring manager. First, a requirement can cause an adverse impact even when no one intended it. Second, the employer must then show that the requirement is job-related and consistent with business necessity.

A requirement that screens people out, such as a physical standard, must be job-related and consistent with business necessity, so it needs a reason tied to the work. A height minimum needs a reason such as reaching a shelf the job requires you to reach. A preference for a certain look needs a reason tied to the job, or it should go. The test does not ask whether the rule seems reasonable to you. It asks whether the rule is connected to the work and necessary to doing it.

Before posting, write the reason in one sentence and check that the sentence describes the work, not the person. "Must reach the top shelf of the stock room" describes work. "Must look polished for clients" describes an impression and needs more evidence. Keep the reason beside the requirement in your file, so that if an applicant or agency asks, you can answer from the record rather than from memory.

Comparing a rule you can defend with one you cannot

The proofreading requirement and the six-foot height rule look different on the surface, but the same measures sort them. Both are concrete and easy to write. The table sets them side by side on the points the sources state.

MeasureProofreading accurately Height of at least six feet
Source's wording"an essential function, because this is the reason that this position exists" Might have "an adverse impact on Asian Americans" and "would need to be job-related and consistent with business necessity"
Stated figureNone given At least six feet
Standard appliedThe reason the position existsJob-related and consistent with business necessity
What the employer needs to showA link between the skill and the position's purposeA job reason that requires the height

Use the last two rows as your filter. A requirement passes when you can answer the "what the employer needs to show" row with a specific reason from the work. The proofreading line answers from the purpose of the role. The height line answers only when the work actually requires that height. The EEOC example does not declare six feet unlawful. It says the requirement would need justification, and that is the difference between a rule you can defend and one you cannot.

The comparison also shows why a figure needs a reason attached to it. The proofreading requirement has no number, so the only question is whether the skill serves the role. The height rule has a number, and the number has to be justified before it appears in a post. Any figure you add to a requirement should be held to the same standard as the height example.

Why a beard rule needs an exception path

Grooming rules are often copied from an old handbook without a second look. The EEOC's race and color guidance addresses one directly: "However, Title VII requires an employer to make exceptions to a no-beard policy for men with pseudofolliculitis barbae, an inflammatory skin condition that occurs primarily in Black men and that is caused by shaving, unless being clean-shaven is job-related and consistent with business necessity (see Example 9 and accompanying footnote)." The guidance section treats the exception as the default, not as a favor.

For a posting, the sentence sets two obligations. A no-beard or clean-shaven line in your draft needs a stated job reason, not a preference. And the policy needs an exception path for men with that condition, unless clean-shaven status is job-related and consistent with business necessity.

Work through the check. Ask whether the clean-shaven standard exists because the work has a safety, hygiene, or customer-facing need. If the only reason is "we have always looked this way," the requirement has no reason yet. Write the exception path into the policy text itself, so the hiring manager and the applicant read the same rule. The guidance points to a numbered example and a footnote, which shows that the rule is worked out through specific cases, not one sentence.

Set schedule and quota demands as written in the post

Schedule and sales-target requirements are often written loosely: "must be out in the field most days" or "strong call volume." The EEOC's guidance uses a more precise policy as an example: "Company policy requires sales representatives to be in the field from 8:30 a.m. to 5:30 p.m., and that they make sales calls on at least seven clients each and every day." The same guidance section includes a sales policy that states a window and a minimum.

DemandFigure in the quoted policy What your post should state
Time in the field8:30 a.m. to 5:30 p.m.The exact window, not "most of the day"
Client contact At least seven clientsThe minimum count, not "strong call volume"
FrequencyEach and every day Whether the minimum applies daily or on a set schedule

The lesson is to write the demand the way the policy would state it, with the window, the minimum, and the frequency. A vague demand is hard to defend because a reviewer cannot tell what it required. An exact one can be checked against the work. Before posting, have the hiring manager confirm each figure against the role's current policy. If a figure in the post does not match that policy, correct the post rather than the policy, because the policy is what a new hire will be held to after hiring.

Test three: Does the requirement target what you need?

The third test asks whether a requirement measures the thing the job needs or only something close to it. The Office of Personnel Management puts the goal plainly: "Well-developed assessment tools allow agencies to specifically target the competencies and skills they seek." The word that matters is "specifically." A requirement that targets a named competency tells you what to look for and how to check it. A requirement that only points in the general direction of the job leaves room for guesses, and guesses tend to screen out people who could do the work well.

Start by listing the competencies the job needs in plain terms, such as reading a set of figures accurately, handling customer complaints calmly, or lifting boxes to a high shelf. Then, for each requirement in your draft, name the competency it is supposed to measure. Ask whether the requirement measures that competency directly. A degree may stand in for reading skill, but it measures a credential, not the skill itself. A years-of-experience line may stand in for handling complaints, but it measures time served. When a requirement is only a stand-in, look for a more direct check, such as a short work sample or a structured question about a real situation from the job.

Small firms often know the work well but write requirements from habit. The third test closes that gap. If a requirement does not target a named competency, rewrite it so it does. If you cannot name the competency at all, the requirement is probably not ready for a post.

Why the 1971 court case matters for sex-based rules

Some requirements are about sex rather than a skill or a physical trait. The EEOC's questions and answers on the Uniform Guidelines describe a 1971 decision from the Ninth Circuit that bears on this kind of rule. The court, as the EEOC's questions and answers report it, "held invalid state protective laws which prohibited the employment of women in jobs entailing long hours or heavy labor, because the state laws were in conflict with Title VII."

The passage does not set out a full rule for your firm, and it does not tell you what a court would decide about your own posting. What it does show is that a limit on the work women may do, even one presented as protection, was found to conflict with Title VII in that case. For a hiring manager, the practical lesson is to avoid writing sex-based limits into a job description, including limits framed around hours or heavy labor. If a job involves long hours or heavy lifting, state that as a task requirement, tie it to the work, and apply it the same way to every applicant. Write the reason down next to the requirement, as you would for any other standard in the post.

Which one should you pick?

When a requirement fails one of the tests, you have a few options, and the sources point to different choices depending on the facts. The three options compare as follows.

OptionWhat the sources support Figure given in the source
Keep as a must-haveAccurate proofreading is "an essential function, because this is the reason that this position exists" None
Keep only with a written job reason A requirement that "employees be at least six feet tall" would "need to be job-related and consistent with business necessity"At least six feet
Replace with an exact, checkable demandSales representatives in the field from 8:30 a.m. to 5:30 p.m., making sales calls to "at least seven clients" each day 8:30 a.m. to 5:30 p.m.; seven clients

Choose the first option when a requirement passes all three tests and ties directly to the reason the role exists, as the proofreading example does. Choose the second when a requirement screens people out on a physical or similar standard, and you can state a reason tied to the work. The six-foot example shows that a number needs that justification before it goes into the post. Choose the third when the requirement is a demand on time or output. Write the window and the minimum, as the sales policy does. If a requirement fits none of the three options, drop it.

Keep the accommodation question out of the requirement list

The Job Accommodation Network's job description topics page uses numbered situations to show how a job description should be built. One begins: "Situation 2: The new Food Service Manager is a person who has multiple sclerosis." The scenario puts a specific person's condition next to a job, and the page's lesson is about focus. A job description should describe the work the role requires. It should not be built around the features of the person who might fill it.

Scan your draft for lines that describe a person rather than a duty. A line such as "must be fully healthy" describes a person. A line such as "stands for a full shift at the counter" describes a duty, and it belongs in the post only if the work truly requires it, with a reason written down. Keep the requirement list about tasks, outcomes, and measurable demands.

If an applicant raises a question about how they would perform a duty, handle it as a separate step in the hiring process, not as a line in the posting. Make sure the person who handles those questions at your firm knows the process before interviews begin. The requirement list should give no reason for anyone to guess about a person's health from the wording of the post.

Record each test result before the post goes live

Testing a requirement in your head is not enough. The OPM's guidance makes the case for specificity, and a written record makes the case visible: "Well-developed assessment tools allow agencies to specifically target the competencies and skills they seek." A record shows that you did the work, and it lets someone else check it later.

Make a one-page record for each requirement with five parts. First, the duty statement from the first step. Second, the competency the requirement measures. Third, the answer to the first test, meaning how many current staff could take over the task. Fourth, the job-related reason, written as one sentence about the work. Fifth, the figure and its source, if the requirement includes a number or a schedule. Finish with the outcome: keep as a must-have, keep with a reason, replace with an exact demand, or drop.

Set one rule for the whole draft. A requirement without a complete record does not go into the post. Have the hiring manager sign off on the records, and keep them with the job file. When the post goes live, the records show which requirements were tested, what each one measures, and why it is there.

Related guides: ADA checks: 5 reviews before tests and interviews · 3 California shift terms to put in a job posting · 2 tests a conduct rule must pass before it binds new hires.

Reader questions

Does every requirement need a written reason? Not every one needs a long explanation, but a requirement that screens people out does need a job-related reason. The EEOC's height example says such a requirement "would need to be job-related and consistent with business necessity," so a one-sentence reason tied to the work belongs on file.

What if most of my staff can already do the task? The JAN page frames the question around how many other employees can perform a function or share it. When many can do it, the task is less likely to define the job, and the requirement should move to the preferred list or be dropped.

Can I post a height minimum? The EEOC example does not declare a height requirement unlawful. It says such a requirement would need to be job-related and consistent with business necessity. If the work truly requires a certain reach, write that reason beside the figure before it goes into the post.

Do I need to make exceptions to a grooming rule? The EEOC's race and color guidance says Title VII requires exceptions to a no-beard policy for men with pseudofolliculitis barbae, unless being clean-shaven is job-related and consistent with business necessity. Check any grooming rule against that sentence before you post it.

Can I state a schedule loosely? The sales example in the EEOC guidance gives an exact window and a minimum. A loose phrase like "most of the day" is harder to check and harder to defend, so write the window and minimum the way the policy states them.

Why does a 1971 case matter for a modern posting? The Ninth Circuit decision described in the EEOC's questions and answers found state laws limiting women's work in certain jobs to be in conflict with Title VII. Sex-based limits on work conflicted with Title VII in that case, so the same kind of limit should be kept out of a posting.

Can an applicant's condition appear in the job description? The JAN page uses a situation about a new manager with a specific condition to show that the description should describe the job, not the person. Keep personal characteristics out of the requirement list, and write each line around a duty.

Sources