sub-modules
Earned Value
Catch the overrun in week six — not at closeout when it's a loss.
Overruns don't happen at closeout; they're discovered there. The variance started in week six, visible to anyone watching earned value — but nobody was. Earned Value watches from day one: planned versus earned versus actual per package, thresholds firing while correction is still cheap.
Control cycle
Each stage below keeps the project honest — planned against baselines, charged from live events, and replanned without erasing history.
data Viz
data View
section: stages
Baseline
Work breakdown with resource-loaded schedules seals with reason and authority. The baseline becomes the variance reference for everything after.
Earn
Completed work earns value as events validate, with schedule and cost variances alerting while correction stays cheap.
Replan
New baselines supersede with reason recorded and history retained. Variance restarts honestly instead of resetting to zero by rewrite.
Earned-value guarantees
- Live variances
- Schedule and cost variance computed as events validate, with threshold alerts
- Preserved baselines
- Superseding revisions with reason and authority; history stays queryable
- Loaded resources
- Labor, machines, and funds resolved from live truth before commitment
- section
- capabilities
Control by industry
Earned value bends per industry — same baseline honesty, different delivery stakes.
data Viz
data View
section: industries
Construction
Job costing with progress billing, retention, and change orders. Percent-complete derives from validated quantities instead of superintendent estimates.
Aerospace and Defense
CLIN-level earned value with government reporting formats assembled from live actuals. Baseline changes carry authorization evidence auditors expect.
Professional Services
Engagement burn against fixed-fee and T&M terms with utilization-linked forecasting. At-risk engagements alert before margin inverts.
Earned Value questions
Section 1
What happens on replan?
A new baseline revision supersedes the old one with reason and authority recorded. Variance restarts from the new baseline while history remains queryable.
Section 2
How are variances detected early?
Thresholds on schedule and cost variance fire as events validate — a slipping package alerts the week it slips, with the causing events cited.
Section 3
Our clients punish bad news. Won't early alerts backfire?
Early alerts with recovery options build more trust than late surprises ever could. Clients punish discovered overruns, not disclosed variances with plans attached.
data View
section: faqs
content section
value: Replanning supersedes; baselines are never overwritten, so variance history stays honest. Schedule and cost thresholds alert while there is still time to act, not after the money is gone.
Section 6
Planned, earned, and actual cost tracking per package
Section 7
Schedule and cost variance with threshold alerts
Section 8
Baseline preservation across replan cycles
Section 9
Resource-loaded schedules tied to workforce truth