Living with timesheets
Grid mechanics, expected hours, Team timesheets, and the editing window that governs corrections
The quickstart covers setting a project up and logging your first hours. This is what using timesheets week after week actually looks like.
The week grid
Time tracking → My week seeds a row for every work item on a project you're a member of,
at 0h, before you've logged anything, so what you're expected to work on is visible even
before you log a single hour. A cell is a plain text field, not a number spinner, so
decimal hours (7.5) work and it saves the moment you tab away or hit Enter; clearing a
cell to 0 deletes that entry. Copy last week re-logs every entry from the prior week
onto the matching day this week, skipping any cell that already has hours.
Expected hours
Each day's expected hours come from your own work schedule, not a flat 8 — the schedule's 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. 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.
My month
Time tracking → My month is a calendar: each cell shows logged vs. expected hours and a progress bar, tinted for holidays and leave. Click a day to open its entries, each with its own Edit and Delete — easier than the grid once a day has several entries.
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; CSV exports one row per person (name, title, logged/expected/leave/delta hours) for that week.
The editing window
An admin caps how far back entries are editable at Time tracking → Settings →
"Editing window (days)" — empty means no limit, 0 locks everything before today. Past
that cutoff, both the grid and My month render the cell read-only ("Locked — outside the
workspace editing window"); the API rejects the same write if attempted directly. The
cutoff is per-viewer, carried on the timesheet itself, so the grid always reflects the
live setting.
Admins are never locked out — they can always correct anyone's entry, any date. That bypass is audited every time, including an admin correcting their own past entry, so a correction outside the window always leaves a trace.
Fixing mistakes
Edit a cell on the grid, or open My month, click the day, and use that entry's Edit or Delete — both follow the same editing-window rule as logging new hours.
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 opens My month, clicks that Tuesday, deletes the wrong entry, and adds 8h to the right work item. Had it been 9 days back, the cell would render locked and she'd need Marta, an admin, to make the fix — which lands in the audit log as a backdated correction.