A list of entries is good for one record at a time. It is a poor way to answer “how is my week?” or “is Tuesday missing on this project?”. People logging time in RabbitWork used to jump from one entry to the next — or go back to the spreadsheet just to see the picture.
The weekly and daily timesheet exists for that picture: log and review the period in the same place, without assembling the week from memory.
The problem with only having the list
The list asks “what was the last entry?”. Close asks something else: “is this week complete?”.
On the list, a hole on Tuesday disappears among twenty lines. A total of 6 hours in a day looks normal until you remember the agreement was 8. Duplicating a similar entry meant filling everything in again.
The manager suffered the other side: to find the person’s gap, they opened entry after entry. Friday’s conversation became “send me a screenshot of your tab.”
Two views, the same period
They are not two tools. They are two ways of looking at the same slice.
Week — a grid: projects in the rows, days in the columns, totals on the edge. It is the map. It serves the Friday ritual (or the cutoff day): “is this week complete?”. This is where the person submits the week for approval, when the account uses that flow.
Day — each entry on that date, with the total at the top. It serves when the manager asks “what was that Tuesday?” or when you need to fix one entry without touching the rest of the week.
Switching from Week to Day does not lose the date. The path is Time tracking > Timesheet. The steps are in weekly and daily timesheet.
For a single entry on a project, the timer or the form still works. The timesheet does not replace play: it organizes what was already logged (or will be) in the period.
Timesheet in the Week view
Who uses each view day to day
The person logging time uses Week for the ritual: fill the grid, see what stayed empty, submit. They use Day when the work changed shape in the middle of Tuesday — a meeting in the morning, execution in the afternoon — and the total in the cell does not tell the story.
The manager looks at the person’s week to find a hole before approving. On the day, they check whether a strange total is one entry or several stacked together.
The admin points the team to Time tracking > Timesheet as the default close path, instead of everyone living only on the project tab. The entry list still exists. It stops being the only map of the week.
What changes in Friday’s use
Before: open the list, add it up in your head, find the hole, go back to the project, log, go back to the list.
After: the grid shows the hole. You log in the cell. You duplicate what repeats. The day’s total, in Day mode, updates immediately — without a refresh.
Long project names no longer blow up the grid. An empty list says the next click, instead of a generic blank.
Whoever approves looks at the person’s week in the same format they used to log it. Less “explain that Tuesday” without context.
What this opens
The timesheet becomes the close ritual, not a separate report. Log, review, submit — in the same menu.
Together with the Time tracking hub (June 2026) and approval (August), the person’s path stays short: fill the grid, send the week, see the status. The feature history is in the Changelog.
If your Friday is still adding up the list, it is worth seeing the grid in RabbitWork at rabbitwork.io.
