Category: From the Files of HR Answers

Client: “We are a customer-focused organization, and our teams do a great job serving the public. The problem is, some of those same great service skills don’t seem to show up when they’re working with other departments. How do we shift that?” 

Consultant: This is more common than people think. We often talk about customer service as though it only happens when we are helping the public, a client, or a community member. But internal customers come first. If departments do not communicate well, respond timely, and support each other’s work, the external service experience eventually feels it. Great customer service starts inside the organization. 

Client: “That’s exactly it. They’re polite and helpful with customers, but internally it can feel like, ‘That’s not my problem.’” 

Consultant: That’s where expectations come in. Internal customer service needs to be clearly named as part of the job, not treated like a nice extra. Responding to coworkers, meeting internal deadlines, sharing information, and solving problems across departments are all part of serving the organization. 

You might say: 

“We serve our customers best when we serve each other well internally. Timely communication, respectful problem-solving, and follow-through across departments are expectations of how we work here.” 

Client: “I like that. But how do we make it more than just a nice statement?” 

Consultant: Managers and supervisors have to model it first. If leaders roll their eyes at another department, ignore requests, blame other teams, or treat internal requests like interruptions, employees will follow that lead. 

Leaders should be asking: 

“Are we responding to internal requests the same way we expect employees to respond to the public?” 

If the answer is no, that’s the place to start. 

Client: “So this is really a culture issue?” 

Consultant: Yes, and culture shows up in daily behavior. It shows up in whether emails get answered, whether handoffs are clear, whether departments talk to each other with respect, and whether people follow through when they say they will. 

The message should be simple: internal customer service is not about one department serving another department’s ego. It is about helping the whole organization function well. 

Client: “What if one team feels like another team is constantly making unreasonable requests?” 

Consultant: That’s an important distinction. Internal customer service does not mean saying yes to everything. It means responding professionally, clarifying priorities, explaining timelines, and working toward a solution. 

Instead of ignoring the request or getting defensive, employees can say: 

“I understand what you need. Here is what we can do, here is the timeline, and here is what I need from you to move it forward.” 

That kind of response is respectful, realistic, and accountable. 

Client: “What if we have specific employees or supervisors who are part of the problem?” 

Consultant: Then it needs to be addressed directly. If someone is consistently dismissive, unresponsive, or difficult to work with, that is a workplace behavior issue. Start with coaching, but be clear. 

You might say: 

“I’ve noticed a pattern of delayed responses and frustration in your communication with other departments. I want to be clear that internal service is part of your role. We need you to respond professionally, communicate timelines, and help resolve issues rather than creating barriers.” 

Client: “And if they say they’re too busy?” 

Consultant: Being busy may explain a delay, but it does not excuse poor communication. A quick response that says, “I received this and will get back to you by Friday,” is still service. Silence creates frustration. So does making another department chase you for information. 

Client: “How do we hold people accountable without making it feel heavy-handed?” 

Consultant: Build it into regular expectations. Talk about it in team meetings. Include it in performance conversations. Recognize employees who collaborate well across departments. And when there are problems, address them the same way you would address poor service to the public. 

You might say: 

“Our expectation is that we treat internal customers with the same professionalism we provide externally. When that does not happen, we will coach it, document it if needed, and hold people accountable.” 

Client: “So the key is to define internal customer service, have leaders model it, and follow through when behavior does not match the expectation?” 

Consultant: Exactly. Internal customer service is not fluff. It is how work gets done. When teams communicate well, respect each other’s roles, and follow through, the whole organization gets stronger. 

And if the customer is calling from inside the house, we still answer professionally. 

Client: “My boss says we need an HR audit. I don’t know why, and honestly, I think I’m doing everything right. Should I be worried?” 

Consultant: I understand why that would feel unsettling. When someone says “audit,” it can sound like they are looking for mistakes. But an HR audit does not automatically mean something is wrong. In many cases, it means the organization wants a clearer picture of what is working, what needs attention, and where risk may be hiding. 

Client: “That makes sense, but it still feels like they don’t trust what I’m doing.” 

Consultant: That is a natural reaction. The first step is to find out the “why” behind the request. Your boss may be responding to growth, leadership changes, a Board request, a compliance concern, outdated policies, turnover, or simply a desire to strengthen systems. 

You might say: 

“I want to make sure I understand the goal of the audit. Is there a specific concern we are trying to address, or are we looking for a general review of our HR practices and compliance?” 

That question keeps the conversation constructive instead of defensive. 

Client: “What if there is a specific concern and they just haven’t told me?” 

Consultant: Then it is even more important to ask. You do not need to assume the worst, but you do need enough information to help the process succeed. 

Try this: 

“If there are particular areas you want reviewed, it would be helpful for me to know that upfront so I can gather the right materials and understand the priority.” 

This shows professionalism. You are not resisting the audit. You are helping define it. 

Client: “So what does an HR audit actually look at?” 

Consultant: An HR audit usually looks at the systems, documents, and practices that support employment decisions. Depending on the scope, that may include personnel files, I-9s, policies, job descriptions, wage and hour practices, leave processes, hiring practices, onboarding, performance management, supervisor documentation, and required training. 

It is not just about finding problems. A good audit also identifies what you are already doing well. 

Client: “That part helps. I think I’m worried they’ll find one missing form and decide I’ve failed.” 

Consultant: A helpful audit should not be a “gotcha” exercise. Most organizations have gaps somewhere. Sometimes the gap is a missing document. Sometimes it is an outdated policy. Sometimes it is an informal practice that works most of the time, but creates risk when a difficult situation comes up. 

The value of the audit is that it gives you a roadmap. It helps separate urgent compliance issues from lower-priority clean-up items. 

Client: “What should I ask before the audit starts?” 

Consultant: Ask a few practical questions so everyone is aligned. 

You might ask: 

“What is the purpose of the audit?” 

“What areas are included?” 

“Is this focused on compliance, process improvement, risk reduction, or all of the above?” 

“What will the final report be used for?” 

“What timeline are we working with?” 

“Who should be involved in gathering information?” 

