Do You Actually Know What Your Employees Do?

By VICKY BROWN

Listen to this episode on

Ask a founder whether an employee is exempt from overtime, and the first thing that usually comes up is their salary. Maybe their title. How senior they sound on paper. It makes sense. Those are the things that feel visible and official.

But none of that is actually the question that matters. The real question is what that person spends their days doing, in practice, right now. And a lot of business owners, if they’re being honest, can’t answer that with much precision.

You know what the job was supposed to be. You remember writing the job description, or having someone write it, back when the role was created. You might even have a hopeful picture of what the person is doing today. What you may not know is what the job has quietly turned into.

That gap matters for exempt employee classification, obviously. But it points to something bigger too. It tells you where authority actually sits in your company. Who’s really making decisions. Who’s supervising, and who’s still elbow deep in the daily work itself.

Why founders classify the person instead of the position

Here’s where a lot of classification trouble starts. Business owners look at an employee and think: she’s experienced, he’s responsible, I trust this person to run their own day. All of that might be true. None of it is a legal description of the job.

Classification isn’t a reward for loyalty. It’s not a gold star for maturity or effort. But plenty of founders treat it that way. Moving someone to hourly can feel like a demotion. Moving them to salaried can feel like a promotion. A manager title gets handed out because someone’s been putting in the work, even when they have almost no real management authority.

Exempt doesn’t mean important. Salaried doesn’t mean senior. But it’s easy to start using classification as an emotional signal instead of a structural one, especially in a small business where relationships run deep and everyone’s worn ten hats to get the company this far.

…If you asked an employee to describe exactly how they spent the last two weeks, would it look anything like their job description? For a lot of businesses, it wouldn’t.

How the job quietly drifts

Small businesses rarely have clean, tidy positions. Someone supervises two people in the morning, handles a customer issue in the afternoon, jumps in on production when things get busy, and closes out the day doing admin work. You call that person a manager, because managing genuinely is part of what they do.

Then the company grows. And often, the hands-on part of that job expands instead of shrinking. The manager ends up covering open shifts, filling scheduling gaps, and processing the same transactions as the team they’re supposed to be leading.

At that point, the classification question is really pointing at something else entirely. If a manager can’t manage because the team is understaffed, that’s not just a wage and hour concern. It’s a sign the management structure itself isn’t functioning the way it was designed to.

If a director is spending most of the week on routine administrative tasks, maybe the role was built before there was actual director level work to hand over. Changing the payroll code doesn’t fix any of that. It just relabels the problem.

A question worth sitting with

If you asked an employee to describe exactly how they spent the last two weeks, would it look anything like their job description? For a lot of businesses, it wouldn’t.

Job descriptions tend to get written once, usually during hiring, and then nobody touches them again. Meanwhile the job itself keeps moving. Duties get reassigned. A manager leaves and someone else absorbs half their responsibilities. A new system automates the analytical part of a role, but the title stays exactly the same.

None of those individual changes feel big enough on their own to trigger a formal review. That’s exactly why the drift stays hidden for so long. The original classification might have been completely correct. Nobody ever went back to check whether it still fit.

Whether you’re an entrepreneur jumping into a leadership role, a seasoned business pro with new HR responsibilities, or just starting your HR career – we’ve got the right path to guide you through your HR hurdles.

Check out the Leaders Journey Experience.

When exempt status is solving the wrong problem

There’s a version of this that’s a little harder to say out loud. Sometimes exempt classification gets used to avoid a scheduling problem instead of actually solving a classification question.

Tracking hours is a hassle. The role has an irregular schedule. Busy season means someone has to stay late, and overtime feels unpredictable and expensive. Calling the role exempt makes all of that disappear, at least on paper. Not in reality.

Most of the time, this isn’t anyone trying to dodge overtime laws on purpose. It’s simpler than that. Staffing is thin. Schedules are managed loosely. Nobody built an approval process for extra hours, so leadership genuinely doesn’t know how long the work actually takes. When you notice the classification decision is really being driven by “this would be easier to administer,” that’s worth pausing on. The harder question underneath it is whether what you’re asking of that role is even reasonable in the first place.

Reviewing the role instead of the label

So how do you catch this before it turns into a real problem? Start by reviewing the role itself, not just the label attached to it.

Ask the employee what a typical week actually looks like, in their own words, before you hand them the job description and ask if it’s accurate. Talk to their manager about where real decision making authority sits: what can this person decide on their own, and what needs sign off. Look at how much of the role is genuinely managing people versus doing the same work as the team around them. Then hold all of that up against the job description, the org chart, the pay, and the current classification, and see how far apart they’ve actually drifted.

This isn’t about running a legal analysis on your own. It’s about gathering accurate facts before drawing a conclusion. And it helps to ask a better question than “can I defend this classification.” Ask instead whether the way you’ve built the role actually makes sense, both for the business and for the person doing it.

As a company grows, the owner naturally gets further from the day to day, which means you might still be picturing a position the way it existed a year or two ago, while the manager and employee are living inside a completely different version of it. That’s why managers matter here too. They don’t need to become wage and hour experts, but they do need to recognize when a shift in someone’s responsibilities is significant enough that it deserves a second look.

A business that can clearly explain what each person does, what they’re actually responsible for, and where they sit in the org chart is simply easier to run. Easier to classify correctly, yes, but also easier to evaluate, staff, and plan around. So if you’re sitting with a classification question right now, resist the urge to reach for a cleaner title or a tidier payroll fix. Look at the job itself first. It will usually tell you what the classification should be, and it’ll probably tell you something about the business too.

Spread the word

This website uses cookies to ensure you get the best experience on our site.