Time tracking
Time tracking by project, without the Friday-afternoon guesswork
Hours logged a week late are not data, they are a reconstruction. The point of making it quick to log time is that it gets logged while it is still true.
Two minutes a day, not twenty on Friday
Time gets entered in hours and quarters — 2, 1.5, 0.25 — against a project and, if you want the detail, against a task inside it. A whole stretch goes in at once: pick the range, say how many hours a day, and working days only.
That last part matters more than it sounds. The fastest way to get bad time data is to make logging it slow, because then people do it from memory on Friday, and memory rounds everything to eight hours.
Approvals only where they earn their keep
Not every project needs someone signing off hours, and turning it on everywhere is how approval queues get ignored. It is a per-project switch.
Where it is on, a pending entry is a request, not a fact: it does not count towards consumption, margin or capacity until it is approved. The moment it is, it counts everywhere at once.
Logged hours, clocked hours, and the gap between them
If you also run clocking-in, the two numbers rarely match, and the difference is where the margin quietly goes. Fichaloto shows both side by side and calls the gap what it is: hours that were worked and are not attached to any project, so they cannot be billed and cannot be explained.
Frequently asked questions
Do pending hours count towards project margin?
No. A pending entry is a request, not a fact: it counts for nothing until someone approves it, and then it counts everywhere at the same time.
Can someone delete hours that were already approved?
On a project marked as sensitive, no — they request the removal, and those hours keep counting until someone resolves it. Approving the request actually deletes them; rejecting leaves them as they were.
Can I log against a specific task rather than the whole project?
Yes, and those hours are compared against that task's estimate in the planner, so you can see task by task what is eating the budget.
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.