Timesheet mechanics

Ask AI

The week grid, expected hours, the day view, Team timesheets, and the editing window that governs corrections

The quickstart covers creating a project and logging your first hours. This page is the week-to-week reference.

The week grid

Time tracking → My time shows work items with logged time in the selected week. Selecting an item in Add work item adds a temporary row; nothing is saved until you enter a duration.

Type directly into a day cell. Durations accept 2, 1.5, 15m, 1h 30m, or 01:30. Enter or Tab commits the value; Escape cancels the edit. Clearing a saved cell or entering 0 deletes its time and note, with a short Undo offer. A day is capped at 24 hours, and future dates cannot be logged.

Project headings are read-only totals. Copy last week copies work-item rows only; it never copies hours. Show weekend remembers your preference. When weekend time exists, the weekend stays visible and an explanation replaces the checkbox.

Adding a work item

Add work item opens on Recent across your projects (your 12 latest work items from the last 90 days, plus Suggested ones), with your projects beside it: the ones you are on or logged to in the last 30 days. On a phone they are chips, with All N pinned at the end. Pick a project for its Recent here, Activities and, with a tracker, Your open issues; All projects reaches the rest, and a project's + on the grid opens the picker on that project.

Typing filters both lists; from 3 characters it searches the picked project, or all your projects, never the whole workspace. A tracker issue several of your projects could take asks which one. With no match, the picker offers Create activity (if you may), Log to General time and Create project (if you may).

Expected hours

Each day's expected hours come from your own work schedule - its per-weekday hours if it has them (Friday can be 6h while the rest of the week is 8h), or an even split of weekly hours otherwise. With no stored schedule the timesheet falls back to 40h over five days. A day outside your working days, a holiday, or a day before your start date all show 0 expected; approved leave subtracts from the day's expected hours too. See Work schedules for setting those per-day hours.

The summary shows logged time, remaining time (or time over expected), and leave. Small charts show daily logging, progress and leave as a share of scheduled time. Leave is already deducted from expected hours; do not add it to logged time. Time over expected is a comparison with your schedule, not a payroll overtime decision.

My month

Time tracking → My time → Month is a completion calendar: each day shows its logged hours, coloured Complete, Partial, Missing, Future or Non-working. Leave hours appear on the day. Clicking today or a past date opens My day; future dates remain visible but cannot be opened for logging. Workspaces with monthly approvals see the month's submission status and available submission action here too.

The Month / Week / Day switch keeps your selected date. Previous/next navigation updates the URL, so refresh and shared links retain the period. The three views share the My time heading and summary. Log time in Month opens the selected day.

My day

Time tracking → My time → Day holds a single date: each entry has an edit and a delete action, its hours and notes are editable in place, and the header carries Add work item plus previous/next-day arrows. A Month / Week / Day switch moves between the three personal timesheets.

Team timesheets

Managers get Time tracking → Team timesheets - a week grid across "your people": yourself, direct reports, and anyone on a team you manage. Admins see the whole workspace. The team picker defaults to "All my people" but can narrow to one team. Remind incomplete nudges everyone listed on the page whose week is short - an in-app notification, once per person per week.

The editing window

An admin caps how far back entries are editable at Settings → Time tracking → Editing window → "Backdate limit" - empty means no limit, 0 means today only. Past that cutoff the week grid disables the cell, My day renders read-only, and the API refuses the same write with a 403 backdate_locked. The cutoff rides on the timesheet response, per viewer.

Admins bypass the backdate limit, but future dates and closed, submitted or approved periods still prevent edits. A submitted timesheet must be withdrawn or an approved one reopened before correction. Every write past the cutoff is audited, including an admin's own backdated correction.

Worked example

Northlake's editing window is 7 days. On Monday, Aleksandra notices last Tuesday's entry - 8 hours logged on the wrong work item - is 6 days back, still inside the window. She clicks that Tuesday in My month, which opens My day, edits the entry, and switches it to the right work item. Had it been 9 days back, My day would render read-only and she'd need Marta, an admin, to make the fix - which lands in the audit log as a backdated correction.