Earned Value & Performance
Connect contracted scope, earned value, and earned schedule to the finish goal.
Evidence detailsChecking
Not assignedData Date sourceLoading the accepted schedule date.Checking effective role and scopeBounded evidence only · original schedule source remains protectedEarned Value & Performance content
No earned evidence yet: declare a scope and calculate to read position.
Shared Directed EV vocabulary keeps this scope consistent across surfaces.
Declare the unit meaning and weighting basis before treating EV as decision-grade.
Select a review for evidence.
Select prefixes or discipline.
Select a scope and review.
Derive variances only when required inputs exist.
SV/CV ≥ 0 · SPI/CPI ≥ 1.0
Select a review to compare PV, EV, and AC.
Ceiling: signal—not cause, responsibility, or a committed finish date. Missing values remain unavailable; they are never replaced with zero.
PV planned value, EV earned value, and AC actual cost remain separate cumulative series. A line is absent when its evidence is missing.
The cost curve needs at least two evaluated snapshots.
Evidence boundary: cumulative cost position by Data Date; this is not a forecast, causation, or responsibility finding.
Bounded, evidenced, and expiring; Green must be earned. No report is not a zero report.
Completeness, liveness, and attestation remain explicit checks.
Select a review to inspect requirements.
Authority ceiling: closure licenses only the bounded observation set; it does not certify completion, cause, responsibility, or entitlement.
Parallel families, ordered movement, cross-checks, declared boundaries, and anchored discussion questions. No aggregate project score.
Choose a project to load the bounded KPI mosaic.
Width is observed work in comparable reviews—not a finish prediction or a cause finding.
Two reviews with different Data Dates are needed before the remaining-work snapshot comparison can render.
Observed schedule reserves and option types. Liquidity is an asset classification—not measured conversion time or execution capacity.
Choose a project with saved reviews. One review shows levels; two reviews are required for motion.
Velocity is not direction. A period can complete a great deal of work and move the finish not at all, because the work it completed was not the work holding the finish.
Choose a project with two or more saved reviews to read its heading.
Dollar SV fades to zero as PV converges on BAC, so a late project can still report SV = 0. Earned Schedule restates it in time: SV(t) = ES − AT stays negative while the finish is late.
SV(t) ≥ 0 and SPI(t) ≥ 1.0; read position before movement.
SV(t) = 0
- PositionSV(t)ES − ATweeks · 1 sample
≥ 0 ahead; < 0 behind
- MomentumdSV/dtChange in SV(t)weeks/week · 2 samples
+ regain; − lose
- Changed²SV/dt²Change in velocityweeks/week² · 3 samples
+ improve; − deteriorate
- Persistenced³SV/dt³Change in accelerationweeks/week³ · 4 samples
Trigger, never verdict
ES = planned week at earned fraction; AT = elapsed time; SPI(t) = ES / AT.
Conditional estimate: IEAC(t) may produce a Forecasted Finish Date when the same review and scope pass every evidence gate; it is never a promise or P6 writeback.
Reading ES, SV(t), and SPI(t) from the saved reviews. Two reviews at different Data Dates are the minimum.
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 update from visible page evidence. Blocked and withheld states name the boundary; no completion percentage is inferred.
Discussion questions and talking points
Observed → derived → withheld remains explicit. These talking points stay tied to the selected evidence; they are not an unrestricted database question box.
Unavailable context remains explicitly not supplied.
This talking point preserves the page’s evidence and authority boundary.
