Fichaloto

Blog

What we have learned building this

Working-time records, project profitability, capacity and permissions. Written by the people building the product, decisions and mistakes included.

Time records and clocking in

See what Fichaloto does with this

Compliance

What failing to keep a Spanish time record really costs

The number everybody repeats is wrong, and the one actually in force is smaller than it sounds. The expensive part of having no time record is not the fine: it is what happens afterwards to the burden of proof.

8 min read

Data protection

GPS and fingerprint clock-in: where the line sits

The two questions sound alike and have very different answers. Location can be used under conditions that are reasonable. Fingerprints are special category data, and the bar is far higher.

8 min read

Time records

The spreadsheet time record: when it works and when it stops

Start with the part nobody says: a spreadsheet is legal. No rule imposes a format. The problem is not legality. It is that a spreadsheet proves very little on the day you need to prove something.

6 min read

Time and attendance

Clocking in where nobody carries a company phone

In an office people clock in from their computer and there is no debate. In a warehouse, on a site or in a shop there are thirty people, no company phones and one door they all come through inside ten minutes. There the options are three.

8 min read

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

Remote work

See what Fichaloto does with this

Overtime, holiday and shifts

See what Fichaloto does with this

Projects, capacity and margin

See what Fichaloto does with this

Working with clients

The client asks how their project is going. What do you show them?

There are three possible answers and two of them are bad: the Friday email written by hand, which stops going out around March, and a full account login, which shows things it should not. The third is a narrow window they can look through whenever they want.

7 min read

Billing

The July milestone that nobody invoiced until November

Nothing is lost: it is billed late, which is a different thing and almost always worse than it looks. The arithmetic fits in a paragraph, and the reason it always happens in August fits in a sentence.

6 min read

Capacity

Before accepting a project: how to check whether the team can deliver

You need three numbers: the hours the project will need each month, the free hours your team has in those months, and a buffer. Almost nobody has the second one.

5 min read

Projects

Accounting for hours on a funded project, without reconstructing them at the end

The timesheet built in March to account for last year almost always adds up. That is exactly the problem: it adds up too neatly.

9 min read

Capacity

The resourcing meeting costs more than you think

Nobody budgets for this meeting. It is the most expensive one you run and the one that produces the fewest decisions per minute spent.

9 min read

Operations

What a fragmented stack really costs you

Add up the licences and it does not look like much. The cost sits somewhere else, and it never appears on an invoice.

9 min read

Capacity

Being allocated at a hundred per cent is not billing at a hundred per cent

Most arguments about utilization are really arguments about what is being measured, and nobody has said so out loud.

7 min read

Profitability

Fixed fee or time and materials: who carries the risk

This is not a commercial preference. It is a decision about who pays if the work turns out to be bigger than anyone thought.

7 min read

Profitability

A margin built from hours alone is incomplete

People cost is the one everybody measures. The other cost shows up after you have already closed the engagement.

7 min read

Capacity

Planned, clocked, charged: three numbers that should match and usually do not

Most companies can tell you what they planned and what they invoiced. Very few can tell you, for a given week, whether those two things are related.

7 min read

Profitability

Three reasons your project margin is better on screen than in the bank

If a project shows a healthy margin and the year still ends tight, the margin is not lying to you on purpose. It is missing three specific things.

7 min read

People: hiring, training and pay

See what Fichaloto does with this

Clients, support and pipeline

See what Fichaloto does with this

Permissions, data and integrations

See what Fichaloto does with this

Migration

Changing tools without losing the history

The fear is not the new software: it is the Saturday spent keying in eighty people by hand and the Monday spent finding out that twelve are missing. Order fixes it, and the order is nearly always the same.

8 min read

Security

The access list nobody maintains and everybody needs

The uncomfortable question is not what they had access to. It is how they could still get back in, and almost nobody can answer that with confidence.

8 min read

Security

Access that never expires is access still live three years later

Nobody decides to grant access forever. They just do not set a date, which is the same thing under another name.

7 min read

Security

Five fields, written at the moment you grant it

Recording access takes thirty seconds when you grant it and an afternoon when you try to remember it.

6 min read

Security

Technical access is almost always all or nothing

You want them to fix this and only this. What you end up handing over is the key to everything, and both sides know it.

7 min read

Security

«Why can Ana see that?» is a question your HR software should answer

Anybody who has administered SuccessFactors knows the screen. Everybody else has spent an afternoon clicking through roles trying to work out where a permission came from.

6 min read

Integration

What to ask an HR API before you write a line of code

Every vendor says they have an API. The interesting questions are what it covers, what it refuses to do, and whether it obeys the same rules as the screens.

6 min read

Choosing a tool

See what Fichaloto does with this