When Boot-Up Time Counts as Paid Work

When boot-up and login minutes are paid (and when they aren't)

If the employee has to start the computer, open required software, or log into your systems before they can do the job, that time is usually paid. Federal law still leaves ordinary commuting and some true prep unpaid — but once required login starts the workday, the minutes before the official clock-in count.

If early arrival is truly free personal time with no expectation of system readiness, it may stay unpaid. If managers expect machines "up" at start time, or the only way to clock in is after a long boot, treat the setup as paid. California is stricter: regular daily minutes still count, even when each day looks small.

What to fix this week

• List the apps employees must open before they can take a call, patient, or transaction.
• Ask supervisors what "ready at 9" actually requires.
• Spot-check last week's clock-ins against VPN or app login logs.
• Let people clock in before setup finishes, or redesign so paid time starts when required systems start.
• Stop praising "already logged in" that never hits the time card.
• In California and other strict states, do not write off regular five-minute gaps.

Where employers get caught

• A cashier who opens the register system at 8:52 and clocks in at 9:00 every day.
• A remote agent who connects the VPN at 8:50 so the queue opens on time at 9:00.
• A clinic assistant who boots the charting system before the first patient is scheduled.
• App or VPN logs that show early work while time cards show only scheduled start.

Pay the login — not just the scheduled start

If they cannot do the job without booting up and logging in, put that time on the card. The cheapest fix is capturing the real start once, not reconstructing months of system logs later.