Straight into the service manual page
WrenchQuarry
More

3 overtime tests before making a team lead salaried

WrenchQuarry Editorial Team · Published · 13 min read · How these guides are written

You are about to change how a team lead is paid. Salary feels simpler. It hides the timecard and ends the weekly overtime math. That relief lasts until someone asks whether the role actually qualifies as exempt. If it does not, the hours come back, and so does the back pay.

Three tests answer the question before you make the change. Each test targets one part of the exemption: what the person is paid, what they do, and how you would prove it if anyone asked. Run all three in order. Stop at the first failure, because the later tests cannot rescue it.

This matters most to owners and dispatchers. You are the ones writing the schedule, approving the promotion, and fielding the phone call at 7:00 a.m. on a Saturday. You need to know which kind of week you are living in: a salaried week with no overtime, or a salaried week where overtime still follows.

Why salary alone does not decide the overtime question

Salary is a pay method. Exemption is a legal status. They travel together often, which is why people treat them as one thing. They are not one thing.

Oregon's Bureau of Labor and Industries states plainly that all salaried employees must be paid overtime unless they meet the test for exempt status as defined by federal and state laws. See the Oregon BOLI overtime page for employers. Salary is the starting point of the conversation, not its conclusion.

Washington's Labor and Industries agency describes a similar frame. Its notice explains that L&I is using an eight-year implementation schedule to incrementally raise how much more than the minimum wage a salaried employee must earn to be exempt from overtime. Read the Washington L&I notice 25-27. The schedule moves in stages, and the pace of the increase varies based on the size of the employer.

That structure tells you something practical. The pay threshold moves over time, and your decision should hold up across stages rather than just the week you write the offer letter.

Michigan's wage act keeps the overtime floor visible for everyone else. Section 408.934a covers compensation for a workweek in excess of 40 hours, with exceptions, rules, and compensatory time in lieu of monetary overtime compensation. The default rule requires compensation at not less than 1-1/2 times the regular rate for employment in a workweek in excess of 40 hours. The act then lists exceptions. Each exception is a doorway you must walk through deliberately.

So the first habit is separation. Ask two questions in order: is this person paid on a salary basis, and does the role meet the duties test for exemption? A yes to the first question never answers the second.

The first test: does the pay meet the salary threshold

The salary test asks whether the annual pay clears the exempt floor that applies to you. Federal rules and state rules both speak here. Federal and state floors both apply here. Where they overlap, you need to know which stage your business sits in.

Washington's approach is a staged schedule. L&I describes an eight-year implementation that raises the pay a salaried employee must earn beyond minimum wage to be exempt from overtime. The increase applies to executive, administrative and professional workers, plus computer professionals. Those are the categories the schedule touches, and your team lead must actually sit in one of them for the schedule to help you.

Size of the business changes the pace. L&I states that the pace of the increase varies based on the size of the employer. Two shops with identical team-lead pay can be on different timelines. That is not a detail to guess about; it is a fact to confirm for your payroll size before you set the number.

The practical version of test one:

  • Write down the annual salary you intend to offer.
  • Identify the exemption category the duties would fall under.
  • Confirm the pay floor that applies to your business size and jurisdiction.
  • Confirm which stage of the schedule applies now.
  • Compare your number to the floor, and treat anything below as a failed test.

A floor can change by year, and a floor can change by employer size. Set a calendar note to re-check the figure when your payroll crosses into a larger size band. A salary that passes today can fail next year without anyone touching the offer letter.

Oregon's guidance carries the same warning in sharper words. BOLI cautions that misclassification of salaried employees as exempt creates liability for unpaid overtime. That is the cost of a quiet assumption, and the liability sits with the employer.

Michigan's act is the reminder of what you are trying to avoid. For employees who are not exempt, the default rate is 1-1/2 times the regular rate above 40 hours in a workweek. The act also sets out alternative computations. In a work period of 28 consecutive days, the employee receives for tours of duty that in the aggregate exceed 216 hours compensation for those hours in excess of 216 at a rate not less than 1-1/2 times the regular rate. In a 14-day period accepted under a written agreement or written employment policy arrived at before performance of the work, the computation changes again: for employment in excess of 8 hours in a workday and in excess of 80 hours in the 14-day period, the employee receives compensation at 1-1/2 times the regular rate, which shall be not less than the statutory minimum hourly rate.

