Microsoft Project Online retires September 30, 2026, migrate to a modern platform before it's too late.Start migration
Status computed, not collected

Every project in one view, with a status nobody had to type

Onplana rolls your projects into portfolios whose health is derived from the dates and the blocked work rather than reported by whoever updated the sheet last, so the red one turns red the week it slips instead of the month somebody notices.

What changes about the monthly review

Building the deck

  • Email twenty project managers for a status by Thursday.
  • Chase the six who did not reply on Friday morning.
  • Paste each project's dates and spend into the master sheet.
  • Recolour the RAG cells by hand, from the same numbers.
  • Find out in the meeting that the red one went red three weeks ago.
  • Do it again next month, from the top.

Reading it instead

  • The status is already there, computed from the project.
  • It changes the week the project slips, not the week you ask.
  • Budget and cost performance roll up with it.
  • Click a red project and you are in it, not in a note about it.
  • The people who will not log in get a share link instead.

How it works

In tier order, because this spans the whole range and pretending otherwise would be the dishonest way to show it. Each step says what it is on.

Step 1

Free

Answer the cross-project question first

One report across every project, with the columns and grouping you choose, and a share link for the people who will not log in. This is the part most teams actually need, and it is the reason the first step here costs nothing rather than being the trial of something else.

Step 2

Business

Group them into portfolios that roll up

A portfolio is a set of projects with an owner, and it rolls up health, budget and cost performance. The health colour is computed, not collected: you stop chasing twenty people for a status on Thursday because the status is already there, and it changes when the project does rather than when somebody remembers.

Step 3

Enterprise

Decide what gets funded, with the trail intact

A twelve-stage intake pipeline with multi-reviewer gates, weighted scoring and a Change Control Board, plus what-if analysis that adds or removes a project and shows you the budget and timeline impact before anyone commits to it. This is the tier where portfolio management stops being reporting and starts being a decision.

Test it on your own projects, free

Cross-project reporting is on the Free plan, so the question this category exists to answer is one you can put to your own data without paying anything. Import a couple of plans, build the report, and see whether the view tells you something the deck did not.

We are not quoting an analyst figure about how much time PMOs lose to status collection. The number that decides this is how long your own last monthly review took to assemble, and you already know it. When the portfolio rollup is what you need, see what Business costs.

What it costs, and what it does not do

Cross-project reporting is on Free. Capacity across the portfolio and the dashboard builder are Professional. Portfolios with the health rollup, plus goals and key results, are Business. What-if analysis and the intake pipeline are Enterprise. It replaces the master spreadsheet and the monthly deck assembled out of twenty status emails.

The honest limit

The health colour is derived and there is nothing to override it. Red means the end date has passed or more than a fifth of the tasks are blocked; amber means under a tenth of the schedule is left. You cannot type a considered amber onto a project the rules still call green, and you cannot tune the thresholds. That is the point for a PMO whose reporting has quietly gone green before, and it is a genuine mismatch for one whose portfolio manager is expected to apply judgement to the colour. If that is you, this will annoy you every month, and it is better that you find out here.

Questions a portfolio review asks first

Where does the red, amber and green actually come from?

It is computed from the project, not typed in by whoever updated the sheet last. A project goes red when its end date has passed, or when more than one in five of its tasks is blocked. It goes amber when less than a tenth of its schedule is left. Otherwise it is green, and a completed or cancelled project stays green rather than going red for having ended.

Can I override the status when I know better than the rules?

No, and you should know that before you buy rather than after. There is no field to type a status into: health is derived every time it is read. If your reporting depends on a portfolio manager setting a considered amber that the dates do not yet justify, this will frustrate you. If your reporting has ever gone green because nobody updated it, that is exactly what this removes.

What do I get before the portfolio tier?

More than you would expect, and that is deliberate. Cross-project reporting is on the Free plan with no upgrade: configurable columns, grouping, charts and a public share link. Per-person capacity across every project and the drag-and-drop dashboard builder are on Professional. Portfolios with the health rollup are Business, and goals and key results linked to the projects that move them come in at the same tier.

Can I model cutting a project before I cut it?

Yes, on Enterprise. Scenario planning adds or removes projects from the portfolio and compares the budget and timeline impact against today. It is the question every portfolio review asks and it is the tier it sits on, so price that one rather than the one below it if what-if is the reason you are looking.

Does it handle intake and prioritisation, or only projects already running?

Both, at Enterprise. Proposals move through a twelve-stage pipeline with designated reviewers per gate, quorum rules, weighted evaluation criteria and a Change Control Board, and an approved proposal becomes a project with the governance trail still attached to it.

Can I bring what I have across?

Microsoft Project files and Project Online come across, with tasks, dependencies, resources and costs, and import is on every plan rather than behind an upgrade. Primavera P6 XER is read. There is no importer for Planview, Clarity or ServiceNow, so coming off one of those means exporting to a format we read rather than a direct migration.

If the question is the PMO function rather than the software category, Onplana for PMOs is written for the role. If it is capacity across the portfolio, capacity across every job goes into that half in detail.

Build the cross-project view before you buy the portfolio one

Reporting across every project is on the Free plan. Bring two plans across, build the report, and decide from what you see rather than from this page.

Start free