These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Time Tracking
- Features
- Timesheets
Timesheets
Roll each person's week into one timesheet, submit it and follow it to approval and lock.
OverviewMy Timesheets×
Time Tracking · Timesheets
New
My Timesheets
Timesheets
| Timesheet number | Week ending | Total hours | Billable hours | Forecast hours | Status | |
|---|---|---|---|---|---|---|
| TMS-11088 | 20 Oct | 40 | 32 | 10 | Draft | |
| TMS-53728 | 17 Oct | 40 | 32 | 8 | Submitted | |
| TMS-88979 | 06 Oct | 40 | 32 | 6 | Approved | |
| TMS-73800 | 22 Oct | 40 | 32 | 16 | Locked | |
| TMS-50836 | 17 Oct | 40 | 32 | 15 | Draft |
6 of 6 records
Draft tms-396Timesheets · TMS-11088
DraftWeek ending20 Oct
Total hours40
Billable hours32
Forecast hours10
What you can do
One sheet per person per week
The timesheet is the weekly unit that gets approved and locked. Every Friday at 16:00 Pacific, the week’s entries roll into one Draft sheet per person and week ending; a person who already has a sheet for that week is never given a second one. The sheet shows total hours, billable and non-billable hours, forecast hours, overtime threshold and hours, and the variance from forecast.
The person reviews the sheet and submits it. It then moves through approval to Approved or Rejected, with the rejected reason shown to the person. Approved sheets record when they were exported to billing and to payroll. A sheet can also be Locked.
How the work is organized
- Automatic weekly rollup. People do not create sheets by hand; the Friday rollup does it.
- Totals on the sheet. Billable, non-billable and overtime hours are visible before submitting.
- Monday reminders. Anyone without a submitted sheet for last week gets a reminder on Monday at 09:00 Pacific, copied to their resource manager.
What to agree during setup
Agree the week ending day and the submission deadline. Decide where forecast hours come from and what variance is acceptable. Agree how rejected sheets are fixed and resubmitted, and who follows up on missing sheets after the Monday reminder.
Check the handoff on an actual case
An engineer logs 42 hours across two client projects and an internal training code during the week. On Friday at 16:00 the rollup creates his Draft sheet: 42 total hours, 36 billable, 6 non-billable, against a forecast of 40. He checks the entries, adds a missing description and submits on Friday evening.
A designer on his team forgets to submit. On Monday at 09:00 she gets a reminder, copied to her resource manager, and submits before lunch. The resource manager sees both sheets on the status board and knows the team’s week is in.
What your team sees
- My Timesheets — The signed-in person’s sheets with week ending, totals, forecast, status and any rejected reason.
- Timesheets by Status — Every sheet grouped by Draft, Submitted, Approved, Rejected and Locked.
- Timesheets Awaiting Approval — Submitted sheets with totals, forecast and variance.
The Timesheets page in the app gives a filtered browser of sheets with the status distribution, saved scopes and the selected sheet’s detail.
Follow the work through
- Time entry to payroll export: See where the sheet sits in the flow.
- Timesheet approval routing: What happens after submission.
Rehearse access with a resource account before go-live.
What it keeps track of
Data model- Timesheets
- Weekly aggregate per Resource per Week Ending. The approval-and-lock unit.
- Time entries
- The atomic time grain: one row per Resource per Date per Project, Task and Project Code.
- Resources
- Local mirror of the resource master carrying Time Policy assignment, default approval rules and manager hierarchy.
Who uses it
Permissions- Resource
- , Resource Manager, Controller.
- Resource
- S submit their sheets.
- Resource Manager
- S follow up on late or rejected sheets.
- The Controller watches the status board before period close.
Set up Time Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.