Can Employees Refuse to Use AI for Religious Reasons?

As the integration of generative artificial intelligence moves from a novelty to a workplace mandate, organizations are encountering a complex new frontier in employment law: religious objections to technology. Ling-yi Tsai, an HRTech veteran with decades of experience steering organizations through digital transformations, joins us to discuss the intersection of faith and automation. In this conversation, we explore how traditional legal protections under Title VII are being applied to modern tools, the rising volume of accommodation requests that have jumped from monthly occurrences to several per week, and the specific pitfalls HR must avoid to prevent costly litigation. This discussion synthesizes the shift in legal standards for undue hardship and the tactical necessity of maintaining a “human-in-the-loop” approach when evaluating how employees interact with emerging tech.

Under Title VII, religious protections apply to any “sincerely held” belief, regardless of whether a mainstream faith endorses it. How should HR verify the sincerity of a claim against AI usage without overstepping, and what specific legal risks exist if a company dismisses these objections as non-traditional?

The verification process is one of the most delicate tightropes an HR professional must walk because the law is incredibly protective of individual interpretation. When an employee claims that using generative AI is a form of idolatry or a violation of human soul-work, you cannot simply look up a religious handbook to see if their church agrees with them; in fact, trying to quote scripture to disprove them is a recipe for a $600,000 jury award. The focus should never be on the “validity” of the theology but rather on the consistency and sincerity with which the individual holds that belief in their own life. If an employer dismisses a claim because it sounds “theologically far-fetched” or isn’t backed by a major religious institution, they risk failing the first element of a Title VII claim, which is often a losing battle in court. It is far safer and more cost-effective to assume the belief is adequate and move immediately to the interactive process, rather than attempting to play the role of a theological arbiter and incurring massive legal fees.

Legal standards for denying accommodations recently shifted from “de minimis” costs to a requirement for proving “substantial increased costs.” What specific operational metrics should a business track to demonstrate this hardship, and how should a company’s total headcount influence the feasibility of an AI exemption?

The 2023 Supreme Court ruling in Groff v. DeJoy fundamentally changed the math for HR, effectively retiring the old standard where a mere $30 in overtime or a minor scheduling shift could justify a denial. Now, you truly have to pull out a calculator and document “substantial increased costs” in relation to the specific conduct of your business, which means tracking metrics like lost billable hours, the cost of manual data entry versus automated processing, and the potential impact on service delivery timelines. For a small 16-person firm, the loss of efficiency from one person refusing AI might represent a crippling percentage of their total output, whereas a 500-employee corporation would have a much harder time proving that one individual’s manual workflow constitutes a “substantial” burden. You must be prepared to show the hard numbers of how diverting tasks to other employees or maintaining legacy systems creates a concrete financial or operational drain that goes beyond mere inconvenience.

Many roles now requiring AI were performed manually only a few years ago. During the interactive process, what step-by-step approach should be used to evaluate if a “pre-AI” workflow is a reasonable accommodation, and how do you resolve conflicts with supervisors who insist the technology is mandatory?

The most logical starting point in this “high-tech” dispute is actually to look backward; if a job was performed successfully three years ago without AI, there is a very strong argument that the pre-AI workflow is a reasonable accommodation today. HR should begin by auditing the specific tasks the employee performs and identifying exactly where AI has been injected into the process, then compare those requirements against the manual methods used in the recent past. When supervisors push back, insisting the technology is “mandatory” for modernization, HR must act as an educator to explain that “mandatory” in a company policy does not override federal religious protections. You resolve this by asking the supervisor to articulate the specific harm of the manual process—is it a matter of an extra hour of work, or does it truly break the entire production chain? If the tasks can be reassigned or the employee can be transferred to a role where AI is less central, those options must be exhausted before a denial is even considered.

Past litigation involving biometric scanners showed that debating religious scripture instead of focusing on logistical alternatives can lead to massive jury awards. What specific procedural lessons should HR departments apply from these historical technology disputes, and how can they ensure their internal documentation remains objective?

