Outgrace
OutgraceThe Leadership Magazine, home

Remote, hybrid or on-site: a test for each role

Sort each role by the work it needs, then test every remote, hybrid or on-site decision against the UK rules on refusing requests.

Most work-location policies are written as a mood, not a test. Staff hear that the company values time together, or that remote working is a benefit, and then each manager decides role by role, often on whoever argued hardest. The result is a set of decisions nobody can explain when someone asks why. This framework takes a different route. It sorts each role by the work it actually requires, using three demands: collaboration, physical presence and confidentiality. It adds a fourth test for the legal exposure of saying no, because in the UK a refusal is a decision the employer must justify. One warning comes first. This is our judgement, not a finding. The sources we reviewed contain no occupational research on which tasks suit remote, hybrid or on-site work, so the sorting below is reasoning to test, not evidence to cite.

The sort itself is simple. For each role, rate the three demands as high, partial or low, using the role's actual tasks rather than its job title. A role rated high on physical presence goes on-site. A role rated high on confidentiality stays on-site or in restricted hybrid until the controls are named. A role rated high on collaboration needs a fixed, shared pattern, which in our judgement usually means hybrid. Where the ratings conflict, the strictest one governs, and the reason goes in writing. Nothing here replaces a manager's knowledge of the team. It forces that knowledge into sentences someone else can check.

Chapter one: 1. Collaboration: how much work needs shared time

Start by asking how much of the role's output is produced jointly, and how quickly. Do not count meetings. A payroll analyst who works alone to a fixed close date has little collaboration to protect. A product designer who revises a layout with engineers across a single afternoon does. The test is concrete. List the three recurring sessions the role cannot do without, then ask whether each needs a real-time exchange or could run as a written thread that ends with a recorded decision. If two of the three need real time, the role rates high.

What goes wrong is that managers count calendar entries and miss the informal work: the quick correction that prevents a week of rework, the question asked across a desk, the new joiner watching how a senior colleague handles a difficult client. None of that appears in a diary. In our judgement, a role with someone in their first six months, or a team being rebuilt, should lean towards more shared presence than its calendar suggests. That is a working assumption. Nothing we reviewed measures it, and a team should check it against its own experience before writing it into policy.

Chapter two: 2. Physical presence: does the work need a place

Next, ask whether the work needs a particular place. Some tasks cannot happen anywhere else: a stock count in a warehouse, a bench in a laboratory, an inspection on a construction site, a machine that must be run by hand. Others need only a screen and a connection, although the person may still prefer to sit near colleagues. Keep those two kinds of demand apart. A role that requires a place should be on-site, and the policy should name the task that requires it. A role that merely benefits from a place should default to hybrid, with in-office days set by the team rather than negotiated one person at a time.

The usual failure is treating presence as a proxy for trust. A manager who wants to see people at their desks is asking about supervision, which is a management problem with its own remedies: clear objectives, regular check-ins, and output that can be seen. Keep the two apart. If a role is on-site because of the work, one sentence will say so. If it is on-site because the manager wants to watch, the designation will not survive the first request, and it should not.

Chapter three: 3. Confidentiality: what leaves the building

Third, ask what happens to information if the work leaves the building. Some roles handle data restricted by contract, by regulation or by the company's own rules. The practical test is blunt. Could the person do this job from a home network, on a managed laptop, in a shared flat, with a printer in the next room? If the honest answer is no, the role rates high and stays on-site or in restricted hybrid until controls exist that the company can name. Those controls matter more than the building. In our judgement, a managed device with locked access can be more tightly controlled than an open-plan floor.

Put the test to the information security and legal teams, not to the line manager alone. Ask them to confirm, in writing, what the role may and may not take off-site. Where a role handles regulated data, a lawyer or the relevant regulator should confirm which rules apply. This framework does not say what those rules are. A policy that pretends otherwise has moved from judgement into advice that nobody qualified has given.

Chapter four: 4. The right to ask: what a refusal must prove

The fourth pillar is the one most policies skip. In the UK, every employee holds a legal right to request flexible working, and the government's guidance says the request can be made from the employee's first day in the job. The guidance gives working from home as one example of flexible working, alongside flexible start and finish times. The statutory process the guidance calls making a statutory application must be dealt with in a reasonable manner. An employee who believes it has not been can take the employer to an employment tribunal.

An employer can refuse, but only with a good business reason, and the tests above are written to meet that standard. A decision to mark a role on-site or hybrid is, in effect, a prediction that a request will be refused. Write it as one. Ask what the business reason is, in one sentence, and whether a manager could repeat it to the employee who asked. If the answer rests on preference rather than on the work, the designation is weak, and the policy should say so before someone else does.

The guidance has two limits we must flag. It says Acas publishes a code of practice on handling flexible working requests, but the text we reviewed does not reproduce the examples of reasonable handling, or the full list of changes an employee can ask for. Read the code and the complete guidance before drafting. The rules also differ in Northern Ireland, where the UK-wide summary does not apply. A company with staff there needs advice specific to that jurisdiction. That is a question for an employment lawyer, not for this framework.

A sort for each role

Answer each question for the role's actual tasks, not its job title. Any unresolved answer goes back to the manager before the designation is set.

  • Does the role depend on joint, real-time work that cannot run as a written exchange with a
  • Would someone in their first six months lose learning or context by working remotely?
  • Does any task need a specific physical place, such as a site, a laboratory or a machine?
  • Could the role be done from home, on a managed device, without exposing restricted data?
  • Have the information security and legal teams confirmed the confidentiality answer in writ
  • Is every on-site or hybrid requirement stated as a business reason in one sentence?
  • Has the manager's wish to supervise been separated from what the work requires?
  • Will the designation be reviewed if a request produces a refusal or a dispute?

Outgrace checklist

Where it breaks

The framework breaks in three places. The first is a blanket rule applied to a whole team without the task list, which recreates the mood-based policy it was meant to replace. The second is a confidentiality answer given on paper but not backed by controls. In our judgement, that is the most costly failure, and it is often found only after something has gone wrong. The third is a refusal issued without a stated business reason. In the UK, that is the point at which a request stops being an internal conversation and becomes a dispute the employer must defend.

None of this makes a refusal unnecessary. It makes a refusal specific, which is a different and more defensible thing. A role that cannot pass the tests should say which test it fails, and a role that passes should say that too. Where a manager disagrees with a rating, the disagreement belongs in the file, not in the corridor.

An employer can refuse an application if they have a good business reason for doing so.

UK government, flexible working guidance on gov.uk, gov.uk

On Monday, list every role the company has marked on-site, hybrid or remote, and set the four tests beside each one. Start with the roles where practice and written policy disagree, because the first request is likely to come from one of them. Ask information security for the confidentiality answer in writing. Ask an employment lawyer to read the designation sentences before they reach staff, particularly for anyone working in Northern Ireland. Where a role fails a test, say which test and why. A policy that names its reasons is harder to argue with, and far easier to revise when the work changes.

Newsletter

The Briefing

One email a week: the leaders we profiled, the ideas worth stealing, and nothing else.

Weekly, free, one click to leave. Read our privacy policy.