These questions help turn a vague request into a manageable project. 

Client: “What if the audit finds things that need to be fixed?” 

Consultant: Then you have useful information. That is the point. Finding an issue in an audit is much better than finding it during a complaint, investigation, agency inquiry, employee dispute, or lawsuit. 

You can frame it this way: 

“I’m glad we identified this now. Let’s prioritize the items that create the most risk and build a practical plan to address them.” 

That response shows leadership and ownership. 

Client: “I like that. I don’t want to sound defensive, but I also don’t want people thinking HR is a mess.” 

Consultant: Exactly. The message should be: we are reviewing our systems because responsible organizations review their systems. Payroll gets reviewed. Finances get reviewed. Safety practices get reviewed. HR should not be different. 

An audit can confirm good practices, strengthen weak spots, and help leadership understand the resources HR may need. 

Client: “What do you mean by resources?” 

Consultant: Sometimes audits reveal that the issue is not effort—it is capacity. HR may be doing the best it can with limited time, outdated forms, unclear supervisor processes, or no centralized system. 

An audit can help leadership see where support is needed, whether that means updated templates, supervisor training, better tracking tools, policy revisions, or more realistic timelines. 

Client: “So it may actually help me explain what I’ve been trying to say?” 

Consultant: Absolutely. A well-done audit can give language and structure to things HR already knows. Instead of saying, “We need better documentation,” the audit may show where documentation is inconsistent, why that matters, and what steps will improve it. 

That is much easier for leadership to understand and act on. 

Client: “How should I respond to my boss now?” 

Consultant: Keep it calm, curious, and collaborative. 

You might say: 

“I’m open to the audit and want to make sure we get the most value from it. Can we talk about what prompted the request, what areas you want reviewed, and what you hope we will learn from the process?” 

That response shows confidence. You are not assuming blame. You are asking for clarity. 

Client: “So the key is not to panic, ask why, understand the scope, and use the findings as a roadmap?” 

Consultant: Exactly. An HR audit is not a declaration that something is wrong. It is a tool to understand where things stand and where they can be stronger. 

Audit is not a dirty word. Sometimes it is just the checkup your HR systems need before a real problem appears. 

And if you need help defining the scope, gathering documents, or turning audit findings into a practical action plan, we are here to help. 

Client: “I have a new employee who has only been here about 30 days, and they’re already asking about a promotion. They’re doing well so far, but it feels really soon. How do I respond without discouraging them?” 

Consultant: First, take a breath. Ambition is not a bad thing. In fact, it is great when a new employee is excited about growth. The caution is making sure enthusiasm does not outrun your systems. 

A promotion should not be based only on early energy, a strong first impression, or the fact that someone is eager. It should be based on clear standards, demonstrated readiness, and an actual organizational need. 

Client: “That makes sense. I don’t want to shut them down, but 30 days feels way too soon to know if they’re ready.” 

Consultant: Exactly. At 30 days, you may have a promising start, but you probably do not have enough information to confirm sustained performance. A promotion means the employee has consistently demonstrated the skills, judgment, reliability, and results needed for the next level. 

You might say: 

“I appreciate your interest in growing with us, and I’m glad you’re already thinking about your future here. Since you’re still early in your role, our focus right now is making sure you have a strong foundation. Let’s talk about what readiness for future opportunities looks like.” 

That keeps the door open without making a premature commitment. 

Client: “What if they say they already know the job and are ready for more?” 

Consultant: That is where clear measurement matters. Promotion decisions should be tied to defined criteria, not confidence alone. What does the next role require? What skills, outcomes, behaviors, or certifications must be demonstrated? Has the employee shown those things consistently over time? 

You might say: 

“I’m glad you’re feeling confident. For us to consider a promotion, we look at specific readiness factors, including performance in the current role, consistency over time, ability to work independently, decision-making, teamwork, and the requirements of the next position. Let’s use those as our guide.” 

This shifts the conversation from “I feel ready” to “Here is how readiness is measured.” 

Client: “I also worry that if I talk about growth, they’ll think I’m promising a promotion.” 

Consultant: That is an important distinction. Development conversations are not promises. You can support an employee’s growth while being clear that promotions depend on both readiness and business need. 

Try this: 

“I want to support your development, and I also want to be clear that a promotion depends on two things: demonstrated readiness and an available position that meets the organization’s needs. We do not create a promotion simply because someone is doing well; we promote when the role exists and the person is ready for it.” 

That is honest, kind, and practical. 

Client: “So I should be clear that there has to be an actual opening?” 

Consultant: Yes. This is a big one. A promotion is not just a reward for good performance. It is movement into a different role or level of responsibility. If there is no vacant position, no approved structure, or no business need for the higher-level work, then it may not be the right time. 

You might say: 

“Right now, we do not have a vacant position at that level. That does not mean growth is off the table. It means our next step is to focus on development, continued performance, and preparing you for future opportunities when they become available.” 

This avoids creating a job that the organization does not actually need. 

Client: “What should I give them instead of just saying no?” 

Consultant: Give them a roadmap. Identify what they should focus on over the next several months. That might include mastering core duties, learning additional systems, taking on a project, improving technical knowledge, or building communication and problem-solving skills. 

You could say: 

“Here are the areas I’d like you to focus on first: consistently meeting expectations in your current role, building depth in our processes, and demonstrating independent problem-solving. We can check in again at your 90-day mark and talk about what progress looks like from there.” 

That gives them something productive to work toward. 

Client: “What if they keep pushing?” 

Consultant: Stay steady. You can acknowledge their ambition while reinforcing the process. 

Try this: 

“I appreciate your motivation, and I do not want to discourage that. At the same time, promotion decisions have to follow our process. We need enough time to assess sustained performance, and there must be an available position that matches the business need.” 

This keeps the conversation from becoming personal. 

Client: “So the key is to encourage the ambition, but bring it back to the system?” 

Consultant: Exactly. A promotion conversation should never be based on pressure, enthusiasm, or fear of losing someone. It should be based on clear standards, consistent measurement, and the organization’s actual staffing structure. 

