Skip to content
Inside the Boundary

All notes  /  The boundary

People Who Work From Anywhere

Geofenced clock-in applied to remote workers checks that someone is at home, which is a different thing entirely.

The boundary · Analysis

A boundary around a workplace verifies presence at work. A boundary around a home verifies presence at a home, and the two are not comparable.

Why it gets proposed

A hybrid policy requires office days, and someone wants to confirm them.

Or remote workers are hourly, and the employer wants a start time.

Or a manager is uneasy about people they cannot see.

The first is a narrow, answerable question. The second and third are not what this technology answers.

Checking office attendance

Legitimate, and the narrowest version works: a punch when they arrive at the office, on office days.

No punch on remote days, because there is nothing to verify.

Which means the system must know which days are which, and a mismatch should be a question rather than a refusal.

Do not extend the boundary to cover homes in order to have a punch every day. That is a different processing operation with a different justification, and it will be read accurately.

Clocking in from home

If hours are contractual and paid by time, a start time is a legitimate record.

But it does not need location. A tap is a tap; verifying that it happened at their registered address adds nothing about whether they started work.

And it puts a home address in the attendance record for everyone, permanently.

Use a plain clock-in with no location check for remote days. The same product usually supports it as a setting, and asking for it is the whole conversation.

The manager's concern

Usually about output visibility rather than about hours.

A punch does not answer it, and a person can clock in and do nothing, which everyone involved knows.

What works: visible work, shorter cycles, written updates. This is a management information problem and location does not touch it.

What to check in the product

Can location checking be disabled per person or per day type?

Can a remote day be recorded without a position?

Does the app behave differently on office and remote days, or is it one setting for everyone?

Products designed for shift work frequently cannot do this, which is a genuine limitation for a hybrid workforce rather than a detail.

The line to hold

Presence at a workplace is checkable and occasionally worth checking.

Presence at a home is not the employer's question, and building a record of it is the point at which a reasonable attendance system becomes something else.

Ask whether location can be disabled per day type

A procurement question specific to hybrid workforces.

Office days: a punch with a location check.

Remote days: a punch with none.

Many products designed for shift work cannot distinguish them, and that is a genuine limitation rather than a detail.

Without it, you either check location at people's homes or you do not record remote days at all.

An implementation prompt

During configuration, employee time tracking can prompt questions about fields, ownership and output. Confirm current capabilities and document each plan, integration or policy assumption.

Independent reference

For an external point of reference, see CIPD resources. Use this established source as an external check before turning the principle into a workplace rule.