Overview
Timesheets capture how time was actually spent on the project. Team members log hours against tasks or phases; the system rolls them up by role and by phase, compares them to the plan from Resources, and computes costs using the role rates.
It is intentionally simple. There is no granular per-minute tracking and no kill-switch when someone goes over budget. The point is visibility, not policing.
When to use it
- Time-and-materials projects where actual hours drive invoicing.
- Internal cost tracking on fixed-fee projects so you know the margin.
- Forecasting — "are we ahead or behind on phase X?".
How it works
1. Log time
Daily or weekly. Pick a task or phase, enter hours, optional note. Mobile-friendly entry — most timesheets get filled in on a phone.
2. Submit for approval
Weekly submission to a project manager who approves or rejects. Rejected entries can be revised.
3. Roll-ups
Approved hours roll into the project view: planned vs actual per role and per phase, with cost columns from the role rates.
4. Export
Excel for the finance team, PDF as backup for invoicing.
Tips
- Daily entry is much more accurate than weekly. Push for daily even if you only approve weekly.
- Use phases, not individual tasks, as the default unit. Task-level granularity sounds great and never lasts.
- Review the planned-vs-actual chart once a week — that is where overruns become visible while there is still time to do something.