How CHROs Set Fair Hybrid Work Policies Across Roles

With 11 employees at Simply Noted, we're small enough that hybrid workforce policy questions hit differently than at a big company. Some of our team, the folks running the note-writing robots and shipping product, have to be on site. Others, like parts of marketing and customer support, genuinely don't. The unfair version of hybrid policy is applying remote flexibility rules written for desk jobs to people whose actual work requires physical presence, then acting surprised when it breeds resentment.

What's worked for us is being upfront that the criteria isn't about trust or seniority, it's about the literal nature of the task. If your job requires standing next to a machine, that's not a punishment, it's just the job description. We try to balance it by giving site based roles other kinds of flexibility, schedule swaps, earlier start times, that desk roles don't need as much.

The mistake I see in bigger companies is layering remote perks on top of an org chart instead of a task list. Fairness in hybrid policy isn't equal treatment, it's honest treatment based on what the work actually demands.

I think organizations make a mistake when they use "flexibility" and "remote work" interchangeably. Some jobs simply need to be done onsite, whether that's because of equipment, customers, safety, or the nature of the work. That doesn't mean those employees shouldn't have flexibility.

I've approached this by first getting very clear about what the work actually requires and then looking for where we can create choice, in whatever form that may be. For someone who needs to be onsite, that might mean flexibility around start and end times, shifts, or schedules. For someone whose work can be done remotely, location can be another form of flexibility.

This also gives managers a much better way to explain differences across teams. You're not trying to make every role look the same. You're making decisions based on the work and then asking the same question of every role: where can we give people meaningful choice?

Not every job can offer the same flexibility, but every job deserves the same consideration of what can flex.

Deciding which activities necessitate in-person interaction boils down to understanding the tasks that directly benefit from proximity and collaboration versus those that thrive in a remote structure. At TradingFXVPS, where a significant portion of our operations revolve around supporting traders across different time zones with minimal latency, we established early on that roles tied to managing on-site infrastructure like data centers requiring physical maintenance—needed clear on-location expectations. For other functions, like customer support or marketing, we leveraged robust communication tools to keep productivity high while allowing flexibility.

A principle that worked well for us was transparently aligning location expectations to measurable business outcomes. For example, when we restructured our marketing initiatives to be fully remote, we saw a 15% boost in campaign output within six months, as team members were empowered to work in their optimal environments. Simultaneously, on-site teams experienced greater efficiency as they felt their roles were purposefully aligned to critical, location-dependent needs. This balance was achieved by piloting mixed models and gathering structured feedback from employees and managers, ensuring any standards we set felt equitable.

With my experience leading a tech-driven organization and a background in performance marketing, I'm attuned to how location policies ripple across productivity and morale. An overlooked insight is that standardization doesn't mean uniformity—being fair in expectations is about tailoring them transparently to a role's requirements, not forcing homogeneity. By continuously reinforcing the "why" behind the location strategy and the data it's anchored to, we built trust, which is essential in any work model. Employees engaged more fully, not just because the standards were clear, but because they were grounded in mutual benefit.

To make location expectations workable, we created an attendance brief for every recurring in person requirement. It explains the purpose, who should attend, how often it happens, and the best backup option when someone faces a barrier. The brief stays short enough for planning and clear enough to avoid last minute confusion. This helps everyone prepare with the same expectations before each meeting or visit.

We never use attendance to fix performance or culture concerns. We handle those issues through clear goals, regular feedback, and better workflows. This keeps site visits tied to a real business need. It gives employees and managers a fair process that feels consistent and easy to follow.

I run this exact split every week. Rathly is an on-site agency, Smarfle is a fully remote SaaS team, and I have had to defend location decisions to both sides at once. The test I use is not whether a task could theoretically be done remotely, it is whether being in the same room removes a coordination cost that would otherwise show up as delay or rework. Client strategy sessions at Rathly go in person because reading a room in real time changes what we pitch mid-meeting. Engineering work at Smarfle stays remote because the coordination cost there is solved by shared documentation, not proximity.

