Most tools force you to pick a tracking philosophy. Real organizations need both.
Freelancers, contractors and trusted seniors want a manual timer. Salaried and in-office staff need an always-on agent. TimeLogger runs both, for different people, at the same time — under one policy engine, producing one set of approved hours.
A narrow, true claim beats a broad, vague one.
No competitor offers a first-class manual timer and a first-class always-on agent in one product, governed by one policy engine, with a screenshot-free mode that's lawful where screenshot tools are banned.
Scrin & Monitask
Manual-only — can't serve continuous-capture environments.
WorkTime
Automatic-only, with no projects, no tasks and no timesheet approvals at all.
TeamLogger
Three modes, but no approval workflow, no non-invasive mode, and no compliance story.
Our claim, narrow and true: one workspace, four tracking modes, every capture governed by policy, and hours you can actually sign off on. The part competitors can't copy without rebuilding.
Eight commitments we design against.
These aren't slogans — each one shows up as a constraint in the product. Together they're why a credibly restrained tool can win a category with a reputation problem.
Two modes, one truth
Manual and Automatic produce identical downstream data. Every report works the same, whichever mode produced the time.
Policy over settings
Nothing is a global toggle. Every capability is a field on a tracking policy, assignable to a workspace, team, member or device.
The employee always has a mirror
Whatever the employer sees about a person, that person sees about themselves — barring one narrow, time-boxed, audited exception.
Collect the least that answers the question
Counts before content. Scores before screenshots. Metadata before media.
Legality is a feature
Region-aware defaults ship on day one. An unlawful configuration is blocked in the UI with a reason, not disclaimed in a contract.
Never lie about what's running
Silent Mode exists only where law and device ownership allow, is off by default, and requires a signed acknowledgement.
Offline is the normal case
The agent must be fully correct with no network for days, then reconcile without losing or duplicating a minute.
We end at approved hours
Every request to compute money, entitlement or presence is answered with an export and an API endpoint.
What we'll never build — stated as a principle, not an omission.
If a prospect requires these, they're not our customer, or they integrate us with a tool that has them. A stated boundary reads as confidence; an unstated gap reads as immaturity.
Attendance
Punch in/out, presence, punctuality and absenteeism pull us into HR system-of-record territory and country-specific labour rules.
Invoicing
A finance workflow with tax, currency and compliance surface far beyond our value.
Payroll
Statutory exposure and per-country rules — a system-of-record obligation we will not carry.
Budgets vs estimates
A project-management concern that belongs to Jira, Asana or ClickUp.
Shift scheduling
Rostering is its own product category.
Leave & holiday management
HRIS territory.
Geofencing
Location enforcement is a distinct legal regime and a different product. No GPS, no IP-based location, ever.
We produce verified hours and evidence. We hand them off. We compute hours — other systems compute money.