The landmark case involving the evangelical coal miner and the “Mark of the Beast” biometric scanner serves as a haunting warning: the company wasted its energy debating the Bible instead of simply asking how the employee could clock in using a traditional method. HR departments must learn to strip all theological debate out of their internal documentation and focus strictly on the interactive process and the feasibility of alternatives. Documentation should read like a logistics report—listing the dates of meetings, the specific accommodations discussed, and the calculated costs of each option—rather than a critique of the employee’s faith. By keeping the record focused on the “how” of the work rather than the “why” of the belief, a company protects itself from looking biased or hostile in front of a jury. Sensory details matter here too; an objective log showing that the company offered three different manual alternatives demonstrates good faith much more effectively than a memo questioning the employee’s logic.

Using AI to brainstorm accommodation options for an employee who objects to the technology could create discoverable evidence in a lawsuit. How might a plaintiff’s attorney use these AI-generated prompts against a company, and what alternative methods should HR use to document their good-faith efforts?

There is a profound irony—and a significant legal danger—in using AI to solve a problem caused by an objection to AI. If an HR manager asks a chatbot for five ways to accommodate a religious objector and the tool suggests three perfectly viable options that the company then ignores, a plaintiff’s attorney will put those prompts on a giant screen in front of a jury to prove a lack of good faith. It creates a “smoking gun” that shows the company knew of possible solutions but chose not to implement them, which can be devastating during discovery. Instead, HR should rely on collaborative human brainstorming sessions with legal counsel and department heads, documenting these efforts through traditional meeting minutes and dated internal memos. This ensures that the evidence reflects a thoughtful, human-led inquiry into the employee’s specific needs rather than a generic, potentially incriminating list generated by an algorithm.

What is your forecast for religious accommodations in the workplace as AI adoption increases?

I anticipate a significant surge in litigation as we move toward the “first big case” that specifically addresses generative AI and religious freedom, which will likely set a national precedent for the coming decade. As AI moves from being a peripheral tool to a core component of analytical and creative roles, the friction between corporate efficiency and individual conscience will only intensify. We are currently seeing the volume of these requests triple or quadruple, and as employees feel more empowered by recent Supreme Court shifts, they will be less likely to back down when told a technology is mandatory. My forecast is that the most successful companies will be those that build “flexibility by design” into their digital transformation strategies, allowing for human-only lanes of production that can accommodate diverse beliefs without breaking the overall system. Those who view AI as an all-or-nothing requirement will likely find themselves spending their projected AI cost-savings on legal settlements and jury awards instead.

Explore more

Debunking Common Myths of Workplace Sexual Harassment

Professional environments are currently navigating a complex transformation where the traditional boundaries of conduct are being scrutinized through the lens of empirical data and modern legal standards. Statistical evidence gathered as recently as 2024 indicates that nearly half of all women and roughly one-third of men have experienced some form of harassment or assault within a professional context, suggesting that

PHP Patches Critical Memory Flaws in Image Processing

Security researchers recently identified a pair of severe memory-safety vulnerabilities within the core image-processing capabilities of PHP, the programming language that currently powers a massive majority of active web servers. These critical flaws, specifically targeting the widely used functions getimagesize and iptcembed, were discovered by security researcher Nikita Sveshnikov and represent a profound risk to the global web infrastructure. By

Why Is Pacific Plastics Facing a California Labor Lawsuit?

The intricate landscape of California labor regulations often presents a significant challenge for industrial manufacturers who must balance high-volume production with strict statutory compliance. This reality has come to the forefront as Pacific Plastics, Inc. faces a class action lawsuit filed in the Orange County Superior Court, documented under Case Number 30-2026-01558517-CU-OE-CXC. The litigation, initiated by the law firm Blumenthal

How Does Tycoon2FA Bypass MFA via Device-Code Phishing?

The sudden and effective resurgence of the Tycoon2FA phishing platform serves as a stark reminder that even the most coordinated international law enforcement operations struggle to permanently dismantle decentralized cybercrime infrastructures. While a significant multinational intervention in March 2024 successfully targeted its core servers, the architects of this Phishing-as-a-Service model managed to rebuild their entire digital landscape with remarkable speed.

Can HDFC AMC Rebuild Trust After a Major Cyber Breach?

The discovery of unauthorized access within the IT infrastructure of HDFC Asset Management Company on May 16, 2026, has sent ripples through the Indian financial landscape, serving as a stark reminder of the fragile nature of digital security in an era of hyper-connectivity. While the breach was initially flagged by an anonymous tip rather than internal monitoring systems, the management