The principle that made this feel fair across both teams was writing the criteria down as a rule about the work, never about the person or the role title. Nobody at Rathly is in office because of seniority or trust, and nobody at Smarfle is remote because they earned it. The rule is stated as which activities require it, published the same way for everyone, and applied to new hires on day one rather than negotiated case by case. That single change stopped the quiet resentment that shows up when people suspect location policy is really about who the boss likes being near.

It's not title-based. If there's a detox, we have to have a person in the building because the dangerous moments are the transitions. I don't think building a schedule or reconciling claims or reviewing a policy draft is going to be much safer because that laptop is in East 60th Street.

We had to be able to do it on a document where everyone in the business could open it up and see next to each job why we put them in there and then they could challenge it and write a challenge to the role in writing and the manager had to answer that challenge in writing. So a couple of people had it addressed to them. The rest of us could see it and so that's how we did it. It was not about fairness. It wasn't about the criteria or anything like that. It was about what practice made it feel fair. If we explained it in words why that was the case it didn't mean that it was fair. We just went for it. Just because we said why we put them in there didn't mean it meant it was fair. It just came out as favoritism, and the entire point is that people noticed the challenges that won.

No manager is further away from the people they manage than the building. In this field, the overnight techs are the ones holding the hardest hours. An admission at midnight is a dangerous transition. If leadership means one face on a screen at 3am, the organization's morale is slowly decaying. A shift change is a dangerous transition, and a family session where someone is about to hear something they've been dreading for years is a dangerous transition too.

A location policy is a kind of treatment plan. One thing is talking about the average person in a location policy. Something else is talking about that specific person in front of you now.

The most practical principle is to make location decisions based on the work itself rather than the person performing it. Activities requiring physical equipment, customer presence, sensitive on-site coordination, or high-bandwidth collaboration may genuinely benefit from being performed in person; focused individual work often does not. The key is applying the same criteria across comparable roles and documenting the reasoning, rather than allowing location expectations to vary by manager preference. Research from Stanford's Institute for Economic Policy Research found that hybrid work reduced attrition by one-third among employees in a large randomized study, without damaging performance evaluations or promotions. That finding reinforces an important point: flexibility does not have to mean inconsistent standards. A clear activity-based framework—supported by common performance measures, defined collaboration windows, and transparent exceptions—makes hybrid policies easier for managers to administer and easier for employees to perceive as fair. Location should be treated as a work-design decision, not a proxy for commitment or productivity.

I ask one question: does the work actually get better when people are in the same room? At Kate Backdrops, our warehouse team has to be on-site.. But our marketing and design folks? I don't care where they sit, as long as the work ships. The trap is applying one rule to everyone. We tied presence to the task, not the title. When a photoshoot or a new product review needs eyes and hands together, people show up. When it does not, they do not. Fairness means being honest about what each role genuinely requires and recognizing that treating every role the same often misses the mark entirely.

Start with clarity, end with consistency. At CheapForexVPS, where remote teams form our backbone and data-center teams anchor operations on-site, defining location-specific expectations was mission-critical. A principle that worked for us was grounding decisions in task alignment rather than titles. For instance, launching a server upgrade required tangible, hands-on coordination that justified on-site shifts for technical staff, while strategy and sales planning thrived asynchronously and stayed fully remote. To make this balance succeed, we conducted a workforce survey, uncovering that 73% of employees valued transparency over uniform policies. This data empowered us to clearly communicate both the "why" and "how" behind location-based decisions.

For managers, equipping them with a decision framework—evaluating outcomes, collaboration intensity, and urgency helped standardize expectations across teams without micro-managing. Ensuring clarity was only half the battle; we reinforced it through monthly check-ins, where 90% of leaders reported improved buy-in. These efforts have not only minimized friction but also enhanced retention. When policies resonate with employees' realities, teams instinctively lean toward fairness—not resistance.

The activity decides, not the role. We stopped asking which jobs are remote and started asking which specific activities lose something when everyone is on a screen.