When you respond with clarity, the employee learns something important: growth is welcome here, but it is thoughtful, fair, and tied to real readiness. 

And if you need help building promotion criteria or career path language, we’re here to support you. 

 

Client: “I’m new to HR. I took the classes, got the certification, and I thought I understood the rules. But now I’m in the workplace, and employees and managers don’t follow the theory. HELP!” 

Consultant: First, welcome to real-life HR—where the textbook was helpful, the certification was valuable, and the people did not read Chapter 4 before arriving at work today. 

You are not doing anything wrong. This is the moment when HR shifts from “knowing the rules” to learning how to apply them with actual humans, competing priorities, different communication styles, and managers who may be learning right alongside you. 

Client: “That makes me feel better, but also…where do I even start?” 

Consultant: Start with the basics. When things feel messy, HR foundations are your friend. 

That means asking: 

Do we have a policy? 

Do we have a process? 

Do people know the process? 

Are we applying it consistently? 

Have we documented what happened? 

It sounds simple, and that is the point. When you are new to HR, it is easy to feel like every situation needs an advanced strategy. Most of the time, the first step is just getting back to the foundation. 

Client: “What if the manager says, ‘That’s not how we usually do it’?” 

Consultant: That sentence should make your HR antenna go up—not in a panic, but with curiosity. 

You can say: 

“I understand that may be how it has been handled before. Let’s look at the policy and the reason for the process so we can make sure we are being consistent.” 

This keeps the conversation calm and professional. You are not accusing anyone of doing it wrong. You are simply bringing the discussion back to the organization’s expectations. 

Client: “What if employees don’t understand why HR is asking for certain things?” 

Consultant: That happens all the time. Employees may experience HR processes as unnecessary steps, delays, or “extra paperwork.” They do not always see the compliance, fairness, or documentation reason behind the request. 

So explain the why. 

For example: 

“I know this feels like an extra step, and we use this process so requests are reviewed consistently and we have a clear record of what was discussed.” 

Or: 

“I’m asking for this information because it helps us understand what support may be appropriate and keeps the process fair for everyone.” 

You do not need to over-explain every legal concept. Just give enough context so the person understands this is not random HR confetti being thrown into their day. 

Client: “What about managers? I thought they would already know how to handle employee issues.” 

Consultant: Some do. Some don’t. Some are wonderful technical experts who were promoted and then handed people problems with very little training. That does not make them bad managers. It means they may need structure, coaching, and reminders. 

With managers, focus on practical guidance: 

“What happened?” 

“What have you already said to the employee?” 

“What does the policy say?” 

“What outcome are you looking for?” 

“What documentation do we have?” 

These questions slow the situation down and help move the manager from reaction to process. 

Client: “What if they want to jump straight to discipline?” 

Consultant: Then you help them pause. One of HR’s most helpful roles is asking, “Are we there yet?” 

You might say: 

“Discipline may be appropriate, and before we decide that, let’s make sure expectations were clear, the employee had an opportunity to respond, and we have the facts documented.” 

This does not block accountability. It strengthens it. 

Client: “I think I’m worried people expect me to know everything.” 

Consultant: They might and that does not mean you have to pretend you do. 

A strong HR response is not always immediate. Sometimes the best answer is: 

“I want to make sure I guide this correctly. Let me review the policy and follow up with you.” 

That is not weakness. That is good HR. 

The goal is not to be a walking encyclopedia. The goal is to be steady, thoughtful, and reliable. 

Client: “So I don’t have to have the perfect answer right away?” 

Consultant: Correct. Please release yourself from the fantasy that HR professionals have a magical binder labeled “Every Weird Thing That Could Happen at Work.” 

We wish. It would be laminated. 

What you do need is a habit of returning to the basics: policy, process, consistency, communication, and documentation. 

Client: “What should I focus on building first?” 

Consultant: Build a simple HR toolkit. Nothing fancy—just useful. 

Start with: 

A reliable employee handbook 

Clear forms for common requests 

A documentation template for manager notes 

A checklist for new hires and separations 

A process for complaints and investigations 

A calendar for key deadlines 

A habit of confirming important conversations in writing 

These tools help you respond consistently, even when the situation feels new. 

Client: “And what about the people side? Because that’s the part that feels unpredictable.” 

Consultant: It is unpredictable. Employees and managers are all different. Some need a lot of explanation. Some need reassurance. Some need boundaries. Some need to be reminded that “I didn’t know” is not a long-term strategy. 

Your job is not to make everyone respond the same way. Your job is to create enough structure that different people can still move through the same fair process. 

Client: “That helps. So the answer is not that theory was wrong—it’s that theory is only the starting point?” 

Consultant: Exactly. The classes and certification gave you the map. The workplace gives you weather, detours, potholes, and occasionally someone who insists they have always driven through the flower bed and it has been fine. 

That is where HR judgment develops. 

You will learn when to coach, when to document, when to slow things down, when to escalate, and when to say, “No, we are not doing that.” 

Client: “So what should I remember when I feel overwhelmed?” 

Consultant: Remember this: HR is learned in layers. 

You do not need to master every situation on day one. Start with the foundation, ask good questions, use your resources, and keep people moving toward fair and consistent practices. 

And when theory meets reality, take a breath. You are not behind—you are becoming an HR professional. 

And if you ever need help sorting through the “this was not in the textbook” moments, we’re here to support you. 

Client: “We have an employee who disagrees with their performance rating, and now they’re comparing themselves to others. They’re saying things like, ‘I do more than they do,’ or ‘Why did they get a higher rating than me?’ How do we handle that without getting pulled into a debate about everyone else?” 

Consultant: This is such a common performance review challenge. When employees are disappointed or frustrated, comparison can feel like their strongest argument. The key is to acknowledge what they are saying, but redirect the conversation back to their own performance, goals, and measurable expectations. 

Client: “So I shouldn’t respond to the comparison?” 

Consultant: You don’t want to debate another employee’s performance, rating, workload, or manager feedback. That’s not information you can appropriately discuss, and it usually takes the conversation in the wrong direction. 

