Skip to content

Docs

Time tracking

Hours attach to the work itself, so reports and invoices are the same numbers your team entered rather than a monthly reconciliation.

Where to find it: Time in the mode switcher.

What this section is about

The timesheet is a week grid: a row per project, split into the two things an hour can be — project work, or meetings and comms — and a column per day. You type hours into a cell, and that is the whole interaction for most people most weeks.

An hour can also be pinned to a specific ticket, which is what makes a ticket's cost visible and what lets time reach a client's Jira board. Pinning requires being assigned to that ticket.

Some hours arrive on their own. If Riley is switched on and a meeting was recorded, an entry is written for every internal attendee with the meeting's name on it. A twice-daily sweep also picks up meetings on your calendar that nothing recorded. Both land in a review queue rather than straight on your timesheet, because the duration and the project are a machine's best guess until a person says otherwise.

Important features to use

  1. 01A filled cell opens the day's breakdownTyping works while a cell is empty. Once there is time in it, clicking opens a drawer listing each entry for that day — because a number typed into a filled cell is ambiguous (a correction, or a second entry?). Two meetings with one client in a day is now routine, so the drawer is where you edit each one on its own terms.
  2. 02The stopwatch runs on the serverStart it without knowing where the hour is going; pick the project when you stop. Closing the tab does not lose it, and only one timer runs per person. Cancel is a first-class answer for a clock you started by accident or left running overnight.
  3. 03Clear the In review queue regularlyIt is a list, not a modal per entry, and it is not week-scoped — Thursday's unreviewed hour is still waiting next week. Each row can be edited before you accept it: the hours and the note are both yours to change, and delete is a real answer for a call you are not logging.
  4. 04Fetch the calendar on demandThe toolbar has a sweep button for closing out the day rather than waiting for the scheduled pass. It cannot create anything the scheduled sweep would not, so pressing it twice is harmless — and if nothing was added, it tells you which of the four reasons applies rather than reporting a bare zero.
  5. 05Set your timezoneSettings → User → Timezone. It decides which day an hour lands on and what "today" means across the app. It is detected on your first load, and after that the stored value is the answer — so a laptop taken abroad does not quietly re-file the hours logged there.
  6. 06A meeting hour cannot be pinned to a ticketMeetings are attributable to a project, not to one of its tickets, so the ticket control is withheld on that row. Putting a meeting inside a ticket's total would make that ticket look more expensive than the work in it was.

Common questions

Hours in the review queue — do they count?
Not until accepted. Unreviewed entries are excluded from reports, from the client dashboard, from invoices and from anything pushed to a client's Jira. An agent's guess never reaches a client-facing number.
An unreviewed entry is filed against the wrong client. Can I move it?
Yes — an unreviewed entry can be re-filed to any project you can see, including one under a different client, because its client is itself a guess. Once accepted, an entry moves only within its own client.
Why is a 30-minute meeting logged as 30 minutes and not 45?
The recording is trimmed to the last thing anybody said before being rounded up to the quarter hour. A notetaker leaves a call a little after everyone else, and without the trim every recurring standup would be overstated by 50%.
Riley logged an hour I do not want. What do I do?
Delete it from the review queue. It will not come back — a deleted auto-logged hour is treated as "not mine" permanently, even if a later pass sees the same meeting.
Can I log time for somebody else?
An admin can. A contractor logs their own hours only.
What happens to logged time if a ticket is deleted?
It is kept. Time entries are never destroyed — deleting a project or a ticket hides them, and restoring brings them back.