Workers Say Major Bank Cheated Them Out of Pay While Computers Booted Up

Human Resources Director reporter Tez Romero reports that Bank of America is facing a proposed class action over a routine many office workers know too well: waiting for computers to load before the day even begins. 

According to Romero, former Business Analyst Tava Martin alleges that hundreds of hourly employees spent 15 to 30 minutes each morning booting Windows, authenticating into VPNs, opening secure apps, and downloading spreadsheets – before the bank considered them “on the clock.” She filed suit in federal court on October 23 in the Western District of North Carolina.

Romero writes that Martin worked both remotely and at the bank’s Jacksonville facility, but the expectations were the same. 

Workers had to be “phone ready” the moment their scheduled shift started. If they weren’t immediately able to take or make calls, performance scores suffered and disciplinary action was on the table.

Those expectations created an unavoidable squeeze. As Romero explains, the systems were layered: Windows first, then a security token to reach the VPN, then multiple web applications with separate passwords, then the day’s Excel files. 

The first call could only happen when all of that was done, yet the bank allegedly treated that time as off-the-clock prep.

When Lunch Isn’t Really a Break

Romero also details what happened at noon. During unpaid meal breaks, systems often disconnected, forcing another round of logins. Workers typically spent three to five minutes just re-establishing access after lunch – sometimes longer if a fresh reboot was needed.

The day didn’t end cleanly either. Romero notes that employees had to log out of programs and shut down securely, adding another two to three unpaid minutes after the shift. A couple of minutes sounds trivial until you multiply it by five days a week, 50 weeks a year, across hundreds of people.

Romero points to an eyebrow-raising pattern in Martin’s paystubs: exactly 40 hours when she worked a full week, or exactly 32 when she missed a day. 

That’s the telltale sign of paying for the schedule rather than the real time spent working, which included all those pre- and post-shift tasks and mid-day reconnects.

What the Law Says About “Little Things”

Attorney and YouTuber Steve Lehto cuts right to the principle: the question isn’t whether a worker is typing furiously every second – it’s whose time it is. If the employer controls that time, it should be paid. In his video breakdown, 

Lehto describes the modern ritual – multi-factor authentication, VPNs, encrypted devices, mandatory apps – and notes the lawsuit’s claim that these steps could take up to half an hour each day before a worker was even allowed to punch in.

Lehto frames it with a century-old analogy. Miners once argued about pay for the time spent traveling from the surface to the actual workface underground. You were at the mine, waiting in line for the man-car, but not yet producing ore. Is that your time – or the company’s? 

The parallel is sharp: if you’re required to be there and follow required steps to access your workstation, you’re not free to use that time for yourself.

Both Romero and Lehto highlight a key piece of federal guidance that makes this more than a philosophical debate. Back in 2008, the U.S. Department of Labor issued specific guidance for call centers under the Fair Labor Standards Act (FLSA). 

As Romero reports, the DOL said starting computers to download instructions and applications is an example of a “first principal activity” of the day – time that must be counted and paid. That guidance also reminds employers to keep records of all hours worked, including pre- and post-shift tasks.

Why Minutes Become Overtime

Romero’s reporting includes a concrete example. In one mid-March week, Martin was paid for 40 hours with no overtime. 

But with at least 20 minutes of unpaid time per shift across five shifts – pre-shift, lunch reconnects, shutdowns – there were 100 extra minutes that should have been counted at time-and-a-half, given her regular $46.17 hourly rate through a staffing agency.

That rate mattered less than the control. Romero notes Bank of America set schedules, training, and policies, and reserved discipline and termination authority. In wage-and-hour law, who holds the levers matters more than whose name is on the paycheck.

Lehto observes that small slices of time become big numbers in class actions. Two minutes at shutdown here, five minutes after lunch there, 25 minutes on a tricky morning login – over months and years, across hundreds of workers, the unpaid totals can swell into meaningful damages.

The “Phone Ready” Rule Meets the Time Clock

