Time tracking
Time clock software where the hours land in the project by themselves
One button: in, break, out. With the location recorded every time and fenced by radius when you need it, kiosks for people who carry no work phone, and the exact minutes off the clock going into the project with nobody typing them in afterwards.
Most time clocks record hours. Then the hours go nowhere.
Almost every company we talk to already records attendance somehow — a badge reader, a spreadsheet, an app that does that and nothing else. The hours get recorded and then they sit there. Nobody can say what went into which client this month without exporting two systems and reconciling them by hand.
In Fichaloto the clock and the project are the same database. When someone clocks in and picks what they are working on, those minutes go into the project as they are — no rounding to the nearest quarter hour, because this is not an estimate: it is what the clock read.
What gets clocked, and from where
Everything a working-time record needs to survive a review, and nothing you have to buy separately:
- In, break and out — a single button that changes with the state. The system already knows which one is next; offering three is asking the person to do the program's job.
- From a phone or a laptop — the same button sits on the dashboard and on the Clock screen. There is no app to install.
- From a kiosk — a tablet on the wall, with a four-digit PIN per person. For warehouses, sites and shops, where nobody carries a work phone. How geofencing works.
- With the location recorded — IP and city every time; coordinates and the centre's radius when the company requires it.
- With a simplified view, if you need one — for the people who only come in to clock in: one screen with the clock, the button, the break and “I forgot to clock in”, no menu and nothing else. You turn it on from permissions and pick who gets it, person by person.
- Against a project — switch it on and people pick one as they clock; the hours are logged automatically. Logging hours by project.
Scheduled and clocked, in the same cell
A clock-in on its own says nothing. What says something is comparing it with what was owed. So you write schedules — named weekly patterns, with two slots per day for split shifts — and put fifteen people on one in a single go.
On top of that sits the shift grid: one row per person, one column per day, and in each cell the schedule on top and what was clocked underneath. One day is changed by tapping its cell, without touching anyone's pattern. Shift scheduling.
Nothing gets rewritten, and you run the check yourself
Most clocking software stores hours in a table that gets edited. Clocking in writes a row, clocking out updates it, and a manager fixing a slip updates it again. What you end up showing is the latest state of a value overwritten an unknown number of times, with no record of it.
Here every entry is a new row and nothing is updated or deleted. A correction does not overwrite the original: it points at it and records who signed it and when. Both remain, and the hours on screen are calculated by reading the facts — the way an account balance is the sum of its movements.
Every entry also carries the fingerprint of that person's previous one, so if somebody emptied the table and rewrote it, the chain would not add up. And verification is not a certificate we hand you: it is a button inside your own account reporting how many entries it read, how many have altered content, and exactly where the chain breaks. A record only the vendor can check does not prove very much. The full argument is in our piece on tamper-proof clocking records.
Forgotten clock-outs are not fixed by whoever forgot
An entry with no clock-out stays open and counts as zero hours worked — which is what makes it visible. The next morning an email goes to the person who left it open, and whoever reviews the team's entries sees it in amber at the top of the screen.
Fixing it is not something you do yourself. You ask from the Clock screen, saying what time you left, and someone with permission approves it; on approval the entry is actually created and signed with who did it and when. A working-time record that everyone can edit at will is worth nothing as a record, and the first thing any audit asks is who changed what.
Spanish working-time law, if that is why you are here
Fichaloto is built in Spain, where recording start and end of each working day has been a legal obligation since 2019, records must be kept for four years and the labour inspectorate can ask for them. That is why the signing, the audit trail and the "you cannot edit your own entry" rule are not optional extras here. What the Spanish law actually requires.
Frequently asked questions
Do we have to buy clocking hardware?
No. People clock from the phone or laptop they already have, and where there is no work phone you turn any tablet into a kiosk: open a link once and leave it there. Nothing to buy and nothing to maintain.
Can we stop people clocking in from home?
Yes, by switching to "only from a work centre" and giving each centre its coordinates and radius. Our advice, though, is to let it through and flag it instead: blocking looks stricter and strands the person at a customer's office or with a poor signal, while flagging gives you the same information plus a list to review. Clocking out is never blocked, so nobody ends up with an open day because they stepped out on an errand.
We have several companies in a group with different rules.
Each legal entity can be stricter than the account, never looser: it can require a location the account does not require, and set its own radius. Not the other way round, because then creating an entity would be the way to escape the group's own controls. Work centres also belong to the entity that holds them.
Does the lunch break count as working time?
Not if you use the break button: lunch is recorded as a break and does not add to the day's total. If you would rather not have breaks, switch the button off and people clock out and back in, which is the same thing told differently.
Does it work outside Spain?
The clock itself does — it records times, locations, centres, kiosks and shifts anywhere. The interface is in English and Spanish. What is Spain-specific is the payroll-adjacent side: public holiday calendars, collective agreements and invoicing rules are written for Spanish practice, so a UK or Irish company gets the time tracking and the project side, and will want its own tools for payroll.
Getting started
Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.
What we have written about this
How to choose
Twelve questions worth asking before you sign
None of these twelve questions is technical. Every one of them is answered in a sentence, and you can ask for the answers in writing before signing anything.
9 min read
Compliance
A clocking record that cannot be quietly rewritten
Most time-tracking tools store hours in a table anyone with database access can edit. That is fine until the day somebody asks you to prove a number.
8 min read
Time and attendance
The clock ran all night. Now what?
Forgetting to clock out — or to punch out, if your team says it that way — is the single most common incident in any time-and-attendance system, and the way a product handles it tells you most of what you need to know about it.
6 min read