Project, Programme and Portfolio Governance
Govern every project from one connected hierarchy
DemandFlow® manages portfolios, programmes and projects as a single connected structure, not a stack of disconnected tools. Stage gates, change control, baselines, risks, benefits and earned value all live against the same project record. Governance becomes a by-product of the work, not a separate reporting exercise.
The Challenge
Governance breaks down between the spreadsheet and the steering board
Most PMOs run portfolios in slide decks, track risks in spreadsheets and approve changes over email. The data is scattered, the audit trail is thin, and by the time a report reaches the board it is already out of date. When a project slips, no one can show what the baseline was or who approved the change.
No single source of truth
Portfolio mix sits in one spreadsheet, the risk register in another, and change approvals in an inbox. Reconciling them for a board pack takes days, and the numbers rarely agree across the three.
Baselines that cannot be proven
When a project overruns, the original plan has usually been overwritten. There is no immutable record of the committed budget or end date, so variance arguments come down to whoever remembers the last agreement.
Gates that are gates in name only
Stage gates exist on a process diagram but not in the tooling. Projects pass checkpoints informally, override decisions go unrecorded, and there is no consistent checklist applied across the portfolio.
Hierarchy
A real portfolio, programme and project structure
DemandFlow® models the full governance hierarchy as connected records. A Portfolio holds programmes and projects, a Programme coordinates related projects, and every project links up to its strategic pillar. Roll-ups and drill-downs follow the structure rather than a manually maintained spreadsheet.
Portfolio
The Portfolio record holds the strategic collection of projects and programmes, with a business sponsor, executive sponsor and budget owner. Approved CAPEX is captured per year, alongside a portfolio carbon reduction target and a rolled-up total emissions figure across every project in the portfolio.
Programme
A Programme coordinates related projects that deliver outcomes no single project could achieve alone. Each carries a programme manager, executive sponsor, start and end dates, priority, an overall risk rating and a last review date, with its own list of member projects and programme-level gates.
Project
Every Project links to its portfolio, programme, customer and strategic pillar. It records status, RAG, percent complete, planned dates, project type, complexity tier and funding decision, then exposes more than thirty related panels covering gates, risks, benefits, change and finance.
Stage Gates
Configurable stage gates with a full override trail
Gates in DemandFlow® are enforced records, not diagram boxes. A reusable Gate Template defines the checklist for a lifecycle stage and the roles allowed to approve it. Each gate evaluation is recorded against the project with a result, a score and the approver who signed it off.
Gate templates
A Gate Template defines the criteria that must be satisfied before a project proceeds past a checkpoint, tied to a lifecycle stage of Initiation, Planning, Execution or Closure. Templates name the approver roles and the override approvers, so the same governance standard applies consistently across the portfolio.
Checklist items
Each template is built from individual checklist criteria. A Gate Checklist Item defines exactly what to evaluate and how it is assessed, so a gate is a concrete set of pass conditions rather than a subjective judgement made differently by each reviewer.
Gate results
A gate evaluation records a status of Pending, Passed, Failed or Overridden, a percentage score, and who requested and approved it with dates. When a gate is overridden, an override justification is captured. Programmes carry their own gate evaluations through Programme Gate.
Change Control
Change requests that baseline the project automatically
A Change Request is raised against the project baseline and carries scope, schedule, cost, resource and quality impact. A single approver reviews it. On approval, DemandFlow® captures an immutable snapshot of the project before state, so before and after are always provable.
Change request
Each change records its type (Standard, Normal, Emergency or Major), a nine-state status workflow, a reason code, and which axes it affects across scope, schedule, cost, resources and quality. Quantified impact fields capture schedule delta in days, the new planned end, the cost delta and the new budget at completion.
Automatic baseline snapshot
When a change is approved, a Project Snapshot is captured automatically. It is an immutable baseline recording the version, the reason, the previous and new budget at completion, the previous and new planned end, and the change request that triggered it, giving a defensible before and after for every approved change.
Approve, then implement
Approval and implementation are deliberately separate steps. A change can be approved, scheduled, then implemented later, with the implementation result recorded as Successful, Partial or Failed alongside actual start and end dates, review notes and lessons learned. Governance reflects what actually happened, not just what was agreed.
RAID Management
Risks, issues and dependencies on the project record
Every project carries its own risk register, issue log and dependency map as related records. Risks and issues use consistent probability and impact scales, and dependencies are modelled as directional relationships between projects so portfolio-level contention is visible.
Risk register
Each risk records a category, probability, impact, potential cost, mitigation strategy, triggers and a contingency plan. Status moves through Open, Monitoring, Resolved, Closed or Materialised, with a next review date. Risks can be flagged as human-raised or AI-predicted, so the register shows where each entry came from.
Issue log
Issues track active problems with a category, an impact assessment and a contingency plan. Status follows Open, Monitoring, Resolved or Closed with a next review date, keeping the live issue list distinct from the forward-looking risk register rather than blurring the two together.
Dependencies
Dependencies are directional links between two projects, typed as Finish-to-Start, Start-to-Start, Finish-to-Finish, Delivers Input or Shared Resource. Each carries a criticality of Low to Critical, a lag in days, a status and mitigations, so the PMO can see where one project’s slippage puts another at risk.
Benefits and Performance
Benefits realisation and earned value, measured not estimated
Governance is about outcomes, so DemandFlow® tracks both why a project was funded and how it is performing. Benefits run from baseline to target to actual with calculated variance. Earned value metrics are computed on the project record rather than maintained by hand.
Benefits realisation
Each benefit is defined at approval with a category, a measure type, a baseline value and a target. As delivery progresses, the actual value drives an automatically calculated variance and realisation percentage. Status moves from Expected through Tracking to Partially or Fully Realised, with a review frequency and an optional linked KPI.
Earned value management
The project computes earned value metrics directly: budget at completion, planned value, earned value, actual cost, schedule and cost variance, the schedule and cost performance indexes, estimate at completion and variance at completion. These are read-only calculated fields, so schedule and cost performance are first-class governance data.
Milestones and payments
Project Milestones cover deliverables, approvals, phase gates and payments, each with a RAG status, percent complete and a days-variance figure. Milestones carry acceptance criteria and testing status, optional payment terms and penalties, and an escalation path that runs up to board level when something needs to be raised.
Capacity and Funding
Connect delivery to people and to the approved roadmap
Governance fails when plans ignore capacity and funding. DemandFlow® books people to projects by role and percentage, and ties project delivery to the approved financial roadmap. In DemandFlow®, the roadmap specifically means the budget-committed work, not a generic timeline.
Resource allocation
Resource Allocation books a named person, in a specific role, at a percentage over a date range. Because allocations are explicit records, the PMO can analyse capacity and contention across the portfolio and see where the same people are committed to competing projects at the same time.
The approved roadmap
The Roadmap holds annual budget lines with monthly forecast and actual figures, representing the budget-committed work. Roadmap drawdown records how much budget each project consumes from its portfolio allocation, connecting funding decisions to real spend rather than leaving them stranded in a planning deck.
Prioritisation to funding
Medium-term planning scores candidate projects on initiative, benefit and platform value, then records a decision of Selected, Deferred or Rejected. On approval, the selected projects’ cost lines generate roadmap lines for the next fiscal year, so the prioritisation exercise flows straight into the committed budget.
AI PMO
AI-generated health insight across the portfolio
DemandFlow® includes an optional AI PMO layer that runs scheduled inference over live project data. It produces health assessments, recommendations and executive narratives as records attached to the project and portfolio. These outputs are clearly labelled as AI-generated and are reviewed by people, not acted on automatically.
Project health insight
The daily AI run produces a health assessment for each project: a RAG status, a narrative summary and the top risks it has identified. Alongside it, AI Recommendations surface specific, actionable suggestions that a user can dismiss or act on, with the history retained on the project for trend analysis.
Portfolio narrative
At portfolio level, the AI layer writes an executive narrative of overall health with portfolio-level recommendations. A daily Portfolio Snapshot captures point-in-time project health so RAG trends can be charted over time, giving the board a consistent record rather than a one-off slide.
Milestone readiness
A milestone-briefing run generates a readiness assessment for upcoming milestones, flagging where delivery looks at risk before the date arrives. Completed projects are written to an immutable planned-versus-actual record, which feeds the learning layer so historical benchmarking improves over time.
Make governance a by-product of delivery
When gates, change control, baselines, risks, benefits and earned value all live against the same project record, the board pack writes itself and every approval has a provable audit trail. DemandFlow® gives PMOs one connected hierarchy from portfolio strategy down to the last checklist item, so governance keeps pace with delivery instead of trailing behind it. Book a demo to see your own portfolio modelled in DemandFlow®.
One Platform. Strategy to Stack.
Ready to Take Control?
Join the leading companies who have transformed their technology management with DemandFlow®.
Book a personalised demo today.