Risk, Decisions, Governance
Decisions
How to log and track formal decisions in GreenVee at the project, program, and portfolio level.
A Decision is a formal open question that needs to be resolved. It might be a choice between two vendors, an approval to proceed with a scope change, a governance sign-off, or any other question where the outcome needs to be recorded.
Decisions in GreenVee are not meeting notes or informal to-dos. They are structured records that remain visible until they are resolved.
Fields
Section titled “Fields”| Field | What it means |
|---|---|
| Title | A clear, short statement of the decision to be made |
| Context | Background information — why is this decision needed? What are the options? |
| Due Date | When the decision needs to be made by |
| Assignee | The person responsible for the decision (optional). You can filter decisions by Assignee in Insights, though it is not currently set from the decision creation or edit dialog |
Where Decisions live
Section titled “Where Decisions live”A Decision belongs to one of three levels:
- Project — a decision that affects a single project (most common)
- Program — a decision that affects multiple related projects
- Portfolio — a strategic decision that affects the portfolio as a whole
This flexibility means you can escalate a decision from project to program level if it turns out to affect more than one project.
Decisions and State Reports
Section titled “Decisions and State Reports”A State Report has a free-text Decisions field. When you author a State Report, you can note open decisions there in your own words, making them visible to stakeholders who read the report. This is a text summary, not a link to the Decision record — it’s one of the main ways open decisions get noticed and resolved even so.
See State Reports for how this works.
Decisions vs. actions
Section titled “Decisions vs. actions”A Decision is a question that needs an answer. A Risk Action or Opportunity Action is a task that needs to be done. These are different things. If something needs a judgment call before it can be executed, log a Decision first. The action follows once the decision is made.