Share

Grand Theft Absence: Tips for Employers Navigating Suspicious Sick Time

Alert
11.16.2026
By Zak Kuchler, Stephanie Scheck & Dawn Valdivia

On Thursday, November 19, millions of Americans will wake up "sick." The cause will not be a virus. It will be Grand Theft Auto VI.

Thirteen years in the making and delayed multiple times, Rockstar Games' latest installment may be the most anticipated video game release in history. Early projections anticipate roughly $1 billion in sales within its first days. For employers, the more sobering number is the one measured in empty chairs. Widely circulated reports estimate that as many as 1.5 million U.S. workers could skip work on launch day, resulting in significant lost output. Recent workforce surveys point in the same direction: nearly one in five workers plans to take the day off, time-off requests for November 19 are running well above a normal Thursday, and roughly a third of employed gamers say they will call in sick rather than ask for the time in advance.

None of this is new. When the franchise's last installment launched in 2013, a notable share of fans admitted they planned to call in sick. The day after the Super Bowl produces the same spike every year. So, employers can see the pattern coming: a wave of call outs on launch day—and, based on data from prior launches, the day before—with absences bleeding into Friday.

What has changed is the law. When the last installment launched in 2013, only one state required paid sick leave. Today, many states, the District of Columbia, and dozens of cities, have their own rules on notice, documentation, and retaliation protections. The temptation to push back is understandable, but in many of the places where employers operate, paid sick time is now a statutory right. The law sharply limits how an employer may question, verify, or discipline its use. Handle a suspicious absence the wrong way, and a minor attendance headache can become a retaliation claim that costs far more than one lost shift. The Grand Theft Auto VI launch is a useful stress test for how employers should respond to sick time that looks questionable—before and after it happens.

The Launch Day Problem Under State Sick Leave Laws

Picture the scenario. An hourly employee calls in sick on release day, a week after telling coworkers they had preordered the game. The next morning, the employee posts a screenshot of their in-game progress. The instinct is to deny the time, demand a doctor's note, or write the employee up. Under state paid sick leave laws—for example, Arizona's Fair Wages and Healthy Families Act, California's Healthy Workplaces, Healthy Families Act, Colorado's Healthy Families and Workplaces Act, and Minnesota's Earned Sick and Safe Time law—each of those moves carries real risk. The details vary by state, but four themes drive the analysis.

Covered purposes are broad—and gaming is not one of them. Paid sick time generally must be provided for an employee's own illness, injury, or health condition, including diagnosis, care, treatment, and preventive care, and caring for a family member with those needs. Most states also cover absences related to domestic violence, sexual assault, or stalking. Playing a new video game is plainly not a covered purpose. The hard part is not knowing that—it is proving it.

Notice rules generally favor the employee. When the need is foreseeable, employees generally must give reasonable advance notice; for unforeseeable absences, notice is typically required only as soon as practicable. Many states also limit how much notice an employer may require, and some states, like Arizona and Minnesota, allow an employer to enforce a notice procedure only if it has first given employees a written policy. An employer that skipped that step cannot deny sick time because the employee failed to follow it.

Documentation is the exception, not the rule. Most states allow documentation requests only after an extended absence, typically three or four consecutive workdays, depending on the state. California's statute does not set a documentation threshold, so employers there should be especially cautious about requesting notes for short absences. Across the board, documentation should confirm only that the time was used for a covered purpose. Arizona, for instance, bars requiring documentation to explain the nature of the health condition. Pressing for medical details creates its own exposure.

And the clock is working against employers. States with paid sick leave laws prohibit retaliation against employees for requesting or using sick time, and several bar absence control or attendance point policies from counting protected sick time as an absence that leads or may lead to discipline. Some states go further by presuming retaliation. In Arizona, for example, any adverse action taken within 90 days of protected activity is presumed retaliatory, and the employer can rebut that presumption only with clear and convincing evidence that it acted for other, permissible reasons. California has a similar, shorter presumption.

Applied to the launch-day call out, these rules cut against each of the instinctive responses. A hunch, a coworker's comment, or a suspicious date will rarely be enough to justify discipline, and in a state like Arizona, it will rarely pass the clear and convincing bar needed to overcome the presumption.

None of this means an employer must simply absorb genuine fraud; sick time used for a reason the law does not cover is not being used as the statute contemplates. These statutes generally do not expressly authorize discipline for misuse, but discipline for well-documented, non-covered use is generally defensible when handled consistently. Employers should act only on solid, well-documented evidence, never on assumptions, and should measure every step against any applicable retaliation presumption.

Separating Suspicion From Evidence

Whether an absence can be treated as misuse turns on the quality of the proof. Employers should be honest with themselves about how much they actually have.

