Time Tracking That Feeds Billing and Cost

01Logging

• A timer on the task

  Start a timer against the task you are working on, pause it, resume it, and save it as a time entry.

• The timer follows you

  In the cloud it keeps counting as you move around the product and across browser tabs, and it is still there when you come back.

• Manual entry

  Log the hours after the fact with a note, a start time, an end time and break time.

• Billable or not

  Mark an entry chargeable or internal, and change it for many entries at once.

• Create the task as you log

  If the work has no task yet, create one from the time entry dialog rather than leaving the screen.

• Entries stay on the task

  Every entry belongs to a real task in a real project, so nothing has to be matched up afterwards.

02Rules

• Estimated hours cap

  Logging past a task's estimated hours is refused unless the person has the permission to exceed it.

• Closed tasks are protected

  Logging time on a closed task needs its own permission, so old work does not quietly change.

• Separate permissions

  Manual entry, editing an entry, deleting an entry, seeing everyone's time and importing time are each their own permission.

• Submitted weeks lock

  Once a week is submitted and pending or approved, its entries can no longer be edited or deleted.

03Views

• The time log list

  Date, person, project, task, hours, note, start, end, break, billable, and whether it came from the timer, filtered by project, dates and people.

• Daily timesheet

  One day at a time with a week strip, and weekends and holidays already marked.

• Weekly timesheet

  A whole week across every project in one grid, with a cell for each task and day.

• Month calendar

  A calendar of logged hours per day, where clicking a day opens the entry form.

• Hours chart

  Hours by day for a month, broken down by person and by task, split billable and non billable.

04Approval

• Submit a week

  Pick an approver, add a comment, and send the week for review.

• Hours check on submit

  Orangescrum compares what you logged against the hours expected for the week and tells you if you are short or over.

• Approve or reject with a reason

  A rejection needs a note, and the note goes back to the person who submitted the week.

• Email both ways

  The approver is emailed when a week arrives, and the submitter is emailed with the decision.

• Manage approvers

  Nominate who can approve, activate or deactivate them, and see how many timesheets are waiting on each.

• Audit trail

  Every approval decision is written to a log, so the history of a week is recoverable.

05Downstream

• Cost from hours

  Billable hours become cost to company and cost to client using the rates you set per person or per project.

• Invoicing

  Billable hours that have not been invoiced yet are listed ready to pick from, and become a client invoice.

• Utilisation

  Logged hours drive utilisation and resource reporting without anyone re entering them.

• Timesheet report

  Estimated, billable, non billable, approved, rejected and pending hours, by project or by person.

06Import

• Bring in existing time

  Import time logs from a CSV, with a preview that shows which rows are valid before anything is written.

07Export

• CSV, PDF and Excel

  Export the log as CSV or PDF with the columns and date format you choose, and the timesheet report as a spreadsheet.

08API

• Log time from elsewhere

  Self-hosted exposes time logs through its key authenticated public API for reading and writing.