To start with
What is Fichaloto?
Fichaloto es una plataforma española de recursos humanos, control horario, gestión de proyectos y planificación de equipo, pensada para empresas que trabajan por proyecto o por cliente, sin tope de plantilla. Se ficha dentro de Fichaloto —entrada, pausa y salida, con ubicación, centros de trabajo, kioscos en tablet y turnos— y en la misma pantalla están la ficha de cada persona, las horas dedicadas a cada proyecto y cliente, y la capacidad libre del equipo. Es modular: cada empresa enciende solo los bloques que usa. La desarrolla y opera NUDAYOSH, S.L., desde Madrid.
What size of company is it meant for?
How you work decides it, not how many of you there are: it fits best in companies that bill or justify their time by project or by client — consultancies, engineering firms, technical practices, installers, agencies, professional practices and service companies. There is no headcount limit, and every listing has search, filters and pagination precisely so it still reads well as the team grows. Below five people plenty of firms get by with a spreadsheet and that is fine. And if you are several hundred, write to us before you sign up: we would rather tell you up front what is solved and what would need adjusting than have you find out halfway through.
How is Fichaloto different from other HR platforms?
En cuatro cosas concretas. Primera: se configura hondo y sin tocar el código —el vocabulario de la casa, los permisos recurso a recurso y acción a acción, los catálogos, los calendarios laborales, quién aprueba qué y los informes— y esa configuración la lleváis vosotros, sin pedirnos nada. Segunda: la imputación de horas a projects, la capacidad del equipo, el CRM, el reclutamiento, la formación, el control horario, el ticketing, la API, la facturación y la rentabilidad van TODOS dentro: no hay ediciones, ni extras, ni una función guardada para el plan de arriba. Tercera: se integra con lo que ya tenéis mediante una API REST abierta —clientes, personas, projects, tareas y ausencias en los dos sentidos, y las horas imputadas de salida— sobre las mismas entidades y las mismas reglas que la pantalla, sin conectores de terceros ni intermediarios. Y cuarta: cuando llamas hablas con quien escribe el código, en castellano y sin centralita.
What the law says
Is time and attendance recording compulsory in Spain?
Yes. Since 12 May 2019, article 34.9 of the Spanish Workers' Statute, introduced by Royal Decree-Law 8/2019, requires every company to record the start and end of each person's working day, to keep those records for four years, and to keep them available to staff, their representatives and the Labour Inspectorate. The law does not impose a particular medium: paper or a spreadsheet are still valid today if the record is reliable and tamper-proof. A royal decree on digital time recording is going through the process and would tighten these requirements, but as of today it has not been published in the official gazette.
What is the penalty for not keeping time records?
Failing to keep the working-day record is a serious offence under article 7.5 of the Spanish law on labour offences and penalties (LISOS). Under article 40.1 of the same text the fine runs from €751 at the lowest grade to €7,500 at the highest, and it applies per workplace. Falsifying the record is a very serious offence, with fines from €7,501 to €225,018.
Is a spreadsheet enough for the working-time record?
Today, yes, with conditions. Article 34.9 of the Spanish Workers' Statute does not impose any particular medium: it requires the record to be daily, to capture the start and end of each person's working day, to be kept for four years and to be available to the workforce, their representatives and the labour inspectorate. A spreadsheet can meet that. The problem arrives when you have to prove it has not been touched: a file anyone can open and rewrite without leaving a trace is hard to defend before an inspection, and falsifying the record is a very serious offence. There is also a royal decree on digital time recording in progress which, if published, would tighten these requirements. In Fichaloto every mark is chained to the previous one with a fingerprint, so the series can be shown to be complete and untouched.
Do people have to clock in when working from home?
Yes. Article 14 of Spain's Law 10/2021 on remote work says explicitly that people working remotely must record their hours exactly as those who go into the office do, showing the start and the end. There is no exemption for working from home. In Fichaloto you clock in from your phone or your computer, and the account decides whether location is required and whether people can clock in away from a work site: for remote work, usually yes.
How are overtime hours kept in check?
With the same record. Article 35.5 of the Workers' Statute requires overtime to be totalled monthly and a copy of that summary given to each person; article 35.2 caps it at 80 hours a year, not counting hours compensated with time off within the following four months or those worked under force majeure. What it takes to keep them in check is comparing what was clocked against the working day each person is due, and that comes from the schedule and the collective agreement on their record. In Fichaloto the weekly grid shows the schedule on top and what was clocked underneath, day by day, so the excess shows up while it can still be compensated and not once it is already eighty.
How long do working-time records have to be kept?
Four years. Article 34.9 of the Workers' Statute says so, and throughout that time they must be available to the workforce, their legal representatives and the labour inspectorate. That is a practical reason not to keep them on loose sheets: three years on, the hard part is not having the data but finding it. In Fichaloto the record is searched and exported by person and by period, and it is not deleted when someone leaves.
What if someone refuses to clock in?
Clocking in is not optional for either side: the company is required to keep the record and the person is required to have their working day recorded. Refusing repeatedly is a breach handled through whatever disciplinary route the collective agreement sets out, but before getting there it is worth asking why: almost always the system is in the way — you have to log in to a computer someone else is using, the app asks for permissions that feel intrusive, or location fails in a unit with concrete walls. That is why Fichaloto lets people clock in from a phone, from a computer and from a tablet kiosk with a code, and location can be required or not depending on the site.
What is the difference between time recording and access control?
Time recording is the legal obligation: registering the start and end of each person's working day, every day, and keeping it. Access control is a broader idea with no regulation of its own: knowing who is on a site, usually with turnstiles, cards or fingerprints, and it normally answers a security or access need rather than an employment one. They get confused because many devices do both, but only the first is required by law and only the first has to be shown to an inspection. Fichaloto does time recording.
How clocking in works
Do people clock inside Fichaloto, or is another program needed?
Inside. There is a button on the dashboard — in, break and out — and a “Clock” screen with the whole week: what you clocked against what you owed, day by day. People clock from a phone, from a laptop, or from a tablet kiosk with a four-digit PIN if they carry no work phone. No separate app to install and no terminal to buy.
Can people clock in from their phone?
Yes, and it is the most common way. The clocking screen works in a phone browser with nothing to install: in, break, back, out, with the project the day goes to if the account asks for it. If the site has coordinates and a radius, the phone sends its location when clocking and the mark keeps the distance; if not, clocking still works. And for anyone without a company phone there is the kiosk: a tablet fixed by the entrance where each person types their code.
Can we require people to clock only from the work centre?
Yes, with the radius you choose. Every work centre has its coordinates and its radius — 100 metres for an office, 500 for a building site, where the signal is worse — and when someone clocks, the location the browser gives is compared against that radius. You can either refuse a clock-in from outside or let it through and flag it, which is what we recommend: blocking looks stricter and strands the person at a customer's office or with poor coverage, while flagging gives you the same information plus a list to review. Clocking out is never blocked. On top of that, each company in the group can tighten the rule on its own, but not loosen it. And wherever people clock, the IP and the city they clocked from are always recorded.
Can time recording cover several work centres?
Yes, and it is one of the reasons people set it up. Each site is registered with its address, its coordinates and its radius, and it can belong to the account, to a company in the group or to a client — the works, or a client office where someone is posted. Each person can have one or several. It also matters because the penalty for not keeping the record applies PER WORK CENTRE: with four sites, the same offence is multiplied by four.
Can shifts and schedules be planned?
Yes. You write named weekly patterns — “Split-shift office”, “Afternoon shift” — with two slots per day, which is how the Spanish split shift works, and put fifteen people on one in a single go. On top of that sits the weekly grid: one row per person, one column per day, and in every cell the schedule on top and what was clocked underneath, because the question is never one of the two on its own but whether they match. One day is changed by tapping its cell, without touching anyone's pattern, and next week is set up by copying this one.
What if someone forgets to clock out?
An entry with no clock-out stays open and counts as zero hours worked, which is what makes it noticeable. The next morning an email reaches whoever left it open, and whoever reviews the team's entries sees it in amber at the top of their 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 everyone can edit at will is worth nothing as a record, and the first thing any inspection asks is who changed what.
Can the working-time record be changed afterwards?
No, and that is exactly the point. In Fichaloto the record is not edited, it is appended to. Every clock-in, break, return, clock-out, correction and annulment is a new row the database itself refuses to modify or delete. Correcting a time does not rewrite the original: it adds a mark saying which one it replaces, and both stay, with who signed it and when. Deleting a day does not delete it either: it adds an annulment, so the day stops counting but the record still shows it existed. And every mark carries the fingerprint of the previous one for that same person, chained with a secret that appears on no screen and in no export: if somebody emptied the table and rewrote it, the chain would not add up. There is a button to check it that you press, not us, and it says how many marks it read, how many are altered and how many are missing.
Do we need another tool for the legal time record?
No. El control horario de Fichaloto es completo por sí solo: entrada, pausa y salida con ubicación, centros de trabajo, kioscos en tablet, turnos y solicitudes de corrección con aprobación y firma. Los apuntes no se editan: se corrigen pidiéndolo, y cada corrección queda trazada con quién la pidió, quién la aprobó y qué decía antes. Si ya ficháis en otro sitio, no pasa nada: el fichaje se apaga desde vuestros propios ajustes y el resto de la plataforma funciona igual.
Hours, projects and money
Can I see how many hours go into each project and each client?
Yes, and it is the reason the product exists. Every logged hour is tied to a project, and every project to a client and an hours budget. If a project is picked when clocking in, the exact minutes on the clock land on it by themselves, with no rounding to the quarter hour and with nobody writing them down afterwards; and if not, clocked hours sit next to logged hours so you can see how much of what was clocked has been logged and how much has not. The project record compares real hours against estimated ones at all times and flags the deviation with a traffic light, so a project running over shows up in week three and not on next month’s invoice.
Can I tell whether my team is clocking the hours I planned?
Yes, and it is one of the reasons both things live in the same database. If you plan somebody full time on a project, you can see what they actually clocked against what was planned, per person and per week. And when clocking in, anybody on several projects picks which one those hours go to —anybody on just one has it preset— so clocked and charged stop being two separate acts with three days and a rounding error between them. What we do not do, and will not do, is log keystrokes, take screenshots or count idle time: we measure the work, not the worker.
Is a project’s cost just the team’s hours?
No, which is why both are declared. Each person has their own hourly cost, which a particular project can override when they cost something else there —a senior profile on loan, a rate agreed with that client— and separately you record the project expenses: subcontractors, licences, travel, materials. They cut the margin exactly like hours do and appear on the same screen, so the number you look at on a Tuesday is the one you will see at the bank. And every figure opens up: click the margin and you see the whole subtraction —which hours, whose, at what rate, which expenses— and where each part is changed. A metric that will not explain where it came from gets argued about in every meeting.
How do you know whether a project is profitable?
By comparing what it cost against what was charged, and that needs both halves. The cost comes from the hours logged multiplied by each person's internal hourly cost, plus any expenses booked to the project; the income, from what was quoted and what was invoiced. Fichaloto shows it by project and by client, with the gap between the hours planned and the hours actually spent, and a traffic light when consumption approaches the budget. What changes things is not the final number but when you see it: in month three of a six-month project there is still something you can do.
Can hours worked be invoiced to a client?
Yes. Approved hours logged to a project become invoice lines, with their sequential series, their VAT and withholding, their period and their PDF. Once issued an invoice cannot be changed: to correct it you issue a credit note, which is what Spanish invoicing rules require. It is then reconciled with the bank by uploading the statement, and a paid invoice marks itself when its payment matches.
How do you account for hours on a grant-funded project or an R&D tax credit?
What an auditor or a funding body asks for is the same in every case: who worked, on what day, how many hours, on which project or activity, and how that relates to that person's working-time record. The hard part is almost never having the hours: it is being able to show them squaring with the recorded working day, without one day showing nine hours logged and seven clocked. In Fichaloto both live in the same database and are seen side by side, they export by person, project and period, and the working-time record is chained and signed, so the logged hours rest on something that can be audited. Fichaloto does not file the claim for you and does not replace your adviser: it gives you the data the claim is built from.
People and their permissions
Can holiday and time off be handled in the same place?
Yes. Each person requests their days from their own screen, sees what is left of their allowance and who the request goes to; whoever approves answers from a queue, and on approval those days come off capacity in the planning views, so they stop showing as available. Absence types are a catalogue each company maintains — holiday, personal days, medical, training, whatever their collective agreement uses — each with its own rules on whether it draws down an allowance, whether it needs approval and whether it counts as a working day.
Can I decide who sees what inside the platform?
Yes, and in real detail. Permissions are not three fixed levels: they are granted resource by resource — projects, people, hours, costs, reports, audit trail — and action by action: read, write, amend, approve or delete. With that you build roles such as “project manager who sees the hours used on their own projects but not the profitability” or “administrator who logs everybody's hours but approves none”. Roles can be duplicated so you start from one that nearly fits, one person can hold several at once, and their own things — their hours, their holidays — are always visible without configuring anything.
What about people who only come in to clock in? Is there something simpler?
Yes: the simplified view. You turn it on from Roles and permissions, and anyone it applies to logs in and sees a single screen — their clock, the clock-in button, the break and “I forgot to clock in” — with no side menu and no other screen at all. It only applies to people holding the member role and no other, and on top of that you choose person by person: the same screen lists those people with a tick box each, because there are almost always three or four who do come in to check their monthly hours. Nobody loses a single permission: they simply stop being shown what they never use, and you switch it off whenever you like.
Can I log in as another person to help them?
Yes, and it sits behind its own permission rather than behind being an administrator. Whoever holds it can log in as if they were another person, see exactly what that person sees, and fix something for them without asking for their password — which is the real, and bad, alternative. Everything done inside is recorded in the audit trail under the name of whoever opened the session, not the person. And someone who does not administer the account cannot log in as someone who does: if they could, this permission would be the back door to every other one.
Can I see, person by person, exactly what permissions they have?
Yes, in a report built for it. Roles stack —somebody holding two can do the union of both— so looking at them one at a time never shows what a person can actually do. The report resolves that sum person by person, using the same code the application uses to decide on every screen, and downloads as Excel with three sheets: a matrix of people against permissions, the line-by-line detail, and what each role grants. It sits behind its own permission, because knowing what everybody can do is exactly the map somebody would want before doing something they should not.
Is there a record of who does what?
Of everything that changes something. Every creation, amendment, approval and deletion goes into the audit trail with the person, the date, the IP address and the reason where there is one. And if an administrator acts on somebody else's behalf to help them — without asking for their password, which is the real alternative — the record says both things: who pressed the button and on whose behalf. That is the difference between a log that explains what happened and one that is only good for arguing.
Getting it running
How long does it take to get Fichaloto running?
The account is created in minutes and your headcount is imported in one go. What takes time is not the setup, it is agreeing what you call things: what a project is, what a phase is, and who sees what. In a mid-sized company that is settled in one or two sessions, and from there people clock in and log hours.
Can we migrate from another clocking system or from a spreadsheet?
Yes, and it is the first thing you do. You upload the clocking history in a file — one row per day, with its in and out — and it comes in as marks, flagged as imported so they are told apart from those clocked here. Same for people, clients, projects, logged hours and calendars: fifty-six tables can be downloaded and uploaded again. Before anything is written, the screen shows what is going to happen row by row and what does not add up, so a badly built file shows up beforehand and not afterwards.
Can we try it before signing up?
Yes: fourteen days with the whole platform and no card. It is not a cut-down version, it is the complete platform, and what usually happens is that the real people come in during those days and really clock in, because a product like this is not judged on made-up data. If it does not fit in the end, there is nothing to do: the trial expires on its own.
Is it useful if we already have a payroll bureau or payroll software?
Yes, and it sits well alongside both because it does not do the same job. Fichaloto does not run payroll, does not hold contracts or employment paperwork and does not file social security returns: the only financial thing it knows about a person is their internal hourly cost, which is what a project's cost is worked out from. What it adds is the working-time record, absences and hours per project — exactly what a payroll bureau asks you for every month and you send over by hand today.
Fitting it to what you already have
Can Fichaloto be connected to our ERP or our dashboard?
Yes. Much of the platform can be read and written from outside through a REST API over JSON: clients, people, teams, projects, phases, tasks, milestones, diary, time off and catalogues. Logged hours can be listed, read and deleted. Roles, the audit trail, reports and calendars stay out of it and are managed from the application. You get in with a key created from the application itself, which can be read-only or read and write; a key can never do more than the person it belongs to, so the permissions you have already configured apply just the same to integrations. Every write through the API goes into the audit trail with the name of the key that made it, and the key is revoked in one click the day that program stops being used.
Is generating a key enough to use the API?
No, and that is deliberate. Both things are needed: the key —generated inside the application, shown once and revoked in one click— and a role on its owner that allows using the API. Being an administrator is not enough: this is the one exception to «whoever can do everything can do everything», because the API is a different door, a program walks through it rather than a person with a session, and opening it has to be a decision somebody takes rather than a consequence of holding a job title. Two built-in roles come with that permission already set —one read-only, one read and write— and if it is missing, the API response says exactly what is missing and on which screen to fix it. Once inside, a key can never do more than its owner.
Price, data and the relationship
What does time-tracking software cost for a small business?
It comes down to three things, and none of them is the vendor's logo: how many people will actually use it, whether you only need to meet your working-time obligations or also want to know what each project costs, and in how many places and how many ways people clock in. That is why the published list price of most of this market is not what anyone ends up paying: underneath it sit a minimum number of billable seats, an implementation fee, or a higher tier where the thing you actually need happens to live. Ask every vendor for the total cost of the first year divided by twelve, in writing, and compare that. Fichaloto does not publish a per-seat rate: you get a fixed quote built around your case, with implementation and kiosks inside it, no minimum headcount, no onboarding fee and no lock-in.
Is there lock-in, a set-up fee or a minimum headcount?
There is none of the three. The trial lasts 14 days, asks for no card and expires on its own: if you say nothing, nothing is charged. After that you pay for the people who actually use the platform, with no billable minimum below which you pay for people you do not have. The subscription renews on its own, as with any service of this kind, and is cancelled whenever you like with no penalty and no notice period.
Where is the data stored and how is GDPR met?
The data is hosted on servers inside the European Union and traffic is encrypted in transit. Access is separated by account and by role: every read of somebody else's data goes through the company identifier, so one client's data never appears on another's screen. If you need the hosting provider's details, the exact location and the data-processing agreement for your record of processing activities, we give it to you in writing before anything is signed.
What happens to our data if we stop using Fichaloto?
It is yours and you take it with you. Everything in the account exports from the application itself, table by table, into files any spreadsheet opens: people, clocking records, the marks of the working-time register, logged hours, projects, clients, invoices, absences and the audit history. There is nothing to request and nobody to wait for, and you do not have to still be a customer to have done it before leaving.
Can I suggest improvements and ask for changes to Fichaloto?
Yes, and from inside the application itself. The sidebar has one button to report a bug and another to suggest an improvement, with the same questions as the templates we hand out: what you expected and what happened for a bug; what you would like to be able to do and what problem it solves for an improvement. They reach the same people who write the code, not a switchboard. Whoever administers the account decides who on their team may send them, and sending asks for your password so that nobody writes in somebody else's name from an unlocked computer. We always reply, saying what we decided: accepted with a date, accepted without a date, deferred, or turned down.
What if I need something the product doesn't do today?
Se hace. Lo que compras es una base sólida y probada, no un techo: el código es nuestro, lo escribimos nosotros, y se puede desarrollar prácticamente cualquier cosa para tu caso — una pantalla que no existe, un cálculo con tu fórmula, un informe con el formato que te pide tu cliente, un circuito de aprobación que no se parece a ninguno, una integración con el programa que ya usas. No es un producto cerrado de un fabricante al otro lado del mundo: hablas con quien lo escribe. Primero mira uno de nosotros si ya se resuelve configurando, que pasa muchas veces y entonces no cuesta nada; si no, te decimos qué cuesta y en cuánto tiempo, por escrito, y tú decides. Y si además le sirve a más empresas, entra en la hoja de ruta y sale más barato o gratis. Lo único que no hacemos es prometerlo antes de haberlo mirado, ni decir que sí a algo que rompería el producto para los demás.
How do I report a bug in Fichaloto, and how long do you take to fix it?
From the “Tell us something” button in the sidebar, without leaving the application and without opening an email. The form asks for what is actually needed to fix it: what you expected, what happened, the steps to repeat it, whether it happens again and in which browser. You keep a copy in your inbox, so you can reply to us with a screenshot attached. Anything marked as blocking — meaning work has stopped — is looked at the same day; the rest is ordered by what it costs. In every case we tell you whether we managed to reproduce it, because a bug we cannot repeat is not a bug we have fixed.