What is new
What shipped in Fichaloto, and what each part is for
Grouped by the problem it solves rather than by the date it was built. Each block links to the page that covers it properly.
So nobody has to learn the app
Fichaloto now has an on-screen assistant. It is a small window at the bottom left, behind the question-mark button, that you ask in your own words: “how do I add someone”, “I forgot to clock in”, “where do I export this”. It answers with numbered steps, a warning about whatever usually goes wrong, and a button that takes you to the right screen. How it was built.
Three things make it different from a support chat: it answers on the spot, because what it knows is written down screen by screen and it invents nothing; it knows what the person asking can do, so it will not walk you through steps that end on a “no permission” screen; and it queries no table of the account — no people, no hours, no invoices — nor keeps what it is asked.
The company hands it out with a permission of its own under Roles and permissions, and whoever has it can switch it off from “Where do I start?” once they find their way around.
So you can pull any figure without asking for it
The report builder goes from ten data sets to twenty-four. The ones that were missing: clock-ins, invoices, payments received, the sales pipeline, the agenda, meetings, settlements, shared access, generated documents, the activity log and all of hiring — vacancies, candidates, applications and candidate skills. Each with its own columns, filters and totals.
And the button that said “Export to Excel” actually downloaded a CSV. Now there is a real spreadsheet, with amounts, hours and dates written as numbers and dates — which Excel sorts and adds up — rather than as text. It is in the reports and also in the vacancy list, the candidate funnel and the talent pool, always respecting whatever filters are set on screen.
Working with people outside the company, without opening the house
Two factory roles for people who are not on your payroll. The client sees only the projects you tick for them and touches nothing: not your team, not your costs, not the rest of your client list. The invited contractor does work — logs their hours, moves their own tasks, clocks in — but only on the projects they were invited to.
And whoever runs a project invites from the project, without going through people administration. The email goes out in the recipient's language, the link lives for seven days, and opening it drops that person straight into the work they were called in for. How that access works.
Two things underneath make it trustworthy. A contractor's scope lives in their own project list rather than in the role, so inviting the hundred-and-first contractor shows them nothing about the hundred before them. And every email the product sends is logged — who it went to, the subject and whether it left — so «it never arrived» gets answered by looking rather than guessing.
So the payment you agreed does not slip past its date
The billing calendar now lives on the project, written the day you sign it: a monthly retainer, a single payment, or a table of milestones with their dates and percentages. From then on, «what do we invoice this month?» is answered by looking at one screen instead of opening four contracts.
Tick a box and any due date that arrives uninvoiced shows up on the dashboard, linking to the invoice already drafted against it. It reminds; it does not issue. An invoice carries sequential numbering and tax consequences, so a person still presses the button. The billing plan.
And three things that were already here and now have a page
Not new in the product: capabilities that have been working for a while with nowhere to read about them.
- The clock-in kiosk — a tablet on the wall, a PIN per person and a screen that never shows who clocked in. How it works.
- Import and export — sixty-five entities in CSV, with a row-by-row dry run before anything is written and an all-or-nothing load. Your data.
- Scheduled email reports — twenty-four tiles, and each recipient gets what their own permissions allow. The reports.
For proving working time: the record can no longer be rewritten
The working-time record stopped being a table that gets edited and became marks that are only appended: every clock-in, break, return, clock-out, amendment and annulment is a new row the database refuses to modify or delete, chained with a per-person SHA-256 fingerprint.
Amending a time does not rewrite the original: it adds a mark saying which one it replaces, and both stay, signed. Annulling a day does not delete it: it stops counting and the record still shows it existed. And there is a check the chain button that you press, not us.
What was already there was converted without losing a minute: the intervals already stored became marks and the totals reconcile to the minute against the original, which is kept intact.
- Database triggers against UPDATE and DELETE.
- Fingerprint chain with a per-account secret that appears in no export.
- Verification the customer can run, with two distinct results: altered and missing.
- Read-only download and API for the raw register, fingerprints included.
For getting hours onto the project by themselves
When clocking in, anybody on several projects picks which one those hours go to, and cannot clock in without answering; anybody on one has it preset. On clocking out, those exact minutes land on the project with nobody typing them in, as one time entry per day rather than one per interval.
And for the classic forgotten clock-out: after sixteen hours the day expires. It stops counting, it stops blocking today — it used to leave you unable to clock in at all — and the clock-out button no longer closes it, because stamping the moment somebody remembered as their leaving time is the number that must never reach a project. It is fixed by asking for a correction.
Hours are also entered in hours and minutes — 7.5 · 7:30 · 7h30 · 450m — and not only in quarters, which stopped making sense the day the clock began posting exact minutes.
For knowing what a project really costs
Each person has their own cost per hour, and a specific project can override it when they cost something else there — the contractor brought in for one job, the partner on a reduced internal rate for a strategic account. It sits next to each name, with their own rate as the placeholder.
And a project does not only cost hours: expenses — subcontractors, licences, travel, materials — are entered on the project itself and cut the margin exactly like hours do. Negative amounts are allowed for a credit, which leaves the trail instead of deleting the line.
The five boxes on the project — logged, revenue, cost, margin and usage — open: each shows the whole arithmetic with that project's figures, what goes in, how it combines and which screen changes each input. A margin you cannot take apart is a margin people argue with instead of acting on.
For handing out permissions without fighting them
Every account is born with five built-in roles: administrator, manager, member — which every new person gets automatically — and two for the API. They can be adjusted, and also reset to how they came without changing who holds them.
And there is a report that answers the question people actually ask: «why can this person see that?». Because roles stack, looking at them one at a time never tells you. The report resolves the sum person by person, using the same code the application uses to decide on every screen, and downloads as Excel with three sheets: the matrix of people against permissions, the line-by-line detail, and what each role grants.
For integrating without opening the door wide
The API no longer opens with a key alone. It takes both: the revocable key and its owner holding a role with «API · Use». Without that permission the key authenticates and stays outside, and not even being an administrator skips it: the API is another door, a program walks through it rather than a person, and opening it has to be a decision somebody took.
Both built-in API roles carry it, so setting up a read-only integration is adding a person, giving them the role and generating the key.
And there is a new entity, clocking marks, exposing the raw register with its fingerprints. Read-only, because writing a mark by hand would forge a link.
And everything else, still there
Clocking from a phone or a PIN kiosk, with geolocation and a radius per site. Patterns, shifts and a weekly roster. Absences with approval and balances by collective agreement. Projects with phases, tasks, a Gantt, a board and a calendar. Capacity and utilisation by person, team and project. Tickets with a bell notification and optional email. Invoicing, collections and a sales pipeline. Import and export of all fifty-six entities, and the same list through the API. All of it in Spanish and English, using your company's own words.
Frequently asked questions
Is all this included, or are they separate modules?
Included. Fichaloto does not sell modules: pricing is per person and what exists is there for everybody. What decides who sees what is permissions, not the invoice.
I am already a customer. Do I need to do anything?
No, it is already there. Two things are worth checking: if you use the API, the key now needs its owner to hold an API role — assigned in Roles and permissions; and if you want clocked hours to land on projects by themselves, that is switched on in Your account → Time and attendance.
How do I keep up with what ships?
Here and on the blog, where we write up the design decisions and also what each thing does NOT do. If you need something that is not there, ask: a good part of this list came from customers asking.
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.