Author: Laurie Grenya

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.  

Client: “Employees have started asking about Summer Fridays, alternate schedules, and other summer flexibility ideas. I like the thought of doing something positive for morale, and I am worried it is going to become a fairness fight the minute not every job can do the same thing.” 

Consultant: That concern is valid, and honestly, it is a good sign. It means you already see the issue clearly. Summer flexibility sounds simple until it lands in a workplace where coverage still matters, service still matters, and employees have strong opinions about what fairness should look like. 

That is why this is less about Summer Fridays and more about seasonal flexibility planning. 

Client: “That feels like a better way to frame it. Summer Fridays sound fun until everyone starts measuring who got what.” 

Consultant: Exactly. Once flexibility starts sounding like a benefit, many employees naturally shift into “everyone should get the same thing” thinking. The challenge is that work is not always the same, and trying to force identical flexibility onto very different roles can create more frustration than goodwill. 

So the better question is not, “How do we give everyone the same summer perk?”
The better question is, “What kinds of flexibility can our organization realistically support, and how do we plan for that in a way that is clear and consistent?” 

Client: “So where do we start?” 

Consultant: Start with the work, not the wish list. 

Before offering seasonal flexibility, identify what still has to happen no matter how sunny the weather gets. Ask: 

• What hours must be covered? 

• What services must remain uninterrupted? 

• What work is time-sensitive? 

• Which roles require an in-person presence? 

• Which duties have more flexibility in when the work gets done? 

Those answers matter because flexibility that creates service gaps, coverage gaps, or coworker resentment is not really flexibility. It is delayed frustration. 

Client: “That sounds like where managers can get into trouble if they just start saying yes one person at a time.” 

Consultant: Exactly right. If managers solve it one request at a time, employees will compare notes, and soon the issue is not flexibility. The issue is favoritism, inconsistency, and who had the boldness to ask first. 

This is why organizations need a framework before the summer schedule chatter turns into workplace mythology. 

Client: “What kind of framework?” 

Consultant: One that answers a few practical questions before anyone starts leaving at noon on Fridays. 

For example: 

• What flexibility options are actually on the table? 

• Are they temporary or ongoing through the season? 

• Are they role-based, team-based, or individually approved? 

• What level of performance and dependability is required? 

• Who reviews and approves the request? 

• Under what circumstances can the arrangement be adjusted or ended? 

This keeps flexibility tied to work realities instead of manager mood or employee negotiation skills. 

Client: “I like that. It also feels less risky than announcing Summer Fridays and hoping for the best.” 

Consultant: Hope is not a scheduling strategy. 

A smarter approach is to think more broadly. Seasonal flexibility can take many forms depending on the work. It might include adjusted start and end times, compressed schedules, rotating lighter Fridays, fewer internal meetings on Fridays, occasional remote work where duties support it, or short-term pilot arrangements with clear expectations. 

The point is to ask, “What could work here?” instead of “How do we copy the same arrangement everywhere?” 

Client: “That seems like a better message for employees too.” 

Consultant: It is, because it is more honest. Not every role will flex in the same way, and pretending otherwise usually backfires. Employees do not need a fairy tale. They need a process that makes sense. 

You might say: 

“As we look at seasonal flexibility, we are reviewing operational needs, service expectations, and the nature of each role. Our goal is to identify flexibility options that support the work and apply a consistent process when determining what may be possible.” 

That gives people a grown-up explanation instead of a vague promise. 

Client: “What about fairness? That word is going to come up.” 

Consultant: Of course it is. Fairness is always in the room when schedules are involved. The important thing is to define fairness carefully. Fairness does not always mean identical outcomes. It means using a consistent process, tied to real business needs, and communicating clearly about how decisions are made. 

That is a much sturdier foundation than trying to avoid all discomfort by making everything look the same. 

Client: “And I assume we need to watch for whether flexibility for one person creates more work for someone else.” 

Consultant: Absolutely. This is one of the biggest traps. If a flexible arrangement means the same dependable employees are always covering phones, greeting the public, staying late, or cleaning up unfinished work, you have not created flexibility. You have just moved the inconvenience to quieter people. 

Managers need to pay attention to workload distribution, coverage impact, responsiveness, and whether the arrangement is working for the team as a whole, not just for the employee who requested it. 

Client: “So the real lesson is: think bigger than Summer Fridays, and plan before you promise.” 

Consultant: Exactly. Seasonal flexibility can be a great tool for morale, retention, and trust. It can also become an instant source of side-eye if it is rolled out casually. Start with the work. Build a framework. Communicate clearly. And remember that flexibility works best when it is designed on purpose, not handed out in reaction to the loudest request. 

And if your organization wants help thinking through a seasonal flexibility approach that supports morale and still keeps the work covered, we can help.