01

What you get when hours and projects are linked correctly

Those managing projects get a reliable set of actuals when every logged hour is anchored to a date, project, and WBS activity. Nebulas Projects organizes timesheets around exactly these three references, preventing hours from staying generic or disconnected from the work plan.

02

How the link between hours and activities works

Steps

  1. The timesheet records every entry by date, project, and specific WBS activity.
  2. The daily, weekly, and monthly views show the detail of the entries.
  3. The same totals allow you to check the actuals against the plan.
  4. The linked WBS activity keeps track of the relevant responsibility, status, and hours budget.

03

What you need before logging actual hours

Prerequisites

  • A WBS with phases, sub-phases, and activities already defined with responsibility and hours budget.
  • Activities assigned to people or teams with up-to-date status and priority.
  • Authorized access consistent with the client and project context of the job.

04

A hypothetical case: the project with three phases

Hypothesis: a project organized into three WBS phases, each with its own hours budget. A team logs weekly hours against the activity corresponding to the current phase. The monthly timesheet view shows totals per activity, allowing a comparison between actual hours and the budget assigned in the WBS, phase by phase.

05

What to check to keep data clean

  • Check that every entry has date, project, and WBS activity filled in.
  • Periodically compare the weekly and monthly view totals with the WBS hours budget.
  • Verify that the recorded activities match the current status and priority on the board.
  • Check that timesheet access respects the client-project context of the job.

06

What a company can configure with Nebulas Projects

A company can organize timesheets by date, project, and WBS activity, maintaining the link to the hours budget, status, and responsibility defined in the plan structure. The project preserves the context of client, people, assignments, and platform tags, with authorized access consistent for those consulting or entering hours.

07

Operational sequence for verifiable actuals

Steps

  1. Define the WBS with phases, activities, responsibility, and hours budget before starting the project.
  2. Log hours in the timesheet always indicating date, project, and WBS activity.
  3. Check the weekly view for close monitoring of progress.
  4. Use the monthly view to compare totals with the planned hours budget.
  5. Revise status and priority on the board when actuals show deviations.

08

Next step

Those who want to make hours tracking a stable part of management control can start from the WBS of the next project, assigning clear hours budgets before opening timesheets to the team.

FAQ

Frequently asked questions

Do logged hours stay linked only to the project or also to the specific activity?

They stay linked to both: the timesheet organizes entries by date, project, and WBS activity, so every hour is tied to a precise activity within the project.

How can you check whether actual hours respect the planned budget?

The daily, weekly, and monthly timesheet views show detail and totals, useful for comparing actual hours with the hours budget defined in the WBS.

Who can see the hours logged on a project?

Visibility follows authorized access, since the project keeps the context of client, people, and assignments while respecting the access levels set by the platform.

✓

Sources and verification