Weak indicators rarely justify action. Timing alone (e.g., an absence on a release date, holiday or big game day) is seldom enough. Plenty of people genuinely fall ill on days that happen to matter. Acting on secondhand reports or on ambiguous social media activity invites exactly the kind of claim the statute was built to protect. Monitoring employees' social media carries its own risks, too, including under state laws protecting lawful off-duty conduct and the National Labor Relations Act.

Stronger indicators warrant a closer look. The calculus shifts when an employee requested the day as vacation, was denied, and then called in sick; when the employee says outright that the absence was not health-related; or when credible evidence directly contradicts the stated reason. Even then, a word of caution: a person can be ill and still able to play a video game. Activity outside work is not necessarily inconsistent with a covered health condition, and a single suspicious sequence supports investigation, not a foregone conclusion.

Patterns still require individualized review. A recurring string of absences tied to non-health events may justify a conversation, especially if documented over time. But each absence must be evaluated on its own under the applicable statute. An employer cannot use a "pattern" to sidestep its state's documentation threshold or the bar on counting protected absences under the FMLA, ADA, a CBA, or an employer's own PTO policy.

A Playbook for Employers

The most effective response to launch-day absences is not a crackdown after the fact. It is a plan in advance.

Open a release valve before the release. When heavy demand for a day off is predictable, give employees a legitimate way to take it: a voluntary time-off or shift-swap window announced ahead of time. Every employee who takes the day the right way is one less call out to second-guess.

Put your notice policy in writing and in their hands. In some states, an employer that wants employees to follow a notice procedure must first provide a written policy describing how to give notice. Without one, the employer cannot deny sick time for lack of notice. This is also a good moment to confirm that required postings, notices, and sick leave balance statements are current.

Ask for documentation only where the law allows it. Reserve documentation requests for absences that meet your state's threshold, and make sure any request seeks only confirmation that the time was needed for a covered purpose.

Train the front line. Supervisors are usually the first to react to a suspicious call out, and an off-the-cuff comment from a manager can become Exhibit A in a retaliation claim. Train them not to interrogate employees about symptoms, demand notes for short absences, remark on the timing, or threaten discipline. And remind them of a trap that surfaces exactly when staffing is tight: in many states, including Arizona, California, Colorado, and Minnesota, an employer may not require an employee to find a replacement worker as a condition of taking sick time. The supervisor's job is to document what they observe and escalate concerns to human resources.

Investigate carefully, and call counsel before you act. When an employer has concrete evidence that sick time was used for a non-covered purpose, they should investigate in a measured, consistent way and document its findings. Because adverse action can be presumed retaliatory in some states, consult employment counsel before imposing discipline. Counsel can help confirm that the evidence is strong enough to meet the applicable standard.

Apply the rules the same way every time. Treat similar situations the same way across employees and departments. Inconsistent enforcement is often the fact that sinks an employer's defense because it undercuts any later argument that discipline rested on legitimate, non-retaliatory reasons.

Looking Ahead

Grand Theft Auto VI will not be the last event that tempts employees to take an unscheduled day. Major sporting events, long weekends, and the next must-have release will raise the same issue throughout the year. The employers who come out ahead will be the ones who prepare now: review the policies against each state's requirements, train the managers, and treat suspected misuse as a question of evidence rather than assumption. Do that, and you can protect your operations without handing an employee a retaliation claim.

For more information or assistance with paid sick leave compliance, attendance policies, employee discipline (or how far they got on Grand Theft Auto VI), please contact Sharon Beck, Monika Bidner, Amy Conway, Tracey Holmes Donesky, Zak Kuchler, Amanda Laufer, Kyle Malone, Stephanie Scheck, Joel Spann, Naima Starks, Dawn Valdivia, Ben Woodard or the Stinson LLP contact with whom you regularly work.

Related Capabilities

Subscribe to Stinson's
News & Insights
Jump to Page

Stinson LLP Cookie Preference Center

Your Privacy

When you visit our website, we use cookies on your browser to collect information. The information collected might relate to you, your preferences, or your device, and is mostly used to make the site work as you expect it to and to provide a more personalized web experience. For more information about how we use Cookies, please see our Privacy Policy.

Strictly Necessary Cookies

Always Active

Necessary cookies enable core functionality such as security, network management, and accessibility. These cookies may only be disabled by changing your browser settings, but this may affect how the website functions.

Functional Cookies

Always Active

Some functions of the site require remembering user choices, for example your cookie preference, or keyword search highlighting. These do not store any personal information.

Form Submissions

Always Active

When submitting your data, for example on a contact form or event registration, a cookie might be used to monitor the state of your submission across pages.

Performance Cookies

Performance cookies help us improve our website by collecting and reporting information on its usage. We access and process information from these cookies at an aggregate level.

Powered by Firmseek