A Work Timer You Are Not Required to Use
Start a stopwatch, stop it, and decide afterwards whether it becomes a timesheet line. Runs live on the server, so they survive a reload, a cleared browser and a change of device.
Stintt exists so nobody has to run a timer — the calendar already recorded the week. But some work never touches a calendar: the fix between meetings, the call taken on a walk. For those, there is a stopwatch. It is the exception in this product, not the mechanism: a stopped run is a measurement, and it stays a measurement until you file it, which is what lets you stop the clock, look at the number, and decide not to bill it.
- 1Start itName what you are doing and pick a project if you know it. The run is on the server from that moment, not just in this tab.
- 2Stop itThe run closes with the time it actually measured. Nothing has reached a timesheet yet.
- 3File it or drop itFile the run and it becomes a timesheet line in one transaction. Discard it and the measurement goes away without ever having been billed.
Work timer, in the concrete.
- One running clock per person, enforced by the database — no two-timers-at-once double count
- Runs live server-side: start on a laptop, see it on a phone, survive a cleared browser profile
- A stopped run is a measurement. Filing it is a separate, deliberate step
- File it to a project as a timesheet line, or discard it — nothing is billed by default
- Elapsed time is computed from the start timestamp, so a throttled background tab cannot undercount it
- Runs under a minute are treated as misclicks; a single run cannot exceed 24 hours
- Works offline: runs queue locally and are adopted by the server when you reconnect, replay-safe
- Separate from the attendance clock on purpose — clocking out never stops your work timer
3 steps, start to finish
No timer to start, no form to remember.
Start it
Name what you are doing and pick a project if you know it. The run is on the server from that moment, not just in this tab.
Stop it
The run closes with the time it actually measured. Nothing has reached a timesheet yet.
File it or drop it
File the run and it becomes a timesheet line in one transaction. Discard it and the measurement goes away without ever having been billed.
The things people ask before signing up
The point is that you are not required to run one. The calendar, chat logging and reminders cover the week without a stopwatch; this is here for the work that left no trace anywhere else. Nothing prompts you to start it.
The run is on the server, so it is still running when you come back — on any device. That is the difference from the earlier version of this timer, which lived in one browser and lost a day with a cleared profile.
No. A stopped run sits unfiled until you file it. That gap is intentional: it is the moment where you can look at 40 minutes and decide it was not billable.
A single run cannot carry more than 24 hours, so a forgotten timer cannot turn into a week of billable time.
No. They were one clock once, and it was a bug — clocking out stopped the work session you were naming. Attendance records presence; the work timer measures a task. Neither one starts or stops the other.
