Project structure

In RevasOS a project is a collector: it groups the team's tasks under a single container to give visibility into work performed and produce aggregated financial reports.

The project → milestone → task hierarchy

A project can contain:

Direct tasks — tasks assigned to the project without any milestone.
Milestones — macro objectives that segment work into phases.
Milestone tasks — tasks assigned to a specific milestone within the project.

Creating milestones is not mandatory: a project can have only direct tasks, only milestones with their tasks, or a mix of both.

Project
├── Direct task A
├── Direct task B
├── Milestone 1
│   ├── Task C
│   └── Task D
└── Milestone 2
    └── Task E

Milestones

Milestones represent intermediate goals within a project. They group tasks into logical blocks (for example: "Analysis phase", "Development", "Release") and let you monitor progress at a higher level than the individual task.

Tasks

Every task is a self-contained entity. A task exists independently of any project and can also be created from the Tasks module with no project link at all.

When a task is associated with a project it becomes part of that project's hierarchy. The same principle applies when a task is also associated with a specific milestone.

Note:

A task lives on its own. The project is the way tasks are grouped, not the other way round. This means that deleting a project does not delete the tasks — it simply unlinks them.

Project tasks vs standalone tasks

RevasOS offers two contexts for activities:

	Project task	Standalone task
Managed in	Projects module	Tasks module
Linked to a project	Yes	No
Contributes to the project report	Yes	No
Can have a milestone	Yes	No
Works without a project	No — requires at least one project	Yes

How structure impacts the financial report

A project's financial report is built bottom-up: data from each individual task (logged hours, costs, revenue) is aggregated at milestone level and then at project level.

Hours logged on a task's timesheet feed the Actual Time pillar of the report.
Budget lines linked to milestones or tasks determine the Planned pillar.
Invoices reconciled against budget lines populate the Actual Costs and Actual Revenue pillars.

If a task is not linked to any project, its hours do not flow into any project report.

Related concepts

Project structure ​

The project → milestone → task hierarchy ​

Milestones ​

Tasks ​