Project platforms are honest about one project at a time. Ask them about all your jobs at once and the answer is an export button. So every month, in firms that own very good software, somebody builds the same portfolio spreadsheet by hand, and every month it is out of date before it is finished.
Because the project is the product. Cross-project reporting is a different discipline: it needs your definitions of stage, health, and margin, not the vendor's, and it needs data from systems the platform does not own, starting with accounting. The vendors are not hiding the feature. The feature is genuinely yours to define.
Everything that already knows something: the PM platform for status and open items, accounting for cost and billing, the schedule for dates, the spreadsheet the estimator still keeps because it works. The roll-up does not replace any of them; it reads them on a schedule and assembles the one screen the Monday meeting actually needs: every job, its stage, its owner, its stall points, its numbers, current as of this morning rather than as of the last export.
Once the roll-up exists, the client-facing report is a filtered view of it: their project, their format, generated on their schedule. The PM stops rebuilding a deck the night before, and the owner stops learning about problems from the invoice.
Then the definitions are done and the hard thinking is paid for. What is left is removing the human from the assembly, which is the part Excel cannot do.
Whatever holds the truth. The roll-up is platform-agnostic by design; each source contributes what it knows and keeps its job.
As current as the sources allow: typically same-day, on a schedule you pick. The honest constraint is the source systems' own rhythm, and the roll-up shows its own timestamp so nobody guesses.
Bring your Monday meeting spreadsheet. Thirty minutes, straight answer.
Book the audit