You can say: 

“I hear that you have concerns about how your performance compares to others. I can’t discuss another employee’s review or rating. What I can do is walk through your goals, the expectations for your role, and the specific reasons for your rating.” 

That keeps the conversation respectful, but firmly centered where it belongs. 

Client: “What if they say the rating is unfair?” 

Consultant: Then go back to the foundation of the review: pre-defined goals, known measures of success, and documented examples. A rating should not feel like a mystery or a personality judgment. It should connect to what was expected and what actually happened. 

You might say: 

“Let’s look at the goals we set for this review period and the measurements we agreed would show success. My intent is to make sure you understand how the rating was determined, even if you don’t agree with it.” 

This helps move the discussion from emotion to information. 

Client: “What if they bring up specific coworkers and say, ‘I know I did better than them’?” 

Consultant: Stay neutral. Don’t confirm, deny, or compare. Instead, redirect. 

Try: 

“I understand that it may feel natural to compare your performance with others. For this conversation, we need to focus on your role, your goals, your outcomes, and what success looks like for you moving forward.” 

If they keep pushing, you can repeat the boundary: 

“I’m not able to discuss another employee’s performance. I am prepared to discuss yours in detail.” 

Client: “That sounds firm, but I don’t want to dismiss what they’re telling me. What if their comparison actually points to a bigger issue?” 

Consultant: That’s an important point. Redirecting the conversation does not mean ignoring the information. Sometimes an employee’s comments may reveal something worth reviewing later, such as inconsistent expectations, unclear measurements, rating inflation, favoritism concerns, or a need for better manager calibration. 

You can say: 

“I’m going to keep today’s conversation focused on your review. I also hear that you’re raising a concern about consistency, and I will make note of that separately so we can determine whether there is anything we need to look at in our process.” 

That way, you are not letting the insight disappear, but you are also not turning their review into a group comparison exercise. 

Client: “What if they say, ‘Well, what do I need to do to get a higher rating next time?’” 

Consultant: That’s the opening you want. Shift the conversation from defending the rating to defining the path forward. 

You might say: 

“That’s a good question. For the next review period, let’s identify what meeting expectations and exceeding expectations look like in specific terms. That way, you know what we’ll be measuring, and we can check in along the way.” 

Then get specific. Are they being measured on accuracy, deadlines, customer service, leadership, project completion, teamwork, communication, productivity, or technical skill? The clearer the criteria, the easier it is to coach and the harder it is for the conversation to drift into opinion. 

Client: “What if they still refuse to accept the rating?” 

Consultant: They do not have to love the rating for the organization to finalize it. The goal is to make sure they understand the basis for it, have had an opportunity to respond, and know what is expected moving forward. 

You can say: 

“I understand you disagree with the rating. I’ve heard your perspective, and I’ll include your comments with the review. The rating will remain as issued, and our focus now needs to be on the expectations and goals for the next review period.” 

That gives them voice without handing over the decision. 

Client: “Should we let employees submit written comments?” 

Consultant: Yes, if your process allows it. It can be helpful to give employees a place to document their perspective without turning the review meeting into a debate. 

You might say: 

“You’re welcome to provide written comments if you would like your perspective included with the review. I would encourage you to focus those comments on your own performance, accomplishments, goals, and areas where you believe additional information should be considered.” 

That keeps the process professional and useful. 

Client: “So the key is to acknowledge the concern, redirect to their performance, and separately review whether their comments point to a bigger issue?” 

Consultant: Exactly. Performance reviews should be based on clear expectations, known measurements, and documented results. If an employee disagrees, listen and explain. If they compare, redirect. And if their comments reveal a possible process concern, take that seriously—but handle it outside of the individual review conversation. 

And if you need help strengthening your performance review process, rating definitions, or manager calibration, we’re here to support you. 

 

Client: “Every time I ask supervisors to document an employee issue, I get something that reads more like a personal diary than professional notes. I’m worried these notes could hurt the organization instead of help us. What should documentation actually look like?” 

Consultant: You are right to be concerned. Documentation should help the organization understand what happened, what was discussed, and what needs to happen next. It should not include venting, assumptions, labels, sarcasm, or personal commentary. 

The goal is not to “build a case” against an employee. The goal is to create a clear, factual record. 

Client: “What’s the difference between helpful documentation and documentation that hurts us?” 

Consultant: Helpful documentation is factual, specific, timely, and professional. 

Instead of writing: 

“Jordan clearly doesn’t care about this job and is always making excuses.” 

Try: 

“Jordan arrived 18 minutes late for the scheduled 8:00 a.m. shift. This is the third late arrival in the past two weeks. We discussed the attendance expectation and the need to notify a supervisor before the start of the shift if they will be late.” 

The first version gives us frustration and assumptions. The second gives us facts we can use. 

Client: “So supervisors should avoid writing how they feel about the employee?” 

Consultant: Exactly. Documentation is not the place to process frustration. Avoid labels like “lazy,” “rude,” “toxic,” “bad attitude,” or “doesn’t care.” 

Instead, document the behavior: 

“The report was not submitted by the Friday deadline.” 

“The employee interrupted two coworkers during the meeting.” 

“The employee left the front desk uncovered for 25 minutes without notifying the lead.” 

Behavior can be addressed. Labels create risk. 

Client: “How much detail do they really need?” 

Consultant: Enough that someone who was not there can understand the situation. Most notes should answer five basic questions: 

Who was involved?
What happened?
When did it happen?
What expectation was discussed?
What are the next steps? 

A simple note might look like: 

“Met with [Employee] on [Date] regarding [specific issue]. Reviewed [policy, expectation, or performance standard]. Employee shared [brief response, if relevant]. Next steps are [what needs to happen and by when].” 

That is usually enough for routine coaching notes. 

Client: “What should absolutely stay out of documentation?” 

Consultant: Personal opinions, medical assumptions, legal conclusions, jokes, sarcasm, and comments unrelated to the workplace issue. 

A good rule of thumb is this: write every note as if the employee, HR, an attorney, an investigator, or a decision-maker may read it someday. Because someday, they might. 

