Fichaloto

Holiday and absence

Holiday and absence, without the shared calendar and the WhatsApp thread

People request their days and see what is left. Approvers answer from a queue, not from an inbox. And what is approved comes off capacity in planning, so whoever is handing out September's work stops counting on someone who will not be there.

The problem is not the holiday: it is that it lives somewhere else

Most small companies handle holiday with two tools that do not talk: a shared calendar where days get coloured in and a message thread where they get asked for. It works until someone plans a September project around a person with two weeks of September already approved.

The question underneath is never «how many days does Marta have left?». It is «who can I count on next week?», and a calendar does not answer that: crossing approved absences with what is planned does.

The absence types are yours, not ours

Absence types are a catalogue each company maintains — holiday, personal days, medical, training, moving house, whatever your collective agreement uses — and each carries its own rules:

  • Whether it draws down an allowance — holiday does; an hour at the doctor usually does not.
  • Whether it needs approval — and from whom: by team, or across the whole account. Who approves what.
  • Whether it counts as a working day — so a training day does not show up as a day nobody clocked.
  • Which allowance — days or hours, with a balance per person and year and whatever carry-over the agreement allows.

Approving is a queue, not an inbox

Approvers open the screen and see what is theirs to answer, with the requester's balance and their team's overlaps in front of them. They approve or reject — and if they reject they have to say why, because the person will read it — and at that moment two things happen: the person sees it on their screen and the days stop counting as available capacity in the planning views.

Who answers what is configurable: it can be each team's lead, someone in admin for the whole account, or both depending on the case. And the absence circuit is independent of the hours one and the clocking one, because it is not always the same person.

And it is seen alongside everything else

Approved holiday shows in the team calendar, in each month's capacity and in the cover gaps, which is where it is actually used: if in the second week of August nobody left knows how to do a particular thing, that is visible now and not when it arrives. Capacity and cover gaps.

And it exports like everything else, in case your payroll bureau wants it in a file each month.

Frequently asked questions

Can we configure our own absence types?

Yes. They are a catalogue each company maintains, with their own rules: whether they draw down an allowance, whether they need approval, whether they count as a working day and whether they are measured in days or hours. There is no fixed list of ours.

Who approves holiday requests?

The company decides, from Roles and permissions. It can be each team's lead, someone in admin for the whole account, or a combination. Anyone who is not that person's approver cannot resolve their request, even if it reaches management directly.

Does approved holiday come off planning capacity?

Yes, as soon as it is approved. Those days stop counting as available in the month's capacity and show up in the team calendar and in the cover gaps.

Does it handle sick leave too?

The absence and its period are recorded, so capacity and the calendar tell the truth. Fichaloto does not store medical certificates or any health data: that is employment paperwork and belongs wherever the rest of your personnel files live.

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

Keep reading