Skip forward into hiring notes
RosterAcorn

2 tests a conduct rule must pass before it binds new hires

A signature on the handbook does not run these tests for you.

  • Test one: state the business reason in one sentence — if you cannot, the rule is not ready
  • Test one, part two: write rules as observable behavior, not states of mind like "positive attitude"
  • Test two: check your own enforcement history — would every employee get the same response?
  • Documentation: give every rule a one-line business reason in manager notes, and record each enforcement so you have consistency evidence later
  • Handbook lines that fail either test do not become enforceable because someone signed them

Why the rule matters before you print it

You are drafting the conduct section of a policy that a new hire will sign on day one. The signature is not a formality. It sets the standard you will later enforce against that same person, months later, in a disciplinary meeting. So the rule has to be built right the first time.

There is a settled way to check your work. The U.S. Equal Employment Opportunity Commission sets out two tests in its guidance on applying performance and conduct standards. The guidance states the rule plainly: an employer may enforce conduct rules that are not found in workplace policies, employee handbooks, or similar documents so long as they are (1) job-related and consistent with business necessity, and (2) applied consistently to all employees and not just to a person with a disability.

That sentence does a lot of work. It says a written handbook is not required for a rule to hold — and, by the same logic, a rule that is written down and signed does not automatically hold either. The two tests do the deciding. Your job in this post is to run each test on each line of your conduct policy before the new hire ever sees it.

The first test asks why the rule exists. Not why it feels right, or why a past manager liked it, but whether the rule connects to the actual work and to a real business need. If you cannot say in one sentence what breaks in the business if the rule is broken, the rule is not ready.

Think about what "business necessity" covers. It covers safety on the floor. It covers keeping client information confidential. It covers showing up during the hours the work exists. It covers treating coworkers with enough respect that the team can function. Those are real operational needs, and a rule tied to them clears the first test.

Now look at rules that do not tie to anything. A rule that bans a certain style of dress with no safety, hygiene, or customer-facing reason. A rule against personal items at a desk that no one can connect to a workflow. A rule about how a person talks to friends off the clock with no link to the work. Each of these fails the first test on its face, and each one is still sitting in handbooks you have signed.

The EEOC's guidance works through a set of questions built on this test, and it prefaces them with a framing worth knowing: Questions 10 through 15 assume that the conduct rule at issue is job-related and consistent with business necessity. That is a signal that the agency treats test one as assumed before those questions are asked. Settle test one first, then move on.

A practical way to apply this at your desk. Take each conduct line and write next to it the business reason. Keep it short. If the reason is "safety around moving equipment," you have a pass. If the reason is "it has always been this way," you do not. If you need two lines to explain it, tighten it until you can do it in one. A rule you cannot explain in one line is a rule you will struggle to defend later.

There is a second move inside test one that recruiters often miss. Ask what the rule actually requires of the person. Conduct rules are about behavior. If your line says a person must "maintain a positive attitude," you have not described behavior. You have described a state of mind no one can observe. Rewrite it as something a manager can actually see: shouting at a coworker, refusing a task, missing a shift without notice. Behavior can be observed and documented, while a mood is hard for two managers to judge the same way.

Test one, in short: the rule has to do real work for the business, and it has to describe something a person can actually do or not do.

Test two: applied consistently to all employees

The second test is about your own history with the rule. The rule must be applied consistently to everyone, and not pulled out only when the person in front of you has a disability. A conduct rule may be enforced so long as it passes both tests.

Look at the case the EEOC uses. A blind employee has frequent disputes with her supervisor. The dispute itself is the conduct issue. It does not matter that she is blind. What matters is whether the same kind of dispute, between any other employee and any other supervisor, would draw the same response. If your practice is that this employee gets a formal warning and others get a quiet word in the hallway, you have already failed test two.

The second example the agency gives runs the other direction. Mary's disability has caused her to yell at and insult her supervisor and coworkers. Yelling and insulting is conduct. It is the kind of thing any conduct policy should cover. The test is still the same. If a manager has let another employee yell for years without consequence, the rule has not been applied consistently, and enforcing it now against Mary is the exact pattern the test is built to catch.

Jane has Down syndrome and works as a bagger at a grocery store. The standard you set for Jane has to be the standard you set for every other bagger.

The honest reading is that test two is mostly a question about your managers, not about your document. You can write a perfect rule and still fail it the moment a supervisor applies it unevenly. So your onboarding pack cannot stop at the signature. It has to include a way to check what actually happens after.

Here is the comparison the two tests give you, laid out side by side:

TestWhat it asksFails when
Job-related and consistent with business necessity Does the rule do real work for the business?The reason you cannot state in one sentence
Applied consistently to all employees Would every employee get the same response?The rule surfaces only against one person

Running both tests on a live policy line

Take the anti-harassment line in your handbook. Under Wisconsin law, such conduct has the purpose or effect of creating an intimidating, hostile or offensive work environment or has the purpose or effect of substantially interfering with that individual's work performance. Check your own state's and federal anti-harassment rules before adopting this wording. Read your own handbook line for line: does it name a purpose or effect, and a consequence on work performance? A new hire can read a line like that and know what is being described.