Those alternatives exist for non-exempt staff, and that is their whole point. If your team lead fails the salary test, every one of those computations becomes your problem again.

The second test: does the work match the duties the exemption requires

Pay clears the gate, and duties decide whether the person stays inside it.

The Washington notice names the groups the schedule affects: executive, administrative and professional workers, plus computer professionals. A team lead title matches none of them by itself. The duties have to. Ask what the lead actually does in a normal week: hiring decisions, assigning work, approving output, resolving escalations, setting standards, or mostly running jobs and covering calls.

Ask what the lead actually does as the main event of a normal week. Oregon's guidance puts the burden on the employer to prove exempt status, which means you must be able to describe the job in duties rather than in aspirations. A plan to give someone more authority later does not help if the current week is all wrench time.

Here is how to run the second test without a lawyer in the room:

  • List the tasks. Write out what the lead did last week, hour by hour if you can, using the real schedule rather than the job description.
  • Name the exemption category. Pick one: executive, administrative, professional, or computer professional. Washington's schedule names these three plus computer professionals.
  • Match duties to that category. Each category expects certain kinds of work as the main event, and a main event of running jobs with their own hands makes the match thin.
  • Look for the conflict. If the duties pull in two directions at once, resolve that conflict before you decide on a category.
  • Decide with the paperwork. Your conclusion should be written down, dated, and attached to the role, and any conclusion you cannot defend in writing fails the test.

Dispatchers see this conflict in real time. The lead takes the emergency call, jumps on the job, then writes up the schedule at night. From the office it looks like leadership. From a duties test it may look like a skilled worker who also helps. The line between those two descriptions is exactly where overtime claims are won.

One question these sources leave open deserves a single answer here: which specific duties checklist applies to your team lead in your jurisdiction. Ask your state labor agency or your employment counsel for the current duties checklist before you finalize the classification, then write their answer into the offer file.

The third test: can you prove the status if anyone asks

The third test is about proof: facts, dates, and documents rather than good intentions.

Oregon states that the employer's burden to prove exempt status of employees sits on the employer. If the record is thin, the claim goes the other way.

Think like an auditor. Imagine someone asks six months from now why this role was exempt. What do you hand over? The file should answer without anyone having to reconstruct a memory.

Build the file before you announce the salary:

  • Signed offer. Salary amount, pay period, and start date in plain language.
  • Duties summary. The category you chose and a short list of the main tasks.
  • Notes of the decision. Who reviewed it, on what date, and against which pay floor.
  • Pay floor confirmation. The figure you checked, the source you checked, and the size band of your business.
  • Training record. Proof the lead was shown the role, not just told the title.
  • Review date. A calendar date to re-run all three tests.

This file costs an hour to build, and missing it costs far more. Misclassification creates liability for unpaid overtime, and the employer has to prove the status. A dated folder turns a painful argument into a simple walkthrough.

Washington's staged schedule adds a reason to keep the file alive. The pay floor moves over eight years, and the pace varies with employer size. Your file should note which stage you checked and when, so the next review has a starting point.

Michigan's act, for the staff who are not exempt, shows what the records need to support: hours in a workweek above 40 at 1-1/2 times the regular rate, and for an accepted 14-day period, hours above 8 in a workday and above 80 in the period. Whatever schedule you run for non-exempt staff, the team lead's exemption file should show you compared their pay and duties to the standard that applies.

Here is the comparison your pay file should answer at a glance:

TestCore questionEvidence to keepWhat a fail means
PayDoes the annual salary clear the applicable exempt floor?Pay floor figure checked, your salary figure, date checked, employer size bandOvertime still applies
DutiesDoes the role's main work fall into an exemption category?Duties summary, chosen category, notes from the decision makerReclassify before the salary starts
ProofCan you show all of the above if asked?Offer letter, training record, review date, size-band confirmationStatus is unproven, and unproven loses

