How Nebulas Projects makes the project portfolio readable for decision-makers

01

A readable portfolio for deciding

The project register in Nebulas Projects brings together open, closed and to-be-monitored engagements in a single cloud workspace, showing health, status, client, progress and delivery for each one. Managers and teams see priorities and deadlines in the same operational context. Search, filters and sorting help quickly surface engagements that need a decision, making the portfolio readable at every moment of the work.

02

From the register to the single planned activity

Steps

1. Open the project register to see at a glance open, closed and to-be-monitored engagements, with up-to-date health and status.
2. Filter by client, progress or delivery to quickly isolate work that requires a manager's decision.
3. Plan the engagement in the WBS, assigning responsibility, priority, dates, milestones and budgeted hours to each phase and sub-phase.
4. Follow activities on the board, which projects WBS phases into the columns of the shared company workflow.
5. Log hours in timesheets by date, project and WBS activity, checking totals in the daily, weekly and monthly views.

03

What you need to read the portfolio correctly

Prerequisites

• An up-to-date project register, with health, status, client, progress and delivery filled in for every active or closed engagement.
• A Work Breakdown Structure with phases, sub-phases, responsibilities, priorities, dates, milestones and budgeted hours clearly defined.
• A shared company workflow that the board can project into columns consistent with the real status of activities.
• Timesheets organized by date, project and WBS activity, with daily, weekly and monthly views available to the team.

04

A hypothetical case of reading the portfolio

Hypothetical example: needing to decide whether to reallocate resources between two clients, a portfolio manager filters the project register by client and progress. They identify an engagement whose progress has been stalled for a while; opening the WBS, they notice a phase has no updated delivery date. On the board, the related card still sits in the 'in progress' column with no recent movement. Checking the timesheets, they see hours logged on the activity are clearly below the budget planned in the WBS: a useful signal for deciding whether to act on priority or assigned resources.

05

Periodic checks on the portfolio

• Periodically verify that every engagement in the register has health, status, client and delivery filled in and up to date.
• Check that every phase and sub-phase of the WBS has an owner, priority, dates and budgeted hours assigned.
• Compare board columns with the real status of WBS activities to identify mismatches.
• Review daily, weekly and monthly timesheet totals against the hours budgeted in the WBS.

06

How Nebulas Projects keeps the context together

Nebulas Projects brings together portfolio, WBS plan, timeline, activities and logged hours in a single cloud workspace, so managers and teams see priorities, progress and deadlines in the same operational context.

The engagement keeps the context of client, people, assignments, types, statuses, tags and platform settings, respecting authorized access: a shared context that lets the project register, WBS, board and timesheets stay linked to the same engagement as the portfolio grows.

07

Operational sequence for navigating the portfolio

Steps

1. Set up the project register with health, status, client, progress and delivery filled in for every ongoing engagement.
2. Build the WBS with phases, sub-phases, responsibilities, priorities, dates, milestones and budgeted hours assigned to each activity.
3. Connect the board to the company workflow, so every WBS activity finds its own visible column and status.
4. Ask the team to log hours by date, project and WBS activity consistently and promptly.
5. Use the structure, Gantt and combined views to compare planning, progress and actuals across the engagement.

08

The next step

The useful next step is to review the project register with the team on a weekly basis, using search, filters and sorting to surface engagements that need an immediate decision. Comparing the WBS with timesheets logged by date, project and activity makes it possible to verify that recorded work truly reflects the budgeted hours plan defined during planning. This periodic comparison keeps the portfolio readable over time, avoiding surprises close to delivery deadlines.