Blog Remote work
Who declares the remote working address, and who signs it off
The person declares it, the employer approves it, and what is stored is an area rather than a home address. All three decisions have a reason, and all three are usually taken the other way round.
Why the administrator should not type them in
It is the first thing companies try and the first thing that fails. A firm of sixty that wants the remote working location of every employee on record ends up with somebody in HR asking for addresses by email, copying them by hand and getting them wrong. Four months later half are out of date and nobody trusts the list.
There is also a reason that is not about efficiency: in most remote working frameworks the place of work is chosen by the employee within whatever the agreement allows. It is their declaration, not a fact the employer collects about them. Having it written by the person who chooses it changes what the whole record means.
Why approval has to exist
An address that starts checking the moment it is typed is worth nothing: the day somebody clocks in from elsewhere, they edit the address and the flag stops firing. And in the other direction, nobody should be flagged against a figure the employer has never looked at.
So a declaration starts as pending and checks nothing until somebody answers. Approving is the moment the employer says “yes, that is the agreed place” — which is exactly what the remote working agreement has to record.
And rejecting should require a reason. A bare “no” in front of a form leaves the person with no idea what to fix, and it ends in an email somebody has to answer anyway.
Who approves: it does not have to be an administrator
This is where most tools get it wrong, and it is a permissions-model mistake rather than a product one. Looking after a team’s declared addresses and being able to change the time on someone else’s clock-in are two different responsibilities: the second signs a record with evidential weight and the first does not.
They should be separate permissions, so that a team lead can review and approve their own people without touching the timesheet correction queue, and whoever works that queue does not get to decide where anyone lives. Bundled together, giving one to a middle manager forces you to give them the other.
What is stored and what is not
The address is written in full — street, postcode, town, province — because that is what goes into the agreement. What is used afterwards to check is much less:
- The town, which is what lets an alert be explained in plain language: “clocked in from another town”.
- An approximate point, rounded, with a tolerance of several kilometres. Enough to say whether a day matches the area; nowhere near enough to know which building anyone lives in.
- Nothing else. No history of where the person has been, no position outside the moment of clocking in.
The chore nobody wants to repeat
Three details separate a system that maintains itself from one that rots in a quarter: the person can change it when they move — and it goes back for approval — the employer can see at a glance who has not declared one, and reminding them is a button rather than a round of emails.
And one dull but decisive rule: if an address is withdrawn, the days already checked against it do not change. Every day keeps the verdict it had when it was clocked. A record that recalculates backwards has stopped being a record.
Frequently asked questions
Can somebody have two declared addresses?
Yes, and it is more common than it sounds: home plus a second place where they work part of the summer, for instance. What matters is that both are declared and approved, and that the check accepts either.
What about people who never log into the platform?
There has to be a way for somebody with the right permission to enter it by hand, marked as entered by someone else. What cannot happen is that the only route to the data is everybody logging in: there are whole workforces that never open a computer.
Is this special category data?
It is not a special category under the GDPR, but it is personal data and it deserves minimisation up front: storing the area rather than the exact coordinates of a home is exactly that, and it is what makes the processing defensible.
All of this is built into Fichaloto. See how it works.
Keep reading
Remote work
Tracking remote work without surveilling anyone
You can run a defensible remote working policy with no screenshots, no keystroke counts and no idea where anyone is at any given minute. What you measure is the working day and the agreed place, not the person.
Compliance
What a Spanish remote working agreement has to say
Spain requires a written agreement once remote work passes 30 % of working time over three months, and lists what that document must contain. Two of those items are the ones you then have to be able to evidence every day.
Remote work
One record for the office days and the home days
The fully on-site company and the fully remote one are the two rare cases. The norm is the mix, and the mix is exactly what breaks tools designed for one or the other.