Full-time status changes by purpose, while Everhour keeps calendar-based work entries available for timesheet review.
Enter your daily hours and rate to instantly calculate total hours, regular pay, and any overtime — no spreadsheet needed.
The calculator gives you the number — Everhour takes it from there.
One click and you're timing. Start a timer, add an entry, edit the details. This is exactly how it feels in Everhour.
Set a budget, assign rates, and get alerted before you're over.
Measurement
Track your budget through time or costs
Every report you need — configured your way, always up to date.
Tracked hours flow straight into a polished invoice — no copy-paste, no manual math.
A full-time calculation answers whether a worker meets a specific hours standard for a specific purpose. In the United States, the Affordable Care Act uses an average of at least 30 hours of service per week or 130 hours per month for employer shared responsibility purposes. The Bureau of Labor Statistics uses 35 or more hours per week as a statistical convention. An employer may set a different full-time threshold for scheduling, benefits, or internal policy.
The calculation does not replace overtime math. Covered, nonexempt employees in the United States must receive overtime pay for hours worked over 40 in a fixed FLSA workweek, regardless of whether the employer labels the role full-time or part-time. Full-time status can affect benefits or classification, while overtime pay depends on hours worked in each fixed and regularly recurring 168-hour workweek.
Use this formula when the standard depends on average weekly hours: total hours of service in the measurement period ÷ number of weeks in the measurement period = average weekly hours. Include required duty time and work the employer suffered or permitted, including allowed pre-shift or post-shift work. Do not average multiple FLSA workweeks to avoid overtime, because overtime for covered nonexempt employees is tested inside each fixed workweek.
For example, a worker records 32, 30, 34, and 28 hours across four weeks. The total is 124 hours, and 124 divided by 4 equals an average of 31 hours per week. That average meets the ACA 30-hours-per-week full-time threshold for employer shared responsibility purposes. It also falls below the BLS 35-hours statistical convention, which shows why the chosen definition must come before the calculation.
The common mistake is treating 40 hours as the universal full-time rule. Federal overtime uses 40 hours as the weekly threshold for covered nonexempt employees, but the ACA full-time standard is 30 hours per week or 130 hours per month for employer shared responsibility purposes. BLS labor statistics use 35 hours per week. Employer benefit plans, contracts, and handbooks can set their own full-time schedules.
A timesheet should label the purpose of the calculation before showing the result. Use one column for hours worked or hours of service, one column for the rule being applied, and one column for the result. That layout prevents a 32-hour worker from being marked part-time under one definition and full-time under another without explanation. The number alone does not tell the reader which rule produced the label.
A one-off calculator is enough when you need a quick average for a single worker, a benefits eligibility check, or a simple comparison against an employer policy. It works best when the hours are already clean, breaks are already classified as paid or unpaid, and the measurement period is clear. Short breaks that an employer provides, usually about 5 to 20 minutes, count as compensable hours worked under federal law.
A managed workflow becomes necessary when hours come from calendars, timecards, task timers, approvals, and payroll review. Everhour can turn Google, Outlook, and iCloud calendar events into timesheet entries within a configurable window, while excluding all-day, recurring, and pre-connection events. That gives managers a cleaner starting point before they review weekly hours, approve timesheets, and hand totals to payroll or benefits administration.
This content is for general information only, may not be fully up to date, and is provided without any warranty or liability.
High Performer
G2
Summer 2026
Best Ease Of Use
Capterra
Summer 2026
Rated in the top time trackers across G2, Capterra, and TrustRadius — with consistent praise for ease of use, integrations, and support.
No. The ACA uses at least 30 hours of service per week or 130 hours per month for employer shared responsibility purposes. BLS statistics use 35 or more hours per week as a convention. An employer can set a 40-hour full-time schedule for policy or benefits, but that is separate from the federal overtime threshold for covered nonexempt employees.
Yes, for ACA employer shared responsibility purposes, an employee employed on average at least 30 hours of service per week is full-time. That same worker may still be part-time under an employer handbook, union contract, or benefit plan if that document sets a higher threshold. The calculation must name the rule it applies.
A bona fide meal period is generally unpaid only when the employee is completely relieved from duty, and unpaid meal time is not counted as hours worked. An employee who performs duties while eating is still working. Short breaks provided by an employer, usually about 5 to 20 minutes, are compensable under federal law and count in weekly totals.
An employer cannot average multiple workweeks to avoid overtime for covered nonexempt employees under the FLSA. The workweek is a fixed, regularly recurring period of seven consecutive 24-hour periods, and overtime applies to hours worked over 40 in that workweek. Full-time status can use an average under some rules, but overtime uses the workweek.
Weekend hours count the same as weekday hours in the weekly or monthly total unless a policy, contract, or state rule says otherwise. The FLSA does not require extra pay for Saturdays, Sundays, holidays, or regular rest days unless weekly overtime is worked by a covered nonexempt employee. The full-time calculation still uses total qualifying hours.
Everhour can turn Google, Outlook, and iCloud calendar events into timesheet entries within a configurable 15-minute to 3-hour window before or after the event. All-day, recurring, and pre-connection events do not sync, so managers can review calendar-based work entries without treating every calendar item as payable time.
Everhour Timesheets let users submit weekly project hours or working hours for review, then managers can approve, reject, or partially approve submitted time. Submitted and approved time is protected from regular edits, which gives payroll reviewers a clearer record before hours move into payroll or billing work.
Connect calendar events to timesheet entries, review weekly totals, and approve time before payroll. Everhour gives teams a clearer record for full-time checks and payroll handoff.
14-day free trial · No credit card · Cancel anytime
