EIA-748: The 32 EVMS Guidelines in Plain Language

All 32 EIA-748 EVMS guidelines in plain language, grouped in the five categories, with the evidence a reviewer asks for and the guide covering each.

15 min read 8 sections Updated

20 CHECKS

New to this topic?

Read these first to get the most out of this guide:

EIA-748 is the standard an earned value management system (EVMS) is measured against. It has 32 guidelines in five categories. They state what the system must do, not how: each company writes a system description explaining how its own processes meet each one. Below, each guideline is paraphrased in plain language, with the evidence a reviewer typically asks to see and the guide on this site that covers the practice.

For why government programs require earned value at all, start with EVMS fundamentals.

The five categories

Change controlThe baseline line steps to a new level and each change is logged as it landsThe Change control guide
CategoryGuidelinesPurpose
Organization1 to 5Define the work and who is responsible for it.
Planning, scheduling and budgeting6 to 15Build the performance measurement baseline (PMB).
Accounting16 to 21Collect actual cost the same way the work was budgeted.
Analysis and management reports22 to 27Compare plan, progress and cost, and act on it.
Revisions and data maintenance28 to 32Change the baseline only in a controlled, traceable way.

Organization: guidelines 1 to 5

Define the work and who is responsible for it.

UCLLCL
Control chartA point outside the limits, or a run on one side, is a signalThe Control chart guide
#Guideline (paraphrased)Typical evidenceGuide
1Define the authorized work in a work breakdown structure (WBS) suited to internal management control.WBS and WBS dictionary covering all contract scopeWBS
2Identify the program organization (OBS), including major subcontractors.OBS chart; subcontractor list tied to WBS elementsWBS
3Integrate planning, scheduling, budgeting, work authorization and cost collection with each other and with the WBS and OBS.System description; one control account ID used across schedule, budget and cost systemsWBS
4Identify who is responsible for controlling overhead (indirect) costs.Named indirect cost owners per pool
5Cross the WBS and OBS to form control accounts, so cost and schedule can be measured by either structure.Responsibility assignment matrix (RAM) with one manager per control accountCAM role

Planning, scheduling and budgeting: guidelines 6 to 15

Build the performance measurement baseline (PMB).

WORK PACKAGESPLANNING PKGUBMR
Budget baselineThe budget stacks as layers: work packages, undistributed budget and reserve on topThe Budget baseline guide
#Guideline (paraphrased)Typical evidenceGuide
6Schedule the work to show its sequence and the interdependencies needed to meet the requirements.Integrated master schedule (IMS) with logic linked to control accountsDCMA 14-point
7Identify the products, milestones or other indicators used to measure progress.Objective completion criteria per work packageEV techniques
8Set and maintain a time-phased budget baseline at the control account level; far-term budget may be held at a higher level until it can be planned.Time-phased PMB; planning packages for far-term workBudget baseline
9Budget the work by significant cost element (labor, material, subcontract, other direct).Control account plans showing budget by elementWork package planning
10Plan near-term work in discrete work packages budgeted in dollars, hours or other measurable units; keep far-term work in planning packages.Work packages with dates, budget and an EV technique; planning packages converted on a rolling-wave cycleWork package planning
11Make the work packages plus planning packages in a control account add up to the control account budget.Reconciliation report per control accountWork package planning
12Use level of effort (LOE) only for work that cannot be measured discretely, and budget it time-phased.LOE list with justification; LOE share of budget trackedEV techniques
13Set overhead budgets for each significant organization and reflect the planned indirect allocation in program budgets.Forward pricing or budgeted indirect rates applied to the PMB
14Identify management reserve (MR) and undistributed budget (UB).MR and UB logs with every transactionBudget baseline
15Reconcile the program target cost with the sum of all internal budgets and management reserve.Contract budget base (CBB) = PMB + MR, reconciled monthlyBudget baseline

Accounting: guidelines 16 to 21

Collect actual cost the same way the work was budgeted.

ACPVEV
Earned valueCPI = EV ÷ AC, SPI = EV ÷ PVThe Earned value guide
#Guideline (paraphrased)Typical evidenceGuide
16Record direct costs consistently with the budgets, in a formal system controlled by the general books of account.Cost collection by charge number mapped to work packages
17Summarize direct costs from control accounts into the WBS without splitting one control account across two or more WBS elements.Each control account rolls to exactly one WBS elementWBS
18Summarize direct costs from control accounts into the organization without splitting one control account across two or more organizations.Each control account rolls to exactly one OBS elementCAM role
19Record the indirect costs allocated to the program consistently with the overhead budgets.Applied indirect cost by pool and period
20Identify unit, equivalent unit or lot costs when needed.Unit or lot cost reports on production contracts
21Account for material so that cost lands in the right control account, is recorded in the same period its earned value is taken (no earlier than receipt), and all material, including residual inventory, is accounted for.Material EV taken at receipt or later; inventory reconciliation