Client: “What if the employee shares something important during the conversation?” 

Consultant: Include it briefly and factually. For example: 

“Employee stated they were late because their childcare provider was delayed.” 

“Employee disagreed with the feedback and stated they believe the workload is unreasonable.” 

“Employee shared that a health-related issue may be affecting attendance. I paused the conversation and referred the matter to HR for follow-up.” 

You do not need every word. You need the relevant information. 

Client: “So the key is facts, not feelings?” 

Consultant: Exactly. Facts, expectations, employee response, and next steps. 

Good documentation helps supervisors follow up consistently, helps employees understand what needs to change, and helps the organization show that it acted professionally and fairly. 

So yes — no more diary entries. 

Dear diary, this is HR. Keep it factual, keep it professional, and keep it useful. 

And if you ever need help training supervisors on documentation that helps instead of hurts, we’re here to support you.  Reach out anytime. 

 

Client: “We recently promoted a couple of employees into supervisory roles, and now they’re managing people who used to be their peers. How do we help them transition from coworker to supervisor without damaging relationships or avoiding accountability?” 

Consultant: This is one of the most common—and most awkward—leadership transitions. Yesterday, they were part of the group chat. Today, they are expected to assign work, address concerns, hold people accountable, and sometimes make decisions their former peers may not like. 

The key is helping them understand this: they don’t have to become cold or distant, and they do have to become clear. 

Client: “That makes sense. But how do they start without making it weird?” 

Consultant: Name the transition. Pretending nothing has changed usually makes things harder. The new supervisor should acknowledge the shift directly and professionally. 

They might say:
“I know this is a change for all of us. I’ve been part of this team, and I care about the work we do. My role has changed, and I want to be clear that my goal is to support the team, communicate expectations, and help us be successful.” 

This helps reset the relationship without over-explaining or apologizing for the promotion. 

Client: “What if they’re worried their former coworkers will think they’ve changed?” 

Consultant: They probably have changed—at least in role. And that’s not a bad thing. The challenge is to avoid two common mistakes: trying too hard to still be “one of the group,” or swinging too far the other direction and becoming overly formal or controlling. 

A good message is:
“I’m still me, and I also have responsibilities in this role that are different than before. I want to keep good working relationships, and I also need to be fair, consistent, and clear with everyone.” 

That gives them permission to be approachable without being fuzzy about expectations. 

Client: “What about friendships? Some of them are friends outside of work.” 

Consultant: That’s where boundaries matter. A new supervisor does not necessarily have to end every friendship, and they do need to understand that the relationship may need to look different at work. 

They should be cautious about private conversations, side comments, venting, or sharing information they now have access to as a supervisor. Even innocent comments can create the appearance of favoritism. 

You might coach them to say:
“I value our relationship, and I also want to be careful that I’m treating everyone consistently. There may be things I can’t discuss in the same way I could before, and I want to be respectful of that.” 

This is especially important when decisions involve schedules, assignments, performance, complaints, pay, leave, or discipline. 

Client: “What if employees test them? Like, ‘Come on, you know how it really works around here.’” 

Consultant: That will happen. Former peers may test whether expectations are actually expectations or just suggestions from someone they used to joke around with. 

The new supervisor can respond with calm clarity:
“I understand why you’re asking, and I know this may feel different coming from me. This is still the expectation, and I need everyone to follow it consistently.” 

They don’t need to over-defend the decision. They need to communicate the expectation and follow through. 

Client: “What if the new supervisor avoids correcting people because they don’t want to damage relationships?” 

Consultant: That’s very common. New supervisors often delay hard conversations because they are afraid of seeming bossy or disloyal to the team. But avoiding issues does not protect relationships—it usually creates confusion, resentment, or bigger problems later. 

A helpful reminder is:
“Addressing concerns early is not being harsh. It is part of being fair.” 

They can use simple coaching language:
“I want to check in on something I noticed. The expectation is [specific expectation], and I need to see that moving forward. Is there anything getting in the way?” 

This keeps the conversation direct without turning it into a formal disciplinary moment too soon. 

Client: “What if they overcorrect and come in too strong?” 

Consultant: That can happen too. Sometimes new supervisors feel like they have to prove they are in charge. That can damage trust quickly. 

Encourage them to lead with structure, not ego. They should focus on expectations, communication, and consistency—not power. 

They might say:
“I want us to be clear on priorities, deadlines, and communication. If something is unclear, I want you to ask. If something is not working, I want us to talk about it early.” 

That shows leadership without unnecessary authority-flexing. 

Client: “Should we have them meet with the team?” 

Consultant: Yes. A simple transition meeting can help. It does not need to be dramatic. The purpose is to clarify the role, reinforce expectations, and create space for questions. 

A good agenda might include: 

• What is changing 

• What is not changing 

• How communication will work 

• How priorities and assignments will be handled 

• How concerns should be raised 

• What the new supervisor needs from the team 

They might open with:
“I’m excited about this role, and I know transitions take some adjustment. I want to be transparent about how I plan to communicate, set expectations, and support the team.” 

Client: “What does the organization need to do? We don’t want to just promote them and hope they figure it out.” 

Consultant: Exactly. Promotion is not the same thing as preparation. New supervisors need guidance on what is now part of their role. 

At a minimum, they need support in: 

• Setting expectations 

• Giving feedback 

• Documenting concerns 

• Handling confidential information 

• Avoiding favoritism 

• Understanding when to involve HR or leadership 

• Managing conflict 

• Moving from “doing the work” to leading the work 

They also need a place to ask questions before small issues become big ones. 

Client: “So the key is helping them reset relationships, communicate clearly, and understand that leadership changes the role?” 

Consultant: Exactly. Moving from peer to supervisor is a pivot. The new supervisor does not need to abandon who they are, and they do need to step into the responsibilities of the role. 

The best transitions happen when new supervisors are clear, consistent, and supported. They can still be approachable. They can still care about the team. And they can lead with confidence when expectations need to be set. 

And if you are promoting employees into supervisory roles and want to help them start strong, we are here to help. 

Who gets paid when the office closes?

Client: We’re closing the office for the holiday, and suddenly everyone has questions. Who gets paid? Do part-time employees get holiday pay too? What about employees who were already off that day? And someone has already asked whether they can just “use the holiday later.” I would like to be festive, and I would also like payroll to remain grounded in reality. 

Consultant: Ah yes, the holidays. A season of goodwill, sweet treats, out-of-office messages, and at least one entirely avoidable debate about who is getting paid for what. Holiday pay sounds simple right up until real schedules, real policies, and assumptions all collide. 

The starting point is this: office closure and holiday pay are not automatically the same thing. If you want less confusion, fewer hallway debates, and no manager making up rules with peppermint in hand, you need to know what your policy says, what your practice has been, and whether any agreements apply. 

Client: So, if we close the office for a holiday, does everyone automatically get paid? 

Consultant: Not automatically. Closing the office does not, by itself, mean every employee receives paid holiday time. The answer depends on your written policy, any past practice that may have created expectations, applicable collective bargaining or employment agreements, and the wage and hour rules in play. 

Properly classified exempt employees may need to receive pay when the office closes during a workweek in which they work. Non-exempt employees are not automatically treated the same under the law, and organizations can choose to provide a similar holiday benefit through clear policy. 

That distinction matters. So does the tone of the conversation. This is one of those times when “we’ve always done it this way” is not a policy, it is a warning sign. 

Client: So, the first question is really who is eligible for the holiday benefit? 

Consultant: Exactly. Before you answer anyone, you need to know who your organization has said is eligible. Some organizations provide holiday pay only to full-time employees. Some include part-time employees and prorate the benefit. Some tie eligibility to a regularly scheduled workday. Some have different rules in different bargaining units. Some have a policy that looked clear when it was written and much less clear once actual humans started asking questions. 

Holiday pay is a benefit decision first. Payroll just gets stuck holding the calculator when the benefit was not clearly defined. 

Client: Let’s talk about part-time employees, because that is usually where the grumbling starts. 

Consultant: Of course it is. Nothing says “holiday cheer” quite like a debate over whether a benefit should be the same, similar, or different. 

Part-time employees do not automatically have to receive paid holidays just because full-time employees do. The real question is what your organization has promised through policy, agreement, or established practice. Some organizations exclude part-time employees from holiday pay altogether. Some prorate based on regular hours. Some provide holiday pay only if the employee was otherwise scheduled to work on the holiday. 

There is not one magical answer that works for everyone. There is, however, a very important best practice: decide the approach in advance, write it down clearly, and apply it consistently. 

Client: What about employees who were never scheduled to work that day anyway? 

Consultant: Same answer, same foundation. It depends on the policy. Some organizations provide the holiday benefit regardless of whether the day falls on the employee’s normal schedule. Others only provide holiday pay when the holiday lands on a regularly scheduled workday. 

This is where employees often use the word “fair” when what they really mean is “I wish the answer was different.” Fairness matters, and clarity matters right along with it. If your policy is clear and consistently applied, you are in a much better position than if every manager is giving their own holiday-themed interpretation. 

Client: And the question about “using the holiday later”? 

Consultant: Usually no, unless your policy specifically allows for that. Holiday pay is generally tied to the designated holiday, not treated like a floating coupon someone can redeem on a more convenient date. 

If the office is closed on Thursday for the holiday, the holiday benefit usually attaches to Thursday unless your policy says otherwise. Employees do not generally get to move it to the following Tuesday simply because that works better for their plans. 

That said, do not answer too quickly if the request is tied to a sincerely held religious observance. That is not the same conversation as “this day works better for me.” A religious accommodation request deserves its own review. Under Title VII, if the organization learns that its holiday schedule or attendance expectations may conflict with an employee’s sincerely held religious belief or practice, it should pause and consider whether there is a reasonable accommodation available unless doing so would create an undue hardship. Common options can include schedule adjustments, voluntary shift swaps, use of available leave, and sometimes even floating holiday approaches if they fit the organization’s design and operations. 

So the practical takeaway is this: a general request to “move the holiday” is usually answered by the policy. A religious accommodation request calls for a separate analysis, a little more care, and a lot less knee-jerk reaction. The two may sound similar at first, and they are not the same thing. 

Client: Let’s go back to exempt and non-exempt for a minute. That part makes people nervous. 

Consultant: Understandably. It is one of those areas where people want a yes-or-no answer, and the real answer is, “slow down and look at the details.” 

For employees who are properly treated as exempt, salary basis rules may limit when deductions can be made if the office closes during a workweek in which they perform work. That does not mean exempt employees get a mystery bonus every time the doors are locked. It means the organization needs to understand the legal framework before making pay decisions. 

For non-exempt employees, the law does not automatically require the same outcome simply because the office is closed. And an organization may absolutely choose to provide a similar holiday benefit through policy. That is often the better conversation anyway. Not “how little must we do,” but “what do we want our holiday pay practice to be, and can we support it consistently?” 

Client: So non-exempt employees can still receive holiday pay even though the law does not require the same treatment? 

Consultant: Absolutely. There is a difference between what the law requires and what the organization chooses to offer. An employer may choose to provide holiday pay, prorated holiday pay, premium pay for holiday work, floating holidays, or other benefits for non-exempt employees, as long as the approach is lawful, clearly communicated, and consistently administered. 

That is an important point because sometimes people hear “not required” and immediately translate it into “not allowed” or “not possible.” That is not the message. The message is that employers often have choices, and good choices are made on purpose. 

Client: What if someone works on the holiday? Do they automatically get time-and-a-half? 

Consultant: Not automatically. Holiday pay and overtime pay are not the same thing, even though people love to blend them together like leftover casserole. 

Working on a holiday does not automatically trigger premium pay unless your policy, contract, or agreement says it does. Overtime rules are based on hours worked under applicable wage and hour law, not on whether the day came with decorations. 

If your organization promises premium pay for holiday work, then follow the promise. Just make sure managers understand the difference between paid holiday benefits and actual hours worked, especially when payroll calculations are involved. 

