1. Time Tracking
  2. Features
  3. Time Entry and Timers
Feature · Time Entry and Timers

Time Entry and Timers

Log time against project codes on the web, with a running timer, from a phone or by import.

OverviewMy Time Entries
Time Tracking · Time Entry and Timers

My Time Entries

Time entries

New
Entry numberDateProjectTaskProject codeHours
TE-6787006 OctPRJ-876TSK-270PC-23136
TE-2371906 OctPRJ-404TSK-349PC-84213
TE-4186101 OctPRJ-631TSK-507PC-24175
TE-6543409 OctPRJ-700TSK-206PC-19855
TE-7058909 OctPRJ-236TSK-655PC-59066
6 of 6 records
PRJ-876Time entries · TE-67870
Yes
Date06 Oct
TaskTSK-270
Project codePC-2313
Hours6
Entry methodWeb
Example screen with sample data

What you can do

Capture time the way people actually work

A time entry is one person’s hours on one date against one project, task and project code. It records the hours, a description, whether the time is billable, whether it falls on a flagged weekend, the entry method (Web, Mobile, Timer or Import), whether it is locked, any overtime flag and who last edited it. Every entry belongs to the person’s weekly timesheet.

People enter time in four ways. On the web they type hours into the week. With a timer they start, pause, resume and stop; each action is kept as a timer event, and stopping the timer finalizes one entry with the elapsed time rounded to the policy increment. On a phone, entries captured without a signal wait in a sync queue and become time entries when the phone reconnects. Imports bring in time from other tools.

How the work is organized

  • Project codes on every entry. Each entry carries a project code that sets its category, billable flag and rate.
  • Timers that leave a trail. Starts, pauses, resumes and stops are kept as events with their source (Web, Mobile or API), so the finalized hours can be explained.
  • Mobile entries that sync. Each queued entry shows Pending, Synced, Failed or Discarded, with the failure reason when a sync does not go through.

What to agree during setup

Agree which entry methods each team may use and whether mobile entry is allowed under each time policy. Decide the rounding increment for timers. Load project codes before go-live so nobody logs time to a free-text project. Agree what goes in the description for billable work.

Check the handoff on an actual case

A consultant starts a timer at 09:10 for a client workshop, pauses it for a call at 10:30, resumes at 10:45 and stops at 12:05. The timer keeps four events and finalizes one entry of 2.75 hours against the client’s delivery code, rounded to the 15-minute increment in her policy.

That afternoon she logs 1.5 hours of travel from her phone on the train with no signal. The entry waits in the sync queue as Pending and syncs into a time entry when the train reaches the station. Both entries appear on her week, ready for Friday’s rollup.

What your team sees

  • My Time Entries — The signed-in person’s entries with date, project code, hours, billable flag, entry method and lock state.
  • Running Timers — Timers currently running, with start time, last event and accumulated time.
  • Mobile Sync Alerts — Mobile entries still pending or failed, with device and failure reason.

Follow the work through

Review the implementation plan and the data model before importing historic time.

What it keeps track of

Data model
Time entries
The atomic time grain: one row per Resource per Date per Project, Task and Project Code.
Timers
Running-timer state per Resource, finalized into a Time Entry on Stop.
Timer events
Append-only event log for a Timer: Start, Pause, Resume, Stop.
Mobile sync queue
Pending mobile entries awaiting sync, drained into Time Entries on reconnect.

Who uses it

Permissions
Resource
, Resource Manager, Admin.
Resource
S log their own time.
Resource Manager
S watch running timers and sync failures for their teams.
Admin
Helps with device and sync problems.

Set up Time Tracking your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started