Analysis and management reports: guidelines 22 to 27

Compare plan, progress and cost, and act on it.

FORMAT 1–7
Monthly reportThe month closes and the report pages stack up, format by formatThe Monthly report guide
#Guideline (paraphrased)Typical evidenceGuide
22At least monthly, generate schedule variance (BCWP vs BCWS) and cost variance (BCWP vs ACWP) at the control account level, from data that reconciles with the books.Monthly control account reports; cost reconciled to the ledgerEV metrics
23At least monthly, identify significant schedule and cost variances and explain their causes in enough detail for management.Variance analysis reports (VARs) above threshold, with root cause and corrective actionVariance analysis
24Identify budgeted and applied indirect costs, and explain significant variances.Indirect rate variance reporting
25Summarize the data and variances up through the WBS and organization for management and customer reporting.CPR / IPMR formats reconciled to control account dataCPR / IPMR
26Take management action as a result of the earned value information.Corrective action log, closed actions traced to variancesVariance analysis
27Develop revised estimates at completion (EAC) from performance to date, material commitments and expected future conditions, and compare them with the baseline.Monthly EAC review; comprehensive EAC at least annuallyEAC methods

Revisions and data maintenance: guidelines 28 to 32

Change the baseline only in a controlled, traceable way.

ScopeRequests push at the scope line; only the approved change gets through the gateThe Scope guide
#Guideline (paraphrased)Typical evidenceGuide
28Incorporate authorized changes promptly into budgets and schedules; before a change is negotiated, budget it on the estimate.Baseline change requests (BCRs) with dates authorized and incorporatedChange control
29Reconcile current budgets to prior budgets, separating authorized scope changes from internal replanning.Budget log from original CBB to currentChange control
30Control retroactive changes to actual cost, earned value or budget already reported; allow them only for error correction, routine accounting adjustments, directed changes or to improve data accuracy.Retroactive change log with reason per entryChange control
31Prevent revisions to the program budget except for authorized changes.No budget movement without a BCR or MR transactionBudget baseline
32Document changes to the performance measurement baseline.PMB change history traceable to each BCRChange control

Where the guidelines meet: the control account

Most of the 32 guidelines land on one object: the control account, where a slice of WBS scope, one organization, a time-phased budget and a named manager meet (guideline 5). Planning (6 to 15) happens inside it, actual cost is collected against it (16 to 21), variances are analyzed at it (22 to 27), and changes to it are logged (28 to 32). That is why reviewers interview control account managers. See the CAM role and the CAM monthly rhythm.

Preparing for a review

  • Trace one control account end to end: WBS dictionary entry, RAM line, work authorization, schedule tasks, work packages, cost charges, last three months of variance reports, EAC and baseline changes. If that trace holds, most guidelines hold.
  • Run the DCMA 14-point checks on the IMS before reviewers do.
  • Reconcile the budget log: original contract budget base to current, every change backed by a baseline change request or a management reserve transaction.
  • Check the share of budget in level of effort. A high LOE share weakens the performance data and draws attention under guideline 12.
  • Read the last three months of variance analysis for root causes and closed actions, not restated numbers. See variance analysis.

The integrated baseline review tests the planning guidelines on a new baseline. The full EVMS and CAM series covers each practice in depth.

Frequently asked questions

What is EIA-748?

EIA-748 (ANSI/EIA-748, Earned Value Management Systems) is the industry standard that defines what an earned value management system must do. It sets 32 guidelines in five areas: organization, planning/scheduling/budgeting, accounting, analysis and management reports, and revisions and data maintenance. US government contracts above the EVMS threshold require a system that meets it.

What are the 5 categories of the 32 EVMS guidelines?

Organization (guidelines 1 to 5), planning, scheduling and budgeting (6 to 15), accounting (16 to 21), analysis and management reports (22 to 27), and revisions and data maintenance (28 to 32).

Do the guidelines say how to build the system?

No. They say what the system must achieve, not which tools or forms to use. Each company writes a system description that explains how its processes meet each guideline, and reviewers test the system against that description.

Which guidelines are most often cited in reviews?

Findings often cluster around the schedule (6), work package planning and LOE (10, 12), material accounting (21), variance analysis and management action (23, 26), EAC (27) and retroactive changes (30). Those are where daily practice drifts from the written process.

Share this guide: LinkedIn X Follow SymplProcess on LinkedIn