Portfolio and programs: every schedule, inter-project links and joint calculation
See every project schedule in the company with status, finish, float and health, open up to ten projects read-only in one grid and Gantt, link activities across projects, calculate a program as one joint network without changing any project, propose an external constraint as a scenario, and review shared resources.
On this page
Owners and builders with several jobs need two things the single-project Planner can’t give them: one list of every schedule, and a way to see how a late handoff on one project moves another. The company-level Portfolio schedules page (Schedule › All schedules, or /companies/{company_id}/schedules) does both. It reads what each project has already saved and calculated. Nothing on these pages changes a project’s schedule.
Portfolio schedules
The page lists every active project where you have Schedule access and the tool is on.
- KPIs: calculated schedules, behind baseline, negative float, critical activities, stale data dates and the latest finish.
- Filters: name, number or city; region; stage; project manager; status; and program.
- Summary Gantt: each project’s milestones (up to 12) against a Today line.
- Projects table: project, region and stage, status, version, data date, finish, critical count, negative-float count, DCMA grade and last update.
Each project’s status is On track, Behind baseline, Negative float, Not calculated, No schedule or Schedule admin required. A data date older than 45 days is flagged as stale, but its figures still show.
The figures come from each project’s latest stored calculation of its current saved version. Baseline variance uses the most recent named baseline, in calendar days. Health is the latest DCMA check. Nothing is recalculated when you open the page.
Inter-project links
Open Program links & calculation to link an activity in one project to an activity in another.
- Type: FS (the default), SS, FF or SF.
- Lag: whole days from −3,650 to 3,650.
- Reason: phase handoff, shared resource, utility shutdown, site access or other, plus a note of up to 1,000 characters.
The two activities must be in different projects (links within one project belong in its own schedule), and each must exist in its project’s current saved version. Afterwards you can change the type, lag, reason and note, but not the endpoints. A link whose activity has since disappeared shows as stale. You need Schedule admin on both projects to create, edit, remove or even see a link. Adding or removing a link never changes either project’s schedule, and each change is audited in both projects.
Program calculation
A program calculation runs the current saved versions of the linked projects as one joint network, and shows what each project’s finish would be once the links are honoured.
- Choose the scope. Use all projects connected by links (the default), a portfolio program, or an explicit list of up to 25 projects. You need Schedule admin on every one.
- Optionally test a slip. Set slip-impact days (1 to 365, default 10) to see what each link’s predecessor slipping would do, or slip specific activities in one project.
- Calculate. The run is kept as a record, labelled Run #N · programme finish date. Large programs are queued automatically as a background job, with progress and cancel; the page picks the job up again if you reload. You can read the job only while you’re Schedule admin on every project it covers.
- Read it. For each project you see its finish alone, its finish in the program, the change, the critical count, and what drives it. Cross-project driving paths show where one project drives another. Each link shows whether it delays the successor and by how much, and the implied constraint (start on or after, or finish on or after).
The calculation is read-only: no schedule, version or constraint is written. Each project keeps its own data date and deadline, and float is measured to each project’s own finish. Up to 2,000 links are included.
Each project keeps its own options
Each project is calculated with its own options wherever the joint network allows it:
- Calendars resolve per project. A missing calendar falls back to that project’s own first calendar, as it would alone.
- Total float method and open-ended activities critical are applied per project.
- Network-wide options are compared only where they could change a project’s dates. Progress mode, data-date conventions and start-to-start lag from actual start matter only for projects with actuals; expected finish and external relationships only where those dates exist; the lag calendar is compared link by link.
If network-wide options still differ, the run is kept with the status option conflict, the exact options and projects that differ, and no dates. Align the program to one project’s options to calculate anyway, taking every network-wide option from that project; the result lists each override. Lags on links between projects use the joint lag calendar.
Propose an external constraint
To act on a result, choose Propose external constraint on a link. It creates an open what-if scenario in the successor project, named External constraint: activity start/finish on or after date, citing the run. Nothing is adopted. The project’s scheduler reviews the scenario in Scenarios and adopts it or not, like any other. A proposal is refused if the run found a loop through the links, or if the successor’s schedule changed since the run.
Open several projects at once
Open projects (from Portfolio schedules, or /companies/{company_id}/schedules/open) shows the current saved schedules of up to 10 projects in one read-only Planner grid and Gantt.
- Tick the projects. You can open a project where you’re Schedule admin. Projects where you only have view access are listed as (view only) and can’t be ticked.
- Open selected projects. Each project becomes a top-level WBS node, with its own WBS beneath it, and every activity ID carries the project’s key. Grouped by WBS, the rows group by project, then WBS.
- Work with the view. Filters, Group & Sort, columns and layouts apply across all of them. Layouts from chooses which project’s layouts to open and save.
- Edit in one project. Select an activity and Open planner to change it in its own project’s Planner.
Dates come from each project’s stored calculation. Nothing is recalculated, and the combined view never saves. Each project keeps its own data date. Inter-project links between two open projects are drawn as relationships, in the Gantt and the relationship columns; links to a project that isn’t open are listed, not drawn. To see what the links do to the dates, run a program calculation.
Up to 30,000 activities are combined. Beyond that, later activities are left out and the page says so.
Shared resources
Shared resources looks across up to 25 projects (choose a program to narrow it) at evidence each project has already saved: resource histograms, resource identity mappings and workforce capacity reviews.
- People across projects shows each person’s projects, over-capacity days, peak demand and first over-allocated day.
- Shared identities lists resources mapped to the same person, crew or equipment in two or more projects.
- Possible shared resources lists same-named resources that aren’t mapped. These are unverified candidates.
- Evidence coverage shows which projects have each kind of evidence.
Nothing is reserved or written. Peak combined units is an upper bound, not a same-day total. Reports you can’t read under the Workforce, Equipment or Materials permissions show as not visible.
Cross-project leveling
Level shared resources (on Shared resources) levels the people, crews and equipment that two or more of your projects share, as one network.
- Choose the scope: the projects connected by shared identities, a program, or a list. A resource counts as shared when retained resource mappings in two or more projects you administer name the same person, crew or equipment.
- Choose the horizon. Within float never moves a project’s finish. Extend finish where needed may.
- Level shared resources. Each project’s demand is joined over the linked network and leveled for the shared resources only. A shared resource’s capacity is the lowest any project states for it. Large runs go to a background job.
- Read it. Each pool shows its members, capacity used and peaks before and after. Each move shows the activity, its current and proposed start, and what it waits for.
- Propose as scenario turns one project’s moves into an open what-if scenario of start on or after edits in that project, citing the run. The project’s scheduler adopts it or not in Scenarios. It’s refused if that project’s schedule changed since the run.
Leveling is advisory: no schedule is written until someone adopts a scenario.
Limits
- Open projects is read-only. You can see up to 10 projects in one grid, but edit only in each project’s own Planner, one project at a time. It has no REST endpoint yet.
- Program results are proposals. Applying an external constraint is always a reviewed scenario in the affected project.
- A program run is readable only while you’re still Schedule admin on all of its projects.
- Programs refuse a mix of day-precision and minute-precision projects.
- Background leveling jobs re-check Schedule admin when they run, but not an API token’s Workforce, Equipment or Materials scopes.
Mistake: Modelling a cross-project handoff as a hard constraint in each schedule
In the app: Add an inter-project link and run the program. Propose the constraint only when the result justifies it.
Mistake: Reading “Not calculated” as on track
In the app: Not calculated means there’s no stored calculation of the current version. Open the project and save and calculate.
Mistake: Treating possible shared resources as confirmed
In the app: Map them to suite identities in each project first. Same name isn’t proof of the same crew.
Related
Keep exploring
Related across os.construction
- DocsP6 compatibility: settings, import, export and what round-tripsHow closely os.construction matches Primavera P6. Which scheduling settings the engine honours, which P6 calculated fields it works out, what crosses an XER or P6 XML file in both directions, the measured agreement with P6's own dates and costs, and the limits that remain.
- DocsScheduling: CPM planning, analysis and evidence in one workspaceA native critical path scheduling workspace with a P6-validated engine, P6-style layouts and views, Line of Balance and takt planning, Last Planner weekly work plans, activity discussion and a change feed, P6 import options, DCMA health, three-point risk, a reviewed update cycle, portfolio programs, reports, baselines, versions, resources, costs and period performance.
- GlossaryGroup & SortA schedule view setting that bands activities by WBS, activity code or any field, up to several levels, with totals per band and a sort order within each band.
- GlossaryProgram (Schedule)A group of related projects whose schedules are linked and managed together, so a delay on one project can be traced into the others.
- Free toolConstruction schedule (Gantt) templateFree construction schedule template for Excel.
- BlogHow to build a three-week look-ahead schedule the field will actually useThe master schedule says what has to happen. The three-week look-ahead says who does it, where, and what has to be cleared first. Here is how to pull it from the master, break it down to crew level, screen every activity for constraints, get commitments from the trades, and roll it forward each week, with a worked example.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →