The Rule Made Business Sense. Then HR Looked at Who It Left Behind.

Written By: BOSS Editorial
Reading Time: 12 minutes
The requirement had been in the job description for years. Applicants needed a four-year degree. Employees considered for promotion had to be available on certain days. Another department required workers to meet a physical standard that managers believed reflected the demands of the role.
Nobody had written the rules with discrimination in mind. To leadership, they were simply business requirements. Then HR started asking a different question: Who was being screened out? That question can change the way an organization looks at policies that once seemed routine. A rule does not have to mention race, religion, sex, age, disability, or another protected characteristic to deserve scrutiny.
Sometimes the concern is obvious because people are treated differently. In other situations, the wording appears neutral, and the potential problem becomes visible only when employers examine how the rule works in practice.
For business leaders, this is not an argument against standards. Companies need qualifications, schedules, performance expectations, safety procedures, and consistent policies. The harder question is whether those requirements still accomplish a legitimate business purpose without creating unnecessary barriers.
The Rule Did Not Look Discriminatory
Imagine a company hiring for a position that has traditionally required a bachelor’s degree. The degree requirement is copied into each new posting. Hiring managers assume it must be there because it has always been there.
Yet most of the actual work depends on skills employees can acquire through industry experience, technical training, or other paths. Now suppose HR reviews several years of recruiting data and notices that the requirement is eliminating a large portion of otherwise qualified applicants from a particular group.
That does not automatically establish unlawful discrimination. It does create a reason to examine the requirement more closely. The U.S. Equal Employment Opportunity Commission has cautioned that educational requirements can raise Title VII concerns when they disproportionately exclude members of a protected group and exceed what a job actually requires.
Title VII of the Civil Rights Act of 1964, as amended by the Civil Rights Act of 1991, provides that a particular employment practice causing disparate impact based on race, color, religion, sex, or national origin must be job-related for the position and consistent with business necessity. The useful management question is therefore not simply, “Does everyone have to meet this standard?” It is, “Why is this standard here?”
Some Problems Are Easier to Recognize
The most familiar form of workplace discrimination involves different treatment. Suppose two similarly situated employees are being considered for the same promotion, but a manager rejects one because of that employee’s race, religion, sex, national origin, or another legally protected characteristic.
The policy itself is not causing the problem. The employment decision is. U.S. federal employment law generally describes this kind of intentional differential treatment as disparate treatment. Some sources use “direct discrimination” more conversationally, but disparate treatment is the more familiar U.S. legal term. The harder cases often involve rules that appear to treat everyone alike.
Other Problems Appear Only After the Rule Is Applied
Consider a physical test for a warehouse role. Management may have introduced the test because the job once involved repeatedly lifting heavy materials by hand. Years later, equipment now handles much of that work, but the old physical requirement remains part of the hiring process. Every applicant takes the same test. There is no separate standard for different groups.
Yet a neutral rule can still warrant legal scrutiny. Under Title VII, a specific employment practice that disproportionately disadvantages people based on race, color, religion, sex, or national origin may raise a disparate-impact issue even when the rule is applied the same way to everyone.
The relevant Title VII question is not simply whether outcomes differ. The statute asks whether the challenged practice caused the disparate impact and, if so, whether it is job-related for the position and consistent with business necessity.
Ordinary Business Requirements Can Have Unexpected Effects
Most potentially problematic workplace standards begin as attempts to solve legitimate operational problems. That is why leaders should be especially careful with requirements that slowly become organizational habits.
The Degree Requirement
A degree can be essential for some jobs. Physicians, attorneys, engineers in certain regulated positions, and other professionals may need specific education or credentials. Other positions are less clear.
If the work can be performed successfully through equivalent experience, training, certifications, or demonstrated skills, leaders should periodically examine why a degree remains mandatory. If those alternatives measure the capabilities the job actually requires, an employer may decide that a degree-only screen no longer adds enough value to justify keeping it.
The federal Uniform Guidelines on Employee Selection Procedures and related EEOC guidance emphasize that selection procedures with adverse impact should be supported by evidence showing that they are appropriate for the jobs and purposes for which they are used.
The Schedule Requirement
Scheduling rules can also look straightforward until individual circumstances expose a conflict. A company may legitimately need coverage on weekends, evenings, or particular holidays. But rigid scheduling policies can intersect with religious practices and other legally protected needs.
Title VII generally requires covered employers to reasonably accommodate sincerely held religious beliefs, practices, and observances that conflict with work requirements unless the accommodation would impose an undue hardship. In Groff v. DeJoy, the U.S. Supreme Court clarified that undue hardship means a burden that is substantial in the overall context of the employer’s business.
Current EEOC guidance identifies options such as schedule changes, voluntary shift swaps, and exceptions to workplace rules. The lesson for managers is not that schedules cannot be enforced. It is that “this is the rule for everyone” may not be the end of the conversation.
The Physical Requirement
Physical standards require the same discipline. If employees genuinely must lift a particular weight, climb repeatedly, work at a certain height, or perform another physical task to carry out essential duties safely, an employer may have a legitimate reason for setting an appropriate requirement.
But the requirement should reflect the job that exists today. If equipment, automation, redesigned workflows, or different staffing practices have changed the role, an inherited standard can become disconnected from actual performance. That may justify redesigning a test so it measures the physical functions employees actually perform rather than a legacy assumption about the job.
Title I of the Americans with Disabilities Act limits qualification standards that screen out an individual with a disability or a class of individuals with disabilities. Such standards must be job-related and consistent with business necessity, and an employer may still need to consider whether the work can be performed with reasonable accommodation.
The Promotion Standard
Promotion criteria deserve similar attention. A company might require employees to have worked in a particular assignment before becoming managers. Perhaps that assignment historically provided necessary experience.
But what happens when HR discovers that access to the prerequisite assignment has not been evenly available? The promotion rule may look objective by itself. The larger process may tell a more complicated story.
That is why organizations should examine not only the final promotion decision, but also who receives developmental assignments, high-visibility projects, mentorship, training, and opportunities to satisfy the stated prerequisites.
Disparate Treatment and Disparate Impact Are Different Problems
The terminology matters because these legal theories ask different questions. For U.S. readers, the clearer terms are disparate treatment and disparate impact. The more general labels direct and indirect discrimination can describe similar ideas, but they are not the primary terms used in U.S. federal employment law.
Disparate Treatment Focuses on the Decision
With disparate treatment, the central question is generally whether a protected characteristic affected the employment decision. The facts might involve hiring, compensation, discipline, promotion, assignments, layoffs, or termination.
Title VII prohibits employment discrimination based on race, color, religion, sex, and national origin. The Americans with Disabilities Act protects qualified individuals with disabilities as part of the broader framework of employee rights against discrimination, and the Age Discrimination in Employment Act protects workers age 40 and older.
Under the ADEA, a neutral practice that disproportionately affects workers age 40 or older may be lawful if it is based on a reasonable factor other than age. State and local laws may protect additional characteristics.
California, for example, protects additional categories under its Fair Employment and Housing Act. The California Civil Rights Department lists protections including gender identity and expression, sexual orientation, disability, medical condition, marital status, genetic information, reproductive health decision-making, and military or veteran status, along with categories also protected by federal law.
Disparate Impact Focuses on the Practice and Its Effect
Disparate impact under Title VII begins with a particular neutral employment practice and its effect, rather than a claim that a decision-maker acted with discriminatory intent. A statistical difference can prompt review, but it does not by itself establish that the practice is unlawful.
If the required disparate-impact showing is made, Title VII requires the employer to demonstrate that the challenged practice is job-related for the position and consistent with business necessity.
The Civil Rights Act of 1991 also addresses an alternative employment practice that would serve the employer’s legitimate needs with less discriminatory impact. That is more nuanced than saying, “The numbers are different, therefore the policy is illegal.”
“We Have Always Done It This Way” Is Not a Business Case
Policies accumulate. A manager creates a rule after one difficult incident. Another department copies it. A job description gets reused for ten years. A screening requirement moves from one recruiting system to another without anyone reconsidering its purpose.
Eventually, institutional memory disappears, but the requirement remains. That is where a basic policy audit becomes valuable.
What Business Problem Is the Rule Solving?
Start with the objective.
Why does the position require a degree?
Why must the employee work that exact schedule?
Why is that physical test necessary?
Why must someone spend two years in a particular role before promotion?
Why does a grooming standard exist?
A clear answer does not guarantee that a policy is lawful, but the absence of an answer should prompt further review. If management cannot connect a requirement to the work, the organization may be imposing a barrier without gaining much in return.
Could the Same Goal Be Reached Another Way?
The second question is whether the organization’s goal can be achieved through another approach. Suppose the company wants to know whether applicants can analyze complex information. A degree might serve as a proxy for that capability, but a carefully designed work-sample exercise could potentially measure the actual skill more directly.
Suppose a physical requirement was created to prevent injuries. Updated equipment or a more accurate job-specific test might achieve the safety objective without relying on an outdated standard.
The federal Uniform Guidelines on Employee Selection Procedures direct employers validating a selection procedure with adverse impact to investigate suitable alternatives that are substantially equally valid and have less adverse impact. That makes alternatives more than an HR exercise. They can also improve the quality of the selection process itself.
Look at Patterns Before They Become Complaints
Managers naturally deal with individual decisions: one applicant, one performance review, one promotion, one request for an exception. HR has the opportunity to see the pattern.
A recruiting requirement may not seem unusual when looking at a single applicant. Promotion data across three years may reveal something different.
The same principle can apply to turnover, disciplinary actions, performance ratings, scheduling requests, access to training, and other employment decisions.
Organizations do not need to assume that every statistical difference proves discrimination. They should be willing to investigate meaningful disparities rather than dismissing them simply because the written rule is neutral.
A Policy Audit Needs Context, Not Just Numbers
Numbers can identify where leaders should look. They do not always explain why a difference exists. A useful review combines quantitative and qualitative information. HR may ask whether the job has changed, whether managers interpret the policy consistently, whether exceptions are available, whether applicants understand the requirements.
Whether a selection tool has been validated for its intended purpose, and whether employees have repeatedly raised the same concern. The goal is to understand how a policy actually functions, not to treat every difference as proof of a violation.
Review the Rule When the Workplace Changes
Businesses evolve faster than employee handbooks. Technology changes jobs. Remote work changes where jobs can be performed. Automation changes physical requirements. New systems alter the skills employees need. Acquisitions combine policies written for very different workplaces. Employment standards should evolve as well.
Job Descriptions Can Outlive the Jobs They Describe
One of the simplest HR exercises is to compare the formal job description with the work employees perform today. Ask current employees what tasks consume their time. Ask managers which qualifications genuinely predict success. Identify requirements nobody can explain.
This exercise can improve recruiting even when discrimination is not an issue. Companies often complain that qualified candidates are difficult to find while simultaneously using legacy requirements that shrink the candidate pool without improving job performance.
Good Policies Need a Reason, Not Just a History
Consistency matters in management. Employees notice when rules change depending on who is asking. But consistency alone is not enough to make a workplace policy effective—or necessarily legally sound.
A rule can be applied uniformly and still deserve examination because of the result it produces. Conversely, a difference in outcomes does not automatically mean discrimination has occurred. The relevant facts, governing law, affected group, nature of the practice, job requirements, and available alternatives can all matter.
That is why the best time to examine a policy is often before a complaint forces the organization to do it. Use the four questions below as a simple policy-audit record. For each requirement, document the evidence supporting the answer, not just the conclusion.
What is this requirement supposed to accomplish?
Is it connected to the job as it exists today?
Who does it exclude or disadvantage in practice?
Could we accomplish the same legitimate business goal another way?
Sometimes the answers will confirm that the existing standard makes sense.
Other times, a rule that looked perfectly reasonable on paper will reveal a weakness the company had never noticed. That discovery is not necessarily evidence that someone intentionally designed a discriminatory workplace. It may simply be evidence that the workplace changed—and the rule did not.
