What is planned in the next two to four weeks, by work front, against the rate this project has actually been going at.
Project Reports
Choose a project, read its five-report set, then open the saved evidence.
Not assignedEvidence detailsChecking
Project Reports content
No float loss read yet: it appears once a review is analyzed.
Inspect saved schedule uncertainty
DCMA-14, EVM, CPM, Earned Schedule, and Flow Analysis use the latest authorized review for this project.
Choose a project to load its report set.
A WITHHELD report names the evidence it needs. It is not a zero, pass, or healthy reading.
For the release chosen above. Each downloads as a PDF or an Excel workbook.
Which float paths exist, and where float has been consumed since the last update.
Choose a release to read its float movement.
Which crews have to be asked for now, so they are on site when the schedule needs them.
Every metric SPI reads, for this release, in one place: earned value, Earned Schedule, the DCMA checks, flow analysis and motion. A metric it cannot read names the evidence it needs, and each says how it may be combined.
Choose a release to inspect every metric and its processing receipt.
Metrics and calculation lineage
Derived readings, each as Excel or CSV:
SDX carries typed source evidence; SUR carries six analytical views. Parquet packages all nine projected tables in a ZIP for analysis. PDF provides a selective evidence brief, not the full schedule. These are drafts, not SUR/SDX 1.0.
Choose a source file and export
Current-source evidence only. Knowledge time is unmeasured; historical replay and execution authority remain withheld. No raw schedule body or server path is included.
What this release's finish, float and recovery reserve do under six kinds of disturbance, read through the questions each one tests: how much delay float absorbs, where recovery runs out, and which disturbance breaks it first. A counterfactual on the schedule's own logic, not a forecast.
Choose a release to stress its network.
Stress results by question and by disturbance
How every metric moved across the project's releases up to this one: the change since the previous release, the rate of change per week, whether that rate is speeding up, how often the metric changes, and whether the latest move is a shift, a sustained drift or the usual wobble. Co-movement says whether the metrics started moving together. A detector says what changed and how fast, never why.
Choose a release to detect changes across its project.
Changes by metric
Send this release’s reports to Teams, SharePoint or by email link, or make a download link to share yourself. Destinations are set up in Settings.
Requires a selected crew report. This may identify people. Existing subscriptions are unchanged; Google Chat and IFTTT are not supported for this evidence batch.
Requires a selected probe report. The batch carries controls, all nine metric definitions and evidence limits. It may contain many parts; no probe values are truncated.
The station instruments read from this project's release window: what accumulated, which way the barometer is going, where the loss is concentrated, and what is climbing. A nowcast. It does not say when the project finishes, and it never combines its instruments into one index.
Choose a project to name the consequence axis this station ranks by.
Choose a project to read its conditions.
Choose a project to see which instruments produced no reading.
A withheld reading means the station has no instrument for that question. It is not a clean result.
Nine flow metrics, release against release: the finish as a moving surface, the movement that goes back and forth, and what the finish date does not show. Every card says how it is calculated, with this project's own numbers. They are read side by side and never combined into one index.
Choose a project to draw its flow.
Save and inspect Flow evidence
Preview the selected project's recent release window, then save exactly that preview. Saved evidence keeps its original definitions. It is not a refresh, a public share link, or permission to act.
Keep this identifier to reopen the capture. An uncertain save is not retried automatically; inspect its identifier before starting another preview.
Include the native Review
These downloads keep the inspected Flow capture unchanged and add the native Review for its original review anchor. The Review is checked at export time; it is not a saved copy of the Review from when Flow was captured. Its schedule Data Date and evaluation time remain separate from the captured Flow release dates and save time.
Choose a project, then preview or inspect evidence.
Deliver this saved evidence to a webhook
This sends the complete inspected historical capture, not a refreshed reading. Project and actor references are not anonymized. Preview the destination and every part before approving disclosure. Chat delivery is not available here.
Keep the request identifier and saved capture identifier. A timeout is not proof that nothing was sent. Inspect the original request; never resend to repair missing evidence.
Inspect a saved capture first. Nothing is sent automatically.
Observed fields from the selected project's saved reviews. Criticality density, path-class transitions, optionality, and chain coherence are schedule-only candidate proxies; this strip does not claim a trend, cause, adaptability, or forecast.
Choose a project to load its review motion chart.
Choose a project to load the motion strip.
Choose a project to load motion reading.
Checks whether the saved observation stream is comparable. This is not a project health score.
Choose a project to inspect observer health.
Up to five most recently received uploads are shown. Data Date labels schedule-valid time and never reorders an older-date re-upload; a governed baseline remains a separate comparison anchor.
Choose a version above to anchor a saved review.
Selected review
Loading Date Gate, DCMA Results, Directed EV, and uploaded files...
Loading file list...
Observed schedule snapshots become derived views. Readiness is not a health score; a locked view names the evidence needed to unlock it.
Waiting for results.
Open review data to load findings.
Waiting for results.
Open review data to load EV inputs.
If a result cannot load, the saved review still exists. Open Date Gate to inspect the file dates or start a new review with the same files.
Saved schedule uncertainty
Configure or run a simulation in What-If
How does the target's remaining network time vary under declared duration assumptions?
Working hours only—not calendar finish dates, P6 verification or a completion guarantee. Every trial recalculates the whole eligible network, so the driving path can change.
Choose an authorized review.
Activation evidence
Read float and logic changes across up to five receipts known by the selected review. Schedule evidence cannot establish ordinary operating capacity or why a date held.
Relationship comparisons use imported identities, not verified cross-release mappings. Re-keying can change the apparent count.
Choose a project version, then read its activation evidence.
Schedule evidence checks
Inspect network sensitivity, metric blind spots, predecessor-completion reachability and reported field movement. Counterfactual probes are modelled tests, not observed outcomes, physical readiness or P6 verification.
Sensitivity tests at most eight selected edges; the receipt names requested, tested and omitted edges. Movement needs two admitted snapshots from the same native project. Matching activity codes remain provisional.
Choose a project version, then read its evidence checks.
Series inputs and calculations
Inspect the same bounded payload used by the series downloads. Source admission checks bytes and custody; it does not establish causation, verify cross-release identity, or make a forecast an observed finish.
Inspect EVM, critical-path and two-route source receipts separately. Admitted bytes do not guarantee an available or correct calculation.
Choose a project version, then read its evidence.
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.
