submove / behavioral simulation / reaction to RTO

How will your organization react to a return-to-office mandate? Rehearse it first

Last updated: June 2026

To see how your organization is likely to react to a return-to-office mandate, you rehearse it before you announce it: model the workforce as pseudonymized, role-coded profiles inside the real network, then play the RTO policy forward. The model projects banded shifts in engagement, trust, and load for that scenario, and which roles and teams absorb the most.

RTO is one of the most uneven changes an organization can make: the same policy is a minor adjustment for some and a dealbreaker for others. A behavioral simulation lets you rehearse the exact policy while it is still a draft. This is the RTO case of the broader method in what is a behavioral simulation engine.

Why RTO mandates are hard to read in advance

An RTO mandate does not land on an average employee. It lands unevenly across the structure, hardest on the roles whose working pattern it changes the most, such as roles hired on remote terms, and those roles are not evenly spread across the org chart. Average sentiment hides exactly the concentrations that decide how the policy lands.

That is why headcount math and a single engagement number misjudge the reaction. They average away the pockets where the policy asks the most, which are usually exactly the pockets a flat average hides.

How to see the likely reaction before you announce

The method is to rehearse the exact policy against a model of your real organization before it becomes public, so you can adjust it while it is still a draft. With submove that runs as a focused engagement in four steps.

Frame the policy precisely. Name the exact mandate, how many days, which roles and sites, what exceptions, effective when, so the simulation aims at the real decision rather than RTO in general.
Build the model. Represent the affected population as pseudonymized, governed, role-coded profiles inside your real structure. Names and direct identifiers are masked before anything reaches the engine, and the profiles are handled as personal data under our privacy notice.
Run the policy forward. Play the mandate through the organization many times, producing banded trajectories — ranges, not point estimates — for engagement, trust, and load under that scenario.
Read the cockpit together. Interpret where the policy places the most load, then translate that into how you might phase, exempt, or communicate it differently.

A worked example: a three-day in-office mandate

Suppose you are weighing a three-day-a-week in-office mandate across a mixed workforce, some hired in-office, some hired fully remote during the distributed years. On paper it is one policy applied evenly. The reaction will not be even.

Played forward, an RTO mandate of this kind typically projects the sharpest engagement and trust dips not across the whole population but in specific parts of the structure: roles hired on remote terms, whose deal the mandate rewrites, and scarce senior roles where the plan has the least slack if a seat empties. The model tends to surface that a uniform mandate quietly concentrates its heaviest asks on the hardest-to-refill roles, and that a blunt announcement compounds the trust hit beyond the policy itself.

None of that names an individual or makes a claim about a single person's choice. It is a structured read of where the policy places the most load, early enough to do something: phase the rollout, carve the exceptions that matter, or change the communication, before the mandate is public and irreversible.

The same policy is a shrug for some teams and a broken deal for others. Seeing which is which beforehand is the whole point.

What you can do with the read

Phase it. Sequence the rollout so the roles carrying the heaviest change are not hit first or hardest.
Shape the exceptions. Carve the exemptions the model projects will actually reduce the load, not blanket ones.
Communicate deliberately. Lead with the parts of the organization where the model projects the mandate reading most like a changed deal.
Reconsider the dose. Sometimes the read is that two days holds the gains and three days is where the projected trajectory turns.

Simulation or a survey?

A survey reads how people feel now and risks signalling the mandate before you have decided on it. A simulation rehearses the response to the exact policy privately, before anything is announced. They answer different questions and are strongest together.

For the full comparison, see behavioral simulation vs surveys vs change-management tools.

Frequently asked questions

Can you know in advance how employees will react to a return-to-office mandate?

Not person by person — no tool can tell you what one individual will do, and submove does not try. A behavioral simulation plays the specific RTO policy forward across a model of your organization at role resolution and projects banded shifts in engagement, trust, and load, and which roles and teams absorb the most, bounded to that scenario and window. It is calibrated, not validated.

Will a return-to-office mandate increase attrition?

That depends on the policy and the workforce, and no simulation can promise a number. What the model does show is that an RTO mandate tends to land unevenly: the load concentrates in specific roles and teams, for example roles hired on remote terms, rather than spreading evenly across headcount. Rehearsing the exact policy shows where the projected trajectory turns, so the retention question can be weighed with that unevenness visible.

Does this show who will resist or leave?

No. submove never names, scores, or ranks individuals. It shows where the policy is projected to meet the most resistance and place the most load, at the resolution of roles and teams, so you can see which parts of the organization the mandate asks the most of, not what any named person will do.

Should we survey employees before announcing RTO?

A survey can read current sentiment, but asking about RTO can itself signal the decision before you have made it, and it cannot tell you how people will respond to the exact policy. A behavioral simulation rehearses the response privately, before anything is announced.

How is this different from modeling the cost or headcount of RTO?

Cost and space models tell you what the policy looks like on paper. A behavioral simulation answers a different question: how the organization is likely to respond to it, where engagement and trust are projected to slip and which roles carry the most load, so the human side of the decision is visible before you commit.

Rehearse your RTO mandate before you announce it

If you are weighing a return-to-office mandate and want to see how it is likely to land first, you can request a simulation and tell us the situation. Engagements are invitation-only, so we will talk first about whether submove is the right fit.