Skip to content

Your Projects and Plans

Project Basics

The core fields and relationships of a Project record in GreenVee.

A Project is the central unit of work in GreenVee. Everything — schedules, budgets, tasks, risks, documents — ultimately belongs to a project.

Field What it means
Title The project’s display name
Project Type A master-data classification (e.g. “PV Installation”, “Grid Upgrade”) — set by your administrator
Customer The company in the customer role for this project
Planned start / end The originally scheduled dates
Actual start / end Dates recorded as work begins and finishes
Address The physical site location
Budget goal The target budget amount
Currency The currency for all financial figures on this project
Tags Free-form labels for filtering and grouping

Every project has a Project Phase field that shows where it is in its lifecycle. Phases follow a fixed sequence:

Initial → Definition → Planning → Execution → Closing → Successfully Closed

A project can also exit to Cancelled at any point.

For a full explanation of what happens at each phase, see Project Lifecycle.

Relationship Required? Details
Portfolio Yes Every project must belong to exactly one portfolio
Program No Optionally groups the project with related projects under a strategic banner

See Portfolios & Programs for more on how these containers work.

A project can be connected to two other important records in GreenVee:

Technical Structure (plant) — a 1-to-1 link to the physical asset being built or maintained. When this link exists, project data and asset data stay in sync. One project, one plant.

Order — a 1-to-1 link to the sales-side record that authorized this project. When the link exists, you can trace project costs and progress back to the commercial agreement that started it.

Both links are optional. Many projects operate without them, especially in early phases before an asset has been formally commissioned or before a sales order is raised.