Several projects, one view

A view across several projects is useful once the schedules underneath it are worth reading. Before that, the view repeats the gaps.

Start with an inventory. Which files are live. Which are baselines nobody updates. Which share a database, and which are separate exports. Agree the codes. If you truly share one Primavera database, an enterprise project structure can hold them. If you do not, a disciplined roll-up of the exports is the honest version.

The first pack should show finish dates, progress, and where crews or plant clash. Where hours or cost are actually loaded, a simple labour or cash curve. Where they are not loaded, show nothing. An empty curve is better than a curve invented to fill the page.

A monthly pack can keep that view alive. You keep the structure.

This is not advice on which project to fund, and it is not a set of gates for an investment decision. If that is the question, a planning practice is the wrong place to ask it. We also do not propose this view until there are several live schedules, and until one of them has already been made trustworthy.