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.
- Timesheet Management
- Features
- Project work
Project work
Connect organizations, projects and work packages to the weeks and tasks they contain.
OverviewBlocked Tasks×
Timesheet Management · Project work
New
Blocked Tasks
Tasks
| Task key | Title | Work package | Assignee | Due date | Status | |
|---|---|---|---|---|---|---|
| TK-684 | Blocked tsk-876 | WP-4994 | 20 Oct | Blocked | ||
| TK-604 | Blocked tsk-167 | WP-7372 | 27 Oct | Blocked | ||
| TK-642 | Blocked tsk-382 | WP-5325 | 05 Oct | Blocked | ||
| TK-579 | Blocked tsk-369 | WP-7883 | 19 Oct | Blocked | ||
| TK-332 | Blocked tsk-877 | WP-4608 | 14 Oct | Blocked |
6 of 6 records
TK-684Tasks · TSK-29141
BlockedTitleBlocked tsk-876
Work packageWP-4994
Due date20 Oct
What you can do
Give hours a project context
Projects sit under organizations and carry a name, schedule, delivery method, budget and owner. A work package groups related work inside a project and carries its own owner, dates, estimate and status. This structure lets a project manager explain where a weekly submission belongs before any hours are accepted. The Operations Overview shows authorized work packages alongside submitted time and review posture. Active Projects offers a focused list of current delivery work.
How the work is organized
- Name the organization. Admin maintains the organization that receives the project work. The project record can then refer to that organization.
- Set the project. Project Manager gives the project an owner, dates and an appropriate status. Planned, Active, on hold, at risk, Completed and Cancelled distinguish work awaiting start from work underway or finished.
- Break down the work. The manager creates work packages under the project, estimates their hours and names an owner. Tasks and weekly submissions refer to these packages.
What to agree during setup
Agree who may open a project, which delivery method applies and who is responsible for changing its status. Define how work packages are named so a team member can select the right parent for a weekly submission. Decide whether estimates are set before assignments or updated as work changes. The project and work package have separate estimates and actual hour measures; compare them consistently rather than mixing a weekly submitted total with every project rollup. The parent relationship matters when a manager explains the approved week to another reviewer.
Check the handoff on an actual case
Create an organization for a client team and a project with a start and end date, owner and Active status. Add a work package for a delivery phase, give it an estimated number of hours and assign its owner. Create a task inside that package, then enter time against the project and task. Prepare a weekly submission under the package. The project manager should be able to walk from the submitted week to the package and from the package to the project and organization. Change the package to Blocked when the work cannot continue. The package list and task context should make that state visible without changing previously approved time. When the project approaches its end date, use its schedule and current status to decide whether to revise the plan.
What your team sees
- Active Projects — Current projects with owners, organizations and schedule dates for project review.
- Project Schedule — Planned and active delivery dates considered with project status.
- Weekly Submissions Awaiting Approval — Weeks attached to a named package and organization, ready for review.
Follow the work through
Follow project setup into daily capture. See the data model for the exact references.
What it keeps track of
Data model- Organizations
- Client and internal business organizations that projects are delivered for.
- Projects
- Engagements delivered for an organization, with budget and schedule.
- Work packages
- Groupings of work inside a project.
- Tasks
- Individual pieces of work assigned to a delivery team member.
- Time submissions
- Weekly time submissions supporting approval of a submitted weekly timesheet.
- Time entries
- Hours booked by a team member against a task and project.
Who uses it
Permissions- Admin
- Maintains organizations.
- Project Manager
- Owns the project and work package structure.
- Team Member
- Uses that structure for tasks and time.
- Delivery Lead
- Reviews project status and exceptions.
Set up Timesheet Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.