Project portfolio management, end to end
Nine areas covering delivery, benefits, strategy, governance, stakeholders, capacity, cost and change. All of it reads from the tools your teams already use, and none of it asks them to work differently.
What Portavi does
All included in the product rather than sold as separate modules.
Projects & Agile
Every project read the way it runs: sprints, phases, milestones or work in progress.
All plansPrograms & benefits
Programs measured by the benefits they exist to deliver.
All plansPortfolios & strategy
Portfolios, strategic objectives and strategy reviews that leave a record.
Growth plan and aboveGovernance & RAID
A full RAID log, with decisions, lessons, benefits and change requests beside it.
All plansStakeholder engagement
Who has a stake, how engaged they are, and who does what.
All plansCapacity planning
Everyone’s open work across every connected tool, with overload flagged early.
All plansBudgeting & EVM
Cost baselines, reserves and earned value, with a forecast at completion.
All plansChange management
Change requests with baselines and tolerances, so nothing changes silently.
All plansAI summaries & rewriting
Report summaries, at-risk explanations, a morning digest and rewriting.
Growth plan and aboveProjects & Agile
Portavi reads the way each project actually runs, rather than forcing every team into one shape.
Read-only, from the tools you already use
Projects, tasks, sprints and phases sync from Jira, Asana, Monday.com, Azure DevOps, ClickUp, GitHub Projects, Microsoft Planner and Wrike.
Every delivery method, one health model
A Scrum project is read through its active sprint, a Waterfall project through its current phase, a Kanban board through its work in progress, and any project through its next milestone. However a team works, the project still rolls up to the same on track, at risk or delayed.
Date suggestions
When the work underneath a project or program runs past its dates, Portavi suggests new ones for you to accept.
Programs & benefits
A program is measured by what it changed, not by whether its projects closed.
Benefits measured, not just declared
A benefit carries a baseline and a target, measured on the program’s own cycle. Delivered is tracked apart from realised: finishing the work is not the outcome arriving.
Rolled up, never averaged
Cost and schedule figures roll up across a program from summed values rather than averaged ones, so one large project in trouble cannot be hidden behind several small healthy ones.
Change control reaches program level
A program carries its own baseline finish date and budget, and a change request raised against it follows the same approval path as one raised on a project.
Portfolios & strategy
Group programs and projects into portfolios, set objectives against them, and run strategy reviews that leave a record. Objectives can be written in Portavi or mirrored from the tool your teams already keep them in.
Four goals tools
Atlassian Goals through your Jira connection, Asana Goals, ClickUp Goals and Tability.
Straight into the strategy map
Each key result’s progress feeds the strategy map and your strategy reviews, with a link back to the objective in its own tool.
Governance & RAID
A full RAID log for every project and program, and a dashboard of what needs attention across all of them.
A full RAID log
Risks, assumptions, issues and dependencies for every project and program, with decisions, lessons, benefits and change requests beside them.
What needs attention, first
One list across the RAID log, worst first: overdue issues, slipping dependencies, assumptions due a check and high-exposure risks, plus the projects carrying most of it.
Assumptions with a check date
When a check comes due it lands in its owner’s My Focus, and one that proves invalid can raise a risk or an issue in a step.
What waits on what
One piece of work can wait on another across programs and portfolios. When a link slips, it shows by how many days, in red on the timelines and in My Focus for the owners at both ends.
A decisions log that writes itself
The decisions log fills itself from strategy, sprint, cadence and benefit reviews and from risk events, as a by-product of meetings you already run.
Risks raised where the work is
Every project and program has a RAID tab, so a risk or issue is raised beside the work it threatens.
Stakeholder engagement
Who can affect the work, how engaged they are today against how engaged you need them, and who is accountable for what.
One register, and not only your colleagues
Team members synced from your PM tools, Portavi users, and people with no account at all, such as clients, regulators and suppliers, in one register scored for power and interest on every project.
The power and interest grid
Power and interest scores place everyone in Manage closely, Keep satisfied, Keep informed or Monitor, so the quadrant is derived rather than argued over.
The gap you actually have to close
Each stakeholder carries the engagement you have and the engagement you need, and Portavi shows the gap, which is the part a plan can act on.
A RACI that checks itself
Responsible, Accountable, Consulted and Informed on every scope item. Portavi AI can draft the rows from a project’s epics and phases or a program’s benefits, and a draft stays a suggestion until someone accepts it.
It adds up the level above
A program sees everyone across its projects and flags people its projects score very differently. A portfolio sees its steering committee, its key players, and whether every program and project has been covered.
Capacity planning
Who is carrying too much, across every connected tool at once.
One person, not five accounts
Portavi spots the same person across Jira, Asana and your other tools, so their workload is counted once.
Overload before the dates slip
Open and overdue work counted per person across every project, with a heatmap of where the load sits.
Plan the move before you make it
Model moving work between people and see the projected load before you commit.
Budgeting & EVM
What the delivery cost, against what it was supposed to cost.
A baseline with real reserves
Contingency and management reserve, held the way PMBOK sets them up, so you always know what is left of each.
CPI, SPI and a forecast
Planned value, earned value and actual cost, with cost and schedule performance indices and an estimate at completion.
Check-ins that freeze the numbers
Each check-in keeps the figures you reported, so the trend shows how the forecast moved.
Change management
Change requests on projects and programs: raised by the owner of the thing being changed, decided by approvers, then applied.
Five kinds of change
Scope, schedule, budget, resourcing, and other. Each request is raised by the owner of the project or program it affects.
Approvers decide in parallel
Everyone with a say decides at the same time, and one rejection closes the request. Each workspace sets who that is.
Baselines and tolerances
Every project and program carries a baseline finish date and budget. An edit past the workspace’s tolerance becomes a change request instead of a silent change.
It arrives where you already work
Change requests have their own register, a Changes tab on every project and program, actions in My Focus and a section in status reports, and every decision is logged automatically.
AI summaries & rewriting
Written for the reader, from the numbers already on the page.
Executive summaries, when you ask for them
On the Health snapshot and Executive summary reports: where the portfolio stands, what changed and what needs attention.
Why a project is at risk
A sentence or two under an at-risk project, explaining what is driving the risk.
A morning digest on My Focus
Two sentences at the top of your own page: what needs you today, and what moved on your projects overnight.
Rewrite in any text field
Rephrase, shorten or expand status notes, risk descriptions, retrospectives or any other text field.
See it on your own portfolio.
Every trial runs on Growth for 14 days. No credit card required.
Start free trial