Fichaloto

Recruitment

Hiring that ends in an actual employee

Fichaloto keeps your vacancies, who has applied to each one and what stage they are at. And it takes the step almost no recruiting tool takes: when someone accepts, they stop being a candidate and become a member of the team, with their role, their project and their allocation, without their details being retyped anywhere.

The problem is not storing CVs

Almost nobody loses a hire for want of somewhere to file CVs. They lose them for something else: nobody is quite sure who is waiting on a call, the person who has sat three weeks in “screening” does not look stuck to anyone, and the good candidate who missed out in March is buried in an inbox by October, when exactly that profile is needed again.

A funnel with stages exists for that: so the stalled one stands out on its own, and so the rejected one is still findable a year later, with the reason they fell out sitting next to them.

From vacancy to payroll, with nothing retyped

This is the difference from a standalone recruiting tool. In a separate tool, hiring means exporting, retyping the name, the ID and the job title into the HR system, and remembering to add them to the project. Three places, and something gets missed in one of them.

In Fichaloto it is one button. “Onboard to the team” asks for four things — role, project, allocation and start date — and creates the person, their role, their project assignment and their allocation window in one go. From that moment they count towards team capacity, they can clock in if you have time tracking, and they log hours against the project they were hired for.

  • Openings with a number and places. Each vacancy with its project, work location, collective agreement and how many people are needed. It closes itself once they are all filled.
  • A funnel you configure. You set the stages. Each one declares what it means — still going, hired or rejected — so you can rename them without the reports ceasing to add up.
  • A rejection reason is compulsory. The difference between “did not fit” and “we could not match what they asked for” is whether it is worth calling them again.
  • A talent pool that does not expire. One record per person, with everything they have ever applied to, even from three years ago.
  • Duplicate warnings. By ID document, by email and by name with date of birth — and against your own headcount too, so you know whether an applicant already works with you. It never merges two records on its own.

Who sees what

A hiring process holds data that is not for everyone: the CV of somebody outside the company, and the salary range on the vacancy. Both sit behind separate permissions, apart from everything else.

A recruiter — in-house or from an agency — can run the whole process without seeing a single salary and without being able to create users with access to the application: onboarding somebody additionally requires people-administration permission. Adding a person is an administrative act, not a recruiting one, and the product treats it that way.

It comes with everything else, and stays out of the way if you do not use it

Recruitment is not bought separately: it comes with the platform. And if nobody in your business hires, it is taken out of your people's role and does not appear: not in the menu, not in the search, not in the catalogues. What is included and what gets built.

And taking it out takes nobody’s job away: anyone who went from candidate to team member stays on the team with their hours, their projects and their role. What is hidden is the record of whoever never made it in, and it comes back intact the day it is contracted again.

Frequently asked questions

Does it post openings to job boards like LinkedIn?

No, and we would rather say so plainly than have you find out by trying. Posting automatically to those boards requires commercial agreements with each of them. What Fichaloto does do is record where every candidate came from, which is what will tell you six months from now which board is worth spending on — and today almost nobody knows that.

Do we need time tracking contracted as well?

No. Recruitment runs on the base, with projects and people and nothing else. If you also have time tracking, whoever joins can clock in from their first day without anyone doing anything.

What about the data of candidates who are not hired?

Each record stores when consent was given and how long it is kept for. The usual practice in Spain for unsuccessful CVs is one year, and it is configurable. This is not legal advice: the period you use is worth confirming with your own adviser.

Can we load in the spreadsheet we already have?

Yes. Openings, candidates and applications go in and out by CSV and by the API, with the same columns. Uploading the same file twice duplicates nobody.

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.

Keep reading