We operate from an office in Morocco with people working with clients in Europe, the Gulf and the United States, so this had to be resolved rather than fudged. The list we arrived at is short. Anything involving shared judgement in real time is in person: reviewing creative work, the first weeks of a new hire, and a client situation that has gone wrong. Everything else, which is most of the actual production work, happens wherever the person works best.

The principle that made it feel fair to people in site tied roles: if a role has to be on site, the compensation for that is time, not sympathy. Fixed hours that actually end, predictable schedules published in advance, and no expectation of being reachable outside them. The unfairness people feel is rarely about the location itself. It is about watching colleagues have control over their day while you have none. Give the on site roles a different kind of control and the resentment mostly goes.

The practice I would keep: write the reasoning down per activity, publicly, and let people challenge it. When the rule is "creative review is in person because we lose the disagreement on a call", someone can argue that. When the rule is "your role is on site", there is nothing to argue with, so it gets argued about in private instead.

The thing we got wrong first time was setting it by department. Departments contain both kinds of activity, so the policy was immediately unfair to someone in every team.

Running a 140,000 square foot fulfillment operation taught me something counterintuitive: the people who needed to be on-site the most were often the ones I gave the most schedule flexibility to. Our warehouse team couldn't pack boxes from home, but our customer success managers theoretically could. I made a rule that still guides me today: if your physical presence directly impacts another person's ability to do their job in the next four hours, you need to be where they are.

Here's what that looked like in practice. Our warehouse supervisors had to be on the floor because a picker with a damaged inventory question couldn't wait for a Slack response. But our inventory analysts could work from home three days a week because their reports fed into weekly planning cycles, not real-time decisions. The key was identifying the time sensitivity and human dependency, not just the task itself.

The practice that made this feel fair was radical transparency about the why. I held monthly all-hands meetings where I'd literally walk through examples. "Sarah needs to be here Tuesday through Thursday because that's when receiving happens and she's training new staff on quality checks. But she works from home Monday and Friday doing data analysis." When people understood the operational logic rather than feeling like it was arbitrary or based on who I liked, resentment disappeared.

We also paid differently. Our on-site warehouse team got shift differentials and quarterly bonuses tied to facility performance metrics. Remote-capable roles had different bonus structures tied to customer retention and accuracy. I wasn't going to pretend that commuting to a warehouse in Michigan winter was the same as logging in from your kitchen. Acknowledge the difference, compensate for it, and people respect the honesty.

The mistake most leaders make is trying to create perfect equity when the roles themselves aren't equitable. A picker can't Zoom into a packing station. Own that reality, explain your decisions like adults can handle complexity, and compensate people fairly for what you're actually asking them to do.

I decide by asking whether the activity can be completed with the same level of intention, preparation, responsiveness, and professionalism when done remotely. If it cannot, I schedule in-person attendance; if it can, I allow remote work with the same expectations. The single practice that made location expectations feel fair was insisting that remote work be treated with the same intention as office work, including a dedicated workspace, appropriate meeting attire, and attention to background and lighting. Pairing that standard with clear, timely communication ensured managers and employees had a common, consistent measure of performance.

We view physical location as a tool for interaction bandwidth rather than a badge of office. To maintain consistency across a workforce of 650 professionals with varying degrees of mobility, we use a collaboration-by-intent framework that reserves in-person time for high-bandwidth activities where digital latency hinders progress-strategic roadmapping, complex project kickoffs, and deep team bonding. Conversely, we keep routine tasks, status reporting, and technical execution remote to maximize individual focus and efficiency.

Frustration in a hybrid environment usually stems from a lack of clarity regarding why some roles are site-tied while others are not. We solve this by shifting the conversation away from desk days and toward specific business outcomes. If a team lead requests physical presence, they must justify it based on the complexity of the problem being solved. For site-tied roles, such as hardware infrastructure or facilities management, we ensure their value is measured by the same performance metrics applied to remote developers. By focusing on output rather than attendance, the onsite team recognizes that their remote counterparts are held to the same rigorous delivery standards.