Client: This feels like one of those issues that gets emotional fast. 

Consultant: Because it does. Holiday pay is not just about numbers. Employees often attach it to respect, appreciation, family time, and whether they believe the organization values them. That is why vague language causes such a mess. The less clear the policy, the more likely people are to fill in the blanks with assumptions, and those assumptions almost never match. 

This is also one of those topics where sameness and fairness get tangled together. Sometimes an organization has lawful, reasonable distinctions in benefits based on schedule, classification, or policy design. The answer is not to panic. The answer is to explain it clearly and make sure the practice matches the written language. 

Client: What if our policy is vague? 

Consultant: Then the holiday has given you a gift, and it is not one anyone asked for. A vague holiday policy almost guarantees confusion, inconsistency, and at least one manager saying something “helpful” that payroll then has to unwind. 

A strong holiday pay policy should answer questions like:
Who is eligible?
Are part-time employees included?
Is the benefit prorated?
Does the holiday need to fall on a regularly scheduled workday?
What happens if the employee works on the holiday?
What happens when the office closes?
Are floating holidays part of the design, or not? 

If your policy cannot answer those questions, it is time for a cleanup before the next holiday season comes twinkling down the lane. 

Client: So, the bottom line? 

Consultant: The bottom line is that holiday pay is rarely as simple as “office closed, everybody paid.” The better approach is to decide what benefit your organization wants to offer, make sure the practice works with the law, document it clearly, and train managers not to improvise in the name of holiday spirit. 

Good policy design can absolutely leave room for generosity. What it should not leave room for is confusion. 

And if your holiday pay practices are a little too dependent on tradition, memory, or whoever answered the question last year, we can help. We are glad to review the policy, clean up the language, talk through exempt and non-exempt considerations, sort through accommodation questions when they arise, and help you build a practice that is clear, consistent, and a lot less likely to cause festive frustration. Need help before the next holiday payroll? Reach out and we are glad to assist. 

FMLA, State-Specific Leave, Sick Time, and Paid Leave: What Applies, What Stacks, and What Doesn’t 

Client: “I have an employee who needs time off for a medical issue. I know we may have FMLA, state leave, sick time, and maybe paid leave involved. I’m not sure what applies, what runs at the same time, and what we’re supposed to tell the employee. Help?” 

Consultant: Employee leave is a little like lasagna: lots of layers, and it only works if you know what is in each one. 

FMLA may be one layer. State-specific leave may be another. Sick time may provide pay. A paid leave program may provide wage replacement. Your own policy may add another layer. And somewhere in there, the ADA interactive process may need a seat at the table. 

The goal is not to memorize every leave law in the moment. The goal is to slow down, identify the layers, and understand which ones apply, which ones run together, and which ones must be tracked separately. 

Client: “So I shouldn’t just say, ‘You’re on FMLA’ and call it good?” 

Consultant: Correct. FMLA may be part of the answer, and it may not be the whole answer. 

Leave analysis starts with the reason for the absence. Is the employee out for their own serious health condition? Caring for a family member? Bonding with a new child? Managing pregnancy-related limitations? Requesting safe leave? Using sick time for a short-term illness? Each answer may point to a different layer. 

That is why the first response should usually be process-based, not conclusion-based. 

You might say: 

“Thank you for letting us know. We’ll review what leave options may apply based on the reason for your absence, your eligibility, and the information needed to support the request.” 

That buys HR the time needed to review the situation correctly without promising the wrong thing. 

Client: “Can you give me an example of the layers?” 

Consultant: Oregon is a great example because it shows how quickly this gets complicated. 

For Oregon employers, an absence may require review under several possible layers: 

• FMLA: federal job-protected leave. For private employers, FMLA generally applies at 50 or more employees; public agencies and schools are covered regardless of employee count.  

• Paid Leave Oregon: wage replacement and possible job protection. It applies broadly to Oregon employers and employees.  

• OFLA: Oregon job-protected leave. OFLA generally applies to employers with 25 or more employees.  

• Oregon Sick Time: paid sick time generally applies at 10 or more employees, or 6 or more employees if the employer has a Portland location. Smaller employers are required to provide protected, unpaid sick time.  

• ADA/Oregon disability accommodation: the federal ADA generally applies at 15 or more employees, and Oregon disability accommodation obligations generally apply at 6 or more employees.  

• Employer policy or union agreement: PTO, vacation, sick leave, benefit continuation, and return-to-work rules may add another layer.  

That does not mean every absence qualifies under every law. It means HR needs to review the possible layers before giving a final answer. 

Client: “If an employee qualifies for more than one leave, do they get all of them stacked on top of each other?” 

Consultant: Sometimes leave runs at the same time. Sometimes it does not. That is the tricky part. 

Some leave laws provide job protection. Some provide pay or wage replacement. Some provide both. Some may run together. Some must be tracked separately. 

Oregon gives us a good example: OFLA does not run concurrently with Paid Leave Oregon. So if an employee is using Paid Leave Oregon, they are not also using OFLA for that same time period. However, OFLA may still matter before or after Paid Leave Oregon, depending on the reason for leave and the employee’s eligibility. 

For example, an employee may use Paid Leave Oregon for a qualifying medical or family leave reason. Once that Paid Leave Oregon time is exhausted, the employee may still qualify for a separate OFLA-protected leave reason, such as sick child leave, bereavement leave, or pregnancy disability leave. 

A Paid Leave Oregon approval is important. It may address wage replacement and may include job protection depending on eligibility, and it does not end the employer’s analysis. HR still needs to review whether other layers apply, including FMLA, Oregon sick time, employer policy, collective bargaining agreement provisions, and disability accommodation obligations. 

That does not mean additional leave automatically applies. It means HR should not assume the leave analysis is finished just because one layer has been approved or used. 

Client: “What about sick time? Employees often say they want to use sick time first and save protected leave.” 

Consultant: That is a common misunderstanding. Sick time may provide pay. Protected leave may protect the time away from work. Those are different questions. 

A simple explanation is: 

