Key Highlights
- Reddit user plaintextcoder followed a strict no-overtime policy after their boss assigned a project at 4:47 p.m., 13 minutes before their 5 p.m. shift ended.
- The boss had explicitly ordered: “Clock out exactly at 5:00 or you’re written up. No exceptions,” but grew frustrated when the employee left the task unfinished.
- The r/MaliciousCompliance post sparked widespread discussion about contradictory workplace policies and managers who expect unpaid overtime.
Employee Complies With No-Overtime Rule Despite Last-Minute Assignment
A Reddit user known as plaintextcoder shared a workplace confrontation on the subreddit r/MaliciousCompliance that has resonated with thousands of workers facing similar policy contradictions. According to the post, the employee’s manager assigned a new project at 4:47 p.m.—just 13 minutes before the scheduled end of the workday—despite a company policy that strictly prohibited overtime. The boss had previously warned staff: “Clock out exactly at 5:00 or you’re written up. No exceptions.”
Policy Contradiction Creates Impossible Expectation
The employee began working on the assignment immediately but could not complete it before 5 p.m. When the shift ended, they clocked out in accordance with the stated rule. The boss reportedly became frustrated and questioned why the employee did not stay later to finish the task. The employee responded that remaining past 5 p.m. risked disciplinary action, including a write-up that could jeopardize their job, and they were unwilling to violate the policy the company itself enforced.
Reddit Community Shares Parallel Experiences
The post triggered a wave of comments from other Redditors describing nearly identical scenarios. One user wrote: “Oh yeah. Recently, our employer sent a memo that we need to take every single case sent our way. Every. Single. One. Our capacity is at 110%, nearing 120% right now, and we’re nowhere close to gaining the right to refuse cases for the moment. So… we’re losing in efficiency, contractors are overworked, and parts of our own contracts aren’t duly completed.”
Another commenter recounted a tactical response to the same dynamic: “I had a boss who would do this to me. Sure, drop a stack of bug reports on me at 4:45 p.m. on a Friday, no problem. That stopped quickly, because without fail, I would find a bigger problem causing the small problem the user had reported. And the bigger problem was for the upper database management team. Which meant my boss and the two guys making 6 figures weren’t going home at 5, but I was.”
Commenters Question Management Logic
Multiple threads in the discussion focused on why the manager did not simply authorize overtime if the work was urgent. Several users noted they had worked in environments where overtime was either prohibited or expected without additional compensation, placing employees in a bind between policy compliance and managerial pressure.
Why This Matters
The viral post highlights a recurring structural issue in hourly and shift-based workplaces: written policies that forbid overtime often coexist with unwritten expectations that work be completed regardless of hours. This discrepancy can expose employees to disciplinary risk while shielding management from labor-cost accountability. The Daily Dot noted it was unable to independently verify the specific events described by plaintextcoder; the account and the commenters’ experiences reflect self-reported anecdotes rather than confirmed incidents. Nonetheless, the volume of similar stories suggests the dynamic is widespread across industries ranging from tech support to case management.
Frequently Asked Questions
What was the exact policy the boss stated?
The boss said: “Clock out exactly at 5:00 or you’re written up. No exceptions.”
When was the project assigned relative to the shift end?
The boss assigned the project at 4:47 p.m., 13 minutes before the 5 p.m. shift ended.
Has The Daily Dot verified the Reddit post?
No. The Daily Dot stated it was unable to independently verify the events described in the Reddit post; the article is based solely on plaintextcoder’s account and commenters’ shared experiences.