The principle that makes this sustainable is the transparency of output. When every role is measured by clear milestones and financial discipline, location becomes secondary to the result. Employees accept different requirements when they see the office used as a deliberate resource for high-stakes collaboration rather than a tool for monitoring. Intentionality prevents the office from becoming a site for vanity attendance and transforms it into a hub for high-impact decision-making.

I write the criteria around activities, not around job titles. A remote-capable role still has moments that belong on site, and a site-tied role still has heads-down work that doesn't need an audience. So I list the actual activities a team does in a month and sort them into categories like collaborative problem-solving, client-facing work, training and onboarding, equipment or compliance-bound tasks, and solo execution.

Then I attach the in-person requirement to the category and write down why. If nobody on my team can articulate the why in a sentence, I don't put it in a room.

Ownership matters as much as the criteria. I have central leadership own the standard, meaning the shared categories, the documentation format, and the appeal path, and I let individual teams own the schedule inside that standard. That split keeps things from turning into one manager's personal preference dressed up as company policy.

On fairness, I publish the criteria and the resulting expectations for every team in the same place, so a warehouse supervisor can read what the finance team is held to and the other way around. In my company the different in-person requirements across teams read as fair because the reasoning is visible and applied the same way, and they read as arbitrary the moment they live only in someone's inbox. I run it as a pilot for a quarter, collect what broke, then revise the categories rather than the exceptions.

The best way to prevent office v. home groups is to have managers mandate remote days. When people pick their own schedule, physical presence becomes a signal of commitment. Mandating remote days ensures that everyone is informalizing in the office with their teammates at the same time.

You can't miss those impromptu hallway chats when you're all together. Deciding which tasks/buckets should be "presence-required" should be done by measuring output, not input. My team measures the distribution of high-value projects across the organization and uses that to determine whether placing people physically close to one another creates value.

Let's say complex training is better retained when done in person; then you can mandate office days when this particular task is happening. But it also requires executives to come on the same schedule; otherwise, everyone below them will come to the office when the execs come in, and it will grow again.

So if the leadership team comes in 100% on mandatory remote days, you'll have subordinate managers come in too, and enforcing that any manager adheres to the schedule enforces parity across all the groups.

The principle is that client workshops, pricing conversations and final reviews stay synchronous and often on-site, while production work stays async with a written brief. Location follows the risk of misunderstanding, not a blanket office rule.

That split felt fair because seniors could still run a Teesside or London session when the brief was ambiguous, and specialists were not dragged in for tasks a checklist already covered. In-person time is for judgment. Remote time is for execution against that judgment.

To determine which activities truly need in-person presence, I used data to conduct a targeted, results-oriented pilot that relied on role rotations to assess readiness instead of guessing needs. During those rotations, we measured performance to determine whether in-person presence made a difference and where work could continue to be done remotely without compromising performance. I added developmental accountability for each manager so they had to validate the pilot outcomes and support internal moves when readiness was fulfilled. This created a sense of fairness and workability for location expectations because decisions were made based on readiness and manager accountability instead of personal preferences.

I decide location at the activity level rather than by job title. Work requires an on-site presence when it depends on inspecting physical conditions, operating equipment, managing safety, coordinating crews or completing a customer handover. Scheduling, quote preparation, supplier follow-up and documentation can often be completed elsewhere when the information is complete.

The principle I favour is that standards should be based on outcomes, not visibility. Every job should have one live record containing the scope, measurements, photographs, materials, decisions and next action, so office and field teams work from the same information. Fairness does not mean giving every role identical location options. It means offering comparable control where possible. Remote-capable staff may have location flexibility, while site-based teams benefit from predictable rosters, clear finish times and reasonable notice of changes. Managers should be able to explain the operational reason for every in-person requirement.

Care delivery that needs the live 60-minute visit stays with the clinician on the clock. Admin documentation can flex remote if PHI stays in covered systems.

The fairness principle is the visit: if the work is the consult or the signed note, location follows the patient being in Texas during the appointment. If the work is scheduling or chart cleanup under a BAA tool, remote is fine. Standards stay consistent because the legal record rules do not change by zip code.

