A quick, executive read of schedule health using Earned Value Management (EV, PV, SPI, SV). Cost-side metrics (CPI) are intentionally out of scope.
speed EVM (Schedule) Status shows Ahead / On track / Behind derived from SPI (EV ÷ PV).- Ahead SPI ≥ 1.05
- On 0.95 ≤ SPI < 1.05
- Behind SPI < 0.95
assignmentProject “At-a-Glance”
Schedule (EVM)- speed Status (derived from SPI) Ahead / On / Behind
- assessment EV / PV $EV / $PV
- trending_down SV $SV
- starsPM Risk Very High / High / Medium / Low / Very Low
- buildML Risk short text
- psychologyML Success 0–100%
- scheduleStartDate
- timerEndDate
- settingsTypeCategory
- verified_userPrivacyLevel
- visibilityVisitorsCount
workspacesPortfolio “At-a-Glance”
Schedule (EVM)- speed Status (derived from SPI) Ahead / On / Behind
- assessmentEV / PV $EV / $PV
- trending_downSV $SV
- starsAverage RiskWeighted by BAC
- reportRisk CountTotal
- paymentsTotal Budget$
- paymentsLargest Project Budget$
- placeLocations#
- scheduleEarliest StartDate
- timerLatest EndDate
ruleHow it works
Formulas (plain English)- BAC = Project price (planned budget)
- EV = BAC × (completed milestones ÷ total milestones)
- PV = BAC × (elapsed time ÷ total time), clamped 0–1
- SPI = EV ÷ PV
- SV = EV − PV
- CPI = EV ÷ AC — not shown (no Actual Cost)
- Project EV/PV/SPI/SV from the project’s EVM view/rollup
- Portfolio EV/PV/SV are the sum across member projects; SPI uses ΣEV ÷ ΣPV
- Risk is a BAC-weighted average at portfolio level; simple average fallback when needed
visibilityWhen values appear
- EVM Status appears when SPI is numeric (PV > 0 and dates valid)
- EV/PV/SV appear when EV and PV are available (milestones > 0 and dates set)
- Risk appears when team-entered risks are present
- ML signals appear when model has produced outputs
- Visitors/Subscribers appear when a count is available (0 is shown)
- Anything missing is hidden to avoid clutter; a small note indicates pending metrics