The tightest conflict in Romero’s account is the “phone ready” rule. If employees had to be ready to take calls at the dot of their shift, the work to make that happen had to occur before the dot. 

The bank allegedly discouraged reporting time outside scheduled hours, and performance systems punished any delay once the shift began.

That design nudges people to do the setup off-the-clock. In practice, it also breaks the FLSA’s rule that all hours the employer requires or “suffers or permits” a worker to perform must be counted. Even if nobody said “work unpaid,” incentives can make that the only way to meet the metric.

Romero emphasizes that the lawsuit alleges this wasn’t an occasional glitch. It was systemic. 

The same sequence, the same logins, the same penalties for being late to the first call, the same neat 40-hour pay entries – across a cohort of remote hourly Business Analysts with the same tech stack.

A Class Action With a Familiar Playbook

Romero reports that Martin seeks to represent all current and former remote hourly Business Analysts who did this work in the three years before the case is certified, potentially hundreds or thousands of people. 

Many were placed via third-party agencies but followed the bank’s handbook on attendance, timekeeping, and overtime.

Lehto notes the plaintiffs are pursuing both class and collective action paths—vehicles that, if certified, let similarly situated workers band together. He also flags that recent rulings on similar boot-up cases have split depending on the facts. 

Courts are more skeptical when workers can do other paid tasks while the machine loads. They’re more sympathetic when the login sequence is a mandatory gateway and can’t be bypassed.

That distinction matters. If a worker could check paper cases or answer a phone while the computer crawls, some judges have said the boot time isn’t compensable by itself. 

But if the job’s first duty requires the system to be live – taking calls in a secure environment, opening regulated applications – then the boot is part of the job’s first step, not a personal chore.

What Happens Next

According to Lehto, Bank of America hadn’t formally responded at the time of his video, which is unsurprising for a fresh filing. Extensions are common, and big employers tend to fight certification before they ever argue the merits.

Romero underscores that the case is still in early stages. There’s no ruling yet on class certification or the core allegations. 

But the legal theory isn’t novel, and the DOL’s 2008 call-center guidance gives workers a clear hook: if the employer requires those pre-shift digital gate checks to perform the first task of the day, that time belongs on the timesheet.

It’s also hard to ignore the culture signals. Romero’s reporting on “exact 40-hour” paystubs and a strict readiness metric describes a system optimized for tidy accounting, not accurate accounting. 

Those are different things. One hits the scheduling target; the other follows the law’s command to pay for all hours worked.

The Bigger Picture for Hourly Knowledge Work

Lehto’s miner analogy lingers because the tech has changed but the tension hasn’t. When work starts somewhere you can’t reach until the company’s machinery moves, who pays for the wait? 

In an office, the man-car is now a long password, a texted code, a spinning wheel, and a handshake with a server farm. The principle is the same.

Romero’s example week also shows why this dispute lands squarely in overtime territory. If full-time hourly staff regularly tack on unpaid minutes to meet readiness demands, the unpaid time often pushes past 40 hours. Under the FLSA, that’s time-and-a-half, not regular rate. Small gaps get expensive fast.

There’s an easy fix many employers already use: move the time clock to the very first action workers take, or auto-capture system login timestamps and treat them as paid time. 

That approach aligns incentives and paperwork with the real flow of the job. It’s cleaner for payroll, fairer for staff, and safer in court.

Romero lays out a detailed account of a workday that starts earlier than the paycheck. Lehto explains why the law tends to treat those early minutes as work when they’re the only path to doing the job. 

Put together, the story is less about computers and more about control. If the bank dictates how your morning starts, it probably owns that time – and should pay for it.

UP NEXT: “Heavily Armed” — See Which States Are The Most Strapped

Americans have long debated the role of firearms, but one thing is sure — some states are far more armed than others.

See where your state ranks in this new report on firearm ownership across the U.S.

The article Workers Say Major Bank Cheated Them Out of Pay While Computers Booted Up first appeared on Survival World.