Hours that survive contact with a real working day
Most small companies in Bangladesh do not have a time tracking problem so much as a reconstruction problem. Nobody logs hours as they work. At the end of the week, or worse the end of the month, somebody sits down and rebuilds what everyone probably did from memory, calendar invites, and a WhatsApp thread. The number that comes out of that exercise gets used for payroll, for client invoices, and for deciding whether a project was worth doing, and everyone involved quietly knows it is an estimate.
Utso approaches this from the other end. Time is captured while the work is happening, by the person doing it, in a way that is quick enough that they will actually keep doing it. The timer is one click to start and one to stop. It does not ask for a project, a category, and a description before it will begin counting, because a form standing between an employee and their work is the reason time tracking gets abandoned in the first place.
The timer follows you around the app
The live timer persists across all pages. Start it while looking at a task, then go answer something in CRM, check a leave request, or open a project board, and it is still running, still attached to the same entry. It tracks the current entry globally rather than living inside one screen you have to keep open.
This sounds like a small detail and it is the single most common reason timers get abandoned. A timer that only exists on one page trains people to distrust it: they leave the page, come back, find nothing running, and conclude the tool loses their work. After that happens twice, they stop using it and go back to reconstructing hours at the end of the week, which is the exact problem the software was bought to solve.
You can also create a task inline, at the moment you start timing, rather than stopping to go set one up somewhere else first. The friction of “I need to create the thing before I can track the thing” is where a lot of tracked time quietly disappears.
Tag what the hours were for, and mark what you can bill
An entry is not just a duration. Each one carries up to three tags and a billable flag.
The billable flag is the part that changes what the data is worth. Without it, a timesheet tells you how long people worked. With it, the same timesheet tells you how much of that time you can put on an invoice and how much was internal, which is the difference between a record you file and a record you make decisions from. For an agency, a consultancy, or any Bangladeshi business that bills clients for people’s time, that one field is most of the reason to track hours at all.
Tags handle the rest of the shape of the work. Three per entry is a deliberate limit rather than an open-ended free-text field, because unlimited tagging reliably degrades into fifty near-duplicate labels nobody can report on.
Hours stay on the right day, even across timezones
Each entry’s logged date is computed at the user’s local timezone at the moment of clock-in. If someone starts a session in Dhaka and finishes it after crossing into another timezone, the entry still lands on the day they actually worked, rather than being shifted by whatever timezone the server happens to run in.
For a company whose whole team sits in Bangladesh this never comes up, and that is fine. It matters for the cases that do occur: a founder or salesperson travelling, a developer working with an overseas client on their hours, or a contractor in a different country. These are exactly the situations where hours quietly land on the wrong date, get queried in an invoice, and cost more to argue about than they were worth.
Two views: your hours, and your team’s
My Hours is the individual’s own timesheet. It has date presets so you are not building a range by hand every time, inline edit and delete for fixing entries, and CSV export. An employee can answer “what did I actually do last week” without asking anyone, and correct a genuine mistake without filing a request and waiting.
Team Hours is the manager’s view of the same data. The important thing here is bulk action: approve or reject up to 500 entries at once. Timesheet approval is work that arrives in a batch, at the end of a period, all at the same time. A review screen that requires one click per entry turns a legitimate control into something managers rubber-stamp at speed just to clear the queue, which defeats the point of having approval at all.
Approval writes a four-field review trail, so an approved timesheet carries a record of who reviewed it rather than just flipping to a green state with no history behind it.
Where tracked time actually goes
Time tracking is only worth the effort if the hours end up somewhere that matters, and in Utso they connect to the rest of the platform rather than sitting in their own silo. Entries attach to tasks, which belong to projects, which can be linked to CRM clients, so the path from “someone logged two hours” to “this is what that client’s project cost us” exists without exporting anything.
That connection is also what separates time tracking from attendance, and the two get confused constantly. Attendance management answers whether someone was at work and when, it is the biometric punch, the late arrival, the shift. Time tracking answers what the hours were spent on. A factory needs the first. An agency needs the second. A company that does project work for clients and employs shift staff needs both, and in Utso they are separate modules that share the same employee record instead of two products that never reconcile.
Priced as part of Core HR, not as another add-on
Time tracking is included in Core HR, which every account carries at 50 BDT per active employee per month. It is not a separate line item, and there is no per-seat fee for giving someone a timer.
That is deliberate. Time tracking priced per seat creates an obvious perverse incentive: you give the timer only to the people whose hours you are worried about, and then you have partial data, which is worse than none because it looks complete. Every employee having a timer at no marginal cost is what makes the resulting numbers usable.
Payroll, Recruitment and CRM are the optional add-ons on top of Core HR. Full detail is on the pricing page, including a calculator you can run against your own headcount.
Getting started
Utso is free to start, every new company gets a two-month trial of the full platform with no payment details required. Time tracking is available from day one because it is part of Core HR, so you can run a real week of hours before deciding anything.
If time tracking is the piece you care about most, the practical first step is small: turn the timer on for one team for one week, then look at Team Hours and see how much of it is tagged billable. That number is usually the argument.
For the wider picture of how this sits alongside people, attendance and payroll, see HR software Bangladesh, or project management if the hours you care about are attached to client work.