Segments, Task Packages, Tasks & Subtasks

Inside every project, GreenVee organizes work into four nested levels. Together they form the work breakdown that turns a project into a trackable schedule.

Project
  └── Segment          (timeline stage, e.g. "Phase 1 — Foundation")
        └── Task Package   (work package grouping related tasks)
              └── Task         (schedulable work unit, assigned to a Project Member)
                    └── Subtask    (checklist item)

How schedule offsets are calculated

Segments, Tasks, Milestones, Gates, and Events don’t store their timing as a simple “day 5” or “day 12” calendar count. Instead, each item stores an offset in working time from the project’s planned start date, and GreenVee resolves that offset into an actual date using the project’s own calendar settings — its Working hours/day and Working days/week (see Project Basics).

This means:

• A task offset by “16 working hours” lands on a different calendar date for a project working 8 hours/day, 5 days/week than for one working 10 hours/day, 6 days/week.
• If you change a project’s working-hours or working-days setting, every offset-based date across the schedule recalculates.
• Segments and Tasks always schedule this way. Milestones, Gates, and Events additionally let you pin an item to an exact calendar date instead of floating on an offset — see Milestones, Gates & Events.

Segment

A Segment represents a major stage or phase of the project on the timeline — for example, “Design”, “Procurement”, or “Commissioning”.

Field	What it means
Name	The stage label
Description	Longer details about the stage
Color	A visual identifier shown on the Gantt chart
Start offset	When this segment begins, calculated automatically as a working-time offset from the project’s planned start date (see above)
Tags	Free-form labels for filtering

Segments let you see at a glance which part of the project you are in and how stages relate to each other on the timeline.

Task Package

A Task Package is a named grouping of tasks within a segment — sometimes called a “work package”. Use it when a segment contains many tasks that logically belong together (e.g. all electrical tasks within a construction phase).

Task Packages have a name and belong to exactly one Segment.

Task

A Task is the core schedulable work unit. It is assigned to a Project Member (someone formally added to the project) and tracked through its lifecycle.

Field	What it means
Name	Short description of the work
Description	Longer details about what needs to be done
State	Current status: Backlog, To Do, In Progress, In Review, Done, Cancelled, or Duplicate
Scheduled start offset	When the task is planned to begin, calculated as a working-time offset from the project’s planned start date (see above)
Duration	Planned length of the task, also measured in working time (not simple calendar days)
Actual start / end	Dates recorded when the task truly starts and finishes
Not before / Not after	Optional constraint dates — the task must not be scheduled outside this window
Constraint reason	Free text explaining why the constraint dates were set
Tags	Free-form labels
Assigned to	A Project Member — not a raw employee, but someone added to this project
Subscribers	User accounts who want to be notified about updates to this task

Not-before/not-after constraints are enforced by the schedule — including by the Scheduling Optimizer, which will not propose a start time for the task outside its constraint window.

Task Comments

Tasks have a threaded comment thread. Team members can post updates, questions, or decisions directly on the task. Comments can be resolved once addressed, keeping the thread clean.

Subtask

A Subtask is a simple checklist item under a Task. Use subtasks to break a task into small, confirmable steps without creating a full child task.

Field	What it means
Name	The checklist item label
Checked	Whether this item has been completed
Order	The position of this item in the list

Subtasks have no dates, no assignments, and no schedule — they are purely a checklist.

Caution

Tasks are NOT the same as Issues. Tasks are scheduled work inside a project’s plan. Issues are operational problems or defects raised during execution. See Issues vs. Tasks for a full comparison.

For Field Workers

Your day-to-day work lives at the Task level. Check your assigned tasks for what needs doing, use subtasks to tick off steps, and leave a comment if something changes on site.