Portfolio
Compare every project on the same five report families.
Not assignedEvidence detailsChecking
Portfolio content
Data formats
All authorized projects in this account. The project in the workspace header is a navigation context, not a portfolio filter.
Each schedule’s Data Date, finish, and observations from its latest submitted release. Open a card for that project’s own dashboard.
Reading each project’s newest schedule…
Additional account evidence
Dashboard API evidence
Complete dashboard response for this read, including unavailable values and calculation evidence. PDF and Excel include a captured dashboard and its integrity receipt from their own authorized read; later downloads can differ. Legacy freshness fields are compatibility evidence, not submission deadlines.
Waiting for the dashboard response.
An observed concern and a named evidence gap both need attention, but they remain visibly different.
Open the report cell to inspect its review-bound evidence and recovery action.
One project a row and one measurement a column, so a column reads down the account as well as across one project. A check every project misses is one finding about the account; a check no project could answer is a coverage gap, which is why the two are counted apart.
Portfolio API evidence
Complete account-wide Portfolio response for this read: project and review identities, exact matrix values, calculation evidence and limits. Downloads pin this response when its capture receipt is available; changed evidence requires a reload. Included Dashboard and default program contexts keep their own review selection and source receipts, not a join to the main rows. Default program inputs contain no capacity declarations. Stress and interactive capacity scenarios remain separate reads. Complete metric definitions are inspection evidence, not proof that every metric was evaluated.
Waiting for the Portfolio response.
Send captured account context
Account-wide owners and admins can send this complete Portfolio snapshot to a tested webhook, Slack, Teams or Discord destination. This includes other projects, exact values and metric declarations. It is not an anonymized or single-project report. Large captures can require many messages.
No delivery requested.
No automatic retry after a partial or uncertain send. Transport acceptance does not attest remote processing or retention. Configure destinations in Settings → Connections.
Each project's newest release under six kinds of disturbance, the most fragile first: what breaks recovery first, how small a combined hit breaks it, and how much recovery room is left. A counterfactual on each schedule's own logic, not a forecast.
Open the results to stress every project. Projects already stressed answer at once; the rest run in turn.
Stress results by project
Stress inputs, calculations and source evidence
Complete response for this read. Each captured project retains its source receipt, model inputs, tested doses, metric definitions and limits. Downloads use the current authorized cached readings; they do not start a new run and can differ from an earlier view. Large PDF captures include a complete JSON file attachment and its verification receipt. Excel retains the complete typed evidence.
No stress response loaded.
Derived review metadata only. Missing evidence remains WITHHELD, never zero. Attention means an observed concern or a named evidence gap; it is not a project risk score.
Selected project simulation · optional modelled evidence
This is the active project's deliberately selected simulation, not an account-wide forecast or a replacement for observed schedule readings.
Choose an authorized review.
Each assigned activity open on a day counts as one crew of its trade, from each project’s Data Date. Enter the crews you have per trade, one per line as trade, crews (for example ELEC, 3). It is read for this request only and never stored; a trade you leave out shows its peak with no verdict.
| Trade | Projects | Peak crews | Declared | Reads |
|---|
Choose your capital plan (CSV with a header row, or JSON: name, budget, start, duration, trades). Beside each proposal: how finished work of its trades ran against plan on real schedules. Context only: no proposal is scored, ranked, and the ratios are never scaled onto a whole project. Reading creates no proposal register; separately approved exports or share snapshots may retain the captured declaration.
| Proposal | Budget | Start | Duration | Trades against the reference |
|---|
A shown project is in the project list and in the Portfolio. A hidden one is in neither. Hiding deletes nothing: its uploads, reviews and receipts stay, and showing it again brings it back as it was.
Reading the projects in this account…
Only reading order changes. Values, citations, authority, and review provenance stay fixed.
Reactions are observations; they never change the champion by themselves.
Review status and evidence steps
Steps of the decision on this page.
