EVMS on a firm-fixed-price contract is possible, but it is not the normal DoD approach. Defense Federal Acquisition Regulation Supplement (DFARS) 234.201 discourages applying earned value management to firm-fixed-price contracts and subcontracts at any dollar value. In extraordinary cases, a program may apply it after following the required waiver process.
Therefore, a large FFP award does not automatically require an Earned Value Management System (EVMS) simply because it exceeds the familiar $20 million or $50 million thresholds. Those thresholds primarily address DoD cost or incentive contracts. The solicitation, contract clauses, agency policy, approved tailoring, and Contract Data Requirements List (CDRL) determine the actual obligation.
Program teams still need credible cost and schedule control on FFP work. However, they can often obtain useful execution insight through an Integrated Master Schedule (IMS), milestone reporting, technical performance measures, risk reporting, and other tailored deliverables without imposing a complete EIA-748-compliant EVMS.
Why EVMS and firm-fixed-price contracting can conflict
Under FAR 16.202-1, a firm-fixed-price contract establishes a price that does not change based on the contractor’s cost experience. The contractor accepts maximum cost risk and responsibility for the resulting profit or loss.
EVMS serves a different purpose. It integrates authorized scope, schedule, budgets, earned value, actual costs, forecasts, and management responsibility. A formal EVMS gives management an objective view of what work was planned, what work was accomplished, what it cost, and what the remaining effort may cost.
That visibility can help on complex FFP development. However, it does not change the contract’s risk allocation. A negative cost variance does not entitle the contractor to a higher price. Likewise, favorable cost performance does not reduce the negotiated price merely because the contractor completed the work efficiently.
As a result, the Government must weigh the value of detailed internal cost visibility against the administrative burden and potential sensitivity of contractor cost data. On many FFP efforts, schedule, technical, and delivery information provides more useful customer insight than a complete EVMS implementation.
When does EVMS firm fixed price apply under DoD policy?
DFARS 234.201 establishes separate applicability rules by contract type. For cost or incentive contracts and subcontracts valued at $20 million or more, the EVMS must comply with ANSI/EIA-748 guidelines. At $50 million or more, the contractor must use a system determined acceptable by the Cognizant Federal Agency.
However, the rule treats FFP work differently. For firm-fixed-price contracts and subcontracts of any value, applying earned value management is discouraged. The $20 million and $50 million values do not independently override that FFP policy.
The waiver is not a routine threshold approval
DFARS Procedures, Guidance, and Information 234.201 addresses the process for applying EVM to FFP work. It describes extraordinary cases in which cost and schedule visibility cannot be obtained through other means. In those cases, the program manager must request a waiver for the individual contract from the Milestone Decision Authority.
The program manager must also conduct a business case analysis. That analysis includes the rationale for not using a cost contract or fixed-price incentive contract instead. Therefore, a desire for additional monthly reports, by itself, should not be treated as a sufficient reason to impose EVMS.
The waiver is part of the Government’s acquisition and contracting process. Still, an offeror should verify that the solicitation clearly defines the resulting requirements. Ambiguous language can cause major differences in proposed systems, staffing, reporting, subcontractor flow-downs, and price.
The contract creates the contractor’s obligation
A policy decision to use EVMS must be implemented through the solicitation and contract. For DoD contracts, DFARS 234.203 prescribes the EVMS solicitation provision and contract clause for applicable contracts.
If EVMS applies, the contract will normally address requirements through items such as:
- The EVMS provision and clause.
- The Statement of Work or Performance Work Statement.
- Applicable CDRLs and Data Item Descriptions.
- Integrated Baseline Review requirements.
- Reporting frequency, content, formats, and tailoring.
- Subcontractor application and flow-down requirements.
- Government access, surveillance, and system review provisions.
Do not infer a formal EVMS requirement from general references to earned value, percent complete, monthly status, or an IMS. Conversely, do not assume that an FFP label eliminates EVMS when the awarded contract contains an applicable clause and data requirements.
What changes when formal EVMS is required on an FFP contract?
When DoD formally applies EVMS, DFARS 252.234-7002 requires the contractor to use an EVMS that complies with ANSI/EIA-748 guidelines. The clause also addresses system acceptability, Integrated Baseline Reviews, Government access, surveillance, substantive system changes, formal reprogramming, and designated subcontractors.
The contract type remains FFP. However, the contractor must establish and maintain an integrated management baseline for the authorized work. That effort affects planners, schedulers, control account managers (CAMs), finance personnel, accounting organizations, subcontract managers, and program leadership.
The performance baseline is not the contract price
One common error involves treating the FFP contract value as the Budget at Completion (BAC). The two values serve different purposes.
The contract price can include profit or fee and other amounts that do not belong in the Performance Measurement Baseline (PMB). Meanwhile, the Contract Budget Base consists of management budgets for authorized work, including the PMB and management reserve where applicable. Therefore, the EVMS budget structure must reconcile correctly rather than simply copying the negotiated price into the baseline.
For a deeper explanation of the budget term, see Budget at Completion (BAC) Explained. Program teams building the baseline should also review how to build a robust Performance Measurement Baseline.
Actual cost still matters internally
Although the Government does not reimburse the contractor based on incurred cost under an FFP arrangement, EVMS still requires actual costs for valid cost performance measurement. The contractor needs actual cost data aligned with the same work breakdown and accounting periods used for earned value.
However, teams should not substitute invoice amounts, payment milestones, or contract price allocations for actual cost without a valid accounting basis. Doing so can create misleading Cost Performance Index (CPI), cost variance, and Estimate at Completion (EAC) results.
The distinction between cost and schedule performance is covered further in Schedule Variance vs Cost Variance. In addition, CPI vs SPI explains how the two indices support different management questions.
When EVMS is not required, the IMS still matters
No EVMS requirement does not mean no program controls. Complex FFP development and production efforts still need a realistic execution plan. At a minimum, the program team may need to manage technical scope, contractual deliveries, resources, interfaces, risks, and forecast dates.
A well-built IMS often provides the most valuable customer insight on FFP work. It can show the critical path, near-critical paths, integration points, testing sequences, subcontractor dependencies, schedule margin, and forecast completion dates. The IMS should remain logic-driven and statused to a consistent data date.
The exact schedule deliverable remains a contractual matter. Therefore, the solicitation should define the required schedule level, update frequency, native file requirement, calendar conventions, coding, narrative content, and change-control expectations. General phrases such as “provide a detailed schedule” leave too much room for conflicting interpretations.
For practical schedule development guidance, see the complete guide to the DoD Integrated Master Schedule. The relationship between the schedule and earned value is explained in How the IMS Supports Earned Value Management.
Agency rules can differ
DoD policy should not be assumed to apply unchanged across the federal government. For example, the NASA FAR Supplement 1834.201 also discourages requiring EVM on FFP contracts. However, NASA requires an IMS and adequate reporting for development or production contracts valued at $20 million or more.
This difference shows why teams must review the applicable agency supplement and the specific contract. FAR-level policy, agency rules, class deviations, program tailoring, and contractual language can produce different reporting packages.
Fictional example: an FFP development contract
Assume the Government plans an $85 million FFP contract for development, integration, testing, and delivery of a new ground-control subsystem. The work includes custom software, hardware integration, cybersecurity testing, and several Government-furnished equipment interfaces.
The dollar value alone does not automatically trigger DoD EVMS because the planned contract type is FFP. The acquisition team first considers whether an IMS, monthly technical reviews, risk reporting, and milestone forecasts can provide adequate visibility.
In the first scenario, the Government does not pursue an EVMS waiver. The contract requires a resource-informed IMS, monthly schedule updates, a schedule narrative, risk data, and technical performance reporting. The contractor may use earned value internally, but its internal EVMS data does not become a customer deliverable unless the contract requires it.
In the second scenario, the program concludes that other methods cannot provide adequate cost and schedule visibility. The program completes the business case, obtains the required waiver, and includes the applicable DFARS EVMS provision, clause, CDRLs, and subcontractor requirements. Offerors must now price the formal EVMS effort and demonstrate how they will meet the stated system and reporting requirements.
Both scenarios can support disciplined management. However, they create very different contractual obligations, proposal costs, system expectations, and customer access rights.
What proposal and program-controls teams should verify
Before estimating or implementing an EVMS firm fixed price requirement, review the complete solicitation or awarded contract. Do not rely on contract type and total value alone.
- Confirm the exact contract type. Distinguish FFP from fixed-price incentive, cost-reimbursement, time-and-materials, and hybrid arrangements.
- Review the clauses. Determine whether FAR 52.234-4 or DFARS 252.234-7002 appears in the solicitation or contract.
- Inspect every CDRL. Identify required cost, schedule, narrative, risk, and technical datasets. Check frequency and file format.
- Check the scope. Determine whether EVMS applies to the whole contract, selected contract line items, or designated subcontracted effort.
- Identify the review expectation. Confirm whether the Government requires an Integrated Baseline Review and when it will occur.
- Clarify system status. Determine whether the proposed EVMS already has Cognizant Federal Agency acceptance or requires an implementation plan.
- Price the requirement. Include CAM support, scheduling, cost processing, reporting, system administration, baseline control, surveillance support, and subcontract management.
- Resolve contradictions before award. Ask questions when the clauses, Statement of Work, CDRLs, and proposal instructions do not align.
Common mistakes
- Applying the $20 million threshold to every FFP contract. DoD’s FFP policy separately discourages EVM regardless of dollar value.
- Calling an IMS an EVMS. The schedule is a core EVMS component, but an IMS alone does not satisfy EIA-748.
- Assuming FFP prohibits internal earned value. A contractor can use EVM techniques for internal control without creating a contractual EVMS deliverable.
- Setting BAC equal to contract price. Profit, management reserve, undistributed budget, and PMB composition require proper reconciliation.
- Using billing data as actual cost. Payment events and invoices do not necessarily represent the cost of work performed during the reporting period.
- Ignoring subcontractor scope. The contract must identify designated subcontractors or subcontracted efforts when EVMS requirements apply.
- Over-specifying the system. The Government should define required outcomes and data, not invent additional EVMS rules that conflict with the applicable standard or approved contractor system.
Frequently asked questions
Is EVMS prohibited on a DoD firm-fixed-price contract?
No. DFARS discourages its application, but it does not impose an absolute prohibition. In extraordinary cases, the program may pursue the required waiver and business case process.
Does a $50 million FFP contract require a validated EVMS?
Not based on value alone under DoD policy. The $50 million system-acceptance threshold applies within the DoD rules for cost or incentive contracts and other contracts on which EVMS has been properly applied. Review the actual solicitation and contract.
Can the Government require an IMS without requiring EVMS?
Yes. An IMS or other schedule deliverable can be required independently when the contract includes the appropriate requirement. The required schedule content and reporting frequency should be clearly defined.
Can a contractor calculate earned value internally on FFP work?
Yes. Contractors may use earned value techniques to manage scope, schedule, resources, actual costs, and forecasts. However, internal use does not create a Government reporting obligation unless the contract requires delivery or access.
Bottom line
For DoD acquisitions, EVMS on firm-fixed-price contracts is the exception rather than the default. DFARS discourages it at every dollar value and directs programs to a waiver process when extraordinary circumstances justify formal application.
Still, FFP programs need disciplined planning and objective status. The practical solution may be a tailored IMS and supporting technical, risk, and forecast reporting rather than full EIA-748 compliance. Ultimately, the awarded clauses, CDRLs, agency rules, and approved tailoring define the requirement. Schedulers and program-controls teams should read those documents together before building the baseline or pricing the work.