Module guide
Time tracking
A timer that runs while you work, and an honest record of where the fortnight went.
Overview
Time tracking is a running timer and the record it produces. Start it when you begin, stop it when you finish, and the entry lands under the day it belongs to. Below the timer is the last fourteen days grouped by calendar day with a total against each, and the week rolled up at the top. Everything is stored in universal time on the server and shown in your own time zone, and the duration is derived by the server rather than counted by the browser, so a tab left open overnight or a laptop that slept does not invent hours you did not work.
Highlights
The capabilities worth knowing before you dive in.
- A live timer with the elapsed time recomputed from when it started, so a backgrounded tab shows the truth on return
- The last fourteen days grouped by day, with a per-day total and the week rolled up above
- Entries you can edit, add by hand, or remove, for the session you forgot to start
- Export, for taking the record somewhere else
- Durations shown in your own time zone, from universal time held on the server
Important to know
Limits, permissions, and sharp edges to keep in mind.
- The server derives the duration from the start and stop times. The browser never decides how long something took, which is what makes a sleeping laptop harmless.
- One timer runs at a time. Starting a second one is a decision about the first, not a way to track two things at once.
- The list covers the last fourteen days. Older entries exist and are included in exports, but this screen is deliberately a recent window.
- Times are displayed in your time zone. A colleague in another one sees the same entry at their own local time, which is correct and can look surprising.
How to use it
The primary workflow, start to finish.
- Start the timer when you begin. The elapsed time runs from the moment it started.
- Stop it when you finish. The entry lands under today with the duration the server derived.
- Add an entry by hand for the session you forgot to start, and edit one that ran too long.
- Read the fortnight below, and the weekly roll-up above it, to see where the time actually went.
- Export when the record needs to go somewhere else.
FAQ
- I left the timer running overnight. Is the record wrong?
- It records what the clock says, which is the honest answer to what happened. Edit the entry to the time you actually worked; that is what editing is for.
- Does a sleeping laptop lose time?
- No. The duration comes from the start and stop times on the server, not from a counter in the browser, so a sleeping or backgrounded tab shows the correct total when it wakes.
- Can I run two timers at once?
- No. One runs at a time, deliberately, because two simultaneous timers produce a record that cannot be reconciled with a day that has only so many hours in it.
- Where are my older entries?
- They are kept. This screen shows the last fourteen days because that is the window people act on, and an export covers the full range.
Automate this module