Code and ticket macros can stay remote. Broker trainings that teach a live closing file need presence, either in the room or on a dedicated screen-share block, not a half-watched webinar.

Activity decides location, not title. If two people need eyes on the same PDF at the same time, we schedule presence. If the work is macros or code, location is optional. I still do free screen-shares when an office is stuck. The file checklist does not change by zip code. Naming which of the 2 activity types require presence before hiring keeps the rule fair.

Running Pageloot remotely and 3D Studio with site-dependent rendering reviews at the same time forced this question into a real operational decision, not a policy exercise.

The principle that stuck: presence is justified only when the output depends on real-time physical judgment that can't be documented and reviewed asynchronously. For our visualization work, a client walkthrough of a rendered space sometimes required someone physically at a screen with the client to catch micro-reactions and iterate live. That's a legitimate in-person requirement. A status update meeting is not, even if it feels more comfortable face-to-face.

The fairness problem came from inconsistency in *how* we labeled requirements. When we started writing down the specific output, not the role, that needed in-person presence, the resentment dropped. "The Thursday client review requires physical attendance because we adjust renders live" is a workable standard. "Marketing works remotely but ops has to come in" with no further explanation is not, even if both are operationally true.

One practice that helped: any in-person requirement had to have a written answer to "what breaks if this is done remotely?" If the answer was vague, the requirement didn't survive. If it was concrete, people accepted it without pushback, even the ones who had to travel for it.

Ask the first question -- about the activity, not the job title -- in this manner: "The last time we tried this activity remotely, what broke?" Ask every team member to list out a real week of work and cross out all of the activities that did not go well off-site. Utilization review calls with insurers, chart audits, most of the supervision: all went fine. But family sessions did not, nor did the first 48 hours with a new client, nor any handoff between shifts, because that's where the info goes missing, and nobody notices until it matters.

I worked nearly every role in a treatment facility over ten years before this one, and the staff can smell a policy written by someone who never did the job writing the policy. Let the people who actually did the job bring the evidence and write the reason next to each activity in language that a new employee would understand.

It is about fairness - if you cannot allow someone to have flexibility in where they work then at least give them the flexibility of when they work. Our nurses and techs do not work from a kitchen table! They have flexibility in their schedules, approved time swaps and a hard stop at the end of their shifts that management protects.

Yeah, fairness isn't everybody getting the same thing—fair is everybody getting something real and everybody knowing why.

Anything that touches jars, couriers, or a live customer at the till stays on site. Content drafts, tagging, and supplier email can be remote once the person has already worked a packing week.

The principle that felt fair was the product itself. If the task can put the wrong cream in the bag or leave a box on a wrong van, it needs eyes on the shelf. If it cannot, location is flexible. In The UK Wash-Day Report 2026, https://zenvy-beauty.com/blogs/news/uk-wash-day-report-2026, UK women with textured hair spent 132 hours a year on wash-day care. They will not wait while a remote hand guesses stock. Standards stay consistent because the on-site list is short and written, and the remote list still uses the same scripts.

We see many organizations confuse consistency with uniformity across everyday workplace decisions without context. We believe consistency means every role faces the same practical questions before expectations change. We ask what information fades across distance during daily collaboration and communication between teams. We also examine which risks grow and which abilities become stronger through shared presence.

We recommend giving every in person requirement a clear owner from the beginning onward. That owner should check whether each requirement still deserves its cost for everyone involved. We review these decisions regularly so policies stay useful instead of becoming lasting habits. We keep responsibility visible because clear ownership shifts conversations from preference toward thoughtful stewardship.

We found consistency breaks in hybrid organizations when leaders classify entire roles instead of work moments. We treat merchandising work as remote for analysis but meet when samples arrive or conflict. We also keep warehouse roles on site while training scheduling and performance conversations happen remotely. This approach matches the task instead of the title and keeps expectations clear.

We created a task calendar that listed events requiring physical attendance and shared it early. It turned unclear availability into predictable commitments without constant reminders or confusion. Managers could not call people in simply because an in person meeting felt better. We explained the purpose expected time and advance notice for each required visit clearly.