Your Projects and Plans
Portfolios & Programs
How GreenVee groups projects at the strategic level using Portfolios and Programs.
Every project must belong to a Portfolio. Projects can also be grouped into a Program within that portfolio. These two containers give executives and portfolio managers a structured view of where company resources are going.
Portfolio
Section titled “Portfolio”A Portfolio is the top-level strategic container in GreenVee. Think of it as a business unit, a funding bucket, or a strategic initiative that spans many projects.
| Field | What it means |
|---|---|
| Name | The portfolio’s label (e.g. “Renewables Europe 2026”) |
| Currency | The currency used for all financial reporting in this portfolio |
| Leader | The employee accountable for the portfolio |
| Color | A visual identifier used in charts and the navigation tree |
A portfolio can contain many Programs, and directly contain Projects that don’t belong to any program.
Program
Section titled “Program”A Program is a coherent group of related projects within a portfolio. Use it when several projects share a strategic purpose, a delivery timeline, or a common client.
| Field | What it means |
|---|---|
| Name | The program label (e.g. “Grid Modernization — Phase 2”) |
| Project Type | The master-data classification describing what kind of work this program covers |
| Planned start / end | The intended schedule envelope for all projects in the program |
| Leader | The employee responsible for the program |
| Portfolio | The portfolio this program belongs to |
A program can contain many Projects. Projects inside a program still belong to the same portfolio.
Why both exist
Section titled “Why both exist”| Level | Scope | Typical question answered |
|---|---|---|
| Portfolio | Strategic — whole business unit or funding stream | “How much are we spending on solar this year?” |
| Program | Operational — a related cluster of projects | “Are all three substations in the Western Grid upgrade on track?” |
A Portfolio is required — every project must belong to one. Programs are optional, but both levels unlock meaningful roll-up reporting.
Relationship summary
Section titled “Relationship summary”Portfolio (1) └── Program (0..*) └── Project (1..*) └── Project (1..*) ← projects with no program also belong hereEvery Project must belong to exactly one Portfolio. A Project may optionally belong to one Program within that Portfolio.
Two views of the same projects
Section titled “Two views of the same projects”GreenVee gives you two navigation doors into your projects:
- Portfolio tree — drill down from Portfolio → Program → Project. Best when you need the strategic context.
- Flat project list — all projects side-by-side, filterable. Best when you know which project you want.
Both views show the same projects. No data differs between them.