Keep the table in the offer folder as the index to the file rather than a replacement for it.

What a clean promotion packet looks like

A clean packet for one team lead runs about a page and a half. The offer letter says the salary and the start date. A second page carries the duties summary and the category you selected. A third line records the pay floor you checked and the date you checked it. The reviewer signs, you file it, the lead signs, and you file their copy.

That is the whole discipline. Nothing in it requires a lawyer in the room, though one can review it once and save you later. The point is that the decision exists outside anyone's memory.

When the answer is no: the honest path back to hourly

Some leads will fail the pay test. Others will fail the duties test. The honest path is to say so early, before the offer goes out.

If the pay floor is above what the business can sustain, the role stays hourly. Say that to the person, explain the overtime rules that apply, and then set up a plan to revisit when the business can meet the floor. A clear no builds more trust than a soft yes that unravels at the first audit.

If the duties test fails, the fix is usually structural. Move real authority onto the role: scheduling, approval of work quality, and input on who works which job. Or keep the title as a recognition and keep the pay as hourly with overtime. Both paths are honest. What fails is the middle road where the title says one thing and the paycheck says another.

Oregon's warning applies here directly. Misclassification of salaried employees as exempt creates liability for unpaid overtime, and the risk attaches to hours already worked rather than to hypothetical hours in the future.

Running the tests on real schedules

Duties do not live on paper; they live in the week. Before you set the salary, pull two or three recent schedules for the person you have in mind, and read them as an outsider would.

Count the hours spent on core production, then count the hours spent assigning, reviewing, and resolving. If the production count is heavier, the duties test is shaky. If the management count is heavier, the test is stronger.

Do the same for the pay. The busiest week is the one that matters, because that is the week a claim would focus on.

This is not arithmetic for its own sake; it is a way to pressure-test the label before you commit. The salary test looks at a floor, the duties test looks at a week, and the proof test looks at your file. Run all three against real data rather than a job description written for a different person.

Questions owners ask before signing the offer

If the lead sometimes works more than 40 hours, does overtime start automatically? Not automatically. It starts if the role does not meet the exempt tests, because salary does not end the overtime obligation by itself. Oregon's guidance makes that plain: all salaried employees must be paid overtime unless they meet the test for exempt status.

What if our business is small and the floor has not reached us yet? Washington's schedule paces the increases by employer size. Two years from now your size band may sit in a different stage than today. Confirm the figure that applies to your band, note the date you confirmed it, and set a review date.

Can we just call the role exempt in the offer letter and move on? The label is not the proof. The employer carries the burden to prove exempt status, so you must be able to show the duties summary, the pay floor check, and the decision date before the label carries weight when someone asks.

Which test should we run first? Pay. If the salary sits below the applicable floor, the duties and proof tests never get a chance to save the decision. Stop there, adjust the number or the arrangement, then continue.

What if the duties genuinely sit in the middle? Middle is not a category. Choose the category that matches the main event of the week, document why, and set a review date. If the main event changes, re-run all three tests.

Who should we ask when a source leaves a detail open? Your state labor agency or your employment counsel. Ask them for the current duties checklist for your jurisdiction, then put their answer in the file.

Final checklist before the salary goes live

Work through this list the same week you write the offer:

  • Salary figure written down. Annual amount, pay period, start date.
  • Pay floor checked. Figure, source, date, employer size band.
  • Stage confirmed. Which stage of the schedule applies to your business now.
  • Duties summary written. Main tasks of a real recent week, not the job ad.
  • Category selected. Executive, administrative, professional, or computer professional, whichever fits the actual work.
  • Decision notes attached. Who reviewed, on what date, against which floor.
  • Offer letter drafted. Plain language, no title games.
  • Training scheduled. The lead hears the role, the duties, and the pay structure from you.
  • Review date set. A calendar date to re-run all three tests.
  • Offer filed. Signed copy, both sides, same folder.

Run the three tests in order and keep the file honest. Salary then becomes a clean decision rather than a hope, the hours stop being a surprise, the schedule stops being a risk, and the promotion you wanted to give lands without a shadow over it.

General information, not legal or tax advice.

Sources

More field guides