Run test one on it. Is it job-related and consistent with business necessity? Yes. A workplace where people are intimidated or where work performance is substantially interfered with is a workplace that cannot run. You can say that in one sentence. Pass.

Run test two on it. Would you apply this against any employee, in any role, at any level? If your practice has been to let a top performer intimidate a colleague because the numbers were good, the rule has been applied inconsistently, and the signature on the new hire's form does not fix that.

Now take a weaker line from the same handbook: "All employees must maintain a positive and enthusiastic outlook." Test one: you cannot say in one sentence what business need an outlook serves. It describes an internal state, not a behavior. Test two: you cannot apply it consistently, because no two managers will read an outlook the same way. The line fails both tests, and a new hire is about to sign it.

That is the exercise. Walk your conduct section line by line. Run each line through both tests. Fix what fails before the print run.

Where documentation meets the two tests

There is a temptation to treat the signed policy as proof of everything. It is not. The two tests live above the document. A rule the EEOC describes can be enforced even if it never appeared in a handbook. The converse holds too: a handbook line that fails either test does not become enforceable because someone signed it.

This matters most at the accommodation stage, which is where conduct rules and disability obligations meet. The Job Accommodation Network offers guidance on the accommodation process, including a simple principle: a good policy for employers is to only ask for information that is necessary.

Read that against your onboarding pack. If your conduct policy triggers a form that asks a new hire for medical detail they do not yet need to give, you have drifted past what is necessary. The two tests are about the rule. The necessity principle is about the paperwork around the rule. Both point the same direction: take only what the situation actually requires.

One case the EEOC works through makes the point with a long-tenured employee. Darren is a long-time employee who performs his job well. Your policy should read that way too: one standard, one application path, no side doors for tenure or for need.

Building the onboarding moment so the tests hold later

The signature moment is where your two tests either survive contact with the workforce or quietly die. A few things to put in place before that day.

First, give every rule a one-line business reason, written where the manager can see it. Not in the employee-facing text. In your manager notes. When a supervisor has the reason at hand, they apply the rule the same way the next supervisor does. That is test two, working at the moment of decision.

Second, write conduct rules as observable behavior. Swap "unprofessional manner" for the actual act. Swap "attitude" for what a person did. The rewrite does two things at once. It makes test one easier to answer, because a behavior links to a business need faster than a mood does. It makes test two possible, because two managers reading the same behavior can reach the same answer.

Third, plan the record. When a rule is enforced, note what happened, who was involved, and what response followed. That record is your test-two evidence later. Without it, you are relying on memory, and memory is where inconsistency lives. The passages quoted in this post do not set a warning ladder, so write your own sequence into the manager notes and run it the same way every time.

Fourth, keep the information you gather during any follow-up conversation to what the situation needs. The necessity principle applies to your forms as much as to your rules.

Ask your employment counsel or your HR compliance lead what your process requires, and write that into the manager notes so every supervisor runs the same ladder. A related checklist on consistency across offices helps you test whether supervisors in different locations respond the same way.

Worked example: two handbook lines side by side

Two conduct lines sit in the same handbook. Line A: "All employees must maintain a positive and enthusiastic outlook." Line B: "Employees must not shout at or insult coworkers on the floor." Run test one: line A gives no business reason you can state in one sentence, and it describes a state of mind rather than an act; line B ties to a workplace where people can work without intimidation. Run test one, part two: line A is not observable, line B is. Run test two: no two managers read an outlook the same way, so line A can never be applied consistently; line B describes an act two managers would judge the same. Line A fails both tests and should be rewritten or cut before print. Line B passes.

Your next step today

Print your conduct section and work down it line by line. Next to each line, write one sentence naming the business reason. Then write what a manager would actually observe. If either is missing, rewrite the line before the next print run, and put your own and your counsel's process notes into the manager notes so every supervisor runs the same ladder.

Related guides: Eighty percent rule for hiring tests in 4 steps · Employment verification requirements: 5 checks for new hires · Hourly new hires: 3 Washington and New York checks.

FAQ

Can we enforce a rule that never made it into the handbook? Yes, if it passes both tests. The EEOC's guidance is explicit that rules outside written policies can be enforced when they are job-related and consistent with business necessity and applied consistently to all employees. The handbook is a convenience, not the source of the authority.

Does the new hire's signature make an otherwise weak rule enforceable? No. The signature records acceptance. It does not run the two tests for you. A rule that fails test one or test two fails whether or not anyone signed next to it.

What if a manager has been lenient for years and now wants to enforce the rule? Test two is where this lands. Consistency is the requirement, and a sudden shift against one person is the pattern the test is built to catch. Fix the application pattern first. Then enforce.

Does an employee's good performance history change the analysis? No. Performance history does not change which test applies; the EEOC Darren example names tenure and performance without changing the test.

Where does accommodation fit relative to the two tests? The tests decide whether the rule binds, and accommodation questions can arise alongside enforcement; keep those conversations limited to information that is actually necessary for the situation at hand.

Should every conduct line have a written business reason? Yes, keep one for every rule, in your manager notes. It is the fastest proof that test one was run, and it is what a supervisor needs at the moment they decide how to respond.

Sources