Weekly staff hours: 6 checks before you approve

Key takeaways

• Compare raw punches with the hours submitted for approval.
• Review deductions against the Oregon or Minnesota rule linked below.
• Hold unclear timesheets and ask payroll or HR before approval.

If you approve hours for hourly staff in Oregon or Minnesota, that decision is more than a quick scan. State rules on overtime, rounding, waiting time, sleep, and breaks need a closer look before approval.

This post walks through six things to check before you sign off. Each one points to a number, a date, or a rule that you can verify yourself. Where a point comes from an official state page, the link goes to that page so you can read the exact wording.

This is a practical guide, not legal advice. Your payroll provider, your HR team, or an employment attorney can answer questions about your specific workplace. When in doubt, ask before you approve.

The six checks below are grouped by state. Oregon comes first, with overtime, rounding, waiting time, and sleep. Minnesota follows, with rest periods and meal periods. If you manage staff in both states, you can use the same weekly routine for each one and keep the state-specific notes in a separate list.

Hours over 40 in the workweek

Start with the total. In Oregon, the rule that matters most for weekly approval is overtime. The Bureau of Labor and Industries states that covered workers "must also receive at least one and one-half times their regular rate of pay for hours worked over 40 each workweek" (BOLI, Paid time).

That sentence contains three checks.

First, count each workweek separately. A manager cannot approve a two-week total and assume the split worked out. Pull the hours for each workweek and add them up yourself, especially if your timekeeping system shows only daily totals or payroll totals.

Second, check for hours above the threshold. A paycheck that looks normal can still hide this, because the extra hours may have been paid at the straight rate.

Third, the rate is based on the regular rate of pay. Look at the rate printed on the timesheet and compare it with what the employee is actually paid for regular hours. If the overtime line uses an old wage, a rounded figure, or a number typed in from memory, fix it before approval.

Illustrative example: combine the weekly hours

Suppose an employee covered by Oregon's overtime rule works 40 hours early in a workweek and 20 hours later in that same workweek. The total is 60 hours, including 20 overtime hours. Separate payroll reports could hide that weekly total. Add the hours together before checking the overtime line.

A simple habit helps here. Keep a short weekly note for each employee that lists total hours by workweek and the overtime hours you approved. It takes a few minutes and gives you a clear record if someone asks later. For related coverage questions, see overtime coverage rules.

Rounded and edited punch times

If your timekeeping system rounds clock punches, review its settings. The Oregon page allows rounding with precautions. The concern is what the rounding does to real hours over time.

Oregon has been a place where this question has been tested in court. The Bureau's page notes that the "District Court for Oregon issued a ruling November 29, 2022 holding that Oregon's law about tracking and rounding work hours was different than federal law" (BOLI, Paid time). The practical lesson is that a rounding setting copied from a national setup or a vendor default may not fit Oregon's rules. Check the setting against the state page, not only against your software's default.

The same page also states that "while employers may apply a rounding system to the times when employees clock in and out, employers also need to implement precautions to ensure employees are getting paid for all work time each pay period" (BOLI, Paid time). That sentence is the heart of this check.

Here is what to look at before you approve:

• Pull a sample of raw punches for one employee and compare them with the rounded totals. Does rounding ever remove time the employee actually worked?
• If rounding seems to move time in only one direction, treat that as a warning sign and ask your payroll or HR contact to review the setting.
• If you edit a punch by hand, record why. A manual edit that drops time from the total needs a clear reason and a second look.

Rounding that looks harmless on a single day can add up across a month. Rounding a few minutes down at the end of a shift may seem trivial, but if it happens every week, the total shows up in the employee's pay. Check the pattern, not just the one timesheet on your screen.

It also helps to ask the employee. A short conversation about whether their punches look right can surface problems that a report will never show, such as a clock that is hard to reach or a habit of starting work before the first punch. See timesheet approval and edit rules when reviewing the approval process itself.

Waiting time: engaged or waiting to be engaged

Gaps in a shift are easy to overlook. A worker sits at a station waiting for a truck, a patient, or a customer. Is that time paid? The answer depends on how the time is classified.

The Oregon page explains that "wage and hour law divides waiting time into two categories: (1) Engaged to wait and (2) Waiting to be engaged" (BOLI, Paid time). The two categories are different, and the difference matters for what you approve.

Before you approve a timesheet with a waiting period, ask three questions:

• Was the employee required to stay on the premises or at a specific post?
• Was the employee still on duty, ready to take work at any moment?
• Did a supervisor or a process tell the employee to wait there?

If the honest answer leans toward "yes" on these questions, do not assume the time came off the clock correctly. Read the full section of the Oregon page, and when the answer is not clear, ask someone who knows the law for your workplace before you approve.

Waiting time is also where a manager can make a quiet change without meaning to. A supervisor might tell an employee to clock out during a slow hour and clock back in later, to keep a shift tidy. Whatever the reason, that kind of edit should be checked against the two categories above before you approve it. Ask whether the employee was free to leave or was still expected to be ready for work. The answer may not match the timesheet.

