Office space
How many desks and rooms the policy actually requires at the peak, not the average.
HR
Three days in the office buys you a fuller building and costs you flexibility. Two buys the reverse. Neither is wrong, but announcing one without knowing what it costs on the other five factors is how policies get walked back six months later.
A reversed policy is expensive twice: once in the change effort, and once in the trust it spends. The pattern behind most reversals is the same: the policy was set on a single factor, usually office cost or a leadership preference, and the other factors arrived later as complaints.
The second pattern is applying one rule to a whole organisation. A laboratory, a contact centre and a legal team have genuinely different distributions of work. A single number will be too strict for one, too loose for another, and roughly right for nobody.
How many desks and rooms the policy actually requires at the peak, not the average.
Measured against how the workplace supports the work, rather than as a general mood score.
Commute CO₂ per employee, which is reportable and increasingly required to be.
Travel time and distance, which distribute very unevenly across a workforce and drive attendance more than policy does.
What the policy signals to the market you hire from.
How much the workplace helps or hinders the work: measurable, unlike productivity itself.
Three policy options scored on all six factors that move together, with the two patterns behind most reversals and the five checks before you announce. Blank, so you can fill it in with your own numbers.
We can measure the workplace side of it accurately and the rest by asking. Occupancy describes physical use; Dynamics establishes patterns, preferences and where people work when they are not in the office.
An operating model judged on building data alone is judged on half the picture.
It depends on the product. Dynamics asks them to answer questions once. Occupancy does not involve them, though they should be told it is happening. Entry Pass gives them something back.
Participation should be worth their time, and they should know what is collected, what it is used for and what returns to them.
It depends on the product, and the architecture reports patterns rather than people by design. That is a decision taken before the first sensor, not a policy added after a works council asked.
What is processed, on what basis, who may see it and how long it is kept is settled per project before implementation, and written down.
The analysis is not the deliverable, the decision is. Depending on scope: scenarios, a hybrid policy, a space programme, support through design and fit-out, employee enablement, and then measuring again on the same method.
That last step is what turns two snapshots into a trend and a trend into the next business case.
Unlimited scenarios, six factors, costed.
The working-pattern data the model runs on.
In preparation. Balance is the full model.
Why one rule lands differently on a lab and a legal team.
Coordination beats compulsion, with the evidence.