Reports vs. Insights

GreenVee has two ways to communicate status and performance: Reports and Insights. They look similar on the surface — both tell you how things are going — but they work in completely different ways and serve different purposes.

The rule is simple:

Reports are written. Insights are computed.

Side-by-side comparison

	Reports	Insights
What they are	Authored documents written by a person	Live dashboards and charts computed from your data
Primary example	State Report	Charts, trend lines, portfolio scorecards
Stored as a record?	Yes — each report is saved with a date and author	No — Insights reflect current data; they are not stored
Who creates them	A person — project manager, portfolio lead, or program manager	GreenVee — automatically, from the underlying data
When they change	Only when someone edits or creates a new report	Continuously, as underlying data changes
Judgment involved?	Yes — the author decides what to highlight, what the RAG scores mean	No — the system applies consistent rules
Good for	Periodic status communication, governance records, audit trails	Spotting trends, live monitoring, portfolio overviews
Can you look back in time?	Yes — old reports remain as historical records	Limited — Insights reflect current state

Why the distinction matters

A State Report written on a specific date is a statement of what the team understood and communicated at that time. It is part of the project’s record. If a project later goes wrong, those reports are evidence of how it was governed.

An Insight such as a budget burn chart is always up to date. It shows the current picture. It does not have an author — it is computed. You cannot “write” an Insight or attach commentary to it the way you can with a State Report.

Both are valuable. They answer different questions:

• “What is the current schedule status across all projects?” → Insight (live portfolio view)
• “What did the team communicate to the steering committee in March?” → Report (State Report from March)

Common confusion to avoid

Caution

Do not use Insights as a substitute for State Reports in governance settings. An insight chart in a meeting is useful context. A State Report is the formal record. Governance reviewers and auditors expect authored reports — not screenshots of dashboards.

For Project Managers

Write your State Reports even when Insights look fine. Insights show the numbers; State Reports show your interpretation of the numbers. Stakeholders need both.

For Executives

Use Insights for your day-to-day portfolio monitoring. Use State Reports when you need a formal record of what was communicated, when, and by whom.