How it works
How time becomes an approved timesheet.
There is no separate clock-in. Attendance is derived from the timer, so what managers review matches what was captured.
-
1
Sign in and give consent
On the desktop app the employee signs in, picks an organization, registers the device and accepts the monitoring policy.
-
2
Press Start
The server reserves the user's single active-session slot, opens a work session and records a clock-in in one transaction. A second timer cannot run elsewhere.
-
3
Capture runs in the background
A heartbeat every 2 minutes, activity buckets every minute, idle periods and screenshots. Each item enters a durable local queue first and carries a unique id so retries never double-count.
-
4
Press Stop
The session closes, a clock-out is recorded and the day's attendance rollup is recomputed. Breaks are derived from gaps between sessions, never typed in.
-
5
Attribute time to tasks
In the web portal, time segments are tied to projects and tasks while a desktop session is open.
-
6
Submit, review, lock
Weekly timesheets are submitted and approved or rejected with a reason. Approved periods are locked; later corrections go through reasoned adjustments instead of edits.
Time zones done right
Captured time follows each user's time zone. Planned dates follow the organization's. Every bucket remembers the zone it was computed under.
The server clock wins
Client timestamps are stored for reference only. Canonical times use the server, and implausible client clocks are rejected.
Safe when offline
Uploads drain with exponential backoff. Idempotency keys make at-least-once delivery safe.