RTO Policies Hurt Morale—HRCI Says Pilot Before You Mandate

HRCI introduced a five-step process for return-to-office decisions on August 26, 2026, urging employers to define the business problem, examine internal evidence, distinguish among roles, pilot changes and measure results before imposing a broad mandate. The organization’s August 26 release, datelined Washington, also cautions that badge swipes and office occupancy measure compliance—not improvements in morale, engagement, retention or productivity.

The guidance does not identify remote, hybrid or fully on-site work as universally superior. HR News Canada’s coverage of the new framework similarly describes a shift away from blanket rules and toward workplace decisions grounded in an organization’s own data.

The framework starts with a problem, not an office schedule

Under HRCI’s approach, attendance is a possible intervention rather than the objective. Leaders first identify what they believe has deteriorated—such as collaboration, mentorship, culture, productivity or client service—without assuming that more office days will correct it.

1. Define the business problem. State the result that needs to change without building an attendance requirement into the problem itself.
2. Audit internal evidence. Examine engagement, turnover, tenure, real-estate use and manager feedback before treating another employer’s policy as a benchmark.
3. Match requirements to roles. Determine which activities benefit from physical proximity and which can be completed and reviewed elsewhere.
4. Run a limited pilot. Apply the proposed change to a smaller group and gather evidence before expanding it.
5. Measure outcomes. Test whether the original problem improved instead of treating higher occupancy as proof of success.

Role differences are central to the decision. Work involving physical equipment, secure facilities, hands-on tasks, frequent handoffs or direct client contact can require more on-site time than digitally completed work. Yet differentiated rules can create a perception of inequity, making the rationale for each requirement part of the policy decision.

The framework therefore prescribes no universal number of office days. The appropriate arrangement depends on the problem being investigated, the work performed by affected roles and the results produced during the test.

The morale finding comes with important limits

The accompanying Managing the Changing Workplace report says the underlying State of HR survey received responses from 4,583 HR professionals between October 15 and 31, 2025, with 85% practicing in the United States. Among respondents, 83% viewed remote or hybrid work as good for an organization; a solid majority believed RTO policies negatively affected morale, and 24% believed those policies negatively affected productivity.

The same findings capture costs associated with flexible work. Respondents identified reduced belonging, weaker identification with a team or company and lower collaboration as potential disadvantages of remote arrangements. That tension is why the framework treats workplace design as an organization-specific decision rather than a contest with one winning model.

These results reflect the assessments of HR professionals across different workplaces. They are not a randomized comparison of otherwise identical organizations, so they cannot establish that a particular mandate will produce the same effects in every workforce. A limited internal pilot is intended to connect a defined policy change with the conditions and outcomes of one employer.

A pilot worksheet separates attendance from success

The framework can be translated into a compact decision record that keeps the original business problem visible throughout the test. The worksheet below is an editorial implementation of HRCI’s process, not an official HRCI form.

• Stated problem: Record one observable business issue, its owner and the mechanism through which additional in-person work is expected to help. “Employees are not in the office enough” describes attendance rather than the business problem.
• Affected roles: List participating and excluded teams, the activities thought to require physical presence and relevant differences in equipment, customer contact, handoffs or prior hiring commitments.
• Baseline data: Capture the pre-pilot value of each target outcome using definitions and collection methods that can be repeated. Attendance can remain an implementation measure, but it should not replace the outcome being tested.
• Test period: Specify the participating group, schedule change, start and end points, feedback intervals, any feasible comparison group and conditions that would pause the test.
• Outcome metrics: Choose measures tied directly to the stated problem, such as delivery time, error rate, onboarding progress, engagement, morale, retention risk or client response. Set thresholds for expanding, revising or ending the policy before results arrive.

Consider a hypothetical pilot intended to improve collaboration. If office occupancy rises while project cycle time remains unchanged and morale declines, employees complied with the requirement, but the test did not show that the intervention solved its stated problem. An overall improvement should also be examined by role so that gains in one group do not conceal disproportionate costs in another.

Completed pilot evidence remains the missing piece

The available material supplies a decision process and cross-organization survey findings, but it does not provide results from employers that completed the full sequence. It cannot establish that piloting will itself improve morale, retention, collaboration or productivity, and it does not designate one workplace model as the preferred outcome.

The next meaningful evidence would identify the affected workforce, policy change, baseline, test period and results measured with consistent definitions. Until employers publish evidence at that level, occupancy can show that workers followed an instruction; it cannot demonstrate that the instruction resolved the business problem used to justify it.

Also read:

• Business Process Automation: Design Exceptions Before You Scale
• Before You Scale a Digital Business, Make These 8 Operating Decisions
• Fast Business Internet Can Still Leave You Offline: Four Checks Before You Sign