New Hampshire scheduling checks cover the default day's work, meal periods after five consecutive hours, and rest following Sunday work.
Key takeaways
- Check agreements for how they define a day's work.
- Plan meal periods or confirm both eating-at-work conditions.
- Check for uninterrupted rest after Sunday work.
- Review these points again when shifts change.
Most managers build a weekly schedule the same way. You look at who is available, who asked for time off, who closes on Friday, and who can cover the Sunday rush. Then you post it. Hours get a quick glance, if that. The trouble is that a few New Hampshire rules tie directly to the hours on a schedule, and they are easy to miss when you are working fast.
Those rules live in Chapter 275 of the state's revised statutes, titled PROTECTIVE LEGISLATION. Some of the wording needs a careful read. It is still worth reading, because it speaks directly to the decisions you make when you fill a shift. This post covers three rules from that chapter that matter most when you build a schedule for hourly staff. For each one, you will see the statute's words, a plain-language reading, a few examples, and a short check to run before you post.
Two ground rules first. This is a practical guide, not legal advice. If a situation involves a written contract, a union agreement, a dispute, or anything you are unsure about, bring it to an employment attorney or to the New Hampshire Department of Labor before you act. Second, the quotes here reproduce the statutory wording. Laws change, so open the official text yourself before you rely on any detail. Every quote links to the same page, Chapter 275 PROTECTIVE LEGISLATION, so you can read each rule in its surrounding text.
Rule 1: Eight hours is the default day's work in labor contracts
Start with the rule that defines a day's work. The statute says:
> "In all contracts relating to labor, 8 hours' actual labor shall be taken to be a day's work unless otherwise agreed by the parties."
Source: NH General Court, Chapter 275
In plain words, when a labor contract does not say anything different, the law treats eight hours of actual labor as one day's work. Two phrases do most of the work. The first, "in all contracts relating to labor," sets the scope. The second, "unless otherwise agreed by the parties," is the way out. The default can be changed, but only by agreement between the parties.
The word actual matters too. The rule counts actual labor, which is time spent working. That gives you a practical way to read a shift. Take the scheduled start and end times, subtract breaks during which no actual labor occurs, and compare the result against eight. A nine-hour block with a one-hour break without work leaves eight hours of actual labor. The same nine-hour block with only a half-hour break without work leaves eight and a half.
Why this matters on posting day is simple. A schedule is a set of promises about hours. If you post a ten-hour shift for someone whose contract describes a standard day, compare the actual labor with that definition. The quote defines a default day's work; it does not itself impose an eight-hour shift cap. If the agreement is in writing, you can check it in a minute. If it lives in a hallway conversation, you have a problem you can fix before the schedule goes out.
Illustrative example: checking a longer day
Consider a shift with ten scheduled hours and a one-hour break without work, leaving nine hours of actual labor. Before you post it, check whether the employee's agreement defines a day that long. If the agreement covers it, this point is settled. If the agreement is silent or describes a standard day, discussing and documenting the arrangement can help clarify expectations.
Before you post:
- Pull the written agreement or offer for each hourly employee and note any hours it sets as a standard day.
- Work out the actual labor on every shift longer than eight hours by subtracting breaks during which no actual labor occurs.
- Flag any shift that runs past eight hours of actual labor for review before it goes on the schedule.
- Keep a copy of anything an employee has agreed to in writing about longer days.
Rule 2: Check meal periods and the eating-at-work exception
The second rule is about meals. The statute says:
> "An employer may not require an employee to work more than 5 consecutive hours without granting him a 1/2 hour lunch or eating period, except if it is feasible for the employee to eat during the performance of his work, and the employer permits him to do so."
Source: NH General Court, Chapter 275
Read it in three parts. The first is the limit: an employer may not require more than five consecutive hours of work without granting a break. The second is the break itself, a half-hour lunch or eating period. The third is an exception, and it has two conditions that must both be true. It has to be feasible for the employee to eat while doing the job, and the employer has to permit the employee to do so.
The limit is about consecutive hours. A shift of exactly five hours does not go past the limit, since the rule speaks of more than five consecutive hours. A six-hour shift does. The break also has to come before the employee has worked more than five consecutive hours. A half-hour break tacked onto the end of a six-hour run does not help, because by then the limit has already been passed. Placement is part of the rule, not just the length of the break.
The schedule is where this shows up, so the most reliable habit is to look at every posted block longer than five hours and make sure a half-hour meal period appears in the times you post, not just in the employee's head. Take a stockroom employee scheduled from one in the afternoon until seven in the evening, six hours in total. If the posted schedule shows no meal period, check whether one is actually granted or the eating-at-work exception applies; posting the meal is a planning practice. Change the schedule so the employee works from one o'clock until half past three, takes a half-hour meal, then works from four o'clock until seven. That gives two blocks, with the break written in.
The exception is narrower than it looks. Some jobs let an employee eat between tasks, and many do not. A cashier who can take a bite while the line is short may fit the first condition, but only if eating during the shift is truly feasible. A line out the door, a single worker covering the whole floor, or a job where food and hands cannot mix are different cases. The second condition, permission, has to be real too. A manager who says "you can eat at the register if you want" grants permission, but a busy store may still make eating while working infeasible.
If you want to rely on the exception, treat it like a plan, not a hope. Write down the task, why eating during it is feasible, and that the employer permits it. Then ask whether that note would hold up if someone asked you to explain the schedule. If the honest answer is no, put the half hour in.
Before you post:
- Mark every shift longer than five hours.
- Put a half-hour meal period into the posted times for each marked shift, placed before the employee passes five consecutive hours of work, unless the exception applies.
- If you plan to rely on the exception, write down why eating during the work is feasible and that you permit it.
- Check consecutive work periods on split shifts too.
For a closer review of recorded meal time, see unpaid meal break review.
Rule 3: Sunday work needs a full day off in the six days that follow
The third rule concerns Sunday work. Read it anyway, especially if you staff weekends. The statute says:
> "Whoever requires an employee engaged in any occupation to do on Sunday the usual work of his occupation, unless he is allowed during the 6 days next ensuing 24 consecutive hours without labor, shall be fined not more than $50; provided that this section and the following section shall not be construed as allowing any work on Sunday not otherwise authorized by law."
Source: NH General Court, Chapter 275
The core of this rule is in the first half. If you require an employee to do the usual work of their occupation on a Sunday, the fine applies unless the employee is allowed twenty-four consecutive hours without labor during the six days next ensuing.
Two phrases need a careful read. The first is "usual work of his occupation." That reads as the job the employee normally does, not any task that happens to come up on a Sunday. The second is "24 consecutive hours without labor." The break has to be a full day with no work. A few scattered free hours that add up to a day when you total them do not meet the wording.
Here is how it plays out on a schedule. Suppose a line cook works Sunday from seven in the morning until three in the afternoon and is then scheduled Monday through Saturday at those same times each day. Each gap between shifts is shorter than twenty-four hours, so the schedule as posted does not give the break the statute describes. Now suppose the cook is off all of Tuesday. A full calendar day off, midnight to midnight, is the simplest way to show twenty-four consecutive hours without labor, provided no other work falls inside it.
The last part of the quote deserves its own attention. It says the section does not allow any work on Sunday that is not otherwise authorized by law. In other words, meeting the break requirement is not a permit. It addresses only the fine in this section. If Sunday work is restricted by another law, this section does not override those limits. Treat the Sunday check as a minimum, not a finish line.
Sunday changes also deserve a second look. A shift swapped on Friday, or a call-out that pulls someone onto a Sunday, can create a violation in a schedule that passed review last week. Run the check again whenever a Sunday assignment changes.
Before you post:
- Flag every Sunday shift that is part of an employee's usual work.
- For each flagged employee, look at the six days after that Sunday and confirm there is a full twenty-four consecutive hours with no work.
- If the schedule does not show that stretch, change the schedule before you post it.
- Check whether the Sunday work is otherwise lawful.
A quick check before you publish
For each hourly employee on the week's schedule, ask three questions:
- Hours: Does the agreement define a day's work differently from the eight-hour default?
- Meals: Does every shift longer than five consecutive hours show a half-hour meal period, placed before the limit, or a documented exception?
- Sundays: If the employee works a Sunday at their usual job, is there a full twenty-four consecutive hours without labor in the six days that follow?
Build these questions into your process rather than trying to remember them each week. If your scheduling tool offers maximum shift settings or shift notes, consider using them. If you use a spreadsheet, add a column for actual labor hours, a column for the meal period, and a column that flags Sunday shifts. Color coding works too. The point is that a conflict shows up on screen before the schedule goes out, not after an employee brings it up.
Keep a short file as well. Store copies of the agreements that set hours, and a brief note on any exception you relied on and why. The file does not need to be long. It needs to be easy to find. When a question comes up about a schedule from two months ago, a record of what you did and why will serve you far better than memory.
Finally, make the check part of the routine, not a special event. Schedules change. A shift gets swapped, someone picks up a Sunday, a call-out forces a double. Each change can break a rule you already checked. Run the same three questions on any change before it goes live, even if the original schedule passed. For the change process, see schedule change approval.
What these rules do not cover
These three rules are not the whole of Chapter 275, and they are not the whole of what affects your schedule. The chapter contains sections on other subjects. Other state and federal laws may also apply to your business, depending on its size, industry, and the work your employees do. This post does not address those, and nothing here should be read as a complete list.
Two more cautions. First, interpretation can require care. Read the current official text yourself and, where a situation is unclear, get advice from a professional who knows New Hampshire employment law. Second, the rules are only as strong as the records behind them. A schedule that looks compliant but cannot be explained is a weak position.
If you take one thing from this post, let it be this: check the hours before you check the coverage. A schedule that fills every shift but breaks one of these rules has not solved the staffing problem. It has only moved the problem to a later date.
Today, take your next unpublished schedule and run the three questions above for each employee before posting it.
Related guides: Count the daylight saving hour with these 4 clock rules · Ohio shift checks: 3 for age, pregnancy and neutral rules · Reporting time pay when a shift is cut short: 4 rules.
Questions before you post
Does the eight-hour rule cap every shift?
No; it defines a default day's work in labor contracts unless the parties agree otherwise.
Must a meal appear on the posted schedule?
The quoted rule requires granting the meal period unless the exception applies; writing it into the schedule helps you plan.
Does a Sunday rest period settle every scheduling question?
No; Sunday work must also be otherwise lawful, and other scheduling rules may apply.