TIME TRACKING
Record the work while you are doing it.
Start your own timer with a description and optional authorized work reference. Stop it to create a time entry that can be reviewed in the weekly workflow.
An end-of-day estimate loses the detail of the work
Switching between customer tasks makes it hard to reconstruct the day accurately later. A timer records a work session as it happens, while a description explains its purpose. Tsumira connects that session to the current person and, where selected and authorized, the relevant work item. Stopping the session produces an entry that continues through review rather than immediately becoming an invoice.
Start with the right work context
The timer can carry a work reference, description, billing description and billable indicator. The available work items are restricted to what the current person may log against. Choose the correct task or project context before starting where possible, and explain the actual work in a useful description. A billable flag means the recorded effort may need commercial review; it is not customer approval of a charge.
- Optional authorized work reference
- Work and billing descriptions
- Billable indicator
Keep one active session understandable
The implementation limits the operator to one active running timer. That gives the running session an unambiguous meaning instead of quietly accumulating several overlapping work clocks. When the person stops it, elapsed time becomes a recorded entry associated with that session. A separate discard action is available for a timer that should not become recorded work. Check the active session when returning from an interruption.
- One active timer per operator
- Stop into a recorded time entry
- Separate discard action
Review the entry before submitting the week
Recorded time has its own date, duration, description and state. Eligible draft or rejected entries can be corrected through the supported time-entry workflow. The person can then inspect the weekly submission preview before sending time to a reviewer. Keeping timer recording, timesheet approval and financial processing separate makes it easier to explain what has been measured, what has been approved and what may later be billed.
- Recorded date and duration
- Corrections within supported entry states
- Weekly review before submission
A concrete workflow
Choose the session
Select accessible work where relevant, add a description and set the billable context deliberately.
Start your timer
Begin the session for the current operator and check that the intended work is shown.
Stop or discard
Stop when the work ends to create an entry, or discard a session that should not be recorded.
Review the result
Inspect the date, duration and description before including the entry in a weekly submission.
An illustrative working example
Illustrative workflow: a focused customer revision
A designer starts a timer for an authorized project task while revising a customer document. They describe the revision and record its billing context. After finishing, they stop the timer and inspect the resulting time entry. Before submitting the week, they check that the description and duration reflect the actual work. A reviewer later decides on the timesheet; the timer itself has not issued an invoice.
Questions about this topic
Can I run several timers at once?
The current implementation keeps one active running timer for the operator. Finish or discard the existing session before starting a different work session.
Do I have to choose a project task?
The timer accepts an optional work reference. Where you select one, it must be an authorized loggable work item for the current person.
Does stopping a timer charge the customer?
No. It creates a time entry. Submission, approval and any connected billing decision are separate parts of the workflow.
What if I started the wrong session?
Review the active timer. Use the supported discard path if it should not become work, or review the resulting entry and its permitted correction options.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Asana
Workflow concept: Select the externally tracked task as context for a reviewed time-capture plan.
Google Calendar
Workflow concept: Compare planned focus time with the actual session before finalizing its description.
Linear
Workflow concept: Clarify the issue reference that should explain the recorded work session.