North Dakota Paid Sick Leave Explained: What Employers Must Know

North Dakota does not mandate paid sick leave statewide. Employers are free to design their own policy, but must watch for local ordinance activity and account for remote employees working from mandate states.

North Dakota is one of many states where paid sick leave is left entirely to employer discretion, with no statewide statute setting accrual rates, carryover rules, or permitted uses. That does not mean the topic is risk-free. Employers headquartered in North Dakota that hire remote workers, expand into other cities, or bring on employees who live in mandate states can find themselves subject to obligations that have nothing to do with North Dakota law at all.

This is exactly where HR outsourcing earns its keep: a policy built only around North Dakota's baseline can leave a company exposed the moment its workforce spreads beyond state lines.

Local ordinance risk in a no-mandate state

Even in states without a statewide paid sick leave law, cities and counties can pass their own ordinances requiring paid sick leave for employees working within their boundaries. These ordinances can appear with little warning and often carry different accrual and notice requirements than anything a company has built into its existing policy. An employer that only tracks state-level law can miss a local requirement entirely.

Because ordinance activity changes over time and varies by jurisdiction, the safest approach is to confirm current status directly. Anything not addressed here should be verified with the state labor office, and employers can start with the U.S. Department of Labor's state labor office contact directory.

Multi-state employees change the picture

A company based in North Dakota that hires a remote worker living in a state with a paid sick leave mandate generally has to comply with that state's law for that employee, regardless of where the company itself is headquartered. This catches many growing employers off guard, since it is natural to assume one policy can cover the whole team. Policy should be built around where people actually work, not just where the company is registered.

Employers expanding through talent acquisition and remote hiring should treat each new state as a fresh compliance question rather than assuming North Dakota's light-touch rules travel with the employee. A single national policy document, if it is not built carefully, can either overpromise benefits that North Dakota does not require or underdeliver on what a mandate state actually requires for a remote hire living there.

The federal FMLA baseline

The federal Family and Medical Leave Act provides unpaid, job-protected leave to eligible employees at covered employers, based on headcount and hours worked thresholds. FMLA is not paid sick leave, and it is not triggered by every illness. It is a distinct protection that guarantees job restoration for qualifying medical and family reasons, separate from any day-to-day sick pay a company chooses to offer. Employers should keep FMLA policy language and any voluntary paid sick leave policy clearly separated in employee-facing materials so the two are never confused. More detail is available from the U.S. Department of Labor Wage and Hour Division.

Building a voluntary policy the right way

Even without a state mandate, a written voluntary sick leave or PTO policy protects the company by setting clear expectations. A workable policy generally addresses how time accrues or is granted, whether unused time carries over into the next year, what uses are permitted, what documentation an employee may be asked to provide for extended absences, and how much advance notice is expected for foreseeable absences. Because North Dakota sets no statutory floor, the company has flexibility here, but that flexibility should be used deliberately rather than left undefined.

Employers that also operate in other states should build the North Dakota-based policy as one part of a broader, multi-state leave framework rather than as a single flat document, so that adding a mandate-state hire later does not require rebuilding the whole policy from scratch.

How HR outsourcing keeps policy current

Laws change, ordinances get passed, and remote hiring patterns shift, often faster than an internal HR function can track across every jurisdiction where employees live. BEG's certified HR professionals monitor sick leave and paid leave developments across all fifty states and update policy language as rules change, powered by isolved. That includes flagging when a new hire's home state triggers an obligation the existing handbook does not cover, and blending in talent acquisition and direct hire support as the team grows. See the North Dakota HR outsourcing page, the HR outsourcing overview, or get instant pricing.

For a look at how a neighboring no-mandate state compares, see how Ohio paid sick leave policy is handled.

General information, not legal advice. For anything not covered above, confirm current requirements with your state labor office: DOL state labor office contacts.

Frequently Asked Questions