EIA-748 EVMS 32 Criteria Explained for Construction

<div class="ge-article-wrapper"><nav class="ge-toc" aria-label="Table of contents"><p class="ge-toc-label">In this article</p><ul class="ge-toc-list"><li><a href="#what-eia-748-actually-covers">What EIA-748 Actually Covers</a></li><li><a href="#the-five-categories-explained">The Five Categories Explained</a></li><li><a href="#worked-example-mapping-existing-processes-to-the-32-criteria">Worked Example: Mapping Existing Processes to the 32 Criteria</a></li><li><a href="#uk-government-adoption">UK Government Adoption</a></li><li><a href="#when-is-eia-748-compliance-required">When Is EIA-748 Compliance Required?</a></li><li><a href="#common-mistakes">Common Mistakes</a></li><li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li></ul></nav><article class="ge-article-body"><p>If you've ever been asked whether your earned value system is "compliant," what they're really asking is whether it meets the EIA-748 standard. This is the ANSI/EIA-748 Earned Value Management Systems standard, and it defines 32 specific criteria that an EVMS must satisfy to be considered credible. It's not a guideline. It's not a suggestion. It's the benchmark that government clients, defence organisations, and increasingly UK infrastructure programmes use to determine whether your <a href="/en/earned-value/definitions/earned-value-management">earned value management</a> processes are genuinely working or just decorative.</p><p>EIA-748 is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For the practical side of setting up an EVMS, see the <a href="/en/earned-value/implementation-guide">implementation guide</a>.</p><h2 id="what-eia-748-actually-covers">What EIA-748 Actually Covers</h2><p>The 32 criteria are organised into five categories. Each category addresses a different aspect of how you plan, execute, control, and report project performance. Miss one category and the whole system has a gap.</p><p>Here's how it breaks down:</p><pre class="ge-ascii-diagram ge-anim"> EIA-748: 32 EVMS CRITERIA ============================ Category 1: ORGANISATION (5 criteria) +-----------------------------------------------+ | 1. Define authorised work (WBS) | | 2. Identify organisational structure (OBS) | | 3. Integrate WBS with OBS at control accounts | | 4. Identify overhead management approach | | 5. Integrate planning with cost accounting | +-----------------------------------------------+ | v Category 2: PLANNING, SCHEDULING &amp; BUDGETING (10 criteria) +-----------------------------------------------+ | 6. Schedule authorised work | | 7. Identify work packages and planning pkgs | | 8. Establish budgets for authorised work | | 9. Establish budgets for each work package | | 10. Sum all budgets = Performance Measurement | | Baseline (PMB) | | 11. Identify and control management reserve | | 12. Assign budgets at control account level | | 13. Establish scheduling/work flow | | 14. Identify discrete, apportioned, LOE work | | 15. Establish overhead budgets/rates | +-----------------------------------------------+ | v Category 3: ACCOUNTING (6 criteria) +-----------------------------------------------+ | 16. Record direct costs consistently | | 17. Summarise direct costs by WBS element | | 18. Summarise direct costs by OBS element | | 19. Record indirect costs properly | | 20. Identify unit/lot costs where applicable | | 21. Material accounting integrates with EVMS | +-----------------------------------------------+ | v Category 4: ANALYSIS &amp; MANAGEMENT REPORTS (6 criteria) +-----------------------------------------------+ | 22. Identify CV and SV at control account | | 23. Identify cost and schedule variances | | monthly and cumulatively | | 24. Identify reasons for significant variances | | 25. Identify EAC based on performance | | 26. Manage indirect costs against budgets | | 27. Develop and implement corrective actions | +-----------------------------------------------+ | v Category 5: REVISIONS &amp; DATA MAINTENANCE (5 criteria) +-----------------------------------------------+ | 28. Incorporate authorised changes | | 29. Reconcile budgets to target cost/contract | | 30. Control retroactive changes to records | | 31. Prevent unauthorised revisions to PMB | | 32. Document management reserve changes | +-----------------------------------------------+ </pre><p>That's a lot of criteria. But here's the thing most people miss: you probably already do most of this. You just don't document it systematically or call it by the right names.</p><h2 id="the-five-categories-explained">The Five Categories Explained</h2><h3>Category 1: Organisation (Criteria 1 to 5)</h3><p>This is about structure. Can you show how the work is broken down (your WBS) and who's responsible for delivering each piece (your OBS)? The intersection of WBS and OBS creates control accounts, which are the fundamental unit of earned value measurement.</p><p>On most UK construction projects, the WBS maps to your cost code structure and the OBS maps to your package managers or section engineers. The problem? They're often maintained in separate systems that don't talk to each other. Criterion 3 specifically requires that integration.</p><h3>Category 2: Planning, Scheduling and Budgeting (Criteria 6 to 15)</h3><p>The biggest category, and the one where most contractors fail their first review. You need a Performance Measurement Baseline (PMB) that ties your schedule to your budget at the work package level. That means every scheduled activity has a budget, and those budgets sum to <a href="/en/earned-value/definitions/budget-at-completion">BAC</a>.</p><p>Criterion 11 is the one that catches people out: management reserve. You need to identify it separately from the PMB and control how it's allocated. Most UK contractors just have a "risk allowance" buried in the prelims. That's not good enough.</p><h3>Category 3: Accounting (Criteria 16 to 21)</h3><p>Your cost recording must align with your WBS. Every pound of direct cost should be traceable to a WBS element and an OBS element. On NEC4 Option C contracts, this maps well to the Defined Cost categories, but you need consistency between your accounts system and your EVM reporting.</p><h3>Category 4: Analysis and Management Reports (Criteria 22 to 27)</h3><p>This is where the earned value metrics live. You must calculate <a href="/en/earned-value/cost-schedule-variance">cost and schedule variances</a> at the control account level, explain significant variances, produce <a href="/en/earned-value/definitions/estimate-at-completion">EAC</a> forecasts, and show corrective actions. Criterion 27 is important: it's not enough to identify a problem. You must show what you're doing about it.</p><h3>Category 5: Revisions and Data Maintenance (Criteria 28 to 32)</h3><p>The boring but essential bit. How do you handle changes? When a compensation event is implemented and <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> needs adjusting, there's a controlled process. No one can just edit the baseline on a whim. Criterion 30 specifically prohibits retroactive changes to cost or schedule records. If you logged it, it stays logged.</p><h2 id="worked-example-mapping-existing-processes-to-the-32-criteria">Worked Example: Mapping Existing Processes to the 32 Criteria</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> Hargreaves Construction Ltd has won a £45M Network Rail GRIP Stage 5 package under NEC4 Option C. The client requires EVMS compliance. The commercial director asks you to assess current readiness.</p><p>You run a gap analysis against the 32 criteria. Here's what you find:</p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Category</th><th>Criteria Met</th><th>Gaps</th><th>Key Issue</th></tr></thead><tbody><tr><td>Organisation (1 to 5)</td><td>3 of 5</td><td>WBS exists but not integrated with OBS at control account level. Overhead approach not documented.</td><td>Need to map cost codes (WBS) to section engineers (OBS) and create formal control accounts.</td></tr><tr><td>Planning (6 to 15)</td><td>5 of 10</td><td>Budgets exist by package but not at work package level. No PMB. Management reserve mixed into prelims. No distinction between discrete and LOE work.</td><td>Biggest gap. Need to build PMB from bottom up: schedule each work package, assign budget, sum to BAC of £45M. Separate £1.8M management reserve.</td></tr><tr><td>Accounting (16 to 21)</td><td>4 of 6</td><td>Direct costs recorded by WBS but not summarised by OBS monthly. Material accounting not integrated.</td><td>Modify monthly cost report to include OBS breakdown. Link procurement to WBS.</td></tr><tr><td>Analysis (22 to 27)</td><td>2 of 6</td><td>CV and SV calculated at project level but not at control account level. No formal EAC using earned value. Corrective actions verbal only.</td><td>Need control account level reporting. Implement EAC using <a href="/en/earned-value/eac-etc-tcpi">BAC/CPI formula</a>. Document corrective actions.</td></tr><tr><td>Revisions (28 to 32)</td><td>3 of 5</td><td>Change control exists but no baseline change log. Management reserve drawdown not documented.</td><td>Implement baseline change register. Track MR separately.</td></tr></tbody></table></div><p><strong>Result:</strong> 17 of 32 criteria met. 15 gaps identified. Estimated effort to close: 6 to 8 weeks with a dedicated commercial analyst.</p><p><strong>Cost of compliance effort:</strong> Approximately £35,000 to £45,000 in staff time and system configuration. On a £45M contract with a 60/40 pain/gain share, the improved forecasting alone is worth substantially more.</p></div><h2 id="uk-government-adoption">UK Government Adoption</h2><p>EIA-748 originated in the US Department of Defense. But UK government has adopted its principles through several routes:</p><p>The Ministry of Defence (MOD) requires EIA-748 compliant EVMS on major defence procurement under DEFCON 649 and the Acquisition Operating Framework. If you're working on a project above the Government Major Projects Portfolio (GMPP) threshold, expect EVMS requirements to reference EIA-748 either directly or through equivalent UK guidance.</p><p>Network Rail and National Highways don't mandate full EIA-748 compliance on every project, but both require earned value reporting on major schemes. Their EVM requirements are functionally based on the same 32 criteria, even if they don't cite the standard by name. I've seen Network Rail reviewers use the 32 criteria as a checklist during Integrated Baseline Reviews, even when the contract documentation doesn't mention EIA-748 specifically.</p><p>The Infrastructure and Projects Authority (IPA) has pushed for EVM adoption across UK government since 2016. Their guidance references the same principles, and compliance assessments follow the same five-category structure.</p><h2 id="when-is-eia-748-compliance-required">When Is EIA-748 Compliance Required?</h2><p>Not always. Here's the practical decision:</p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Project Type</th><th>EIA-748 Requirement</th><th>Notes</th></tr></thead><tbody><tr><td>MOD procurement above £100M</td><td>Mandatory</td><td>DEFCON 649</td></tr><tr><td>GMPP projects</td><td>Expected</td><td>IPA guidance</td></tr><tr><td>Network Rail GRIP 5+ above £50M</td><td>De facto required</td><td>Earned value reporting mandated, criteria used in IBR</td></tr><tr><td>National Highways major schemes</td><td>Required for EVM</td><td>RIS2 programme monitoring</td></tr><tr><td>Private sector</td><td>Rarely required</td><td>But useful as a maturity framework</td></tr><tr><td>NEC4 Option C/D below £20M</td><td>Not required</td><td>Simple EVM sufficient</td></tr></tbody></table></div><p>The honest answer? Even when it's not contractually required, the 32 criteria are the best checklist available for ensuring your EVMS actually works. I've used them as an internal audit tool on projects where nobody asked for compliance, simply because they expose the gaps you'd otherwise miss.</p><h2 id="common-mistakes">Common Mistakes</h2><p><strong>Treating compliance as a paperwork exercise.</strong> Writing a system description that ticks all 32 boxes on paper but doesn't reflect how the team actually works. Reviewers see through this instantly. If your system description says you calculate <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> at control account level but your actual reports only show project-level SPI, you'll fail.</p><p><strong>Trying to comply overnight.</strong> Full compliance takes 2 to 3 months of sustained effort on a major project. Plan for it. Budget for it. Trying to retrofit compliance in the week before an IBR is a recipe for embarrassment.</p><p><strong>Ignoring Category 5 (Revisions).</strong> Everyone focuses on the planning and reporting criteria. But the revisions criteria are what keep the system credible over time. Without controlled baseline changes, your <a href="/en/earned-value/definitions/planned-value">Performance Measurement Baseline</a> erodes until the earned value data is meaningless.</p><p><strong>Confusing compliance with maturity.</strong> Meeting the 32 criteria is the floor, not the ceiling. A compliant system can still produce poor forecasts if the inputs are garbage. Compliance means the processes exist. Maturity means they're used well.</p><div class="ge-product-note ge-anim"><p><strong>How Gather helps.</strong> Gather's AI reads your site diaries daily and maps progress against your cost-loaded programme, giving you accurate earned value data without manual spreadsheet updates. <a href="https://gatherinsights.com/contact">Book a demo</a> to see it working on a live NEC4 project.</p></div><h2 id="frequently-asked-questions">Frequently Asked Questions</h2><h3>Is EIA-748 the same as ANSI-748?</h3><p>Yes. The full title is ANSI/EIA-748-D (the D denotes the current revision). It's published by the National Defense Industrial Association (NDIA) in the US. People refer to it as EIA-748, ANSI-748, or just "the 32 criteria" interchangeably.</p><h3>Do UK contractors need EIA-748 certification?</h3><p>There's no formal certification. Unlike ISO standards, you don't get a certificate. Instead, compliance is assessed during an Integrated Baseline Review (IBR) or a surveillance review conducted by the client or their assurance team. You demonstrate compliance through your <a href="/en/earned-value/definitions/evms-system-description">EVMS system description</a> and by showing that your actual practices match what's documented.</p><h3>How long does it take to achieve compliance?</h3><p>For a contractor with existing cost and schedule systems, typically 6 to 12 weeks of focused effort. The work is mainly in integrating existing systems (linking WBS to OBS, creating a PMB, documenting the system description) rather than building new ones from scratch. On one rail electrification project I worked on, the team achieved compliance in 8 weeks by starting with what they already had and filling the gaps rather than building from zero.</p><h3>Can a small contractor achieve EIA-748 compliance?</h3><p>Yes, and it's easier than most think. The 32 criteria don't prescribe specific tools or systems. A small contractor using well-structured spreadsheets with a clear WBS, integrated schedule, and disciplined cost recording can meet the criteria. It's the processes and discipline that matter, not the software.</p></article></div>