Before you report
Portfolio Status Rollup
Combine status reports from different templates into one portfolio summary, and see where the files mean different things by the same words before anyone reads it.
Read any number of status files as .xlsx or .csv, in whatever template each project uses, inside your browser. Nothing is uploaded.
Status files
Add each project’s status file, in whatever template it uses: a row per project, or a two-column sheet of field and value.
A project's status file
Drop a spreadsheet here
Excel or CSV. Add as many as you have.
Every template, read in its own terms
Projects report in their own templates. One has a row per project; another is a two-column sheet of field and value, read down the page. One writes dates day first, another month first. One says Yellow, another Amber, another scores health from 1 to 5. The tool reads each file its own way and puts every project on one scale, so the rollup compares like with like.
Where the files disagree
The dangerous differences are the ones that look the same. A column called Forecast holds a finish date in one template and a cost in another. A date like 03/04 is March in one file and April in the next. Progress is 0.6 here and 60% there. One project appears in two files with two different statuses. The tool lists every one of these before the summary, so each can be settled rather than averaged away.
Scores and colors
When a template scores health as a number, the tool asks which way the scale runs and where green ends, and shows the mapping it used. Nothing about a score says whether 1 is best or worst, and guessing the wrong way round turns a healthy project red.
What this does not do
It does not produce a portfolio score or average colors across projects: the summary is the projects side by side, with counts. It cannot add money across files in different currencies. And it reports what the files say; to check whether a status is supported by its own numbers, use the Status Report Evidence Checker.