A useful way to review a shift is to write two short notes: one for the time the employee was working, and one for each gap. If you cannot tell which category a gap belongs in, do not approve it until you have asked.

Sleep on shifts under 24 hours

Some jobs include long shifts during which workers are allowed to sleep, and some managers see this more often than others. If your timekeeping system applies an automatic sleep deduction, review it against the shift's length. Before you approve a week that includes one, check whether the shift qualifies for that deduction.

The Oregon page is direct on the length of the shift: "if the shift is less than 24 hours, sleep may not be excluded from hours worked" (BOLI, Paid time).

That sentence gives you a clear question to ask about any short shift. Check whether any sleep time was deducted. Look at the timesheet and find out:

• How long was the full shift, from first punch to last punch?
• Is there an automatic sleep deduction on the timesheet?
• Has any deducted sleep time on a shift under 24 hours been restored?

The quoted wording is a prohibition, not a suggestion. Use it to check the deduction. Do not approve a short shift with a sleep deduction just because the system applied it by default.

A good habit is to set your timekeeping system to flag any sleep deduction on a shift under 24 hours. A flag gives you a chance to look before the hours are final.

Rest periods under 20 minutes

Now the checks for Minnesota. The state's administrative rule on rest and meal periods gives two numbers that matter every week. The first is about short breaks: "rest periods of less than 20 minutes may not be deducted from total hours worked" (Minnesota Office of the Revisor of Statutes, 5200.0120).

Check whether your timekeeping system applies automatic break deductions. If it does, compare each deduction with the actual break rather than accepting the setting alone. Look for these patterns:

• A fixed break deduction on every shift, even when the employee clocked in and out for breaks at other times.
• Breaks that show up in the timesheet as deductions but do not match the punch record.
• A supervisor who edits a shift to remove a short rest period without a documented reason.

When you find one of these, correct it before approval. If you are not sure whether a particular break counts as a rest period, ask your payroll contact. The point is to catch the deduction before it becomes a habit that repeats every week.

Read the full page and confirm the rest of your policy with your HR team.

Meal periods of thirty minutes

The second Minnesota number concerns meal periods. The rule describes thirty minutes or more as ordinarily long enough for a meal period (Minnesota Office of the Revisor of Statutes, 5200.0120).

The word "ordinarily" matters. The rule describes what is usually enough. It does not promise that every thirty-minute break will qualify, and it does not say that a shorter break can never qualify. A meal break shorter than thirty minutes deserves a closer look, and so does any break that the employee was asked to take in a way that did not really let them stop working.

Before you approve a week with meal deductions, ask:

• Is the meal period deducted automatically, or does it match the actual punches?
• If the period is shorter than thirty minutes, why? Is there a documented reason, and does the rule support it?
• Was the employee actually free to leave their duties during the break? Record any calls, line watching, or paperwork for payroll or HR to review before approval.

That last question is where many errors hide. Ask payroll or HR to resolve questions about work during a deducted meal period. Check the punches and the work context together.

Meal periods also connect back to rounding. If a meal punch is rounded, the rounding can shorten or lengthen the deduction. Look at the raw times before you accept the total.

Here is a useful test for any meal deduction. Imagine the employee were asked, at the end of the week, to describe how the break actually went. Could they say they were off duty for the full period? If the honest answer is no, or if the answer depends on who you ask, the deduction needs a second look before it goes into the payroll total.

Putting the six checks into your weekly routine

You do not need to run all six checks in the same way every week.

• Add the hours for each workweek and check the overtime line.
• Compare rounded totals with raw punches, and look for one-directional drift.
• Scan the shift for waiting time and decide whether it was on duty or off duty.
• Review sleep deduction flags in Oregon.
• Compare Minnesota rest deductions with the punch record.
• Review Minnesota meal deductions against the actual break.

Expect the first few weeks to take longer. Once you know where your timekeeping system tends to go wrong, such as an automatic deduction that never matches the punches, you can focus your attention on those spots and move faster on the rest.

If a check raises a question you cannot answer, do not approve the week and hope it works out. Hold the timesheet, write down what you saw, and ask the person who manages payroll or HR. Resolve the question before approval.

Finally, keep the sources close at hand. Keep the Oregon Bureau of Labor and Industries page on paid time and the Minnesota rules at 5200.0120 available to confirm details before you act. The goal of approval is not speed. It is a timesheet you can explain to the employee, to your payroll team, and to a state agency if one ever asks.

Today, pull one employee's weekly timesheet and compare its deductions with the raw punches; write down any mismatch for payroll or HR.

Questions before approval

What should I do with an unclear deduction?

Hold the timesheet and ask payroll or HR to resolve it before approval.

What records should I compare?

Compare raw punches, rounded totals, deductions, and the employee's account of the shift.