Blog 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.
The classic failure: two systems
A company that starts working remotely and already had time tracking usually ends up with the old clock for office days and a separate sheet — or a second product — for home days. From then on everything costs twice: closing the month, answering a claim, working out the remote percentage that decides whether a written agreement is required.
The percentage is the one that hurts, because it drives a legal obligation. With two systems, computing it is a manual quarterly exercise nobody does until somebody asks.
The piece that fixes it fits in one word
Have every clock-in store its mode: on site, remote, at a client, travelling. One word per entry, picked at clock-in or inferred from where it happens, which turns a single record into both records at once.
With that, the remote percentage is a division rather than a project. And the person has nothing to remember: they clock in the same way on Mondays and on Wednesdays.
Four things that become easy
- The 30 % threshold. You see it coming months ahead, per person, and it stops being an inspection surprise.
- Agreed office days. If the agreement says two days on site, the record says so too, with nobody keeping a separate tally.
- Headcount in the building. Knowing how many people are coming in tomorrow becomes a query on the same data rather than a booking form.
- Expense compensation. If it is calculated on actual remote days, the number is already there.
What not to do
Do not infer the mode from the IP address or the network alone. A corporate VPN makes home look like the office, and an office with a guest network does the opposite. The IP is a reasonable hint for proposing the mode; a poor basis for deciding it on its own.
And do not tie clocking in to the mode being “right”. If somebody comes into the office on a day marked as remote, what you have is a conversation, not a block. The record has to capture what happened, not what was planned.
Frequently asked questions
How is the 30 % calculated exactly?
Against working time over a three-month reference period, or the proportional equivalent for shorter contracts. In practice, with the mode stored on every entry it is remote hours divided by total hours for those three months.
What about split days — morning at home, afternoon in the office?
That is why the mode belongs on each entry rather than on the day: a single day can have a remote clock-in and an on-site return from the break, and the split of hours falls out on its own.
Is it useful if the company does no remote work at all?
Yes, and you would not notice: every entry stays on site and there is not one extra screen. The benefit shows up the day you start, which is usually sooner than planned.
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.
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.
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.