A 9/80 work schedule places 80 planned work hours across nine workdays in a two-week cycle. The common design uses eight nine-hour days, one eight-hour day, and one additional day off. It changes when people work, not necessarily how much they work.
The important payroll question is not whether the two-week total equals 80. Employers must first identify the fixed, recurring workweek, then compare actual hours with the applicable federal, state, local, collective-bargaining, and policy requirements. A schedule that shows 44 hours in one workweek and 36 in the next may require overtime review even though the cycle totals 80 hours.
This guide explains the arithmetic, shows why the workweek boundary matters, compares 9/80 with remote and four-day schedules, and provides an implementation sequence for planning, time capture, review, and a controlled pilot.
What is a 9/80 work schedule?
A 9/80 schedule is a two-week arrangement with 80 planned working hours across nine workdays. A common pattern has four nine-hour days and one eight-hour day in the first week, followed by four nine-hour days and one day off in the second week. Friday is often the alternating day off, but an employer can choose another day to meet coverage requirements.
Here is the arithmetic for that common pattern:
Week 1: 9 + 9 + 9 + 9 + 8 = 44 planned hours
Week 2: 9 + 9 + 9 + 9 = 36 planned hours
Two-week total: 80 planned hours
Workdays: 9The pattern preserves 80 planned hours over two weeks. It does not create a reduced-hours schedule, guarantee a three-day weekend for every employee, or determine the employee’s legal pay treatment. Breaks, holidays, leave, schedule swaps, and work performed outside the plan must be handled separately.
An 80-hour two-week total is not the federal overtime test. Write down the employer’s fixed workweek, calculate each workweek separately, and have HR or payroll review the result before publishing a pay-impacting schedule.
How is overtime calculated?
Under the federal Fair Labor Standards Act, covered, nonexempt employees generally must receive overtime pay at not less than one and one-half times their regular rate for hours worked over 40 in a fixed, recurring seven-day workweek. Federal rules generally do not allow employers to average hours across two or more workweeks to avoid overtime. See the U.S. Department of Labor overtime guidance.
Apply that rule conditionally to the 44/36 example. If the employer’s defined workweek aligns with those boundaries, and the employee is covered and nonexempt, the 44-hour week requires review for four hours of potential federal overtime. The 36-hour week does not cancel those hours because the two-week total is 80. The final calculation can depend on the defined workweek, actual hours worked, exemption status, jurisdiction, daily thresholds, collective-bargaining terms, and any valid alternative-workweek arrangement.
The workweek boundary can materially change the analysis. In California, for example, qualifying alternative-workweek schedules have formal adoption requirements, including a secret-ballot election and advance written disclosure under the applicable regulation. California’s process is not a nationwide rule. Employers using that example should review the California regulation and the California DLSE enforcement manual, then obtain advice appropriate to their workforce and jurisdiction.
For each proposed schedule, calculate planned hours at three levels: by work date, by the employer’s fixed workweek, and across the full 14-day cycle. HR or payroll should then check classification, actual time, applicable thresholds, leave and holiday treatment, and any required adoption process. A calendar plan is an input to that review, not its conclusion.
How 9/80 compares with remote work and four-day schedules
These models answer different questions. A 9/80 schedule changes the distribution of working time. Remote work changes where work is performed, not necessarily when. A four-day schedule can reduce total hours or compress full-time hours into four longer days. The actual hours must be stated before making a comparison.
| Model | Typical time pattern | Main operational tradeoff |
|---|---|---|
| 9/80 | Nine workdays across two weeks, commonly with an alternating day off | Regular extended break, longer workdays, and more complex coverage |
| Four-day schedule | Four days per week; may be four eight-hour days, four ten-hour days, or another design | Weekly day off, but total hours and daily intensity vary |
| Remote work | Work performed away from the usual worksite; hours may remain fixed | Less commuting for some roles, but location flexibility is not time flexibility |
9/80 or four days
Define the actual daily and weekly hours first. A four-day schedule can be reduced-hours or compressed full-time work, while 9/80 commonly preserves 80 hours over two weeks.
Remote or on-site
Decide separately where work happens and when employees must be available. Remote work can be combined with a 9/80 or four-day design.
Benefits and tradeoffs to measure
A predictable extended weekend may appeal to employees who value concentrated personal time. An employee who commutes to a worksite may also avoid one commute in a two-week cycle. Those are plausible benefits, not guaranteed improvements in productivity, satisfaction, recruitment, retention, or well-being.
Longer days may create fatigue or time pressure for some employees. Alternating absences can reduce coverage, complicate handoffs, and make meetings harder to schedule. The effect will vary by role, workload, commute, staffing model, and how much work depends on same-day collaboration.
Research on compressed workweeks is mixed and does not establish the effect of every 9/80 design. A 2025 systematic review reports varied findings across outcomes and settings. A longitudinal study of one construction company should be treated as context-specific evidence, not proof that every 9/80 arrangement will produce the same result.
Convert each expected benefit or concern into a measure. Useful measures include commute days avoided, coverage gaps, response times, actual overtime, payroll cost, fatigue reports, absences, missed deadlines, rework, safety indicators where relevant, and manager coordination time. Compare results with a baseline rather than assuming the schedule will improve or harm a particular outcome.
Decide whether the schedule fits the work
Assess coverage by hour and day, not only by whether the team is scheduled. Check customer response requirements, safety-sensitive tasks, meetings, handoffs, shared dependencies, and the hours when partners or customers are active. A Friday-off field does not demonstrate that Friday coverage is sufficient.
Ask employees about preferences and practical constraints. Involve HR when the policy intersects with accommodation, protected leave, religious observance, pregnancy, disability, caregiving, or fairness concerns. The EEOC overview of prohibited employment policies and practices provides general context, but it is not a 9/80 implementation guide.
- Proceed to a controlled pilot when compliance review is complete and coverage requirements can be met.
- Pilot with a limited group when operational effects are uncertain but the schedule can be tested safely.
- Redesign or pause when legal or payroll questions remain unresolved, essential coverage is unavailable, or fatigue concerns cannot be managed.
A practical implementation sequence
Keep the planned schedule, actual time entries, approved payroll records, and aggregate reporting distinct. A calendar entry describes an intended shift. It does not prove the hours worked, resolve an exception, or determine pay.
Illustrative data design
The following is a proposed implementation structure, not a ClickUp-published schema. It represents one approved plan version for one employee and one defined workweek. Actual time entries, approval events, payroll exports, and aggregate metrics belong in separate record types.
{
"planned_schedule_id": "SCH-E1042-2026-11-02-V1",
"employee_id": "E-1042",
"jurisdiction": "US-CA",
"employee_classification": "nonexempt",
"workweek_start": "2026-11-02T00:00:00-07:00",
"workweek_end": "2026-11-08T23:59:59-08:00",
"schedule_version": 1,
"planned_shifts": [
{
"work_date": "2026-11-02",
"planned_hours": 9,
"shift_start": "08:00",
"shift_end": "18:00"
},
{
"work_date": "2026-11-06",
"planned_hours": 8,
"shift_start": "08:00",
"shift_end": "17:00"
}
],
"coverage_requirements": [
{
"work_date": "2026-11-06",
"interval": "09:00-17:00",
"minimum_staff": 2
}
],
"review_status": "pending_hr_payroll"
}For the declared schedule grain, a proposed uniqueness rule is employee_id + workweek_start + schedule_version. If multiple systems can write concurrently, enforce that key in the database and use a transactional upsert. A search followed by create is not sufficient duplicate prevention. For imported time entries, use a source-system and source-record identifier so retries do not create a second raw observation. Preserve immutable schedule versions, correction reasons, approval actors, and timestamps.
Deterministic checks should calculate daily and workweek totals, identify missing fields, compare coverage with minimums, detect work on a scheduled day off, flag boundary-crossing entries, and enforce approved status transitions. AI may extract shift details or summarize an exception for review, but it should not independently classify an employee, interpret wage law, approve payroll-impacting hours, or write a corrected time record.
What scheduling software can and cannot do
ClickUp can support parts of the coordination workflow. Its Calendar view documentation describes displaying dated tasks, moving them on the calendar, and syncing with Google or Outlook calendars. Workspace work schedules affect task scheduling, non-working days, capacity, and Timesheets. ClickUp also documents time tracking and Timesheets for recording and reviewing time. Availability varies by plan and configuration.
These capabilities support planning, visibility, and time-record workflows. They do not by themselves calculate legally required overtime, validate wage laws, determine leave entitlements, or replace payroll and HR decisions. Verify any specific connector, export, permissions, and rules before describing a direct payroll workflow.
The Employee Schedule Template and Shift Schedule Template can organize schedule information, availability, shifts, and related tracking. They are configurable starting points, not complete 9/80 implementations or legal validators. For help designing and configuring ClickUp workflows, see ClickUp consulting or ClickUp setup and automation.
Run a controlled pilot
Collect baseline data before launch and review at least two complete schedule cycles. That is a practical starting point, not a universal minimum. A four-week baseline may provide a broader comparison where operations and data quality permit. Use a limited team when possible and set continuation criteria before the schedule begins.
- Compare planned and actual hours, overtime, and payroll cost.
- Track coverage gaps, response times, deadlines, rework, and relevant safety indicators.
- Ask employees about fatigue and schedule satisfaction, and route absences and leave through the appropriate HR process.
- Measure manager coordination burden, missed handoffs, meeting constraints, and schedule swaps.
- Restrict access to individual time and feedback records. Report aggregate results when individual detail is unnecessary.
- HR or payroll has cleared applicable pay, leave, and schedule-adoption exceptions.
- Coverage is acceptable across the days and intervals the operation requires.
- Quality, deadlines, and response times show no sustained decline against the baseline.
- Actual hours and overtime are reconciled to approved records, including day-off work and swaps.
- Employee feedback and fatigue measures support further testing.
- A named pilot owner documents a continue, adjust, or stop recommendation.
Short-term satisfaction scores do not establish lasting retention or productivity gains. At each review, compare observed results with the baseline and pre-set criteria. The pilot owner should document the recommendation, while HR or payroll clears outstanding pay and leave exceptions before any schedule change takes effect.