1. Time Tracking
  2. Process
  3. Timer and mobile capture
Process · Timer and mobile capture

Timer and mobile capture

Turn timer events and offline mobile entries into time entries without losing or doubling hours.

Step by step

  1. Start a timer Resource

    Resource starts a timer against a project code from the web, mobile or the API.

    • Timer running
    • Updates Timers, Timer events
  2. Pause and resume Resource

    Each pause and resume is recorded as an event, and accumulated time is kept on the timer.

    • Time accumulated
    • Updates Timer events, Timers
  3. Stop and finalize Resource

    Stopping the timer finalizes one time entry with the elapsed time rounded to the policy increment.

    • One entry created
    • Updates Timers, Time entries
  4. Capture offline Resource

    On a phone without a signal, Resource records the entry into the sync queue as Pending.

    • Entry Pending
    • Updates Mobile sync queue
  5. Sync on reconnect Resource

    When the phone reconnects, the queued entry becomes a time entry and is marked Synced, or Failed with a reason the person can fix.

    • Entry Synced or Failed
    • Updates Mobile sync queue, Time entries

Where it usually breaks

And how to keep it from happening.

  • A timer is left running overnight.
  • A mobile entry is captured on a code that was retired before it synced.
  • The same mobile entry is retried and appears twice.
Resource
, Resource Manager, Admin.

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