01

A portfolio you can read in seconds

Nebulas Projects brings together the portfolio, WBS plan, timeline, activities, and logged hours in one cloud workspace, so managers and teams see priorities, progress, and deadlines in the same context. This reduces time spent hunting for scattered information and makes decisions about where to step in calmer.

02

How the project register organizes the overview

Steps

  1. The project register shows open, closed, and at-risk engagements with health, status, client, progress, and delivery.
  2. Search, filters, and sorting help surface the work that needs a decision.
  3. Each engagement keeps the context of client, people, assignments, types, statuses, and tags.

03

What's needed before reading the portfolio effectively

Prerequisites

  • Engagements created with client, people, and assignments correctly associated.
  • Types, statuses, and tags set consistently in the Nebulas platform.
  • Authorized access configured for the managers and teams involved.

04

A hypothetical case: spotting the engagement that needs attention

Hypothetical example: a manager opens the project register and filters by health and delivery. In a few steps they isolate the engagements whose progress is behind the expected date, without checking each client or project individually.

05

Planning and logged hours as continuity controls

  • The WBS organizes phases, subphases, and activities with responsibility, status, priority, dates, milestones, hour budgets, and progress.
  • Structure, Gantt timeline, and combined views keep hierarchy and planning together.
  • The board projects WBS activities into the company workflow columns, with cards, search, filters, and history.
  • Timesheets organize entries by date, project, and WBS activity, with daily, weekly, and monthly views to check logged hours.

06

What a company can configure in Nebulas Projects

A company can structure roles and contextual data so that every engagement keeps client, people, assignments, types, statuses, and tags consistent, while respecting authorized access. This supports traceability useful for those reviewing priorities and progress without losing operational continuity.

07

Suggested operating sequence

Steps

  1. Open the project register and sort by health or delivery to spot priorities.
  2. Use filters to isolate open engagements that need an immediate decision.
  3. Check the engagement's WBS to review phases, responsibilities, and hour budgets.
  4. Check the board to see the operational status of activities in the workflow.
  5. Check timesheets to compare logged hours against planning.

08

Next step

To make the portfolio even more readable, verify that every engagement in Nebulas Projects has client, people, types, and statuses set correctly, so the register, WBS, board, and timesheets stay consistent over time.

FAQ

Frequently asked questions

What does the Nebulas Projects register show?

It shows open, closed, and at-risk engagements with health, status, client, progress, and delivery, with search, filters, and sorting to highlight what needs a decision.

How are logged hours connected to the engagement?

Timesheets organize entries by date, project, and WBS activity, with daily, weekly, and monthly views to check logged hours.

What contextual information does an engagement keep?

An engagement keeps client, people, assignments, types, statuses, and tags, respecting authorized access on the Nebulas platform.

✓

Sources and verification