“Sick time may apply to pay during your absence, and protected leave may also apply to the reason you are away from work. We are required to review whether the absence qualifies under applicable leave laws, even when paid time is available.” 

That helps employees understand it is not always either/or. 

Client: “What should managers do when an employee mentions a medical issue or need for leave?” 

Consultant: Managers do not need to become leave law experts. They do need to know when to pause and involve HR. 

A good manager response sounds like: 

“Thank you for letting me know. I’m going to connect with HR so we can make sure you receive the right information about leave options and next steps.” 

Managers should avoid promising approval, denying leave, asking for medical details, or telling employees they do not qualify unless HR has completed the review. 

Client: “So what is the practical takeaway?” 

Consultant: Use a leave map. It can be simple. For each leave request, identify: 

• The reason for the absence;  

• The employee’s work location;  

• The employer coverage thresholds;  

• The employee’s eligibility;  

• Whether the leave is paid, protected, or both;  

• Whether leaves run together or separately; and  

• What communication or documentation is needed.  

That small step can prevent big mistakes. 

Client: “So the bottom line is: don’t guess, identify the layers?” 

Consultant: Exactly. Employee leave has layers. FMLA, state-specific leave, paid leave programs, sick time, employer policy, union agreements, and accommodation obligations may all show up in the same conversation. That does not mean they all work the same way. 

Leave administration is one of those HR areas where “close enough” can create real problems. A good process helps employees receive the protections and pay they are entitled to, and it helps the organization apply the rules consistently. 

And if your leave layers are starting to slide around the pan, we can help. HR Answers can assist with leave mapping, policy review, manager training, and practical tools to help your team understand what applies, what stacks, and what needs to be tracked separately. When there is a lot to consider, or you’re just not sure- we are here to help. 

 

Client: “We have a student who wants experience, and we were thinking of bringing them in as an unpaid intern. We’ve also tossed around calling a few roles ‘volunteer’ positions to help with staffing. That should be okay as long as everyone agrees, right?” 

Consultant: Be careful! Organizations can get themselves in trouble fast. A person is not automatically an unpaid intern or a volunteer just because everyone uses that label. If the person is really functioning like an employee, wage and hour laws may treat them like one. Under federal law, for-profit employers generally must pay employees, and unpaid internships at for-profit organizations are evaluated using the U.S. Department of Labor’s “primary beneficiary” test. (DOL) 

Client: “Okay, so what makes an unpaid internship legitimate?” 

Consultant: For a for-profit organization, the question is whether the intern is the primary beneficiary of the relationship. The Department of Labor points to seven factors, including whether there is a clear understanding there is no expectation of pay, whether the internship looks like an educational experience, whether it is tied to coursework or academic credit, whether it works around the academic calendar, whether it is limited to the learning period, whether the intern complements rather than displaces paid staff, and whether there is no entitlement to a paid job at the end. No single factor controls, and the analysis depends on the full picture.  

Client: “So if they’re mostly helping us catch up on filing, answering phones, or covering regular work, that’s probably not great?” 

Consultant: Correct. Once the “internship” starts looking like free labor for work you otherwise would assign to employees, your risk goes up. One of the biggest warning signs is when the intern is doing productive work that replaces or reduces the need for paid staff rather than receiving a structured learning experience.  

Client: “What about nonprofits or public organizations? Can they use volunteers more freely?” 

Consultant: They have more flexibility, and there are still rules. Federal guidance recognizes true volunteers in charitable, religious, civic, humanitarian, and public-service settings when the service is offered freely and without expectation of compensation. The guidance also says volunteers typically should not displace regular employees or perform work that would otherwise be done by regular workers.  

Client: “That sounds promising. We are a non-profit.  Could we have an existing employee volunteer a few extra hours in the same department?” 

Consultant: That is one of the classic traps. Federal guidance says paid employees of a nonprofit and public agencies generally cannot “volunteer” to do the same type of services for their employer on an unpaid basis. 

Client: “What if the person says they don’t mind not getting paid because they just want experience?” 

Consultant: Intent helps explain the relationship, and it does not override the law. A friendly agreement does not make an unlawful unpaid arrangement lawful. If the role functions like a job, the organization may owe wages regardless of what the person agreed to. That is why structure matters so much.  

Client: “What should we be asking before we launch any internship or volunteer role?” 

Consultant: Start here: 

• Who primarily benefits from the arrangement—the learner or the organization? 

• Is there a real educational component with defined learning goals? 

• Is it tied to a school program, academic credit, or a training plan? 

• Is the work limited in duration and built around learning? 

• Are we avoiding using this person to fill a staffing gap? 

• If this is called a volunteer role, is it truly voluntary and appropriate for our organization type? 

• Is this person already our employee doing the same kind of work? 

If those answers get fuzzy, the safer path is often to make it a paid role. 

Client: “We’re in Oregon. Is there anything else we should keep in mind?” 

Consultant: Yes. Oregon BOLI says bona fide internships and training programs may be exempt from minimum wage and overtime requirements, and civil rights protections still apply. BOLI also says that student learners whose work experience does not meet the criteria for trainee status are employees entitled to the full protections of Oregon wage laws. That means the label matters far less than the facts. (Oregon) 

Client: “So the real lesson is don’t use ‘intern’ or ‘volunteer’ as a budget strategy?” 

Consultant: Exactly. “Unpaid” is not a shortcut. It is a classification decision with real legal consequences. When organizations get this wrong, the risk can include unpaid wages, overtime exposure, recordkeeping issues, and a messy explanation for why someone doing real work was never treated like an employee in the first place. The better approach is to design the role intentionally, document the purpose, and pressure-test it before the person starts. (DOL) 

Client: “That makes sense. So the key is to evaluate the relationship, not just the title?” 

Consultant: Exactly. If it is truly a learning experience, build it that way. If it is really work that helps your organization operate, pay for it accordingly. Clear planning on the front end is much easier than cleaning up a misclassification problem later. 

And if you need help reviewing an internship idea, pressure-testing a volunteer model, or deciding whether a role should really be paid, we’re here to help. Reach out anytime.